O365

Office 365: Convert Mailbox to Shared Mailbox after Cutover Migration

When performing a cut-over migration the Exchange attribute indicating that the mailbox was a shared mailbox is lost. To correct this I have done the following steps:

List out all of the shared mailboxes form my on-premises Exchange and export them into a CSV file.

Now prepare the CSV file with the list of user principal names of all mailboxes to be converted. Make sure the column header for the user principal names is “UserPrincipalName”

Now we run the following powershell script to change the mailbox type of all items in the CSV file.

Please note

Running Exchange Online Powershell commands / scripts requires you have had installed the Microsoft Online Service Sign-In Assistant, Windows Powershell, Windows Azure Active Directory Powershell

For more info:

http://www.microsoft.com/en-us/download/details.aspx?id=41950

http://jermsmit.com/azure-active-directory-module-for-windows-powershell-how-to-connect/

 

Tech Short: Office365 – Convert select on-premises mailboxes to mail-enabled users

When you convert on-premises mailboxes to mail-enabled users (MEUs), the proxy addresses and other information from the Office 365 mailboxes are copied to the MEUs, which reside in Active Directory in your on-premises organization. These MEU properties enable the Directory Synchronization tool, to match each MEU with its corresponding cloud mailbox.

Using the steps provided here I was able to export a list of only user mailboxes and leaving out other mailbox types

Run the following PowerShell command:

The following full steps of what to do next can be found here: http://community.office365.com/en-us/w/exchange/835.cutover-exchange-migration-and-single-sign-on.aspx

Office 365: Errors during cutover migration

This is an error I’ve received when running a cut-over migration batch in Office 365.

  1. Error: ProvisioningFailedException: The parameters passed to the cmdlet represent a managed account, which doesn‎’t match the namespace state, which is federated.

I’ve reached out to support, to help me troubleshoot this.  So far there hasn’t been much I’ve been able to find online regarding my situation.

More to be shared as soon as I have additional information.

Update – 02/04/2015

With the idea that this may have something do with our domain being federated as we had already setup a ADFS server when we were configured for Hybrid.

So let’s recap on the Error: ProvisioningFailedException: The parameters passed to the cmdlet represent a managed account, which doesn’t match the namespace state, which is federated.

Focusing on the message above I was able to find do some research to research based on some blog searches that indicated the issue was with our federation status.
I ran the following command from our ADFS Server: Get-MsolDomain

Results:

I had also reviewed the setting using Get-MsolDomainFederationSettings followd by the federation properties with Get-MsolFederationProperty

Using the Get-MsolDomain I was able to identify that the domain for jermsmit.com was verified and also had a federated authentication status.

I change this back to Managed by running the following command:

This was verified by running the Get-MsolDomain to check my results.  And that worked.

I then moved forward by deleting the current failed batch; which took some time.  Once deleted, created a new batch.  At this time the cut-over migration sync is working

 

– Jermal

Notes:  To run the commands in this post you need connect the active directory power shell to your office 365 account – http://jermsmit.com/azure-active-directory-module-for-windows-powershell-how-to-connect/

 

How to Remove Users From the Office 365

The time may come to clean up. Here are steps I have taken

To delete the account for one or more users

  1. Sign in to Office 365 with your work or school account.
  2. Go to the Office 365 admin center.
  3. Go to Users > Active Users.
  4. Choose the names of the users that you want to delete, and then select DELETE Delete.
  5. In the confirmation box, select Yes.

Done; not so fast.  The deleted users is not fully gone yet. It takes 30 days after you have deleted the user for it to purge from Office 365.  However there is a way to do this faster

To delete, deleted users in Office 365

Connect to Exchange Online using the Windows Azure Powershell module.

To connect you enter the following cmdlet’s:

This will prompt you for your credentials and stores them within $msolcred.

Next we enter to connect using the stored credentials

Now that you are connected you can issue the following command to list deleted users

Display deleted user

To remove the deleted user

If you had multiple users, this method would work to remove all deleted users recycle bin

 

Tech Short: Convert a Mailbox, Exchange 2013

Here are some steps that worked for me in converting a user mailbox to a shared mailbox.

Info: You can convert the following mailboxes from one type to another

  • User mailbox to resource mailbox
  • Shared mailbox to user mailbox
  • Shared mailbox to resource mailbox
  • Resource mailbox to user mailbox
  • Resource mailbox to shared mailbox

Example reason why you might wan’t to do this:

You have a mailbox account with the name of  bookclub and are looking make it a shared account because its consuming a license. To address this we will convert it to a shared mailbox account by issues the following commands in the Exchange Management Shell

 

If you have multiple accounts, the following steps may apply to you

 

Please note the following csv document formatting:

Ref: http://technet.microsoft.com/en-us/library/jj710164%28v=exchg.150%29.aspx