'Passed URI is not valid' when running Set-FederatedOrganizationIdentifie r
We currently have an Exchange 2010 only environment. I have successfully created a federation trust with the Microsoft Federation Gateway. I have created the necessary txt records for the federated delegation (exchangedelegation.mydomain.com and mydomain.com). The certificate has been distributed successfully to all of the Exchange 2010 servers. In the Manage Federation wizard on the Manage Federated Domains screen, I add exchangedelegation.mydomain.com and mydomain.com and set exchangedelegation.mydomain.com as the account namespace. After entering my email address as the organization contact I click next. When I click manage I get the error: Error: 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.".". An unexpected result was received from Windows Live. Detailed information: "InvalidUri InvalidUri: Passed URI is not valid.". InvalidUri: Passed URI is not valid. Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.1.267.0&t=exchgf1&e=ms.exch.err.ExB5F48C Exchange Management Shell command attempted: Set-FederatedOrganizationIdentifier -DelegationFederationTrust 'Microsoft Federation Gateway' -AccountNamespace 'exchangedelegation.mydomain.com' -OrganizationContact 'myaddress@mydomain.com' -Enabled $true Has anybody else received this same error? Thanks in advance for your help!
March 21st, 2011 11:42pm

Hi, Yes, I'm having the exact same problem. Everything seems to have been done correctly so far, I reproduced the error in two labs. The CAS have direct internet access. DNS records were verified first. We used the wizard and auto-generated self-signed certificate. Also, running, Test-FederationTrust: RunspaceId : f8207b1c-786b-4e0e-90b4-b4c94c3228e3 Id : FederationTrustConfiguration Type : Error Message : The property ApplicationUri is missing in the FederationTrust object. And running Get-FederationTrust: Name ApplicationIdentifier ApplicationUri ---- --------------------- -------------- Microsoft Federat... So, clearly there is a problem when the trust is created that no AppID or AppURI is generated. This used to be done manually in the Office 365 preview, but was not supposed to be necessary in the beta. At that time the "New-FederationTrust" cmdlet returned an AppID value to also enter in a TXT record in DNS. Now, I'm not sure how to get the AppID or AppURI (usually the SMTP domain) set properly and validated by the MFG. Have you had any response?
Free Windows Admin Tool Kit Click here and download it now
March 25th, 2011 7:15pm

When you successfully complete the Manage Federation wizard (the Set-FederatedOrganizationIdentifier command is ran) the ApplicationUri will show up. So when you run the Manage Federation wizard you get the same error as I did?
March 25th, 2011 9:29pm

The problem I was having was on Microsoft's end.
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 11:21pm

Hi - can you provide more details on the resolution for this issue? What was the problem on microsoft's end?
September 16th, 2011 8:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics