Microsoft Intune 网络终结点Network endpoints for Microsoft Intune

此页列出了 Intune 部署中代理设置所需的 IP 地址和端口设置。This page lists IP addresses and port settings needed for proxy settings in your Intune deployments.

作为仅限云的服务,Intune 不需要诸如服务器或网关的本地基础结构。As a cloud-only service, Intune doesn't require on-premises infrastructure such as servers or gateways.

受管理设备的访问权限Access for managed devices

若要管理防火墙和代理服务器后面的设备,必须启用 Intune 的通信。To manage devices behind firewalls and proxy servers, you must enable communication for Intune.

备注

本节中的信息也适用于 Microsoft Intune 证书连接器。The information in section also applies to the Microsoft Intune Certificate Connector. 连接器的网络要求与托管设备相同。The connector has the same network requirements as managed devices.

  • 由于 Intune 客户端使用 HTTP (80)HTTPS (443) ,因此代理服务器必须支持这两种协议。The proxy server must support both HTTP (80) and HTTPS (443) because Intune clients use both protocols. Windows 信息保护使用端口 444。Windows Information Protection uses port 444.
  • 对于某些任务(例如下载经典电脑代理的软件更新),Intune 需要对 manage.microsoft.com 的未经身份验证的代理服务器访问权限For some tasks (like downloading software updates for the classic pc agent), Intune requires unauthenticated proxy server access to manage.microsoft.com

可以修改单个客户端计算机上的代理服务器设置。You can modify proxy server settings on individual client computers. 还可以使用“组策略”设置来更改位于指定代理服务器后面的所有客户端计算机的设置。You can also use Group Policy settings to change settings for all client computers located behind a specified proxy server.

托管的设备需要允许“所有用户”通过防火墙访问服务的配置。Managed devices require configurations that let All Users access services through firewalls.

下表列出了 Intune 客户端访问的端口和服务:The following tables list the ports and services that the Intune client accesses:

