Office 365 URLs and IP address ranges
Summary : If your organization uses Office 365 and restricts computers on your network from connecting to the Internet, below you'll find the endpoints (FQDNs, Ports, URLs, IPv4, and IPv6 address ranges) that you should include in your outbound allow lists to ensure your computers can successfully use Office 365.
Office 365 endpoints: Worldwide | Office 365 operated by 21 Vianet | US Government Defense | Office 365 Germany
Last updated: 1/31/2017 - See what changed
Subscribe via RSS
to receive notice when endpoints are changed.
Tips: Use the endpoints here alongside our standard Office 365 plans including; US Government, education, non-profit, and commercial plans hosted in our worldwide or local datacenters. If you're using a plan within the Office 365 operated by 21 Vianet, Office 365 US Government Defense, or Office 365 Germany endpoints offerings, please use the articles that cover those offerings.
Use the XML file to view a single list with all of the endpoints or to automatically process changes.
Office 365 requires internet connectivity from every computer connecting to the service.
If you're configuring access from your network to Office 365, managing Office 365 endpoints describes how to manage your firewall and proxy settings with scripts and sample PAC files.
If you're troubleshooting access to Office 365, troubleshooting Office 365 connectivity describes how to troubleshoot endpoints found in your network traces or firewall logs.
Content delivery networks and client connectivity offer more insight into how clients connect to Office 365 and how standard internet services are incorporated.
Warning: IP addresses filtering alone isn’t a complete solution due to dependencies on internet based services such as Domain Name Services, Content Delivery Networks (CDNs), Certificate Revocation Lists, and other third party or dynamic services. These dependencies include dependencies on other Microsoft services such as the Azure Content Delivery Network and will result in network traces or firewall logs indicating connections to IP addresses owned by third parties or Microsoft but not listed on this page. These unlisted IP addresses, whether from third party or Microsoft owned CDN and DNS services are dynamically assigned and can change at any time.
What's wrong with using IP filtering alone?
|
|
Tip: If IP address filtering is your only option at the firewall, an automatic proxy configuration file can be used to route the destinations marked below as CDNs through an alternate path, such as through an outbound proxy. See the Routing office 365 traffic over the internet and ExpressRoute scenario in the article Routing with ExpressRoute for Office 365 for help with more complex routing configurations.
Every Office 365 service requires the endpoints in the Office 365 portal and shared as well as the Office 365 authentication and identity to function. Beyond that you'll need to select the services you've deployed or plan to deploy in your organization and filter accordingly. If you've fully adopted all Office 365 services in your organization, the entries from every service section below are required. If not, use these links to get to just the services your organization has adopted. The FQDNs and IP addresses tables are collapsed to improve navigation, you'll need to expand the sections to see the tables. If you want to search for a specific endpoint, search the XML file for the current list of endpoints organized by service or the RSS feed to see a historical view including the dates when specific endpoints were added or removed.
How are changes to this page made and how can I be notified?
Changes for each Office 365 service are combined and published at the end of each month. Occasionally emergency changes will occur outside of the end of month publishing. Expect changes three business days prior to the last business day of the month. When an endpoint is added, an effective date is listed in the RSS feed. If you're new to RSS, here is how to subscribe via Outlook or you can have the RSS feed updates emailed to you.
Some of our services do overlap with one another and you will notice the overlap or duplication in the lists of endpoints. There is also some domain name overlapping with our consumer services; while the root domain name is the same, Office 365 operates from a separate sub-domain. If you’re going to add IP addresses to your allow lists, keep in mind that IPv6 is optional and not required. We provide it here for customers who wish to use IPv6.
How to use the ExpressRoute for Office 365 column
The endpoints listed as a Yes in the ExpressRoute for Office 365 column are available both over the internet and over ExpressRoute with Microsoft peering configured. Some services that Office 365 leverages are also available with Public peering configured and those are noted here; however, Public peering is not required to use ExpressRoute with Office 365 for the Office 365 applications supported over ExpressRoute.
Want to provide feedback about Office 365 endpoints?
There's a lot of information on this page, can we present it to you in a simpler way?
Please consider voicing your thoughts at the bottom of this page, under the heading Was this information helpful? Click yes or no and enter detailed feedback. The more feedback we get from you the easier it will be for us to improve the page.
Office 365 portal and shared
To use any Office 365 services, you must be able to connect to the endpoints marked required below. If your organization uses the Office 365 management pack, Cloud App Security, or the Security and Compliance export services, you'll find the associated endpoints below. All IP addresses entered directly in the Destination IP column are also listed in the IP tables and XML file for your convenience.
Expand to see the portal and shared FQDNs
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Office 365 Portal |
Client Computer | Logged on user |
*.office365.com |
No |
No4 |
TCP 443 |
|
|
2 |
Required: Office 365 Portal |
Client Computer | Logged on user |
home.office.com portal.office.com agent.office.net www.office.com outlook.office365.com signup.microsoft.com |
No |
Yes |
TCP 443 |
|
|
portal.microsoftonline.com |
No |
No |
TCP 443 |
||||
|
3 |
Required: CDNs used for portal and shared |
Client Computer | Logged on user |
prod.msocdn.com appsforoffice.microsoft.com Contentstorage.osi.office.net |
Microsoft and Akamai |
No |
N/A |
TCP 443 |
|
4 |
Required: Shared infrastructure |
Client Computer | Logged on user |
clientlog.portal.office.com nexus.officeapps.live.com nexusrules.officeapps.live.com |
Various |
No |
TCP 80 & 443 |
|
|
suite.office.net |
No |
Yes |
|
||||
|
account.office.net |
No |
Yes |
|
||||
|
5 |
Required: Certificate revocation lists |
Client Computer | Logged on user |
No |
No |
N/A |
TCP 80 & 443 |
|
|
6 |
Required: Some Office 365 features require endpoints within these domains. Note: Many specific FQDNs within these wildcards have been published recently as we work to either remove or better explain our guidance relating to wildcards. |
Client Computer | Logged on user |
*.onmicrosoft.com *.office.com *.office.net *.live.com |
No |
No4 |
N/A |
TCP 80 & 443 |
|
*.msedge.net |
No |
||||||
|
*.microsoft.com *.msocdn.com |
Various |
||||||
|
7 |
Optional: Shared help and support |
Client Computer | Logged on user |
support.office.com products.office.com templates.office.com contentstorage.osi.office.net technet.microsoft.com amp.azure.net assets.onestore.ms auth.gfx.ms browser.pip.aria.microsoft.com c.microsoft.com c1.microsoft.com connect.facebook.net dgps.support.microsoft.com mem.gfx.ms platform.linkedin.com support.content.office.net video.osi.office.net videocontent.osi.office.net videoplayercdn.osi.office.net |
Various |
No |
N/A |
TCP 80 & 443 |
|
8 |
Optional: Deprecated FQDNs |
Client Computer | Logged on user |
*.glbdns.microsoft.com |
No |
No |
N/A |
TCP 80 & 443 |
|
9 |
Optional: Microsoft Azure RemoteApp |
Client Computer | Logged on user |
dc.services.visualstudio.com liverdcxstorage.blob.core.windowsazure.com telemetry.remoteapp.windowsazure.com vortex.data.microsoft.com www.remoteapp.windowsazure.com |
No |
Varies3 |
N/A |
TCP 443 |
|
10 |
Customer Operations Manager environment | Machine1 Account |
office365servicehealthcommunications.cloudapp.net |
No |
Varies3 |
N/A |
TCP 443 |
|
|
11 |
Optional: Import Service for PST and file ingestion |
Refer to the Import Service for additional requirements. |
|||||
|
12 |
Optional: Cloud App Security |
Client Computer | Logged on user |
*.portal.cloudappsecurity.com |
No |
No |
|
TCP 443 |
|
13 |
Optional: Security and Compliance export |
Client Computer | Logged on user |
protection.office.com *.blob.core.windows.net office365zoom.cloudapp.net equivioprod*.cloudapp.net zoom-cs-prod*.cloudapp.net equivio.office.com compliance.outlook.com |
No |
Varies3 |
N/A |
TCP 443 |
|
14 |
Optional: Office 365 Management APIs |
Client Computer | Logged on user |
manage.office.com |
No |
No |
N/A |
TCP 443 |
|
15 |
Optional: Graph API (Graph.windows.net and Graph.Microsoft.com |
Client Computer | Logged on user |
graph.microsoft.com graph.windows.net |
No |
No |
N/A |
TCP 443 |
|
16 |
Optional: Discovery Service API |
Client Computer | Logged on user |
api.office.com |
No |
No |
N/A |
TCP 443 |
|
17 |
Optional: 3rd party office integration. |
Client Computer | Logged on user |
firstpartyapps.oaspapps.com prod.firstpartyapps.oaspapps.com.akadns.net telemetryservice.firstpartyapps.oaspapps.com wus-firstpartyapps.oaspapps.com |
Varies |
No |
N/A |
TCP 443 |
|
18 |
Optional: Microsoft Groups. |
Client Computer | Logged on user |
groupsapi-prod.outlookgroups.ms groupsapi2-prod.outlookgroups.ms groupsapi3-prod.outlookgroups.ms groupsapi4-prod.outlookgroups.ms |
Varies |
No |
N/A |
TCP 443 |
|
rink.hockeyapp.net sdk.hockeyapp.net api.localytics.com analytics.localytics.com outlook.uservoice.com |
|||||||
|
19 |
Optional: Required for Delve |
Client Computer | Logged on user |
delve.office.com apc.delve.office.com aus.delve.office.com can.delve.office.com eur.delve.office.com gbr.delve.office.com ind.delve.office.com jpn.delve.office.com lam.delve.office.com nam.delve.office.com |
No |
Yes |
|
TCP 80 & 443 |
|
20 |
Optional: Required for Delve |
Client Computer | Logged on user |
r3.res.outlook.com |
Akamai |
No |
N/A |
TCP 80 & 443 |
1Keep in mind that Machine accounts won’t work with proxies that require outbound authentication.
3 See additional information about supported services over Azure ExpressRoute and the Public peering path.
4 There are specific sub-FQDNs within this domain that are available on ExpressRoute, learn more by reading the section, Deciding which applications and features route over ExpressRoute.
Expand to see the portal and shared IP Addresses
Note: ExpressRoute for Office 365 currently does not support IPv6. Customers not using ExpressRoute will want to ensure both IP lists below are reachable over the internet.
|
Office 365 portal and shared IPv4 endpoints routable through the Internet and ExpressRoute |
Office 365 portal and shared IPv4 endpoints routable through the Internet only |
Office 365 portal and shared IPv6 endpoints routable through the Internet only |
Office 365 Certificate Revocation List (Root URLs) |
|
|
|
|
Expand to see Azure Rights Management (RMS)
The endpoints listed in this section are required if you're using Azure Rights Management.
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
||||||
|
2 |
Required: Portal and shared |
See Office 365 portal and shared including the well known certificate root CRLs. |
|||||
|
4 |
Required: Azure Rights Management (RMS) |
Client Computer | Logged on user |
*.aadrm.com *.azurerms.com ecn.dev.virtualearth.net |
No |
No |
N/A |
TCP 443 |
|
*.cloudapp.net1 |
No |
Varies2 |
N/A |
TCP 443 |
|||
|
8 |
Optional: Rights Management connector |
On-premises server |
*.aadrm.com |
No |
No |
N/A |
TCP 443 |
1Azure Rights Management Office 2010 Clients Only.
2 See additional information about supported services over Azure ExpressRoute and the Public peering path.
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Office 365 authentication and identity
To use any Office 365 services, you must be able to connect to the endpoints marked required below. If your organization uses Azure AD Connect AAD Connect, AD FS, or Multi-factor authentication, you'll find the associated endpoints below. All IP addresses entered directly in the Destination IP column are also listed in the IP tables and XML file for your convenience.
Expand to see the authentication and identity FQDNs
If you’re using Active Directory Federation Services (AD FS) with your deployment, you can also use AD FS client access policies with Windows Server 2012 R2 or client access policies with AD FS 2.0 to further restrict and control access to Office 365.
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Certificate revocation lists |
||||||
|
2 |
Required: Authentication and identity |
Client Computer | Logged on user |
api.login.microsoftonline.com clientconfig.microsoftonline-p.net device.login.microsoftonline.com hip.microsoftonline-p.net hipservice.microsoftonline.com login.microsoft.com login.microsoftonline.com logincert.microsoftonline.com loginex.microsoftonline.com login-us.microsoftonline.com login.microsoftonline-p.com nexus.microsoftonline-p.com stamp2.login.microsoftonline.com login.windows.net |
No |
Yes |
TCP 80 & 443 |
|
|
accesscontrol.windows.net secure.aadcdn.microsoftonline-p.com |
No |
No |
N/A |
TCP 443 |
|||
|
3 |
Optional: Legacy/temporary FQDNs |
Client Computer | Logged on user |
*.msecnd.net *.microsoft.com *.microsoftonline-p.com *.microsoftonline-p.net |
Akamai and Microsoft |
No |
N/A |
TCP 443 |
|
*.windows.net |
No5 |
||||||
|
*.microsoftonline.com |
Varies |
Yes4 |
N/A |
TCP 443 |
|||
|
4 |
Optional: Multi-factor authentication (MFA) |
Client Computer | Logged on user |
account.activedirectory.windowsazure.com secure.aadcdn.microsoftonline-p.com3 |
No |
No |
TCP 443 |
|
|
5 |
Optional: DirSync (legacy) |
DirSync Server | Machine1 and Service Account |
*.microsoftonline.com login.windows.net provisioningapi.microsoftonline.com adminwebservice.microsoftonline.com |
No |
Yes |
TCP 443 |
|
|
mscrl.microsoft.com |
No |
No |
N/A |
TCP 80 & 443 |
|||
|
6 |
Optional: Azure AD Connect (recommended) |
Azure AD Connect Server | Service Account |
*.microsoftonline.com login.windows.net provisioningapi.microsoftonline.com adminwebservice.microsoftonline.com |
No |
Yes |
TCP 443 |
|
|
mscrl.microsoft.com secure.aadcdn.microsoftonline-p.com3 |
No |
No |
N/A |
TCP 80 & 443 |
|||
|
Public DNS |
No |
No |
N/A |
TCP 53 |
|||
|
7 |
Optional: Azure AD Connect (w/SSO option) – WinRM & remote powershell |
Client Computer | Service Account |
Customer STS environment (AD FS Server and AD FS Proxy) | Ports TCP 80 & 443 |
No |
No |
Customer environment |
TCP 80 & 443 |
|
8 |
Optional: STS such as AD FS Proxy server(s) (for federated customers only) |
Client Computer | N/A |
Customer STS (such as AD FS Proxy) | Ports TCP 443 or TCP 49443 w/ClientTLS |
No |
No |
Customer environment |
TCP 443 or TCP 49443 w/ClientTLS |
|
9 |
Optional: AD FS Proxy server(s) (for federated customers only) |
Customer AD FS Proxy (WAP) | N/A |
Customer AD FS Server (FS) | Port TCP 443 |
No |
No |
Customer environment |
TCP 443 |
|
10 |
Optional: Azure AD Connect Health |
Azure AD Connect Health Server | Service Account |
management.azure.com *.blob.core.windows.net *.queue.core.windows.net *.servicebus.windows.net - Port: 5671 (If 5671 is blocked, agent falls back to 443, but using 5671 is recommended.) *.adhybridhealth.azure.com *.table.core.windows.net policykeyservice.dc.ad.msft.net secure.aadcdn.microsoftonline-p.com |
Microsoft |
Varies2 |
N/A |
TCP 443 |
|
login.windows.net login.microsoftonline.com |
No |
Yes |
TCP 443 |
||||
|
11 |
Customer Operations Manager environment | Machine1 Account |
office365servicehealthcommunications.cloudapp.net |
No |
Varies2 |
N/A |
TCP 443 |
|
1Keep in mind that Machine accounts won’t work with proxies that require outbound authentication.
2 See additional information about supported services over Azure ExpressRoute and the Public peering path.
3 This FQDN needs to be in your client's IE Trusted Sites Zone to function.
4 There are specific sub-FQDNs within this domain that are not available on ExpressRoute, learn more by reading the section, Deciding which applications and features route over ExpressRoute.
5 There are specific sub-FQDNs within this domain that are available on ExpressRoute, learn more by reading the section, Deciding which applications and features route over ExpressRoute.
Expand to see the authentication and identity IP Addresses
Note: ExpressRoute for Office 365 currently does not support IPv6
|
Office 365 authentication and identity IPv4 endpoints routable through the Internet and ExpressRoute |
Office 365 authentication and identity IPv6 endpoints routable through the Internet only |
|
|
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Exchange Online
To use Exchange Online, including mail retrieval, OWA, Unified Messaging, and so on, you must be able to connect to the endpoints marked required below. If your organization uses Exchange Hybrid, Delve, or is migrating email to Office 365, you'll find the associated endpoints below. All IP addresses entered directly in the Destination IP column are also listed in the IP tables and XML file for your convenience.
Expand to see Exchange Online FQDNs
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Portal and shared |
See Office 365 portal and shared including the well known certificate root CRLs. |
|||||
|
2 |
Required: Authentication and identity |
||||||
|
3 |
Required: Exchange Online Protection SMTP services |
||||||
|
4 |
Required: Client SMTP Relay |
Client Computer | Logged on user |
smtp.office365.com |
No |
Yes |
TCP 587 |
|
|
5 |
Required: Exchange Online (including OWA, Outlook, and so on). |
Client Computer | Logged on user |
outlook.office365.com *.outlook.office.com autodiscover-*.outlook.com |
No |
Yes |
TCP 80 & 443 |
|
|
6 |
Required: Exchange Online (including OWA, Outlook, Autodiscover, and so on). |
Client Computer | Logged on user |
*.outlook.com |
No |
No4 |
TCP 80 & 443 |
|
|
7 |
Required: Exchange Online (including OWA, Outlook, and so on). |
Client Computer | Logged on user |
xsi.outlook.com r1.res.office365.com r3.res.office365.com r4.res.office365.com |
Akamai |
No |
N/A |
TCP 80 & 443 |
|
8 |
Optional: Exchange Online Unified Messaging/SBC integration. |
On-premises Session Border Controller |
*.um.outlook.com |
No |
No |
|
Any-TCP/UDP (Bidirectional for inbound, calls , MWI) |
|
9 |
Optional: Exchange Hybrid Only |
Existing Exchange Client Access Servers and Mailbox Servers | Machine account1 |
outlook.office365.com *.outlook.office.com |
No |
Yes |
TCP 80 & 443 |
|
|
10 |
Optional: Exchange Hybrid Co-existence |
Customer on-premise Exchange |
No |
Yes |
Customer IP |
TCP 443 |
|
|
11 |
Optional: Exchange Hybrid Proxy Authentication |
Customer on-premise STS |
No |
Yes |
Customer IP |
TCP 443 (+ TCP 49443 for cert based authentication) |
|
|
12 |
Optional: Used to configure Exchange Hybrid, using the Exchange Hybrid Configuration Wizard. Note: These endpoints are only required to configure Exchange hybrid. Rows 8-10 describe the ongoing traffic. |
Existing Exchange service | N/A |
hybridconfiguration.azurewebsites.net *.hybridconfiguration.azurewebsites.net *.store.core.windows.net mshrcstorageprod.blob.core.windows.net |
No |
Varies3 |
|
TCP 80 & 443 |
|
domains.live.com2 |
No |
Yes |
|
TCP 80 & 443 |
|||
|
13 |
Optional: Exchange Online IMAP4 migration |
IMAP4 Service | N/A |
outlook.office365.com *.outlook.office.com |
No |
Yes |
TCP 143/993 |
|
|
14 |
Optional: Exchange Online POP3 migration |
POP3 Service | N/A |
outlook.office365.com *.outlook.office.com |
No |
Yes |
TCP 995 |
|
|
15 |
Optional: All other Exchange Online migration tools |
Existing Exchange service (EWS or MRS) | N/A |
outlook.office365.com *.outlook.office.com |
No |
Yes |
TCP 80 & 443 |
|
1Keep in mind that Machine accounts won’t work with proxies that require outbound authentication.
2 Only required for Exchange 2010 SP3 Hybrid Configuration Wizard.
3 See additional information about supported services over Azure ExpressRoute and the Public peering path.
4 There are specific sub-FQDNs within this domain that are available on ExpressRoute, learn more by reading the section, Deciding which applications and features route over ExpressRoute.
Expand to see the Exchange Online IP Addresses
Note: ExpressRoute for Office 365 currently does not support IPv6
|
Exchange Online IPv4 endpoints routable through the Internet and ExpressRoute |
Exchange Online IPv6 endpoints routable through the Internet only |
|
|
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Exchange Online Protection (EOP)
To use Exchange Online Protection as a stand alone service or as the SMTP engine with Exchange Online, you must be able to connect to the endpoints marked required below. Note the EOP SMTP IP addresses are linked to in row 2, 3, & 4 instead of being listed directly on this page.
Expand to see Exchange Online Protection FQDNs
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
||||||
|
2 |
Required: EOP |
Client Computer | Logged on user |
*.protection.outlook.com |
No |
Yes |
TCP 53 & 443 |
|
|
3 |
Required: Send SMTP email |
Existing email environment | N/A |
<customer domain-key>.mail.protection.outlook.com |
No |
Yes |
TCP 25 |
|
|
4 |
Required: Receive SMTP email |
See Exchange Online Protection IP Addresses | N/A |
Existing email environment |
No |
Yes |
TCP 25 |
|
Note: The wildcard in the second row of the EOP table represents a long list of nodes that are exclusively used for Exchange Online Protection. No other commercial or consumer services use this namespace.
Skype for Business Online
Expand to see the Skype for Business Online FQDNs
To use Skype for Business Online, you must be able to connect to the endpoints described below. To enable authentication, the endpoints listed in the Office 365 authentication and identity section must be reachable. Similarly, for shared infrastructure and portal services, the endpoints in the portal and shared section are must be reachable. These are rows One and Two respectively. Once the required endpoints in these tables are reachable, ensure the endpoints in the Skype for Business Online table below are reachable. To see the IP addresses, expand the IP address section below the table describing the traffic flow.
|
Row |
Purpose |
Source | Credentials |
Source Port |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
|||||||
|
2 |
Required: Portal and shared |
|||||||
|
3 |
Required: SIP signaling, Persistent Shared Object Model (PSOM) connections web conferencing, and HTTPS downloads |
Client Computer | Logged on user |
Ephemeral ports |
*.lync.com |
No |
Yes |
TCP 443 |
|
|
4 |
Required: Call Quality Dashboard |
Client Computer | Logged on user |
Ephemeral ports |
*.cqd.lync.com |
No |
Yes |
TCP 443 |
|
|
5 |
Required: Audio, Video, & Desktop sharing |
Client Computer | Logged on user |
TCP/UDP 50,000-50019, TCP/UDP 50,020-50039, & TCP/UDP 50,040-50059 |
*.lync.com |
No |
Yes |
TCP 443, UDP 3478, 3479, 3480, & 3481, TCP/UDP 50,000-59,999 |
|
|
6 |
Required: Lync Mobile push notifications for Lync Mobile 2010 on iOS devices. You don't need this for Android, Nokia Symbian or Windows Phone mobile devices. |
Client Computer | Logged on user |
Ephemeral ports |
*.lync.com |
No |
Yes |
TCP 5223 |
|
|
7 |
Required: Skype Telemetry. |
Client Computer | Logged on user |
Ephemeral ports |
skypemaprdsitus.trafficmanager.net pipe.skype.com *.pipe.aria.microsoft.com |
No |
No |
N/A. |
TCP 443 |
|
8 |
Required: Skype client quicktips |
Client Computer | Logged on user |
Ephemeral ports |
quicktips.skypeforbusiness.com |
No |
No |
N/A. |
TCP 443 |
|
9 |
Required: Skype for Business chat in OWA |
Client Computer | Logged on user |
Ephemeral ports |
swx.cdn.skype.com |
No |
No |
N/A. |
TCP 443 |
|
10 |
Required: Skype for Business client configurations |
Client Computer | Logged on user |
Ephemeral ports |
a.config.skype.com b.config.skype.com config.edge.skype.com |
No |
Yes |
13.107.3.128 13.107.3.129 23.99.213.58 23.101.115.193 23.101.116.26 23.101.156.198 23.101.158.111 23.102.17.214 23.102.24.114 40.68.229.156 40.68.230.133 40.78.145.194 104.40.75.8 104.40.76.196 191.233.80.151 191.233.95.169 191.234.19.21 191.234.20.241 191.234.21.145 191.234.23.27 |
TCP 443 |
|
11 |
Optional: Federation with Skype and public IM connectivity: Contact picture retrieval |
Client Computer | Logged on user |
Ephemeral ports |
*.api.skype.com *.users.storage.live.com |
No |
No |
N/A. |
TCP 443 |
|
12 |
Optional: Federation with Skype and public IM connectivity: Skype Search |
Client Computer | Logged on user |
Ephemeral ports |
graph.skype.com |
No |
No |
N/A. |
TCP 443 |
To use Skype Meeting Broadcast, the following endpoints need to be accessible to client computers.
|
Row |
Purpose |
Source |Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: For all Skype functionality, the entries are labeled "required". |
||||||
|
2 |
Required: Skype Meeting Broadcast presenter |
Client computer / logged on user |
aka.ms |
None |
No |
N/A |
TCP 80 & 443 |
|
*.microsoftonline.com |
None |
Yes |
TCP 443 |
||||
|
3 |
Required: Skype Meeting Broadcast presenter and attendee |
Client computer / logged on user |
broadcast.skype.com *.broadcast.skype.com1 *.infra.lync.com1 browser.pipe.aria.microsoft.com mlccdn.blob.core.windows.net |
None |
No |
N/A |
TCP 443 |
|
ajax.aspnetcdn.com *.msecnd.net2 |
Verizon |
No |
N/A |
TCP 443 |
|||
|
4 |
Required: Skype Meeting Broadcast attendee |
Client computer / logged on user |
amp.azure.net pipe.skype.com |
None |
No |
N/A |
TCP 443 |
|
*.streaming.mediaservices.windows.net3 *.keydelivery.mediaservices.windows.net3 |
Azure Media Services |
Yes (Azure Public peering) |
N/A |
TCP 443 |
|||
1 The wildcard for lync.com and broadcast.skype.com represents a long list of nodes that are exclusively used for Office 365.
2 The wildcard for msecnd.net represents a dynamically generated endpoint within the CDN that join page libraries are pulled from.
3 The wildcard for streaming.mediaservices.windows.net represents a list of media services endpoints where video content is pulled from.
Note: The wildcard for lync.com and broadcast.skype.com represents a long list of nodes that are exclusively used for Office 365.
Expand to see the Skype for Business Online IP Addresses
Note: ExpressRoute for Office 365 currently does not support IPv6
|
Skype for Business Online IPv4 endpoints routable through the Internet and ExpressRoute |
Skype for Business Online IPv6 endpoints routable through the Internet only |
|
|
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
SharePoint Online and OneDrive for Business
To use SharePoint Online or OneDrive for Business, you must be able to connect to the endpoints marked required below. If your organization uses Exchange Hybrid, Delve, or is migrating email to Office 365, you'll find the associated endpoints below.
Expand to see the SharePoint Online and OneDrive for Business FQDNs
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
||||||
|
2 |
Required: Portal and shared |
See Office 365 portal and shared including the well known certificate root CRLs. |
|||||
|
3 |
Required: Office Online |
See Office Online |
|||||
|
4 |
Required: SharePoint Online and associated applications |
Client Computer | Logged on user |
*.sharepoint.com <tenant>.sharepoint.com1 <tenant>-my.sharepoint.com1 <tenant>-files.sharepoint.com1 <tenant>-myfiles.sharepoint.com1 *.svc.ms |
No |
Yes |
TCP 80 & 443 |
|
|
5 |
Required: CDNs for SharePoint Online and associated applications |
Client Computer | Logged on user |
*.sharepointonline.com cdn.sharepointonline.com Static.sharepointonline.com prod.msocdn.com spoprod-a.akamaihd.net publiccdn.sharepointonline.com privatecdn.sharepointonline.com |
Microsoft & Akamai |
No |
N/A |
TCP 80 & 443 |
|
6 |
Required: OneDrive for Business update verification and download |
Client Computer | Logged on user |
oneclient.sfx.ms |
Akamai |
No |
N/A |
TCP 80 & 443 |
|
7 |
Required: OneDrive for Business: Determines consumer v commercial |
Client Computer | Logged on user |
https://officeclient.microsoft.com/config16 http://odc.officeapps.live.com/odc/emailhrd |
No |
No |
N/A |
TCP 80 & 443 |
|
8 |
Required: OneDrive for Business: Oauth login with AAD |
Client Computer | Logged on user |
login.microsoftonline.com |
No |
Yes |
N/A |
TCP 443 |
|
9 |
Required: Client push notification |
Client Computer | Logged on user |
wns.windows.com |
No |
No |
N/A |
TCP 443 |
|
10 |
Optional: OneDrive for Business: supportability and telemetry |
Client Computer | Logged on user |
ssw.live.com mobile.pipe.aria.microsoft.com watson.telemetry.microsoft.com |
No |
No |
N/A |
TCP 443 |
|
11 |
Optional: OneDrive for Business: Office integration |
Client Computer | Logged on user |
nexus.officeapps.live.com |
No |
No |
N/A |
TCP 443 |
|
12 |
Optional: APIs to allow users to get help and retrieve logs to diagnose. |
Client Computer | Logged on user |
storage.live.com/clientLogs storage.live.com/sendFeedback |
No |
No |
N/A |
TCP 443 |
|
13 |
Optional: embedded email links |
Client Computer | Logged on user |
click.email.microsoftonline.com |
No |
No |
N/A |
TCP 443 |
|
14 |
Optional: SharePoint Hybrid Search - Endpoint to SearchContentService where the hybrid crawler feeds documents |
The crawler on the on-prem SP authenticates to SCS as the tenant that does the feeding. |
*.search.msit.us.trafficmanager.net *.search.production.us.trafficmanager.net *.search.production.emea.trafficmanager.net *.search.production.apac.trafficmanager.net |
No |
No |
N/A |
TCP 443 |
|
15 |
Optional: SharePoint Hybrid Search - Endpoint to SearchContentService to successfully authenticate to remote farm with OAuth authentication and authorization. The authorization server in this scenario is Microsoft Azure Access Control Service (ACS). |
The Host Controller/Node Runner Account on the on-prem SP server. |
accounts.accesscontrol.windows.net |
No |
No |
N/A |
TCP 443 |
|
16 |
Optional: SharePoint Hybrid Search - Required for onboarding script to connect to Office 365 Provisioning Web Services. As a part of script execution adds the Office 365 Service Principal ID to the local farm and sets the correct Service Principal Name in Azure AD for the on-premises URL. This ensures that the outbound query federation can occur between the Office 365 tenant and the on-premises farm |
Global admin or equivalent credentials on the tenant for which Hybrid Search is being configured |
provisioningapi.microsoftonline.com |
No |
No |
N/A |
TCP 443 |
1 This FQDN needs to be in your client's IE Trusted Sites Zone for Explorer View to function.
Expand to see the SharePoint Online IP Addresses
Note: ExpressRoute for Office 365 currently does not support IPv6. Customers not using ExpressRoute will want to ensure both IP lists below are reachable over the internet.
|
SharePoint Online IPv4 endpoints routable through the Internet and ExpressRoute |
SharePoint Online IPv6 endpoints routable through the Internet only |
|---|---|
|
|
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Office 365 Video
To use Office 365 Video, you must be able to connect to the endpoints marked required below.
Expand to see Office 365 Video FQDNs
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
||||||
|
2 |
Required: Portal and shared |
See Office 365 portal and shared including the well known certificate root CRLs. |
|||||
|
3 |
Required: SharePoint Online endpoints listed above as required |
||||||
|
4 |
Required: Office 365 Video |
Client Computer | Logged on user |
*.keydelivery.mediaservices.windows.net *.streaming.mediaservices.windows.net |
Azure Media Services |
Uses Azure Media Services 1 |
N/A |
TCP 443 |
|
5 |
Required: Office 365 Video |
Client Computer | Logged on user |
ajax.aspnetcdn.com |
Yes |
No |
N/A |
TCP 443 |
|
6 |
Required: Office 365 Video |
Client Computer | Logged on user |
r3.res.outlook.com |
Akamai |
No |
N/A |
TCP 443 |
|
7 |
Required: Office 365 Video |
Client Computer | Logged on user |
spoprod-a.akamaihd.net |
Akamai |
No |
N/A |
TCP 443 |
1 See additional information about supported services over Azure ExpressRoute and the Public peering path.
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Office Online
To use Office Online, you must be able to connect to the endpoints marked required below.
Expand to see the Office Online FQDNs
|
Row |
Purpose |
Source |Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
||||||
|
2 |
Required: Portal and shared |
See Office 365 portal and shared including the well known certificate root CRLs. |
|||||
|
3 |
Required: Office Online |
Client Computer | Logged on user |
*broadcast.officeapps.live.com *excel.officeapps.live.com *onenote.officeapps.live.com *powerpoint.officeapps.live.com *view.officeapps.live.com *visio.officeapps.live.com *word-edit.officeapps.live.com *word-view.officeapps.live.com |
No |
Yes |
TCP 443 |
|
|
4 |
Required: Content Delivery Network for Office Web Apps |
Client Computer | Logged on user |
*.cdn.office.net |
Akamai |
No |
N/A |
TCP 443 |
Note: The wildcards under the officeapps.live.com namespace, such as *visio.officeapps.live.com represents a 20+ list of regional nodes that are subject to change as the service expands.
Expand to see the Office Online IP Addresses
Note: ExpressRoute for Office 365 currently does not support IPv6
|
Office Web Apps IPv4 endpoints routable through the Internet and ExpressRoute |
Office Web Apps IPv6 endpoints routable through the Internet only |
|
|
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Yammer
To use Yammer, you must be able to connect to the endpoints marked required below.
Expand to see the Yammer FQDNs
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
||||||
|
2 |
Required: Portal and shared |
See Office 365 portal and shared including the well known certificate root CRLs. |
|||||
|
3 |
Required: Yammer |
Client Computer | Logged on user |
*.yammer.com1 *.yammerusercontent.com1 |
No |
No |
TCP 443 |
|
|
4 |
Required: Yammer |
Client Computer | Logged on user |
*.assets-yammer.com1 |
Varies |
No |
N/A |
TCP 443 |
|
5 |
Optional: Document, video, & image storage/rendering |
Client Computer | Logged on user |
ajax.googleapis.com *.cloudfront.net |
No |
No |
N/A |
TCP 443 |
1 This FQDN needs to be in your client's IE Trusted Sites Zone to function.
Note: The wildcard for yammer.com represents a long list of nodes that are exclusively used for Office 365.
Expand to see the Yammer IP Addresses
|
Yammer IPv4 endpoints routable through the Internet only |
|
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Sway
To use Sway, you must be able to connect to the endpoints marked required below.
Expand to see the Sway FQDNs
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
||||||
|
2 |
Required: Portal and shared |
See Office 365 portal and shared including the well known certificate root CRLs. |
|||||
|
3 |
Required: Sway |
Client Computer | Logged on user |
sway.com www.sway.com eus-www.sway.com eus-000.www.sway.com eus-001.www.sway.com eus-002.www.sway.com eus-003.www.sway.com eus-004.www.sway.com eus-005.www.sway.com eus-006.www.sway.com eus-007.www.sway.com eus-008.www.sway.com eus-009.www.sway.com eus-00a.www.sway.com eus-00b.www.sway.com eus-00c.www.sway.com eus-00d.www.sway.com eus-00e.www.sway.com wus-www.sway.com wus-000.www.sway.com wus-001.www.sway.com wus-002.www.sway.com wus-003.www.sway.com wus-004.www.sway.com wus-005.www.sway.com wus-006.www.sway.com wus-007.www.sway.com wus-008.www.sway.com wus-009.www.sway.com wus-00a.www.sway.com wus-00b.www.sway.com wus-00c.www.sway.com wus-00d.www.sway.com wus-00e.www.sway.com |
No |
No |
TCP 443 |
|
|
4 |
Required: Sway |
Client Computer | Logged on user |
eus-www.sway-cdn.com wus-www.sway-cdn.com eus-www.sway-extensions.com wus-www.sway-extensions.com |
Akamai |
No |
N/A |
TCP 443 |
|
5 |
Optional: Sway website analytics |
Client Computer | Logged on user |
c.microsoft.com c1.microsoft.com prod.msocdn.com www.google-analytics.com |
No |
No |
N/A |
TCP 443 |
|
6 |
Optional: Sway third party content |
Client Computer | Logged on user |
Access to third party content such as Bing, Flickr, and so on. |
No |
No |
N/A |
TCP 443 |
Expand to see the Sway IP Addresses
|
Sway IPv4 endpoints routable through the Internet only |
|
|
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Planner
To use Planner, you must be able to connect to the endpoints marked required below.
Expand to see the Planner FQDNs
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
||||||
|
2 |
Required: Portal and shared |
See Office 365 portal and shared including the well known certificate root CRLs. |
|||||
|
3 |
Required: Planner |
Browser/ authenticated user |
tasks.office.com controls.office.com cus-000.tasks.osi.office.net ea-000.tasks.osi.office.net eus-zzz.tasks.osi.office.net neu-000.tasks.osi.office.net sea-000.tasks.osi.office.net weu-000.tasks.osi.office.net wus-000.tasks.osi.office.net |
No |
No |
TCP 443 |
|
|
4 |
Required: Planner |
Browser/ authenticated user |
outlook.office365.com www.outlook.com |
No |
Yes |
TCP 443 |
|
|
5 |
Required: Planner |
Browser/ authenticated user |
clientlog.portal.office.com |
No |
No |
TCP 443 |
|
|
6 |
Required: Planner CDNs |
Browser/ authenticated user |
ajax.aspnetcdn.com prod.msocdn.com |
Akamai |
No |
N/A |
TCP 443 |
Expand to see the Planner IP Addresses
|
Planner IPv4 endpoints routable through the Internet only |
|
|
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Microsoft Teams
To use Microsoft Teams you must be able to connect to the endpoints marked required below.
Expand to see the Microsoft Teams FQDNs
|
Row |
Purpose |
Source |Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Authentication and identity |
||||||
|
2 |
Required: Microsoft Teams. |
Client computer / logged on user |
teams.skype.com teams.microsoft.com api.teams.skype.com img.teams.skype.com webhook.teams.skype.com statics.teams.skype.com statics.teams.microsoft.com bots.teams.skype.com settings.teams.skype.com emails.teams.skype.com emails.teams.skype.net scheduler.teams.microsoft.com meetings-cdn.skypeforbusiness.com api.skypeforbusiness.com |
N/A |
No |
N/A |
TCP 80 & 443 |
|
3 |
Required: Microsoft Teams collaboration |
Client computer / logged on user |
*.conv.skype.com1 *.asm.skype.com1 *.cc.skype.com1 *.msg.skype.com1 *.dc.trouter.io1 prod.registrar.skype.com prod.tpc.skype.com amer-client-ss.msg.skype.com amer-server-ss.msg.skype.com us-api.asm.skype.com emea-client-ss.msg.skype.com emea-server-ss.msg.skype.com eu-api.asm.skype.com apac-client-ss.msg.skype.com apac-server-ss.msg.skype.com ea-api.asm.skype.com |
N/A |
No |
N/A |
TCP 443 |
|
4 |
Required: Microsoft Teams media |
Client computer / logged on user |
N/A |
N/A |
No |
|
TCP 443 UDP 3478-3481 UDP + TCP 50000-60000 |
|
5 |
Required: Microsoft Teams shared services |
Client computer / logged on user |
*.config.skype.com2 *.msedge.net *.pipe.skype.com *.pipe.aria.microsoft.com mobile.pipe.aria.microsoft.com ssdesktopbuild.blob.core.windows.net s-0001.s-msedge.net s-0002.s-msedge.net s-0004.s-msedge.net scsquery-ss-us.trafficmanager.net scsquery-ss-eu.trafficmanager.net scsquery-ss-asia.trafficmanager.net mlccdnprod.azureedge.net |
N/A |
No |
N/A |
TCP 443 |
|
a.config.skype.com b.config.skype.com |
N/A |
Yes |
TCP 443 |
||||
|
6 |
Optional: Microsoft Teams third-party integrations |
Client computer / logged on user |
*.giphy.com |
N/A |
No |
N/A |
TCP 443 |
|
7 |
Optional: Messaging interop with Skype for Business |
Client computer / logged on user |
skypemaprdsitus.trafficmanager.net pipe.skype.com swx.cdn.skype.com latest-swx.cdn.skype.com graph.skype.com |
N/A |
No |
N/A |
TCP 443 |
|
*.lync.com |
N/A |
Yes |
TCP 443 |
||||
|
8 |
Optional: Messaging interop with Skype for Business Client Configurations |
Client computer / logged on user |
a.config.skype.comb.config.skype.com config.edge.skype.com |
N/A |
Yes |
|
TCP 443 |
1 These wildcards represent regional installations of these services.
2 There are specific sub-FQDNs within this domain that are available on ExpressRoute, learn more by reading the section, Deciding which applications and features route over ExpressRoute.
Expand to see the Microsoft Teams IP Addresses
|
Microsoft Teams IPv4 endpoints routable through the Internet only |
Microsoft Teams IPv6 endpoints routable through the Internet only |
|
|
|
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Office clients
Office clients include both desktop and mobile clients, the online endpoints these applications use to improve the product experience are detailed below.
Network requests in Office 2016 for Mac
To understand Office 2016 for Mac endpoint requirements, refer to our reference article Network requests in Office 2016 for Mac.
Network requests for Office clients
To understand Office client network requests including, Office 365 ProPlus, Office 2016 for Windows, Outlook App for iOS and Windows, and OneNote refer to the article Network requests in Office 365 ProPlus.
Office 365 remote analyzer tools
To use the Office 365 remote analyzer tools you must be able to connect to the endpoints described below.
Expand to see the Remote Analyzer FQDN and IP addresses
|
Row |
Purpose |
Source | Credentials |
Destination |
CDN |
ExpressRoute for Office 365 |
Destination IP |
Destination Port |
|---|---|---|---|---|---|---|---|
|
1 |
Required: Remote Connectivity Analyzer - Initiate connectivity tests. |
Web Browser | Logged on user |
testconnectivity.microsoft.com |
No |
No |
13.67.59.89/32 40.85.91.8/32 104.208.36.70/32. |
TCP 80 & 443 |
|
2 |
Required: Remote Connectivity Analyzer - Captcha & support services |
Web Browser | Logged on user |
client.hip.live.com wu.client.hip.live.com support.microsoft.com |
No |
No |
N/A |
TCP 80 & 443 |
|
3 |
Required: Remote Connectivity Analyzer - Execution of the tests selected by the customer. |
testconnectivity.microsoft.com | Provided by customer on the testconnectivity website |
On-premises systems for email and collaboration. |
No |
No |
Customer IP ranges |
80, 443, 25, POP3 on (110, 995, or Custom), IMAP4 on (143, 993, or Custom) |
|
4 |
Required: Certificate revocation lists |
Web Browser | Logged on user |
See well known certificate root CRLs in the table below. |
No |
No |
N/A |
TCP 80 & 443 |
|
5 |
Required: Microsoft Support and Recover Assistant for Office 365 - Validate single sign-on user credentials. |
o365diagnosticsbasic-eus.cloudapp.net (104.211.54.99) o365diagnosticworker-eus.cloudapp.net (104.211.54.134) |
On-premises STS |
No |
No |
Customer IP ranges |
Customer configurable. Typically TCP 443 |
(Back to top | Office 365 portal and shared | Office 365 authentication and identity | Exchange Online | Skype for Business Online | SharePoint Online | Office 365 Video | Exchange Online Protection (EOP) | Office 365 remote analyzer tools | Office Clients | Office Online | Yammer | Sway | Planner)
Here’s a short link you can use to come back: https://aka.ms/o365endpoints