How to Configure FQDN and CNAME Records for AD FS Federation
Question details
The user needs to establish the correct DNS configuration, including setting up an FQDN and a CNAME record, to deploy an AD FS federation service linked to an onmicrosoft.com domain.

- Product
- Active Directory Federation Services (AD FS)
- Device & OS
- not provided
- Scenario
- Deploying a new federation server and connecting it to Microsoft cloud services requiring corporate DNS updates.
- Observed behavior
- The corporate DNS requires a specific Host (A) or Alias (CNAME) resource record mapped to the federation server to successfully route authentication and device registration requests.
Ensure you have administrative privileges to access your corporate DNS Server and know the intended Fully Qualified Domain Name (FQDN) for your federation server.
Create a CNAME Resource Record in Corporate DNS
This method uses the Windows Server DNS Manager to add the required alias record for the federation service and Device Registration Service (DRS).
To properly route authentication requests for your onmicrosoft.com domain, your corporate DNS must have an alias pointing to the federation server.
This configuration ensures that both standard federation traffic and Device Registration Service (DRS) queries are handled by the correct endpoint.
Log in to your DNS server or domain controller. Click the Start menu, navigate to Windows Administrative Tools, and select DNS to launch the DNS Manager console.
In the console tree on the left, expand your DNS server name, expand the Forward Lookup Zones folder, and click on your specific corporate domain name.
Right-click the empty space in the details pane or right-click the domain folder, then select New Alias (CNAME) from the context menu.
Type the chosen alias name for your AD FS service (e.g., 'fs' or 'sts'). In the 'Fully qualified domain name for target host' field, input the exact target FQDN of your federation server.
Click OK to save the new CNAME record. Allow adequate time for the DNS changes to propagate across your corporate network.

Manage Your IT Documentation Efficiently with WPS Office
While setting up AD FS federation requires dedicated Windows Server configurations, documenting your IT infrastructure, server IPs, and DNS records does not require an expensive office suite. WPS Office is a robust, free alternative to Microsoft Office that easily handles all your administrative spreadsheets and deployment manuals.
- 1. Download the Installer: Visit the official WPS website and download the free installation package for your operating system.
- 2. Install the Software: Run the downloaded installer and follow the quick on-screen instructions to set up the office suite.
- 3. Open and Edit IT Manuals: Launch WPS Office to seamlessly open, edit, and save your existing .docx and .xlsx infrastructure documentation without formatting loss.

Frequently Asked Questions
What is an FQDN in the context of AD FS?
An FQDN (Fully Qualified Domain Name) is the complete and exact domain name used to identify your federation server (e.g., fs.yourcompany.com). Clients and relying parties use this FQDN to locate and securely communicate with the AD FS service.
Why must I add a specific CNAME record for DRS?
The Device Registration Service (DRS) requires a standard endpoint, typically prefixed with 'enterpriseregistration'. Creating a CNAME record routes this standardized hostname directly to your AD FS server's FQDN, enabling seamless workplace joining and authentication for enterprise devices.
How long does it take for AD FS DNS records to propagate?
Internal corporate DNS updates usually apply immediately or within a few minutes across local domain controllers. However, if the DNS records are public-facing, it may take anywhere from 15 minutes to 48 hours for global DNS propagation to fully complete.




