Symptoms:
When running Hybrid Configuration Wizard you may receive the following error:
The wizard did not complete successfully. Please see the list below for error details.
Updating hybrid configuration failed with error 'Subtask Configure execution failed: Configure Organization Relationship Execution of the Set-FederatedOrganizationIdentifier cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings. An error occurred while attempting to provision Exchange to the Partner STS. Detailed Information "An unexpected result was received from Windows Live. Detailed information: "InvalidUri InvalidUri: Passed URI is not valid.".". at Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, SessionParameters parameters, Boolean ignoreNotFoundErrors) '. Additional troubleshooting information is available in the Update-HybridConfiguration log file on server 365HYP01 located at C:Program FilesMicrosoftExchange ServerV15LoggingUpdate-HybridConfigurationHybridConfiguration_4_8_2014_10_17_44_635325490647602241.log.
In the above error note the highlighted parts which will be useful to troubleshoot the error. The first is indicating that the error occurred when executing Set-FederatedOrganizationIdentifier cmdlet.
The second part is not really helpful saying that the Windows Live responded with unexpected result and InvalidUri. Very helpfulJ.
The following snapshot shows the error:
Troubleshooting:
The next logical step is to check the log file mentioned in the above error, when checking the log file under C:Program FilesMicrosoftExchange ServerV15LoggingUpdate-HybridConfiguration the following error is logged:
INFO : Session=OnPrem Cmdlet=Set-FederatedOrganizationIdentifier -AccountNamespace 'DOMAIN_NAME' -DelegationFederationTrust 'Microsoft Federation Gateway' -Enabled: $true -DefaultDomain 'DOMAIN_NAME' START
[04/08/2014 10:18:01] ERROR : System.Management.Automation.RemoteException: An error occurred while attempting to provision Exchange to the Partner STS. Detailed Information "An unexpected result was received from Windows Live. Detailed information: "InvalidUri InvalidUri: Passed URI is not valid.".".
[04/08/2014 10:18:01] INFO : Session=OnPrem Cmdlet=Set-FederatedOrganizationIdentifier FINISH Time=2093.6758ms
In the log file the main interesting part is the cmdlet which caused the error:
Set-FederatedOrganizationIdentifier -AccountNamespace 'DOMAIN_NAME' -DelegationFederationTrust 'Microsoft Federation Gateway' -Enabled: $true -DefaultDomain 'DOMAIN_NAME'
The second logical step is to try to execute the cmdlet from Exchange Management Shell, check the below snapshot:
The error in the snapshot indicates the same that “unexpected result was received from Windows Live “InvalidUri InvalidUri”
Solution:
Microsoft Knowledge Base Article (KB 2615183): http://support.microsoft.com/kb/2615183 mentioning that the cause of this error due to:
“This issue occurs if the domain name for your organization is blocked. A domain name may be blocked in Windows Live for the Windows Azure Active Directory (Windows Azure AD) authentication system if the domain name is reserved or if it doesn't meet certain requirements.”
To solve this problem you will need to contact Office 365 support, open service request with the error details and domain name and they will remove the domain names from the blocking list.
Once the domain removed from the black list, run the HCW wizard again to complete the Hybrid configuration.
Other Symptoms:
You may also receive the following error:
Updating hybrid configuration failed with error 'Subtask Configure execution failed: Configure Organization Relationship Execution of the Add-FederatedDomain cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings. Unable to reserve the URI "DOMAIN_NAME" for the domain "DOMAIN_NAME" on application identifier "000000004C022B11". Detailed information: "An unexpected result was received from Windows Live. Detailed information: "InvalidUri: Passed URI is not valid.
In the above scenario the error was with the Add-FederatedDomain cmdlet and in this case the domain name was in the blocked list.