Microsoft Intune Managed devices | *.manage.microsoft.commanage.microsoft.com*.dm.microsoft.comEnterpriseEnrollment.manage.microsoft.com
| TCP 80, 443 | Outbound | Intune client and host service (endpoint set 163, required). SSL inspection isn't supported for *.manage.microsoft.com or *.dm.microsoft.com. If your firewall can't use domain names, Microsoft publishes the subnet list on the same page. | Microsoft Learn: Network endpoints for Microsoft Intune |
Microsoft Intune Managed Windows devices | mmcswdc01.blob.core.windows.netmmcswdc02.blob.core.windows.netswda01-mscdn.manage.microsoft.comswda02-mscdn.manage.microsoft.comswdb01-mscdn.manage.microsoft.comswdb02-mscdn.manage.microsoft.comswdc01-mscdn.manage.microsoft.comswdc02-mscdn.manage.microsoft.comswdd01-mscdn.manage.microsoft.comswdd02-mscdn.manage.microsoft.comswdin01-mscdn.manage.microsoft.comswdin02-mscdn.manage.microsoft.com
| TCP 80, 443 | Outbound | Win32 app content (endpoint set 170, required). | Microsoft Learn: Network endpoints for Microsoft Intune |
Microsoft Intune Managed Windows devices (tenant in North America) | imeswda-afd-primary.manage.microsoft.comimeswda-afd-secondary.manage.microsoft.comimeswda-afd-hotfix.manage.microsoft.com
| TCP 443 | Outbound | Intune management extension: Win32 apps, PowerShell scripts, remediations, custom compliance. Allow HTTP partial responses. Use the row for your tenant location (Tenant administration > Tenant details). | Microsoft Learn: Network endpoints for Microsoft Intune |
Microsoft Intune Managed Windows devices (tenant in Europe) | imeswdb-afd-primary.manage.microsoft.comimeswdb-afd-secondary.manage.microsoft.comimeswdb-afd-hotfix.manage.microsoft.com
| TCP 443 | Outbound | Intune management extension: Win32 apps, PowerShell scripts, remediations, custom compliance. Allow HTTP partial responses. | Microsoft Learn: Network endpoints for Microsoft Intune |
Microsoft Intune Managed Windows devices (tenant in Asia Pacific) | imeswdc-afd-primary.manage.microsoft.comimeswdc-afd-secondary.manage.microsoft.comimeswdc-afd-hotfix.manage.microsoft.com
| TCP 443 | Outbound | Intune management extension: Win32 apps, PowerShell scripts, remediations, custom compliance. Allow HTTP partial responses. | Microsoft Learn: Network endpoints for Microsoft Intune |
Intune for macOS Managed Macs | macsidecar.manage.microsoft.commacsidecareu.manage.microsoft.commacsidecarap.manage.microsoft.com
| TCP 443 | Outbound | macOS app and script deployment CDN: macsidecar (North America), macsidecareu (Europe), macsidecarap (Asia Pacific). Only the host for your tenant's region is needed. | Microsoft Learn: Network endpoints for Microsoft Intune |
Microsoft Entra ID Managed devices | login.microsoftonline.comgraph.windows.net
| TCP 80, 443 | Outbound | Authentication and identity (endpoint set 56, required). | Microsoft Learn: Network endpoints for Microsoft Intune |
Microsoft Entra ID Managed devices | enterpriseregistration.windows.netcertauth.enterpriseregistration.windows.net
| TCP 80, 443 | Outbound | Identity supporting services and CDNs (endpoint set 59, required). | Microsoft Learn: Network endpoints for Microsoft Intune |
Windows Push Notification Services Managed Windows devices | *.notify.windows.com*.wns.windows.comsinwns1011421.wns.windows.comsin.notify.windows.com
| TCP 443 | Outbound | Push notifications for Intune device actions and immediate check-ins (endpoint set 171). Microsoft says WNS may not work through proxies; a direct connection is recommended. Allow by FQDN rather than IP range. | Microsoft Learn: Network endpoints for Microsoft Intune |
Windows Push Notification Services Windows devices receiving notifications | *.wns.windows.comlogin.microsoftonline.comlogin.live.com
| TCP 443 | Outbound | WNS client endpoints (ClientDNS) and the identity service hosts WNS lists. | Microsoft Learn: Allowing Windows Notification traffic through enterprise firewalls |
Delivery Optimization Windows devices | *.do.dsp.mp.microsoft.com*.dl.delivery.mp.microsoft.com
| TCP 80, 443 | Outbound | Delivery Optimization cloud service and metadata (endpoint set 172). Proxies must allow byte-range requests. | Microsoft Learn: Network endpoints for Microsoft Intune |
Delivery Optimization Windows devices (peers on your network) | Any (port-based) | TCP 7680 | Inbound and outbound | Peer-to-peer content sharing between devices. Only needed when peering is used. The service stops listening on 7680 when it's idle. | Microsoft Learn: Configure Delivery Optimization (ports) |
Delivery Optimization Windows devices | Any (port-based) | UDP 3544 | Inbound and outbound | Teredo NAT traversal to reach peers across NATs. Required for download mode Group (2) or Internet (3). | Microsoft Learn: Configure Delivery Optimization (ports) |
Windows Autopilot Devices running Autopilot | *.windowsupdate.com*.dl.delivery.mp.microsoft.com*.prod.do.dsp.mp.microsoft.com*.delivery.mp.microsoft.com*.update.microsoft.comtsfe.trafficshaping.dsp.mp.microsoft.comadl.windows.com
| TCP 80, 443 | Outbound | Windows Update during Autopilot (endpoint set 164). | Microsoft Learn: Network endpoints for Microsoft Intune |
Windows Autopilot Devices running Autopilot | | UDP 123 | Outbound | NTP time sync (endpoint set 165). | Microsoft Learn: Network endpoints for Microsoft Intune |
Windows Autopilot Devices running Autopilot | clientconfig.passport.netwindowsphone.com*.s-microsoft.comc.s-microsoft.com
| TCP 443 | Outbound | WNS dependencies for Autopilot (endpoint set 169). | Microsoft Learn: Network endpoints for Microsoft Intune |
Windows Autopilot Devices running Autopilot | ekop.intel.comekcert.spserv.microsoft.comftpm.amd.com
| TCP 443 | Outbound | Third-party deployment dependencies, including TPM attestation (endpoint set 173). | Microsoft Learn: Network endpoints for Microsoft Intune |
Apple Push Notification service Apple devices on all client networks | | TCP 5223, 443 | Outbound | Devices' persistent connection to APNs, which Apple MDM push notifications depend on. Microsoft lists 5223 and 443 to Apple's 17.0.0.0/8 block from all client networks, including redirects. Apple's archived TN2265 describes 443 as the fallback when a device can't reach APNs on 5223. Apple's current network articles on support.apple.com couldn't be retrieved for this dataset; check them before changing production rules. | Microsoft Learn: Manually configure Jamf Pro integration with Intune (network ports)Apple Developer (archived): TN2265 Troubleshooting Push Notifications |
Apple Push Notification service Push provider servers (an on-premises MDM or app server; not needed on devices) | api.push.apple.comapi.sandbox.push.apple.com
| TCP 443, 2197 | Outbound | HTTP/2 provider API. Port 2197 can replace 443 so you can allow APNs without allowing all HTTPS. Devices don't connect to these hosts; servers that send notifications do. Intune is cloud-only and needs no on-premises servers, so an Intune-only estate doesn't need this row. | Apple Developer: Sending notification requests to APNs |
Microsoft Entra Connect Microsoft Entra Connect server | Any (port-based) | TCP 443 | Outbound | Synchronise with Microsoft Entra ID. | Microsoft Learn: Hybrid identity required ports and protocols |
Microsoft Entra Connect Microsoft Entra Connect server | Any (port-based) | TCP 80 | Outbound | Download certificate revocation lists to verify TLS certificates. | Microsoft Learn: Hybrid identity required ports and protocols |
Microsoft Entra Connect Microsoft Entra Connect server to domain controllers | Any (port-based) | TCP 53, 88, 135, 389, 445, 636, 3268 | Outbound | DNS, Kerberos, MS-RPC, LDAP, SMB (Seamless SSO and password writeback), LDAP over TLS, and Global Catalog (Seamless SSO). Initial configuration and password synchronisation also use random high RPC ports 49152-65535. | Microsoft Learn: Hybrid identity required ports and protocols |
Microsoft Entra Connect Microsoft Entra Connect server to domain controllers | Any (port-based) | UDP 53, 88, 389 | Outbound | DNS, Kerberos and LDAP over UDP. | Microsoft Learn: Hybrid identity required ports and protocols |
Microsoft Entra Connect Server running the Microsoft Entra Connect Health agent | Any (port-based) | TCP 443 | Outbound | Send health data to Microsoft Entra ID. The latest agent versions only need 443. Older agents prefer TCP 5671 (Azure Service Bus) and fall back to 443. | Microsoft Learn: Hybrid identity required ports and protocols |