Access to this page requires authorization. You can try signing in or changing directories . Access to this page requires authorization. You can try changing directories . Microsoft 365 requires connectivity to the Internet. The endpoints in this article should be reachable for customers using Microsoft 365 plans, including Government Community Cloud (GCC). Microsoft 365 Worldwide (+GCC) | Microsoft 365 operated by 21 Vianet | Microsoft 365 U.S. Government DoD | Microsoft 365 U.S. Government GCC High | Start with Managing Microsoft 365 endpoints to understand our recommendations for managing network connectivity using this data. Endpoints data is updated as needed at the beginning of each month with new IP Addresses and URLs published 30 days in advance of being active. This cadence allows for customers who don't yet have automated updates to complete their processes before new connectivity is required. Endpoints may also be updated during the month if needed to address support escalations, security incidents, or other immediate operational requirements. The data shown on this page below is all generated from the REST-based web services. If you're using a script or a network device to access this data, you should go to the Web service directly. Endpoint data below lists requirements for connectivity from a user's machine to Microsoft 365. For detail on IP addresses used for network connections from Microsoft into a customer network, sometimes called hybrid or inbound network connections, see other endpoints for more information. The endpoints are grouped into four service areas representing the three primary workloads and a set of common resources. The groups may be used to associate traffic flows with a particular application, however given that features often consume endpoints across multiple workloads, these groups can't effectively be used to restrict access. Data columns shown are: ID : The ID number of the row, also known as an endpoint set. This ID is the same as is returned by the web service for the endpoint set. ID : The ID number of the row, also known as an endpoint set. This ID is the same as is returned by the web service for the endpoint set. Category : Shows whether the endpoint set is categorized as Optimize , Allow , or Default . This column also lists which endpoint sets are required to have network connectivity. For endpoint sets that aren't required to have network connectivity, we provide notes in this field to indicate what functionality would be missing if the endpoint set is blocked. You can read about these categories and guidance for their management in Optimizing connectivity to Microsoft 365 services . Category : Shows whether the endpoint set is categorized as Optimize , Allow , or Default . This column also lists which endpoint sets are required to have network connectivity. For endpoint sets that aren't required to have network connectivity, we provide notes in this field to indicate what functionality would be missing if the endpoint set is blocked. You can read about these categories and guidance for their management in Optimizing connectivity to Microsoft 365 services . ER : This is Yes if the endpoint set is supported over Azure ExpressRoute with Microsoft 365 route prefixes. The BGP community that includes the route prefixes shown aligns with the service area listed. When ER is No , this means that ExpressRoute isn't supported for this endpoint set. Some routes may be advertised in more than one BGP community, making it possible for endpoints within a given IP range to traverse the ER circuit, but still be unsupported. In all cases, the value of a given endpoint set's ER column should be respected. ER : This is Yes if the endpoint set is supported over Azure ExpressRoute with Microsoft 365 route prefixes. The BGP community that includes the route prefixes shown aligns with the service area listed. When ER is No , this means that ExpressRoute isn't supported for this endpoint set. Some routes may be advertised in more than one BGP community, making it possible for endpoints within a given IP range to traverse the ER circuit, but still be unsupported. In all cases, the value of a given endpoint set's ER column should be respected. Addresses : Lists the FQDNs or wildcard domain names and IP address ranges for the endpoint set. Note that an IP address range is in CIDR format and may include many individual IP addresses in the specified network. Addresses : Lists the FQDNs or wildcard domain names and IP address ranges for the endpoint set. Note that an IP address range is in CIDR format and may include many individual IP addresses in the specified network. Ports : Lists the TCP or UDP ports that are combined with listed IP addresses to form the network endpoint. You may notice some duplication in IP address ranges where there are different ports listed. Ports : Lists the TCP or UDP ports that are combined with listed IP addresses to form the network endpoint. You may notice some duplication in IP address ranges where there are different ports listed. Microsoft 365 Unified Domains In response to customer feedback and to streamline endpoint management, Microsoft has initiated the process of consolidating Microsoft 365 apps and services into a select group of dedicated, secured, and purpose-managed domains within the .microsoft top level domain (TLD). To avoid connectivity issues for users, ensure that the following essential domains are included in your allowlist and that connectivity to these domains isn't blocked. Exchange Online SharePoint Online and OneDrive for Business Microsoft Teams Microsoft 365 Common and Office Online Notes for this table:

The Security and Compliance Center (SCC) provides support for Azure ExpressRoute for Microsoft 365. The same applies for many features exposed through the SCC such as Reporting, Auditing, eDiscovery (Premium), Unified DLP, and Data Governance. Two specific features, PST Import and eDiscovery Export, currently don't support Azure ExpressRoute with only Microsoft 365 route filters due to their dependency on Azure Blob Storage (*.blob.core.windows.net). To consume those features, you need separate connectivity to Azure Blob Storage using any supportable Azure connectivity options, which include Internet connectivity or Azure ExpressRoute with Azure Public route filters. You have to evaluate establishing such connectivity for both of those features. The Microsoft 365 Information Protection team is aware of this limitation and is actively working to bring support for Azure ExpressRoute for Microsoft 365 as limited to Microsoft 365 route filters for both of those features. Other endpoints not included in the Microsoft 365 IP Address and URL Web service Other endpoints not included in the Microsoft 365 IP Address and URL Web service Managing Microsoft 365 endpoints Managing Microsoft 365 endpoints General Microsoft Stream endpoints General Microsoft Stream endpoints Monitor Microsoft 365 connectivity Monitor Microsoft 365 connectivity Client connectivity Client connectivity Content delivery networks Content delivery networks Microsoft Azure IP Ranges and Service Tags - Public Cloud Microsoft Azure IP Ranges and Service Tags - Public Cloud Microsoft Azure IP Ranges and Service Tags - US Government Cloud Microsoft Azure IP Ranges and Service Tags - US Government Cloud Microsoft Azure IP Ranges and Service Tags - China Cloud Microsoft Azure IP Ranges and Service Tags - China Cloud Microsoft Public IP Space Microsoft Public IP Space Service Name and Transport Protocol Port Number Registry Service Name and Transport Protocol Port Number Registry Was this page helpful? Need help with this topic? Want to try using Ask Learn to clarify or guide you through this topic? Additional resources Last updated on 2026-08-14