Share via

Hybrid Configuration Wizard Error

Anonymous
2016-07-03T13:20:41+00:00

Hi,

My hybrid configuration stuck at below error. Part of the HCW log is as follows. Appreciate help / advice to fix below error.

Thanks in Advance,

Chandimal

2016.06.28 05:20:20.027 *ERROR* [Activity=Domain Ownership, Session=OnPremises, Cmdlet=Set-FederatedOrganizationIdentifier] FINISH Time=54.9s Results=PowerShell failed to invoke 'Set-FederatedOrganizationIdentifier': An error occurred while attempting to provision Exchange to the Partner STS.  Detailed Information "An error occurred accessing Windows Live. Detailed information: "The request failed with HTTP status 403: Forbidden.".".

2016.06.28 05:20:20.027 *ERROR* [Client=UX, Page=DomainProof] PowerShell failed to invoke 'Set-FederatedOrganizationIdentifier': An error occurred while attempting to provision Exchange to the Partner STS.  Detailed Information "An error occurred accessing Windows Live. Detailed information: "The request failed with HTTP status 403: Forbidden.".".

2016.06.28 05:20:20.027         [Activity=Domain Ownership] Data retrieved

2016.06.28 05:20:20.027         [Activity=Domain Ownership] FINISH Time=55.9s

2016.06.28 05:20:20.027         [Activity=Domain Ownership, Provider=OnPremises] Disposing Runspace.

Microsoft 365 and Office
Microsoft 365 and Office

A comprehensive suite of productivity tools and cloud services that enhance collaboration, communication, and efficiency. Combining classic Office apps with advanced Microsoft 365 features, it supports both personal and business needs

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2016-07-20T05:32:39+00:00

Hi,

My hybrid configuration stuck at below error. Part of the HCW log is as follows. Appreciate help / advice to fix below error.

Thanks in Advance,

Chandimal

2016.06.28 05:20:20.027 *ERROR* [Activity=Domain Ownership, Session=OnPremises, Cmdlet=Set-FederatedOrganizationIdentifier] FINISH Time=54.9s Results=PowerShell failed to invoke 'Set-FederatedOrganizationIdentifier': An error occurred while attempting to provision Exchange to the Partner STS.  Detailed Information "An error occurred accessing Windows Live. Detailed information: "The request failed with HTTP status 403: Forbidden.".".

2016.06.28 05:20:20.027 *ERROR* [Client=UX, Page=DomainProof] PowerShell failed to invoke 'Set-FederatedOrganizationIdentifier': An error occurred while attempting to provision Exchange to the Partner STS.  Detailed Information "An error occurred accessing Windows Live. Detailed information: "The request failed with HTTP status 403: Forbidden.".".

2016.06.28 05:20:20.027         [Activity=Domain Ownership] Data retrieved

2016.06.28 05:20:20.027         [Activity=Domain Ownership] FINISH Time=55.9s

2016.06.28 05:20:20.027         [Activity=Domain Ownership, Provider=OnPremises] Disposing Runspace.

Hi Chandimal,

Glad to hear the issue is resolved. I am here to share the summary of the issue so that other community members who got the same issue can quick find the useful reference. So, please kindly also mark this reply as answered.

  1. The Hybrid traffic was going through the Proxy, which to some degree  prevent the communication with MFG.
  2. The domain which was registered in another tenant. Although removed from the previous tenant, MFG still got some stale records which did not allow your domain registered in MFG again.

Thanks,

Ran

Was this answer helpful?

0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-07-09T08:45:03+00:00

    Hi Chandimal,

    Thanks for the information. There seems not to be with your Exchange server settings. It seems your domain cannot be added in MFG. I would like to collect your tenant information via PM and check with our relative team, if possible escalate to them to see if your domain is blocked in MFG.

    Best regards,

    Ran

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-07-07T10:32:39+00:00

    Hi Chandimal,

    Thanks for the log. The federation trust cannot be established because the OrgID (organization identifier) cannot be created. 403 means the request is hit to the server but for some reason, it is denied. Please go to your Exchange Management Shell and try to see if you are able to run Get-FederationTrust |Fl. If you can, please send us the results to PM.

    Best regards,

    Ran

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-07-05T09:12:02+00:00

    Hi Chandimal,

    According to the error, the issue is probably related to the federation trust between your Exchange org and MFG (Microsoft Federation Gateway). But to have a full understanding, can send us the complete results of the log via PM?

    Thanks,

    Ran

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-07-04T05:32:48+00:00

    Hi Chandimal,

    Form the error, we can see the issue occurred when running Cmdlet “Set-FederatedOrganizationIdentifier”. I found a KB article for this error. It indicates that it might be a timing issue. Please wait for a while and rerun the HCW again.

    https://support.microsoft.com/en-sg/kb/3067975

    If the issue still persists, please run the cmdlet on your on-premises Exchange PS and send us the result via PM. Meanwhile, I would also like to collect the complete results of the log via PM for further troubleshooting.

    Set-FederatedOrganizationIdentifier -DelegationFederationTrust "Microsoft Federation Gateway" -AccountNamespace "Contoso.com" -Enabled $true

    I have sent you a PM to request this information. Please click on the link below to access to your Private Message.

    https://answers.microsoft.com/en-us/site/startsignin

    Thanks,

    Ran

    Was this answer helpful?

    0 comments No comments