Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you run the Set-FederatedOrganizationIdentifier cmdlet to set up a hybrid deployment: "InvalidUri: Passed URI is not valid"


View products that this article applies to.

Problem

You want to set up a hybrid deployment between your on-premises Microsoft Exchange Server 2010 organization and an external federated organization. However, when you run the Set-FederatedOrganizationIdentifier cmdlet to set up the federated organization identifier, the operation isn't successful.

You receive an error message that resembles the following:
InvalidUri: Passed URI is not valid
The following is an example of this error message in the output:
C:\Windows\system32>set-federatedorganizationidentifier -DelegationFederationtrust 'Microsoft Federation Gateway' -
accountnamespace 'exchangedelegation.<Contoso>.com' -Enabled $true
An error occurred while attempting to provision Exchange to the Partner STS. Detailed Information "An unexpected resul
t was received from Windows Live. Detailed information: "InvalidUri InvalidUri: Passed URI is not valid.".".
+ CategoryInfo : InvalidResult: (:) [Set-FederatedOrganizationIdentifier], ProvisioningFederatedExchangeE
xception
+ FullyQualifiedErrorId : C02BD180,Microsoft.Exchange.Management.SystemConfigurationTasks.SetFederatedOrganization
Identifier
Note In this output, <Contoso> is a placeholder for the domain name.

↑ Back to the top


Cause

This issue occurs if the domain name for your organization is blocked. A domain name may be blocked in Windows Live for the Microsoft Azure Active Directory (Azure AD) authentication system if the domain name is reserved or if it doesn't meet certain requirements.

↑ Back to the top


Solution

To resolve this issue, contact Microsoft Support.

↑ Back to the top


More information

For more information about the Set-FederatedOrganizationIdentifier cmdlet, go to the following Microsoft website:

↑ Back to the top


Still need help? Go to the Office 365 Community website.

↑ Back to the top


Keywords: o365, o365e, o365m, o365022013, after, upgrade, hybrid, o365a, KB2615183

↑ Back to the top

Article Info
Article ID : 2615183
Revision : 12
Created on : 7/9/2014
Published on : 7/9/2014
Exists online : False
Views : 773