Additional menu

Tachytelic.net

Office 365:Convert shared mailbox to user mailbox with Powershell

by 4 Comments

It’s easy to change the mailbox type in Office 365 with Powershell.

Using the Set-mailbox cmdlet there are four possible types of mailbox that you can set:

  • Regular
  • Room
  • Equipment
  • Shared

Examples to change the type of a mailbox:

PowerShell to change a mailbox type in Office 365

Use the form below to generate the PowerShell Required to change the mailbox type:

  • Fill in the identity value of the mailbox that you want to convert
  • Select the mailbox type that you want to convert it to.
  • Copy and paste the generated code to a PowerShell window.

Remember to set your PowerShell execution policy, otherwise the script will not run. Set the PowerShell execution policy to at least RemoteSigned.

If you are converting to a “Regular” mailbox, ensure that you assign a license after you have run the conversion.

If successful, you should get output like this:
Image showing successful conversion of mailbox in Office 365 from Powershell

If you found this post helpful, I would really appreciate it if you rated it.

Reader Interactions

Comments

  1. Lucas says

    Hi,

    I am desperatly looking for the right script to change my shared office 365 mailbox to a regulair mailbox. Nothing works. I get the following error:

    Error on proxy command ‘Set-Mailbox -Identity:’ *** REMOVED *** I used my the mailbox email ****’ -Type:’Regular’ -Confirm:$False -Force:$True’ to server AMXPR01M
    B006.eurprd01.prod.exchangelabs.com: Server version 1941996320, Proxy method PSWS:
    Request return error with following error message:
    The remote server returned an error: (500) Internal Server Error…
    + CategoryInfo : NotSpecified: (:) [Set-Mailbox], CmdletProxyException
    + FullyQualifiedErrorId : Microsoft.Exchange.Configuration.CmdletProxyException,Microsoft.Exchange.Management.Reci
    pientTasks.SetMailbox
    + PSComputerName : pod51036psh.outlook.com

  2. Eric says

    Hi Lucas,

    I get the exact same error since 20/10/2013 !
    I already converted hundreds of mailboxes this way, but apparently Microsoft introduced a bug this weekend on their Exchange Online infrastructure.

Leave a Reply