Verify that the federation server is operational in Windows Server 2012 R2
Applies To: Azure, Office 365, Power BI, Windows Intune
You can use the following procedure to verify that a federation server (weather it was configured as the first federation server in a federation server farm or added to a federation server farm) is operational; that is, that any client on the same network can reach a new federation server.
Membership in Users, Backup Operators, Power Users, Administrators or equivalent, on the local computer is the minimum required to complete this procedure.
To verify that a federation server is operational
Open a browser window and in the address bar, type the name, and then append it with federationmetadata/2007-06/federationmetadata.xml to browse to the federation service metadata endpoint. For example, https://fs.contoso.com/federationmetadata/2007-06/federationmetadata.xml .
If in your browser window you can see the federation server metadata without any SSL errors or warnings, your federation server is operational.
You can also browse to the AD FS sign-in page (your federation service name appended with adfs/ls/idpinitiatedsignon.htm, for example, https://fs.contoso.com/adfs/ls/idpinitiatedsignon.htm). This displays the AD FS sign-in page where you can sign in with domain administrator credentials.
Important
Make sure to configure your browser settings to trust the federation server role by adding your federation service name (for example, https://fs.contoso.com) to the browser’s local intranet zone.
Next step
Now that you have verified that the federation servers are operational, the next step is to Prepare your network infrastructure for configuring extranet access.
See Also
Concepts
Checklist: Deploy your federation server farm on Windows Server 2012 R2
Checklist: Use AD FS to implement and manage single sign-on