It is possible to move back users that have been moved from the on-premises Lync deployment to the cloud, and it is also possible to move on-premises users that have been defined and enabled directly in Office 365. In the latter scenario, it is important to create the user also in the on-premises domain (Directory Service).
Enable-CsUser -Identity "BornOnCloud" -SipAddress "SIP:[email protected]" -HostingProviderProxyFqdn "sipfed.online.lync.com"
$cred = Get-Credential
variable and then move the user from Lync Online to the on-premises Front End using the Lync Management Shell (the -HostedMigrationOverrideURL
parameter has the same value that we used in the previous section):Move-CsUser -Identity [email protected] -Target madhatter.wonderland.lab -Credential $cred -HostedMigrationOverrideURL https://admin0e.online.lync.com/HostedMigration/hostedmigrationservice.sVc
Get-CsUser
| fl
DisplayName
,HostingProvider
,RegistrarPool
,SipAddress
cmdlet is used to verify whether the user has moved as expected.Guy Bachar has published an interesting post on his blog Moving Users back to Lync on-premises from Lync Online (http://guybachar.wordpress.com/2014/03/31/moving-users-back-to-lync-on-premises-from-lync-online/), where he shows how he solved some errors related to the user motion by modifying the HostedMigrationOverrideUrl
parameter.