Domains IP 地址IP address
login.microsoftonline.comlogin.microsoftonline.com
*.officeconfig.msocdn.com*.officeconfig.msocdn.com
config.office.comconfig.office.com
graph.windows.netgraph.windows.net
enterpriseregistration。windows。netenterpriseregistration.windows.net
详细信息 Office 365 URL 和 IP 地址范围More information Office 365 URLs and IP address ranges
portal.manage.microsoft.comportal.manage.microsoft.com
m.manage.microsoft.comm.manage.microsoft.com
52.175.12.20952.175.12.209
20.188.107.22820.188.107.228
52.138.193.14952.138.193.149
51.144.161.18751.144.161.187
52.160.70.2052.160.70.20
52.168.54.6452.168.54.64
13.72.226.20213.72.226.202
52.189.220.23252.189.220.232
sts.manage.microsoft.comsts.manage.microsoft.com 13.93.223.24113.93.223.241
52.170.32.18252.170.32.182
52.164.224.15952.164.224.159
52.174.178.452.174.178.4
13.75.122.14313.75.122.143
52.163.120.8452.163.120.84
13.73.112.12213.73.112.122
52.237.192.11252.237.192.112
portal.fei.msua01.manage.microsoft.comportal.fei.msua01.manage.microsoft.com
m.fei.msua01.manage.microsoft.comm.fei.msua01.manage.microsoft.com
portal.fei.amsua0102.manage.microsoft.comportal.fei.amsua0102.manage.microsoft.com
m.fei.amsua0102.manage.microsoft.comm.fei.amsua0102.manage.microsoft.com
portal.fei.msua02.manage.microsoft.comportal.fei.msua02.manage.microsoft.com
m.fei.msua02.manage.microsoft.comm.fei.msua02.manage.microsoft.com
portal.fei.msua04.manage.microsoft.comportal.fei.msua04.manage.microsoft.com
m.fei.msua04.manage.microsoft.comm.fei.msua04.manage.microsoft.com
portal.fei.msua05.manage.microsoft.comportal.fei.msua05.manage.microsoft.com
m.fei.msua05.manage.microsoft.comm.fei.msua05.manage.microsoft.com
portal.fei.amsua0502.manage.microsoft.comportal.fei.amsua0502.manage.microsoft.com
m.fei.amsua0502.manage.microsoft.comm.fei.amsua0502.manage.microsoft.com
portal.fei.msua06.manage.microsoft.comportal.fei.msua06.manage.microsoft.com
m.fei.msua06.manage.microsoft.comm.fei.msua06.manage.microsoft.com
portal.fei.amsua0602.manage.microsoft.comportal.fei.amsua0602.manage.microsoft.com
m.fei.amsua0602.manage.microsoft.comm.fei.amsua0602.manage.microsoft.com
fei.amsua0202.manage.microsoft.comfei.amsua0202.manage.microsoft.com
portal.fei.amsua0202.manage.microsoft.comportal.fei.amsua0202.manage.microsoft.com
m.fei.amsua0202.manage.microsoft.comm.fei.amsua0202.manage.microsoft.com
portal.fei.amsua0402.manage.microsoft.comportal.fei.amsua0402.manage.microsoft.com
m.fei.amsua0402.manage.microsoft.comm.fei.amsua0402.manage.microsoft.com
portal.fei.msua07.manage.microsoft.comportal.fei.msua07.manage.microsoft.com
portal.fei.amsua0702.manage.microsoft.comportal.fei.amsua0702.manage.microsoft.com
portal.fei.amsua0801.manage.microsoft.comportal.fei.amsua0801.manage.microsoft.com
portal.fei.msua08.manage.microsoft.comportal.fei.msua08.manage.microsoft.com
m.fei.msua07.manage.microsoft.comm.fei.msua07.manage.microsoft.com
m.fei.amsua0702.manage.microsoft.comm.fei.amsua0702.manage.microsoft.com
m.fei.msua08.manage.microsoft.comm.fei.msua08.manage.microsoft.com
m.fei.amsua0801.manage.microsoft.comm.fei.amsua0801.manage.microsoft.com
52.160.70.2052.160.70.20
52.168.54.6452.168.54.64
portal.fei.msub01.manage.microsoft.comportal.fei.msub01.manage.microsoft.com
m.fei.msub01.manage.microsoft.comm.fei.msub01.manage.microsoft.com
portal.fei.amsub0102.manage.microsoft.comportal.fei.amsub0102.manage.microsoft.com
m.fei.amsub0102.manage.microsoft.comm.fei.amsub0102.manage.microsoft.com
portal.fei.msub02.manage.microsoft.comportal.fei.msub02.manage.microsoft.com
m.fei.msub02.manage.microsoft.comm.fei.msub02.manage.microsoft.com
portal.fei.msub03.manage.microsoft.comportal.fei.msub03.manage.microsoft.com
m.fei.msub03.manage.microsoft.comm.fei.msub03.manage.microsoft.com
portal.fei.msub05.manage.microsoft.comportal.fei.msub05.manage.microsoft.com
m.fei.msub05.manage.microsoft.comm.fei.msub05.manage.microsoft.com
portal.fei.amsub0202.manage.microsoft.comportal.fei.amsub0202.manage.microsoft.com
m.fei.amsub0202.manage.microsoft.comm.fei.amsub0202.manage.microsoft.com
portal.fei.amsub0302.manage.microsoft.comportal.fei.amsub0302.manage.microsoft.com
m.fei.amsub0302.manage.microsoft.comm.fei.amsub0302.manage.microsoft.com
portal.fei.amsub0502.manage.microsoft.comportal.fei.amsub0502.manage.microsoft.com
m.fei.amsub0502.manage.microsoft.comm.fei.amsub0502.manage.microsoft.com
portal.fei.amsub0601.manage.microsoft.comportal.fei.amsub0601.manage.microsoft.com
m.fei.amsub0601.manage.microsoft.comm.fei.amsub0601.manage.microsoft.com
52.138.193.14952.138.193.149
51.144.161.18751.144.161.187
portal.fei.msuc01.manage.microsoft.comportal.fei.msuc01.manage.microsoft.com
m.fei.msuc01.manage.microsoft.comm.fei.msuc01.manage.microsoft.com
portal.fei.msuc02.manage.microsoft.comportal.fei.msuc02.manage.microsoft.com
m.fei.msuc02.manage.microsoft.comm.fei.msuc02.manage.microsoft.com
portal.fei.msuc03.manage.microsoft.comportal.fei.msuc03.manage.microsoft.com
m.fei.msuc03.manage.microsoft.comm.fei.msuc03.manage.microsoft.com
portal.fei.msuc05.manage.microsoft.comportal.fei.msuc05.manage.microsoft.com
m.fei.msuc05.manage.microsoft.comm.fei.msuc05.manage.microsoft.com
52.175.12.20952.175.12.209
20.188.107.22820.188.107.228
portal.fei.amsud0101.manage.microsoft.comportal.fei.amsud0101.manage.microsoft.com
m.fei.amsud0101.manage.microsoft.comm.fei.amsud0101.manage.microsoft.com
13.72.226.20213.72.226.202
fef.msuc03.manage.microsoft.comfef.msuc03.manage.microsoft.com 23.101.0.10023.101.0.100
Admin.manage.microsoft.comAdmin.manage.microsoft.com 52.224.221.22752.224.221.227
52.161.162.11752.161.162.117
52.178.44.19552.178.44.195
52.138.206.5652.138.206.56
52.230.21.20852.230.21.208
13.75.125.1013.75.125.10
wip.mam.manage.microsoft.comwip.mam.manage.microsoft.com 52.187.76.8452.187.76.84
13.76.5.12113.76.5.121
52.165.160.23752.165.160.237
40.86.82.16340.86.82.163
52.233.168.14252.233.168.142
168.63.101.57168.63.101.57
52.187.196.9852.187.196.98
52.237.196.5152.237.196.51
mam.manage.microsoft.commam.manage.microsoft.com 104.40.69.125104.40.69.125
13.90.192.7813.90.192.78
40.85.174.17740.85.174.177
40.85.77.3140.85.77.31
137.116.229.43137.116.229.43
52.163.215.23252.163.215.232
52.174.102.18052.174.102.180
52.187.196.17352.187.196.173
52.156.162.4852.156.162.48
*.manage.microsoft.com*.manage.microsoft.com 13.67.13.176/2813.67.13.176/28
13.69.231.128/2813.69.231.128/28
13.69.67.224/2813.69.67.224/28
13.70.78.128/2813.70.78.128/28
13.71.199.64/2813.71.199.64/28
13.73.244.48/2813.73.244.48/28
13.75.39.208/2813.75.39.208/28
13.77.53.176/2813.77.53.176/28
13.86.221.176/2813.86.221.176/28
13.89.174.240/2813.89.174.240/28
13.89.175.192/2813.89.175.192/28
40.82.248.224/2840.82.248.224/28
20.189.105.0/2420.189.105.0/24
20.37.153.0/2420.37.153.0/24
20.37.192.128/2520.37.192.128/25
20.38.81.0/2420.38.81.0/24
20.41.1.0/2420.41.1.0/24
20.42.1.0/2420.42.1.0/24
20.42.130.0/2420.42.130.0/24
20.42.224.128/2520.42.224.128/25
20.43.129.0/2420.43.129.0/24
40.70.151.32/2840.70.151.32/28
40.71.14.96/2840.71.14.96/28
40.119.8.128/2540.119.8.128/25
40.74.25.0/2440.74.25.0/24
40.82.249.128/2540.82.249.128/25
40.80.184.128/2540.80.184.128/25
52.150.137.0/2552.150.137.0/25
52.162.111.96/2852.162.111.96/28

