Azure Monitor Agent

The endpoints the Azure Monitor Agent sends configuration requests and data to; the region and workspace parts are placeholders.

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

Where these entries come from

11 from 1 publisher page

Azure Monitor Agent network configuration 1 section · 11 entries · read today 02:28 UTC

Changes in the last 90 days

None of these pages added or removed a destination in the sections this bundle reads.

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

Entries with {virtualmachineregionname}, {loganalyticsworkspaceid}, {datacollectionendpoint} are left out of downloads until you fill in your value.

Format	Destinations	Left out	Download
Plain list, one per line	7	4	Open
GSA V1 domain list	7	4	Open
GSA V1 Graph request body	7	4	Download
GSA V2 rules (review JSON)	7	4	Download
GSA V2 rules (CSV)	7	4	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/azure-monitor-agent. To check them from the workstation itself, run Test-ChangeIntelAccessBundle -Bundle azure-monitor-agent -Value @{ virtualmachineregionname = '...'; loganalyticsworkspaceid = '...'; datacollectionendpoint = '...' } 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

6expected 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
`a0a0a0a0-bbbb-cccc-dddd-e1e1e1e1e1e1.ods.opinsights.azure.com`	Ingest log data	Azure Monitor Agent network configuration · Firewall endpoints 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.
`global.prod.microsoftmetrics.com`	Access the metrics service	Azure Monitor Agent network configuration · Firewall endpoints 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.
`management.azure.com`	Needed only if you send time series data (metrics) to an Azure Monitor custom metrics database	Azure Monitor Agent network configuration · Firewall endpoints 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.
`westus2.monitoring.azure.com`	Needed only if you send time series data (metrics) to an Azure Monitor custom metrics database	Azure Monitor Agent network configuration · Firewall endpoints 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.
`{loganalyticsworkspaceid}.ods.opinsights.azure.com`	Ingest log data	Azure Monitor Agent network configuration · Firewall endpoints 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.
`{virtualmachineregionname}.monitoring.azure.com`	Needed only if you send time series data (metrics) to an Azure Monitor custom metrics database	Azure Monitor Agent network configuration · Firewall endpoints 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

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

Not determined
Destination	Why it's needed	Source
`global.handler.control.monitor.azure.com`	Access the control service	Azure Monitor Agent network configuration · Firewall endpoints Profile not determined · possibly the Microsoft traffic profile In Microsoft 365 Intune (MEM) endpoint set 181 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes.
`my-dce-5kyl.eastus-1.ingest.monitor.azure.com`	Ingest log data	Azure Monitor Agent network configuration · Firewall endpoints Profile not determined · possibly the Microsoft traffic profile In Microsoft 365 Intune (MEM) endpoint set 181 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes.
`westus2.handler.control.monitor.azure.com`	Fetch DCRs for a specific machine	Azure Monitor Agent network configuration · Firewall endpoints Profile not determined · possibly the Microsoft traffic profile In Microsoft 365 Intune (MEM) endpoint set 181 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes.
`{datacollectionendpoint}.{virtualmachineregionname}.ingest.monitor.azure.com`	Ingest log data	Azure Monitor Agent network configuration · Firewall endpoints Profile not determined · possibly the Microsoft traffic profile In Microsoft 365 Intune (MEM) endpoint set 181 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes.
`{virtualmachineregionname}.handler.control.monitor.azure.com`	Fetch DCRs for a specific machine	Azure Monitor Agent network configuration · Firewall endpoints Profile not determined · possibly the Microsoft traffic profile In Microsoft 365 Intune (MEM) endpoint set 181 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes.