Windows Update and Delivery Optimization
Windows Update, Delivery Optimization and Windows Autopatch for managed Windows devices.
Managed device · pages read today 18:37 UTC · Microsoft 365 endpoints version 2026103000, current since 30 Oct 2026 · Windows · Windows Autopatch
Where these entries come from
40 from 3 publisher pages · 2 from Microsoft 365 endpoint set 164- Microsoft Connected Cache content and services endpoints the whole page · 25 entries · read today 18:37 UTC
- Configure your network the whole page · 9 entries · read today 18:37 UTC
- Windows Update issues troubleshooting 2 sections · 8 entries · read today 18:37 UTC
Changes in the last 90 days
*.added to Microsoft Connected Cache content and services endpoints · Intune Win32 apps · TCP 80 · required · 12 Oct 23:22 UTCmanage. microsoft. com *.added to Microsoft Connected Cache content and services endpoints · Intune Win32 apps · TCP 443 · required · 12 Oct 23:22 UTCmanage. microsoft. com *.added to Microsoft Connected Cache content and services endpoints · New Outlook companion apps · TCP 80 · required · 12 Oct 23:22 UTCres. cdn. office. net *.added to Microsoft Connected Cache content and services endpoints · New Outlook companion apps · TCP 80 · required · 12 Oct 23:22 UTCstatic. microsoft *.added to Microsoft Connected Cache content and services endpoints · New Outlook companion apps · TCP 443 · required · 12 Oct 23:22 UTCres. cdn. office. net *.added to Microsoft Connected Cache content and services endpoints · New Outlook companion apps · TCP 443 · required · 12 Oct 23:22 UTCstatic. microsoft *.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80 · required · 12 Oct 23:22 UTCubuntu. com api.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80 · required · 12 Oct 23:22 UTCsnapcraft. io release-assets.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80 · required · 12 Oct 23:22 UTCgithubusercontent. com releases.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80 · required · 12 Oct 23:22 UTCgithubusercontent. com raw.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80 · required · 12 Oct 23:22 UTCgithub. com *.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 443 · required · 12 Oct 23:22 UTCubuntu. com api.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 443 · required · 12 Oct 23:22 UTCsnapcraft. io release-assets.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 443 · required · 12 Oct 23:22 UTCgithubusercontent. com releases.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 443 · required · 12 Oct 23:22 UTCgithubusercontent. com raw.added to Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 443 · required · 12 Oct 23:22 UTCgithub. com packages.added to Microsoft Connected Cache content and services endpoints · Microsoft package updates · TCP 80 · required · 12 Oct 23:22 UTCmicrosoft. com download.added to Microsoft Connected Cache content and services endpoints · Microsoft package updates · TCP 80 · required · 12 Oct 23:22 UTCmicrosoft. com packages.added to Microsoft Connected Cache content and services endpoints · Microsoft package updates · TCP 443 · required · 12 Oct 23:22 UTCmicrosoft. com download.added to Microsoft Connected Cache content and services endpoints · Microsoft package updates · TCP 443 · required · 12 Oct 23:22 UTCmicrosoft. com *.removed from Microsoft Connected Cache content and services endpoints · Intune Win32 apps · TCP 80, 443 · required · 12 Oct 23:22 UTCmanage. microsoft. com *.removed from Microsoft Connected Cache content and services endpoints · New Outlook companion apps · TCP 80, 443 · required · 12 Oct 23:22 UTCres. cdn. office. net *.removed from Microsoft Connected Cache content and services endpoints · New Outlook companion apps · TCP 80, 443 · required · 12 Oct 23:22 UTCstatic. microsoft *.removed from Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80, 443 · required · 12 Oct 23:22 UTCubuntu. com api.removed from Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80, 443 · required · 12 Oct 23:22 UTCsnapcraft. io release-assets.removed from Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80, 443 · required · 12 Oct 23:22 UTCgithubusercontent. com releases.removed from Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80, 443 · required · 12 Oct 23:22 UTCgithubusercontent. com raw.removed from Microsoft Connected Cache content and services endpoints · Windows Subsystem for Linux (WSL) · TCP 80, 443 · required · 12 Oct 23:22 UTCgithub. com packages.removed from Microsoft Connected Cache content and services endpoints · Microsoft package updates · TCP 80, 443 · required · 12 Oct 23:22 UTCmicrosoft. com download.removed from Microsoft Connected Cache content and services endpoints · Microsoft package updates · TCP 80, 443 · required · 12 Oct 23:22 UTCmicrosoft. com
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 | 42 | 0 | Open |
| GSA V1 domain list | 40 | 2 | Open |
| GSA V1 Graph request body | 41 | 1 | Download |
| GSA V2 rules (review JSON) | 41 | 1 | Download |
| GSA V2 rules (CSV) | 41 | 1 | 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/windows-update. To check them from the workstation itself, run Test-ChangeIntelAccessBundle -Bundle windows-update 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
12expected to go through the Internet Access profile, where a block-by-default web filtering policy would have to allow the ones your scenario needs
| Destination | Why it's needed | Source |
|---|---|---|
api.TCP 80TCP 443 |
Windows Subsystem for Linux (WSL) | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
*.TCP 443 |
IoT Edge / IoT Hub communication | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
*.TCP 443 |
IoT Edge / IoT Hub communication | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
*.TCP 443 |
IoT Edge / IoT Hub communication | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
*.TCP 443 |
IoT Edge / IoT Hub communication | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
microsoft.TCP 80 |
Signature validation | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
raw.TCP 80TCP 443 |
Windows Subsystem for Linux (WSL) | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
raw.TCP 443 |
Azure IoT Identity Service | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
release-assets.TCP 80TCP 443 |
Windows Subsystem for Linux (WSL) | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
releases.TCP 80TCP 443 |
Windows Subsystem for Linux (WSL) | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
*.TCP 80TCP 443 |
Windows Subsystem for Linux (WSL) | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
*.TCP 80 |
Xbox | Microsoft Connected Cache content and services endpointsInternet Access profile · indicated, not confirmedThe source publishes TCP HTTP/S ports 80 or 443 and the destination is absent from the Microsoft 365 endpoint list, so Internet Access web filtering is expected when the applicable client or remote-network profile acquires it. Tenant bypass rules and the actual forwarding profile remain authoritative. |
Not determined
29public material doesn't settle it; check the client's forwarding profile
| Destination | Why it's needed | Source |
|---|---|---|
adl.TCP 80, 443 |
No purpose given; Intune (MEM), Default category | Microsoft 365 endpoint set 164 (Worldwide, version 2026103000)Profile not determined · possibly the Microsoft traffic profileIn Microsoft 365 Teams / Skype endpoint set 19 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes. |
aka.TCP 443 |
Azure IoT Identity Service | Microsoft Connected Cache content and services endpointsProfile not determined · possibly the Microsoft traffic profileIn Microsoft 365 Teams / Skype endpoint set 17 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes. |
*.TCP 443 |
IoT Edge / IoT Hub communication | Microsoft Connected Cache content and services endpointsProfile not determinedBroader than the Microsoft 365 entries it includes (such as set 182): those parts are expected to go to a Microsoft profile and the rest to Internet Access. |
*.TCP 80 |
M365 app updates | Microsoft Connected Cache content and services endpointsProfile not determined · possibly the Microsoft traffic profileIn Microsoft 365 Common endpoint set 47 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes. |
*. |
Issues related to HTTP/Proxy; Device can't access update files | Windows Update issues troubleshooting · Issues related to HTTP/Proxy Windows Update issues troubleshooting · Device can't access update files Profile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
device. |
Windows Autopatch | Configure your network · Required Windows Autopatch endpoints for proxy and firewall rulesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
devicelistenerprod. |
Windows Autopatch devicelistenprod.eudb.microsoft.com for tenants with billing addresses in the EU Data Boundary | Configure your network · Required Windows Autopatch endpoints for proxy and firewall rulesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
devicelistenprod. |
Windows Autopatch devicelistenprod.eudb.microsoft.com for tenants with billing addresses in the EU Data Boundary | Configure your network · Required Windows Autopatch endpoints for proxy and firewall rulesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
*.TCP 80TCP 443TCP 80, 443 |
Windows Update Windows Defender Windows Drivers Windows Store; Edge Browser; Teams; Issues related to HTTP/Proxy; Device can't access update files; No purpose given; Intune (MEM), Default category | Microsoft Connected Cache content and services endpoints Windows Update issues troubleshooting · Issues related to HTTP/Proxy Windows Update issues troubleshooting · Device can't access update files Microsoft 365 endpoint set 164 (Worldwide, version 2026103000) Profile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
dl.TCP 80, 443 |
No purpose given; Intune (MEM), Default category | Microsoft 365 endpoint set 164 (Worldwide, version 2026103000)Profile not determined · possibly the Microsoft traffic profileIn 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. |
*.TCP 443TCP 80, 443 |
Delivery Optimization Service; No purpose given; Intune (MEM), Default category | Microsoft Connected Cache content and services endpoints Microsoft 365 endpoint set 164 (Worldwide, version 2026103000) Profile not determined · possibly the Microsoft traffic profileIn 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. |
download.TCP 80TCP 443 |
Microsoft package updates | Microsoft Connected Cache content and services endpointsProfile not determined · possibly the Microsoft traffic profileIn 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. |
*. |
Issues related to HTTP/Proxy | Windows Update issues troubleshooting · Issues related to HTTP/ProxyProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
emdl. |
Device can't access update files | Windows Update issues troubleshooting · Device can't access update filesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
login. |
Windows Autopatch | Configure your network · Required Windows Autopatch endpoints for proxy and firewall rulesProfile not determined · possibly the Microsoft Entra system profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
*.TCP 443 |
IoT Edge / IoT Hub communication | Microsoft Connected Cache content and services endpointsProfile not determined · possibly the Microsoft traffic profileIn 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. |
mmdcustomer. |
Windows Autopatch | Configure your network · Required Windows Autopatch endpoints for proxy and firewall rulesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
mmdls. |
Windows Autopatch | Configure your network · Required Windows Autopatch endpoints for proxy and firewall rulesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
*.TCP 80 |
M365 app updates | Microsoft Connected Cache content and services endpointsProfile not determined · possibly the Microsoft traffic profileIn 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. |
packages.TCP 80TCP 443 |
Microsoft package updates | Microsoft Connected Cache content and services endpointsProfile not determined · possibly the Microsoft traffic profileIn 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. |
payloadprod*. |
Windows Autopatch | Configure your network · Required Windows Autopatch endpoints for proxy and firewall rulesProfile not determined · possibly the Internet Access profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
*. |
Device can't access update files | Windows Update issues troubleshooting · Device can't access update filesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
*.TCP 80TCP 443 |
New Outlook companion apps | Microsoft Connected Cache content and services endpointsProfile not determined · possibly the Microsoft traffic profileIn Microsoft 365 Common endpoint set 47 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes. |
services. |
Windows Autopatch | Configure your network · Required Windows Autopatch endpoints for proxy and firewall rulesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
*.TCP 80TCP 443 |
M365 app updates; Teams; New Outlook companion apps | Microsoft Connected Cache content and services endpointsProfile not determined · possibly the Microsoft traffic profileIn Microsoft 365 Common endpoint set 193 (Default category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes. |
tsfe.TCP 80, 443 |
Device can't access update files; No purpose given; Intune (MEM), Default category | Windows Update issues troubleshooting · Device can't access update files Microsoft 365 endpoint set 164 (Worldwide, version 2026103000) Profile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
*.TCP 80, 443 |
Device can't access update files; No purpose given; Intune (MEM), Default category | Windows Update issues troubleshooting · Device can't access update files Microsoft 365 endpoint set 164 (Worldwide, version 2026103000) Profile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
*. |
Windows Autopatch | Configure your network · Required Windows Autopatch endpoints for proxy and firewall rulesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
*.TCP 80TCP 80, 443 |
Windows Update Windows Defender Windows Drivers Windows Store; Device can't access update files; No purpose given; Intune (MEM), Default category | Microsoft Connected Cache content and services endpoints Windows Update issues troubleshooting · Device can't access update files Microsoft 365 endpoint set 164 (Worldwide, version 2026103000) Profile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
Not expected to reach web filtering
1the cited routing or transport scope does not indicate HTTP/S web filtering; check each entry's explanation for a Microsoft profile, direct platform route or other transport
| Destination | Why it's needed | Source |
|---|---|---|
*.TCP 80TCP 443 |
Intune Win32 apps | Microsoft Connected Cache content and services endpointsMicrosoft traffic profile · indicated, not confirmedIn Microsoft 365 Intune (MEM) endpoint set 163 (Allow category). Microsoft documents that the Microsoft traffic profile is built from this list, combined by traffic category, but not which categories it includes. |