<div>
Hi Christian,<br />
<br />
Which migration approach you are using?
</div>


Hi Christian,

Which migration approach you are using?

<div>
Thanks guys, in trying to fix this, the team also tried the following, <br />
<br />
Remove-MsolUser -UserPrincipalName Frank@contoso.com<br />
Remove-MsolUser -UserPrincipalName Frank@copntoso.com -RemoveFromRecycleBin<br />
<br />
So the mailbox and user are out of Msol, waiting for a ADConnect to complete... but the mailbox in Exchange on-prem still shows as a remote mailbox.
</div>


Thanks guys, in trying to fix this, the team also tried the following,

Remove-MsolUser -UserPrincipalName Frank@contoso.com
Remove-MsolUser -UserPrincipalName Frank@copntoso.com -RemoveFromRecycleBin

So the mailbox and user are out of Msol, waiting for a ADConnect to complete... but the mailbox in Exchange on-prem still shows as a remote mailbox.

<div>
<div class="content wysiwyg-content">
We have some users that were trying to migrate to Office 365, Exchange online... <br />
<br />
They were given E3 licences weeks ago for testing the Msol services, but now we are unable to migrate their mailboxes successfully to the cloud. Would this possibly be because they were already enabled for Exchange Online and so a mailbox was provisioned in the cloud, prior to migrating their on-prem mailboxes? <br />
<br />
How do we fix this? Remove the O365 E3 licenses, wait, migrate the mailbox and assign the license again? <br />
<br />
Whats the general rule of thumb? Migrate mailboxes THEN assign licenses? <br />
<br />
Thanks,
</div>
</div>


We have some users that were trying to migrate to Office 365, Exchange online... 

They were given E3 licences weeks ago for testing the Msol services, but now we are unable to migrate their mailboxes successfully to the cloud. Would this possibly be because they were already enabled for Exchange Online and so a mailbox was provisioned in the cloud, prior to migrating their on-prem mailboxes? 

How do we fix this? Remove the O365 E3 licenses, wait, migrate the mailbox and assign the license again? 

Whats the general rule of thumb? Migrate mailboxes THEN assign licenses? 

Thanks,

Office 365: Assign licenses before mailbox migration?

Microsoft Office is an integrated suite of applications that includes Outlook, Word, Excel, Access, PowerPoint, Visio and InfoPath, along with a number of tools to assist in making the individual components work together. Coding within and between the projects is done in Visual Basic for Applications, known as VBA.

Microsoft Office

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Office 365 is a group of software plus services subscriptions that provides productivity software and related services to its subscribers. Office 365 allows the use of Microsoft Office apps on Windows and OS X, provides storage space on Microsoft's cloud storage service OneDrive, and grants 60 Skype minutes per month. Office 365 includes e-mail and social networking services through hosted versions of Exchange Server, Skype for Business Server, SharePoint and Office Online, integration with Yammer, as well as access to the Office software. All of Office 365's components can be managed and configured through an online portal; users can be added manually, imported from a CSV file, or Office 365 can be set up for single sign-on with a local Active Directory using Active Directory Federation Services.