PowerShell 脚本和 Win32 应用的网络要求Network requirements for PowerShell scripts and Win32 apps

如果使用 Intune 部署 PowerShell 脚本或 Win32 应用,还需要授予对租户当前所在的终结点的访问权限。If you're using Intune to deploy PowerShell scripts or Win32 apps, you'll also need to grant access to endpoints in which your tenant currently resides.

若要查找租户位置(或 Azure 缩放单位 (ASU)),请登录 Microsoft Endpoint Manager 管理中心,选择“租户管理” > “租户详细信息” 。To find your tenant location (or Azure Scale Unit (ASU)), sign in to the Microsoft Endpoint Manager admin center, choose Tenant administration > Tenant details. 该位置位于“租户位置”下,例如“北美 0501”或“欧洲 0202”。The location is under Tenant location as something like North America 0501 or Europe 0202. 在下表中查找匹配的数字。Look for the matching number in the following table. 该行会告诉你要向其授予访问权限的存储名称和 CDN 终结点。That row will tell you which storage name and CDN endpoints to grant access to. 行由地理区域进行区分,如名称中的前两个字母(na = 北美,eu = 欧洲,ap = 亚太)所示。The rows are differentiated by geographic region, as indicated by the first two letters in the names (na = North America, eu = Europe, ap = Asia Pacific). 尽管你的组织的实际地理位置可能在其他地方,但租户位置将是这三个区域之一。Your tenant location will be one of these three regions although your organization’s actual geographic location might be elsewhere.

