Era Host hosting
EraHost – Free Domain, Cheap Hosting!
Client Area
Support 24/7
Menu

What Is clientconfig.microsoftonline-p.net? Complete Setup Guide

3 min read
06.06.2026

Overview

clientconfig.microsoftonline-p.net is a CNAME (Canonical Name) DNS record used by Microsoft Online Services for authentication and identity verification in Microsoft 365 (formerly Office 365) and Azure Active Directory (Azure AD).

Microsoft 365 clientconfig DNS Setup
M365 autodiscover — CNAME chain Outlook uses to find your tenant.

For closely related Microsoft / Outlook / DNS topics, see MX Hosting — Complete Guide, How to Configure Name Servers for Hosting, and "EHLO not accepted from server!".

Purpose of clientconfig.microsoftonline-p.net

  • Verifies domain ownership for Microsoft services.
  • Enables Single Sign-On (SSO) for Microsoft 365 apps (Outlook, Teams, SharePoint, OneDrive).
  • Helps with seamless authentication in Azure AD and federated domains.
  • Ensures that login requests route correctly through Microsoft?s authentication infrastructure.

If your domain is registered to use Microsoft 365 or Azure AD, Microsoft requires a CNAME record pointing to clientconfig.microsoftonline-p.net.

Note: This record is essential for proper authentication and SSO functionality in Microsoft 365 environments.
Linux Hosting
Reliable and fast web hosting!
  • Free domain
  • Modern servers
  • NVMe disks
  • 7-day free trial
Linux Hosting

How to Set Up clientconfig.microsoftonline-p.net (MSOID CNAME Record)

If you're setting up Microsoft 365 or Azure AD, you need to add the MSOID CNAME record to your domain's DNS settings.

Required DNS Record Format

Record Type Host (Name) Value (Target) TTL
CNAME msoid.yourdomain.com clientconfig.microsoftonline-p.net 3600

Replace yourdomain.com with your actual domain name.

Add the MSOID Record in Your DNS Settings

For cPanel Users

  1. Log in to cPanel.
  2. Navigate to Zone Editor > Click Manage.
  3. Click "Add Record" > Select CNAME.
  4. Enter:
    • Name: msoid.yourdomain.com
    • Target: clientconfig.microsoftonline-p.net
    • TTL: 3600
  5. Click Save.

For Cloudflare Users

  1. Log in to Cloudflare > Go to DNS Management.
  2. Click "Add Record" > Select CNAME.
  3. Enter:
    • Name: msoid
    • Target: clientconfig.microsoftonline-p.net
    • TTL: Auto
  4. Ensure Proxy Status is set to "DNS Only" (?? Gray Cloud, NOT ?? Orange).
  5. Click Save.

For Other Registrars (GoDaddy, Namecheap, etc.)

  • Go to DNS Management.
  • Add a new CNAME Record:
    • Host: msoid
    • Type: CNAME
    • Value: clientconfig.microsoftonline-p.net
    • TTL: 3600
  • Click Save.

Now, Microsoft can verify your domain for authentication services.

How to Verify That the clientconfig.microsoftonline-p.net Record Works

Check MSOID Record via Command Line

Linux/macOS

dig CNAME msoid.yourdomain.com +short

Expected Output (Correct Setup):

clientconfig.microsoftonline-p.net.

Windows (Command Prompt)

nslookup -type=CNAME msoid.yourdomain.com

Expected Output:

msoid.yourdomain.com   canonical name = clientconfig.microsoftonline-p.net.

Use Online DNS Checkers

If the correct CNAME appears, the record is resolving properly.

Troubleshooting clientconfig.microsoftonline-p.net Issues

Issue Possible Cause Fix
MSOID record not found CNAME record missing Add msoid.yourdomain.com > clientconfig.microsoftonline-p.net
DNS changes not detected Takes time to propagate Wait 24-48 hours
Cloudflare blocking lookup Cloudflare proxy enabled Set Proxy to "DNS Only" (Gray Cloud ??)
Conflicting CNAME records Duplicate records in DNS Remove incorrect CNAMEs
Microsoft 365 still not verifying DNS propagation delay Wait, then re-check in Admin Center

Final Verification in Microsoft 365

  1. Log in to Microsoft 365 Admin Center > admin.microsoft.com.
  2. Navigate to Settings > Domains.
  3. Select your domain.
  4. Click "Verify DNS Settings".
  5. Microsoft will check the MSOID record.

Once Microsoft detects it, authentication will work properly.

Summary Table

Task Steps
Check What clientconfig.microsoftonline-p.net Is It's a Microsoft authentication CNAME record
Set Up MSOID Record Add CNAME: msoid.yourdomain.com > clientconfig.microsoftonline-p.net
Verify DNS Record Use dig, nslookup, or MXToolbox
Fix MSOID Issues Ensure correct CNAME, wait for propagation, disable Cloudflare proxy
Confirm in Microsoft 365 Go to Admin Center > Domains > Verify

Now your Microsoft authentication (clientconfig.microsoftonline-p.net) should be working properly!

Frequently asked questions
Mostly the canonical `autodiscover.yourdomain.com CNAME → autodiscover.outlook.com` is what M365 setup wizard recommends. clientconfig is part of the discovery chain Outlook walks. Setting up the CNAME makes Outlook auto-configure on first launch. Without it, users manually enter server settings.
Autodiscover CNAME points users to on-prem Exchange's autodiscover service (typically `mail.yourdomain.com`); on-prem Exchange forwards requests to M365 for cloud-only users. Microsoft 365 Hybrid Configuration Wizard configures both. Pure cloud: just CNAME to autodiscover.outlook.com.
Separate step. M365 admin center asks you to publish TXT `MS=ms` to prove domain ownership. After verification, you add MX, SPF, autodiscover CNAME, etc. Don't skip — without verification, domain isn't usable for M365.
CNAME points to on-prem Exchange which points back to clientconfig and doesn't break. Misconfigured hybrid. Typically resolves by re-running the Hybrid Configuration Wizard and letting it set autodiscover correctly. Microsoft's Remote Connectivity Analyzer tool shows what's wrong in the chain.
Related articles
mbstring.internal_encoding — Complete PHP Guide
cpsrvd — Complete Guide to cPanel Service Daemon
Cache-Control: max-age — Complete Guide