Name Space is not Federated
Topic Last Modified: 2011-06-22
The Microsoft Remote Connectivity Analyzer Tool queries the Authentication Platform in the cloud to perform a realm discovery. When that process is finished, the Authentication Platform passes to the requesting client the ADFS endpoint URL that the client requires for authentication. If the identity that you provide does not match an identity federated domain name, the lookup fails.
The Remote Connectivity Analyzer displays the following warning when the domain part of the name is not set up for identity federation:
The domain is not a federated domain.
This message indicates a failure of the realm discovery process. This process is the initial check against the domain name to determine whether the Authentication Platform in the cloud has this domain configured for identity federation. The failure of this process can be caused by an incorrectly typed UPN. The failure can also indicate that identity federation is not yet configured.
To verify whether the domain name is set up for identity federation, follow these steps:
Log on to the Microsoft Online Portal as a Tenant Administrator.
Under Management in the navigation pane, click Domains.
Locate the domain that matches the UPN that was entered for the test.
Verify that the domain type is set to configured for single sign-on.
More Information
For more information planning for identity federation, see Prepare for single sign-on.
For help to upgrade your current Exchange 2010 environment, see Exchange Server Deployment Assistant.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for