Azure 缩放单元 (ASU)Azure Scale Unit (ASU) 存储名称Storage name CDNCDN
AMSUA0601AMSUA0601
AMSUA0602AMSUA0602
AMSUA0101AMSUA0101
AMSUA0102AMSUA0102
AMSUA0201AMSUA0201
AMSUA0202AMSUA0202
AMSUA0401AMSUA0401
AMSUA0402AMSUA0402
AMSUA0501AMSUA0501
AMSUA0502AMSUA0502
AMSUA0701AMSUA0701
AMSUA0702AMSUA0702
AMSUA0801AMSUA0801
naprodimedataprinaprodimedatapri
naprodimedatasecnaprodimedatasec
naprodimedatahotfixnaprodimedatahotfix
naprodimedatapri.azureedge.netnaprodimedatapri.azureedge.net
naprodimedatasec.azureedge.netnaprodimedatasec.azureedge.net
naprodimedatahotfix.azureedge.netnaprodimedatahotfix.azureedge.net
AMSUB0101AMSUB0101
AMSUB0102AMSUB0102
AMSUB0201AMSUB0201
AMSUB0202AMSUB0202
AMSUB0301AMSUB0301
AMSUB0302AMSUB0302
AMSUB0501AMSUB0501
AMSUB0502AMSUB0502
AMSUB0601AMSUB0601
euprodimedataprieuprodimedatapri
euprodimedataseceuprodimedatasec
euprodimedatahotfixeuprodimedatahotfix
euprodimedatapri.azureedge.neteuprodimedatapri.azureedge.net
euprodimedatasec.azureedge.neteuprodimedatasec.azureedge.net
euprodimedatahotfix.azureedge.neteuprodimedatahotfix.azureedge.net
AMSUC0101AMSUC0101
AMSUC0201AMSUC0201
AMSUC0301AMSUC0301
AMSUC0501AMSUC0501
AMSUD0101AMSUD0101
approdimedatapriapprodimedatapri
approdimedatasecapprodimedatasec
approdimedatahotifxapprodimedatahotifx
approdimedatapri.azureedge.netapprodimedatapri.azureedge.net
approdimedatasec.azureedge.netapprodimedatasec.azureedge.net
approdimedatahotfix.azureedge.netapprodimedatahotfix.azureedge.net

Windows 推送通知服务 (WNS)Windows Push Notification Services (WNS)

对于使用移动设备管理 (MDM) 管理的由 Intune 管理的 Windows 设备,设备操作和其他即时活动需要使用 Windows 推送通知服务 (WNS)。For Intune-managed Windows devices managed using Mobile Device Management (MDM), device actions and other immediate activities require the use of Windows Push Notification Services (WNS). 有关详细信息,请参阅允许 Windows 通知流量通过企业防火墙For more information, see Allowing Windows Notification traffic through enterprise firewalls.

传递优化端口要求Delivery Optimization port requirements

端口要求Port requirements

对于对等流量,传递优化将 7680 用于 TCP/IP,或将 3544 用于 NAT 遍历(也可以是 Teredo)。For peer-to-peer traffic, Delivery Optimization uses 7680 for TCP/IP or 3544 for NAT traversal (optionally Teredo). 对于客户端-服务通信,它通过端口 80/443 使用 HTTP 或 HTTPS。For client-service communication, it uses HTTP or HTTPS over port 80/443.

代理要求Proxy requirements

若要使用传递优化,必须允许“字节范围”请求。To use Delivery Optimization, you must allow Byte Range requests. 有关详细信息,请参阅 Windows 更新的代理要求For more information, see Proxy requirements for Windows Update.

防火墙要求Firewall requirements

允许下列主机名通过防火墙,以支持传递优化。Allow the following hostnames through your firewall to support Delivery Optimization. 对于客户端与传递优化云服务之间的通信:For communication between clients and the Delivery Optimization cloud service:

  • *.do.dsp.mp.microsoft.com*.do.dsp.mp.microsoft.com

对于传递优化元数据:For Delivery Optimization metadata:

  • *.dl.delivery.mp.microsoft.com*.dl.delivery.mp.microsoft.com
  • *.emdl.ws.microsoft.com*.emdl.ws.microsoft.com

