The final step is to verify that the restored user can actually sign in and access their Microsoft 365 services. This confirms the restoration was completely successful.
Contact the user or test the account yourself (if you have the credentials) by attempting to sign in to Microsoft 365 services.
Try accessing the following services to ensure full functionality:
- Outlook Web App: Navigate to outlook.office.com
- Microsoft 365 Portal: Go to portal.office.com
- Teams: Access via web browser or desktop application
- SharePoint: Test access to any sites the user previously had permissions to
During the first sign-in attempt, you might encounter temporary issues or redirect errors. This is normal immediately after restoration as authentication tokens and cached credentials need to refresh.
Warning: If you see HTTP 500 redirect errors during sign-in, don't panic. These are common immediately after account restoration and typically resolve within 30 minutes as the authentication system updates.
If the user cannot sign in after 30 minutes, check the following:
# Check sync errors in PowerShell on Entra Connect server
Get-ADSyncConnectorRunStatus
You can also verify the user's cloud identity status:
# Install and connect to Microsoft Graph PowerShell if not already done
Install-Module Microsoft.Graph -Scope CurrentUser
Connect-MgGraph -Scopes "User.Read.All"
# Check user status
Get-MgUser -Filter "userPrincipalName eq 'user@yourdomain.com'" | Select-Object DisplayName, AccountEnabled, UserPrincipalName
Verification: The user should be able to sign in successfully and access their email, calendar, and other Microsoft 365 services. Email delivery should resume normally, and the user should see their historical data intact.