Collaborate for free with online versions of Microsoft Word, PowerPoint, Excel, and OneNote. Save documents, spreadsheets, and presentations online, in OneDrive.
-->
Summary: Office 365 requires connectivity to the Internet. The endpoints below should be reachable for customers using Office 365 plans, including Government Community Cloud (GCC).
Note
Microsoft has released a REST-based web service for the IP address and FQDN entries on this page. This new service will help you configure and update network perimeter devices such as firewalls and proxy servers. You can download the list of endpoints, the current version of the list, or specific changes. This service replaces the XML document linked from this page, which was deprecated on October 2, 2018. To try out this new service, go to Web service.
Office 365 Worldwide (+GCC) | Office 365 operated by 21 Vianet | Office 365 Germany | Office 365 U.S. Government DoD | Office 365 U.S. Government GCC High |
Start with Managing Office 365 endpoints to understand our recommendations for managing network connectivity using this data. Endpoints data is updated at the beginning of each month with new IP Addresses and URLs published 30 days in advance of being active. This allows for customers who do not 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 are 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 Office 365. It does not include network connections from Microsoft into a customer network, sometimes called hybrid or inbound network connections. See Additional endpoints for more information.
The endpoints are grouped into four service areas. The first three service areas can be independently selected for connectivity. The fourth service area is a common dependency (called Microsoft 365 Common and Office) and must always have network connectivity.
Data columns shown are:
Exchange Online
SharePoint Online and OneDrive for Business
Skype for Business Online and Microsoft Teams
Microsoft 365 Common and Office Online
Note
For recommendations on Yammer IP addresses and URLs, see this blog post.
Related Topics
We have the same issue ongoing. Unfortunately I don't know the specifics of what happened but I do know our company moved from an in-house exchange server to Office 365 approximately the time I joined the company. When I began work I was able to set up my exchange account from the internal network with autodiscover and had no issues.
At some point in the past two months we hired another user and when we tried to set him up we could not get it to go through. Someone had the idea of swapping his dns settings to google's 8.8.8.8 and it worked just fine. Switching his dns back to our internal servers does not cause further issues. It only appears to affect the initial set up from the internal network.
Being as how I don't have access to our own servers I cannot really speculate as to what caused the issue to arise but it would be really nice if someone had some suggestions as to what could be causing the problem, if not how to fix it. Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |