you want also want to use the –Force parameter. All you need to do is to use the Remove-MsolUser cmdlet instead of the New-MSOlUser cmdlet.If you have not done this yet, you will need two pieces of software: the Microsoft Online Services Sign-In Assistant for IT Professionals RTW (yes, that’s the official name) and the Azure Active Directory Module for Windows PowerShell. First off, set yourself up to connect to the service through PowerShell remoting.Parameter name: assetGuid (System.String assetGuid, `1& softLocks) (at C:/buildslave/unity/build/Editor/Mono/Collab/Softlocks/SoftlockData.cs:169).Set-MsolUser -UserPrincipalName -ImmutableId RDHiRneDPkiofrZ2nbYu7Q= Here is the UPN of the user who is in cloud and we want to sync the on-premise user to sync to.12/12 Update: Exchange SP3 UR8 v2 (.002) released, Download here 12/10 Update #2: Exchange 2010 SP3 UR8 pulled due to MAPI RPC bug. 12/30 Updated: Added a known issue with 2013 CU7 EDGE and two known issues from CU5 & CU6 that still exist in CU7.
