Defender for Identity sensor

What a Microsoft Defender for Identity sensor on a domain controller or AD FS server needs to reach.

Server or agent · checked against its pages today 02:28 UTC · Defender

Where these entries come from

5 from 2 publisher pages

Microsoft Defender for Identity sensor v2.x prerequisites 1 section · 1 entry · read today 02:28 UTC
Connect to the Defender for Identity service 1 section · 4 entries · read today 02:28 UTC

Changes in the last 90 days

*.atp.azure.comadded to Required ports · TCP 443 · required · 12 Oct 23:22 UTC
*.atp.azure.comremoved from Required ports · required · 12 Oct 23:22 UTC

ChangeIntel reads each page once a day: the destinations in its tables, lists and code blocks, under the sections named above. Entries follow the page; nothing is added that it does not publish.

Downloads

Built from the pages and endpoint sets above, as last read

Format	Destinations	Left out	Download
Plain list, one per line	5	0	Open
GSA V1 domain list	3	2	Open
GSA V1 Graph request body	5	0	Download
GSA V2 rules (review JSON)	5	0	Download
GSA V2 rules (CSV)	5	0	Download

About these formats and checking them on a device

"Left out" counts entries a format cannot hold: IP ranges in web filtering, mid-name wildcards, URLs in a V1 domain list, and unfilled values. The V2 JSON is a review format; Microsoft publishes no Graph request shape for V2 rules yet. See how V1 and V2 evaluate.

The same entries are JSON at /api/v1/access-bundles/defender-for-identity. To check them from the workstation itself, run Test-ChangeIntelAccessBundle -Bundle defender-for-identity from the ChangeIntel PowerShell module there: it resolves DNS and tries TCP and TLS to each published host, and reports certificate issuers that suggest TLS inspection.

The profile each destination goes to is inferred from Microsoft's published material, not confirmed. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile.

Expected to reach web filtering

1expected to go through the Internet Access profile, where a block-by-default web filtering policy would have to allow the ones your scenario needs

Expected to reach web filtering
Destination	Why it's needed	Source
`*.atp.azure.com`TCP 443	Alternately, configure access through a proxy.	Microsoft Defender for Identity sensor v2.x prerequisites · Required ports Internet Access profile · indicated, not confirmed Not in the Microsoft 365 endpoint list the Microsoft traffic profile is built from, so it is expected to go through the Internet Access profile when that profile is on. Not confirmed: the Entra system profile's hosts aren't published.

Not determined

4public material doesn't settle it; check the client's forwarding profile

Not determined
Destination	Why it's needed	Source
`crl.microsoft.com`	Enable access to Defender for Identity service URLs in the proxy server	Connect to the Defender for Identity service · Enable access to Defender for Identity service URLs in the proxy server Profile not determined · possibly the Microsoft traffic profile In Microsoft 365 Common endpoint set 50 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes.
`ctldl.windowsupdate.com`	Enable access to Defender for Identity service URLs in the proxy server	Connect to the Defender for Identity service · Enable access to Defender for Identity service URLs in the proxy server Profile not determined · possibly the Microsoft traffic profile In Microsoft 365 Intune (MEM) endpoint set 164 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes.
`www.microsoft.com/pki/*`	Enable access to Defender for Identity service URLs in the proxy server	Connect to the Defender for Identity service · Enable access to Defender for Identity service URLs in the proxy server Profile not determined · possibly the Microsoft traffic profile In Microsoft 365 Common endpoint set 50 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes.
`www.microsoft.com/pkiops/*`	Enable access to Defender for Identity service URLs in the proxy server	Connect to the Defender for Identity service · Enable access to Defender for Identity service URLs in the proxy server Profile not determined · possibly the Microsoft traffic profile In Microsoft 365 Common endpoint set 50 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes.