Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Today’s Tip…
This is an extension of a previous tip.
Another way to check if domain is available by copying and pasting the following URL string to a web browser:
https://login.microsoftonline.com/getuserrealm.srf?login=user@contoso.com&xml=1
Note - Replace the “bolded” part with the domain you want to check.
Review the results and really pay attention to the NameSpaceType value.
Scenario: If the domain does not exist in Office 365/Azure AD…
<?xml version="1.0"?>
<State>4</State>
<UserState>1</UserState>
<Login>user@fakedomain.com</Login>
<NameSpaceType>Unknown</NameSpaceType>
</RealmInfo>
Scenario: Domain is verified and not federated…
<?xml version="1.0"?>
<State>4</State>
<UserState>1</UserState>
<Login>user@williamfiddes.com</Login>
<NameSpaceType>Managed</NameSpaceType>
<FederationBrandName>WILLIAMFIDDES.COM</FederationBrandName>
</RealmInfo>
Scenario: Domain is verified and federated…
<?xml version="1.0"?>
<State>1</State>
<UserState>2</UserState>
<Login>user@willfid.msftonlinerepro.com</Login>
<NameSpaceType>Federated</NameSpaceType>
<DomainName>WILLFID.MSFTONLINEREPRO.COM</DomainName><FederationGlobalVersion>-1</FederationGlobalVersion>
<AuthURL>https://sts.willfid.msftonlinerepro.com/adfs/ls/</AuthURL>
<IsFederatedNS>true</IsFederatedNS>
<FederationBrandName>WILLFID.MSFTONLINEREPRO.COM</FederationBrandName>
<AllowFedUsersWLIDSignIn>false</AllowFedUsersWLIDSignIn>
<Certificate>MIIC+jCCAeKgAwIBAgIQFnePUJ582Y9I6SQvgH5UgDANBgkqhkiG9w0BAQsFADA5MTcwNQYDVQQDEy5BREZTIFNpZ25pbmcgLSBzdHMud2lsbGZpZC5tc2Z0b25saW5lcmVwcm8uY29tMB4XDTE1MDIyMDIyMzUwNFoXDTE2MDIyMDIyMzUwNFowOTE3MDUGA1UEAxMuQURGUyBTaWduaW5nIC0gc3RzLndpbGxmaWQubXNmdG9ubGluZXJlcHJvLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALt5DTbhIMj08G11GvIFW3SzzzFT4TemNQ91xwDt7gQJvCuBoBqM2gKQ05RMgEkFbXk/U8PCYkE1pDmdGoQhY1nfZWBFDk0bWiQn/JonUcyZHqWkoJHk7JpOy22dqy3VMTyQZQu0oApVaxPan5jiaYrHb9RmM3bO1WiGY92e2Bys8O/fn2Q7GVX4KW+3NaRKUjbmxev5FI07RPR55Um8kYI6VSCWQvMiuMw6K8vFT93X/CEkZSr0bBDl3EKXUdx3FCovhtq2z3BK+cqOV4My38WtOERnIhEkY2Wg8D5lyR2VHn28ybQSmL7/7vT122UbMSJu/U3rVgeJfYCmbJSIKE8CAwEAATANBgkqhkiG9w0BAQsFAAOCAQEAjsaGPkQqambOxuBVKGeoArU/c+jdlN7Vi/aaxcTihz8uBYxwb+7SEn3hTnWwl8rCGcBLXNSeyPdH/1sQWIhKjh9wr3YbpkF8kK+n6P3Vy0ksxZ6mzbdXJtD8qwVz6VgaV1Oy/AXc2+MqVkB5bA3HQ+V1AFIx/InO5iqSKp6Frbk2fegzHjx6dX7io5YDpcEKBHsZcMtpfgObFkDfXqw6RJYMrdkSx+UypIt3lf+sZ+r1u028HdUpTLYDgSVCGYqoGZ/JF9Q+FuYxgbVfVx7o6Oaqg/OdSeMG4SgcylUTJsQF7yNrodQ0MAABh+pR7WOE35muTigYbOevfSJfR/sYUg==</Certificate>
<MEXURL>https://sts.willfid.msftonlinerepro.com/adfs/services/trust/mex</MEXURL>
<SAML_AuthURL/>
<PreferredProtocol>1</PreferredProtocol>
<EDUDomainFlags>0</EDUDomainFlags>
</RealmInfo>
Comments
- Anonymous
March 30, 2017
Thanks for this.interestingly I have users in the same OU, with the same UPN suffix, some are as scenario 1 (so not working) and others are state 3, userstate2 and working as expected.