How to add custom domain to Microsoft 365 and verify TXT on Defender XDR

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

Why this matters

Add custom domain to microsoft 365 and verify txt on a Defender XDR device is one of the highest-volume how-to searches for the Microsoft 365 Admin category. Most users find the menu path inconsistent across Defender XDR model revisions, so this guide gives a generalised path plus model-specific notes.

Pre-requisites

• A Defender XDR device that's powered on and on the latest stable service version / OS.
• The Defender XDR companion app or management tool installed and signed in.
• 5-15 minutes uninterrupted.

Step-by-step

1. Locate the setting. Open settings on your Defender XDR device. For "add custom domain to Microsoft 365 and verify TXT", the option lives under one of: General, Advanced, Connectivity, Accessibility, or a Defender XDR-specific menu. Check the Defender XDR user manual for your exact model if you can't find it.
2. Toggle the feature on. Confirm the on-screen prompt.
3. Configure sub-options. Most features have 2-3 sub-options (mode, schedule, paired device). Pick values that match your real-world usage pattern.
4. Save / apply. Some Defender XDR models auto-save, others require an explicit Done / Save tap.
5. Test live. Trigger the feature in a real scenario to confirm the configuration is correct.

Tips that save time

• Pair this feature with a Defender XDR automation / routine if the device supports it.
• If the feature relies on cloud sync, give it 1-2 minutes after enabling to propagate.
• For multi-user households / multi-admin teams, set per-user profiles so each user sees their preferred state.

Common gotchas

• Feature greyed out, usually service version too old. Update + retry.
• Feature works once then stops. battery saver / power saver mode is killing the Defender XDR app process. Whitelist it.
• Feature works but with delay, usually cloud-sync latency; check internet speed and Defender XDR service status.

Region / variant notes

Some Defender XDR features are region-locked or only available on higher-tier SKUs. If your variant doesn't show "add custom domain to Microsoft 365 and verify TXT" at all, check the Defender XDR model spec sheet to confirm support.

Frequently asked questions

How long should the recovery / setup take?

For most Defender XDR Microsoft 365 Admin cases, allow 15-45 minutes the first time. Repeats are usually under 10 minutes once you know the menu path.

Will this exact procedure work on every Defender XDR model?

The procedure reflects current Defender XDR behaviour. Menu paths shift between service version generations; verify against the manual for your specific model + revision.

Is the procedure safe in production / live use?

Apply during a maintenance window where possible. Capture pre-change state. Defender XDR doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my Defender XDR support coverage?

Standard operation per the user manual + applying official service version updates does NOT void support coverage. Opening managed services, third-party repair, or unauthorised modifications can void support coverage: check before going further.

Related guides

• All Microsoft 365 Admin guides → /microsoft/section/microsoft_365_admin.html
• All Microsoft guides → /microsoft/

Related fixes

Related guides worth a look while you sort this one out:

• How to add custom domain to Microsoft 365 and verify TXT on Defender for Cloud A
• How to add custom domain to Microsoft 365 and verify TXT on Defender for Identit
• How to add custom domain to Microsoft 365 and verify TXT on Defender for Office
• How to add custom domain to Microsoft 365 and verify TXT on Exchange Online
• How to add custom domain to Microsoft 365 and verify TXT on Microsoft 365 admin
• How to add custom domain to Microsoft 365 and verify TXT on Microsoft 365 Apps (

References

• Defender XDR official support portal for your model.
• Defender XDR community forum + Reddit threads.
• Vendor PSIRT / advisory page (where applicable).

Reference material, not professional advice. Validate with your vendor manual and follow local regulations.

Why this matters for your day-to-day

this device that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.

Safety + preconditions

Before any work on the device in front of you:

• Unplug from mains for any internal-access procedure.
• flush cached state (circuit breakers in PSUs, residual battery charge) per manufacturer guidance.
• Use ESD-safe handling for boards and modules, no carpet, no wool sleeves.
• Avoid moisture; never apply liquids near vents or connectors.
• If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.

How to confirm it's actually fixed

On the affected device, the test is rarely "reboot and see". Use this list:

• Active reproduction: trigger the original failure path on purpose.
• Indirect reproduction: do an activity that would expose the same subsystem.
• Status indicator review: every service health indicator / display / app status should be green.
• 24-hour soak: leave the device under normal load overnight; check the next morning.
• Telemetry check: review the device or app's diagnostic log for new error entries.

Escalation guide

For this device, the right escalation depends on impact:

• Cosmetic / minor: log a ticket via the How app or web portal. Response 1-3 business days.
• Mid-impact: phone support. Have your serial number ready.
• Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
• Out of support coverage: third-party repair shop with manufacturer-certified technicians.

More frequently asked questions

Will the procedure work on the international variant?

Some features and service version paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.

How long does this fix usually take?

Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a tenant reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major service version generations sometimes shift the menu path; the option is usually under a similarly-named section.

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

Field notes from real Microsoft 365 Admin incidents

When I work on add custom domain to Microsoft 365 and verify TXT on Defender XDR the rhythm I lean on is the one I have built over years of these tickets. Microsoft Graph PowerShell is the tool I now reach for over the legacy MSOnline module, because the legacy module's deprecation timeline is finally serious. Service Health is the first tab I open before I touch a single setting; half the M365 tickets I work on resolve themselves once I confirm Microsoft has already flagged the incident. Message Trace gives the truth that the user's Sent folder cannot. if a mail did not leave the org, it will say so in plain English.

Tools I actually reach for

For add custom domain to Microsoft 365 and verify TXT on Defender XDR on Defender XDR the cheapest signal I can land usually comes from Exchange Online PowerShell, then Office 365 SaRA tool, Microsoft Graph PowerShell SDK, Message Trace when Exchange Online PowerShell cannot see the layer the fault sits in, and Microsoft 365 admin center for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.

Verification I run before I close the ticket

Before I mark add custom domain to Microsoft 365 and verify TXT on Defender XDR resolved on a Defender XDR unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.

Get-MgServicePrincipal -Filter "displayName eq 'Office 365 Management APIs'"

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Connect-MgGraph -Scopes 'Directory.Read.All'; Get-MgUser -Top 5

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

az ad signed-in-user show  # for cross-check against Entra

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Microsoft 365 Admin detail, the disambiguation order I lean on is stable. I usually start at status.office.com for the ground-truth view on Microsoft 365 Admin. I usually start at admin.microsoft.com for the ground-truth view on Microsoft 365 Admin. I usually start at learn.microsoft.com/microsoft-365 for the ground-truth view on Microsoft 365 Admin. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on add custom domain to Microsoft 365 and verify TXT on Defender XDR have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Defender XDR unit, not things I read about. Service Health is the first tab I open before I touch a single setting; half the M365 tickets I work on resolve themselves once I confirm Microsoft has already flagged the incident. Microsoft Graph PowerShell is the tool I now reach for over the legacy MSOnline module, because the legacy module's deprecation timeline is finally serious. Message Trace gives the truth that the user's Sent folder cannot, if a mail did not leave the org, it will say so in plain English. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand add custom domain to Microsoft 365 and verify TXT on Defender XDR off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Defender XDR on the Microsoft 365 Admin family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For add custom domain to Microsoft 365 and verify TXT on Defender XDR on a Defender XDR unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.