First time experience such error and behaviour, so the situation is that this user has problem getting her OneDrive to work on her desktop, it was her first time setting it up and she receive the above error code after she sign in and authenticate her account.
Well from Azure AD, it will shows that her login activity for OneDrive is successful, but Azure AD doesn’t shows that her setup was failed. At first I suspect it could be network issue, tested another account it went through the setup successfully. Hence, running PowerShell (Msol), to query the user account information and perform comparison and everything was showing in good condition.
Another thing is that she can successfully use the web based on SharePoint Online and OneDrive online.
As I went through to the Exchange Admin center and notice her email addresses missing a type, that is the SPO. This type of email address is generated once the user is assigned with the Office 365 license with Sharepoint Online and OneDrive online features.
The only resolution to this is to recreate the account.
- Backup mailboxes to PST and files to a local drive or external drive
- There are many ways to backup
- Unassign the user license
- Go to Active Directory and disable the account and move it to a unsync Organization Unit
- Go to Azure AD Connect Server and perform the sync
- Go to Office 365 make sure that the account has been move to deleted users, well you could use PowerShell to query -ReturnDeletedUsers.
Get-MsolUser -UserPrincipalName <username>@domain.com.my -ReturnDeletedUsers
- Once it is found, then run the remove command, you can use GUI to remove them at the Azure portal “portal.azure.com”
Get-MsolUser -UserPrincipalName <username>@domain.com.my -ReturnDeletedUsers | Remove-MsolUser -RemoveFromRecycleBin -Force
- Go back to your Active Directory and recreate the user account, and make sure it is in the sync OU
- Run another sync at your Azure AD Connect Server
- Go to Office 365 > Active Users > Search for the user and assign the license
There are few reasons why this happen, for my case was the old Azure AD Connect server died or corrupted and had to re-provision a new one. Users are some still on Exchange on-premise and some are in cloud, due to budget. Sometime things happen.
Anyway, hope this helps!