Can't see free/busy information after migrated from Exchange on-premises to online


After you migrate users from Microsoft Exchange on-premises to Exchange Online, they can't see free/busy information. You can verify that they are experiencing the issue by running the following cmdlet:

Get-organizationrelationship "name of org relationship of cloud to on-prem" | test-organizationrelationship -useridentity

The result resembles the following: 

RunspaceId  : RunSpaceID
Identity    :
Id          : FailureToGetDelegationToken
Status      : Error
Description : Failed to get delegation token: <S:Fault xmlns:S=""><S:Code><S:Value>S:Sender</S:Value><S:Subcode><S:Value>wst:FailedAuthentication</S:Value></S:Subcode></S:Code><S:Reason><S:Text
              xml:lang="en-US">Authentication Failure</S:Text></S:Reason><S:Detail><psf:error
              xmlns:psf=""><psf:value>0x80048827</psf:value><psf:internalerror><psf:code>0x80041084</psf:code><psf:text>The password has to be changed.
             < /psf:text></psf:internalerror><psf:flowurl>;seclog=10&pp
              Microsoft.Exchange.Net.WSTrust.SoapFaultException: Soap fault exception received.
                 at Microsoft.Exchange.Net.WSTrust.SoapClient.Invoke(IEnumerable`1 headers, XmlElement bodyContent)
                 at Microsoft.Exchange.Net.WSTrust.SecurityTokenService.IssueToken(DelegationTokenRequest request, XmlTextWriter debugStream)
                 at Microsoft.Exchange.Management.Sharing.TestOrganizationRelationship.GetDelegationToken().
IsValid     : True
ObjectState : New


This issue occurs if you can't set the ForceChangePassword parameter to false on the cloud authentication platform.


To fix this issue, run the following cmdlet:

Set-MsolUserPassword -UserPrincipalName -ForceChangePassword $false

Still need help? Go to Microsoft Community.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.