Apple 设备网络信息Apple device network information

用途Used for 主机名(IP 地址/子网)Hostname (IP address/subnet) 协议Protocol PortPort
检索并显示 Apple 服务器的内容Retrieving and displaying content from Apple servers itunes.apple.comitunes.apple.com
*.itunes.apple.com*.itunes.apple.com
*.mzstatic.com*.mzstatic.com
*.phobos.apple.com*.phobos.apple.com
*.phobos.itunes-apple.com.akadns.net*.phobos.itunes-apple.com.akadns.net
HTTPHTTP 8080
与 APNS 服务器之间的通信Communications with APNS servers #-courier.push.apple.com#-courier.push.apple.com
“#”是 0 到 50 范围内的一个随机数字。'#' is a random number from 0 to 50.
TCPTCP 5223 和 4435223 and 443
各种功能,包括访问万维网、iTunes 商店、macOS 应用商店、iCloud、消息等。Various functionalities including accessing the World Wide Web, iTunes store, macOS app store, iCloud, messaging, etc. phobos.apple.comphobos.apple.com
ocsp.apple.comocsp.apple.com
ax.itunes.apple.comax.itunes.apple.com
ax.itunes.apple.com.edgesuite.netax.itunes.apple.com.edgesuite.net
HTTP/HTTPSHTTP/HTTPS 80 或 44380 or 443

有关详细信息,请参阅 Apple 的 Apple 软件产品使用的 TCP 和 UDP 端口关于 macOS、iOS/iPadOS 和 iTunes 服务器主机连接和 iTunes 后台进程,以及如果你的 macOS 和 iOS/iPadOS 客户端不获取 Apple 推送通知For more information, see Apple's TCP and UDP ports used by Apple software products, About macOS, iOS/iPadOS, and iTunes server host connections and iTunes background processes, and If your macOS and iOS/iPadOS clients aren't getting Apple push notifications.

Android 端口信息Android port information

根据选择的 Android 设备管理方式,你可能需要打开 Google Android Enterprise 端口和/或 Android 推送通知。Depending on how you choose to manage Android devices, you may need to open the Google Android Enterprise ports and/or the Android push notification. 有关支持的 Android 管理方法的更多信息,请参阅 Android 注册文档For more information on Android management methods supported, see the Android enrollment documentation.

备注

由于 Google 移动服务在中国不可用,因此在中国由 Intune 管理的设备无法使用需要 Google 移动服务的功能。Because Google Mobile Services isn't available in China, devices in China managed by Intune can't use features that require Google Mobile Services. 这些功能包括:Google Play 保护机制功能,如 SafetyNet 设备证明、管理 Google Play 商店的应用、Android Enterprise 功能(请参阅 Google 文档)。These features include: Google Play Protect capabilities such as SafetyNet device attestation, Managing apps from the Google Play Store, Android Enterprise capabilities (see this Google documentation). 此外,Android 版 Intune 公司门户应用使用 Google 移动服务与 Microsoft Intune 服务进行通信。Additionally, the Intune Company Portal app for Android uses Google Mobile Services to communicate with the Microsoft Intune service. 由于 Google Play 服务在中国不可用,因此某些任务最长可能需要 8 小时才能完成。Because Google Play services isn't available in China, some tasks can require up to 8 hours to finish. 有关详细信息,请参阅此文章For more information, see this article.

Google Android EnterpriseGoogle Android Enterprise

Google 针对其 Android Enterprise 蓝皮书的“防火墙”部分中所述的所需网络端口和目标主机名提供了相关文档。Google provides documentation of required network ports and destination host names in their Android Enterprise Bluebook, under the Firewall section of that document.

Android 推送通知Android push notification

Intune 利用 Google Firebase 云消息传递 (FCM),让推送通知来触发设备操作和签入。Android 设备管理员和 Android Enterprise 都要求采用这种机制。Intune leverages Google Firebase Cloud Messaging (FCM) for push notification to trigger device actions and check-ins. This is required by both Android Device Administrator and Android Enterprise. 有关 FCM 网络要求的信息,请参阅 Google 的 FCM 端口和防火墙For information on FCM network requirements, see Google's FCM ports and your firewall.

终结点分析Endpoint analytics

有关终结点分析所需终结点的详细信息,请参阅终结点分析代理配置For more information on the required endpoints for endpoint analytics, see Endpoint analytics proxy configuration.