Understanding Office 365 Endpoints: A Comprehensive Guide

The BGP community that includes route prefixes aligns with the service area listed for Office 365 endpoints. According to Microsoft, these categories and guidance for management can be found in New Office 365 endpoint categories.

One of the key features of Office 365 endpoints is their support for Azure ExpressRoute with Office 365 route prefixes. This means that certain endpoint sets are supported over this network connection. However, if you're excluding an entire service area, the endpoint sets listed as required do not require connectivity.

For endpoint sets that don't require network connectivity, Microsoft provides notes on what functionality would be missing if the endpoint set is blocked. The column also lists which endpoint sets are required to have network connectivity. Each ID is unique and can be returned by the web service for the endpoint set.

The endpoints in Office 365 are categorized into four service areas representing three primary workloads and a set of common resources. These groups may be used to associate traffic flows with a particular application, but they cannot effectively be used to restrict access due to features often consuming endpoints across multiple workloads.

For more information on IP addresses used for network connections from Microsoft into a customer network, also known as hybrid or inbound network connections, see Additional endpoints. If you're using a script or network device to access this data, it's recommended that you go directly to the Web service.

Endpoint Data: Requirements for Connectivity

The endpoint data below lists requirements for connectivity from a user's machine to Office 365. This data is generated from REST-based web services and may be updated during the month if needed to address support escalations, security incidents, or other immediate operational requirements.

This cadence allows customers who don't yet have automated updates to complete their processes before new connectivity is required. The endpoints are updated as needed at the beginning of each month with new IP addresses and URLs published 30 days in advance of being active.

For more information on managing network connectivity using this data, start with Managing Office 365 endpoints. This article provides recommendations for managing network connectivity using Office 365 endpoint data.

Office 365 Endpoints: A List of Required and Optional Destinations

Here is a list of all required and optional destinations in one JSON-formatted list:

* Government GCC High | Notes

* Office 365 Worldwide (+GCC)

* Office 365 operated by 21 Vianet

* Office 365 U.S.

The endpoints below should be reachable for customers using Office 365 plans, including Government Community Cloud (GCC). Office 365 requires connectivity to the Internet.

Office 365 10.13