Applies to: Office 365 for professionals and small businesses, Office 365 for enterprises, Live@edu
Topic Last Modified: 2012-05-23
To help ensure that network traffic from Microsoft datacenters is accepted, you may need to open ports in your on-premises firewall so network traffic originating from IP addresses in the datacenters can enter your on-premises organization.
|To view the change history of this topic, see Change Notification for Exchange Online URLs and IP Address Ranges.|
Microsoft Office 365 relies on third-party content caching engines to achieve good performance and response times. The types of content cached with these third parties are non-SSL resources, such as the images downloaded to draw the Outlook Web App user interface. As stated above, it's possible and supported to use IP-based filtering for the SSL content downloaded from Office 365 and for the Office 365 end-points that make in-bound calls to an on-premises environment. However, it isn’t possible or supported to use IP-based filtering for the non-SSL resources hosted on third-party content caching engines. To express filtering rules that allow those non-SSL resources to be downloaded to clients on your intranet, you need to use hostname-based filtering (as opposed to IP-based filtering). This is because the IPs used by the third-party content caching engines change frequently in a manner which makes it impractical to track each individual IP change. Allow the following hostname for these non-SSL resources:|
The IP Addresses and URLs listed in this section are specific to accessing Exchange mailboxes. For additional URLs and IP Addresses used by all users in Microsoft Office 365 organizations, see Office 365 URLs and IP Addresses.
The following IP addresses are used by Exchange Online in Microsoft datacenters. Your Exchange Online organization is located in a datacenter in the geographic region that's closest to you. Therefore, you only need to allow the IP address ranges specified for your geographic region.
126.96.36.199/25 188.8.131.52/25 184.108.40.206/25 220.127.116.11/25 18.104.22.168/26 22.214.171.124/25 126.96.36.199/25 188.8.131.52/25 184.108.40.206/25 220.127.116.11/25 18.104.22.168/25 22.214.171.124/24 126.96.36.199/25 188.8.131.52/25 184.108.40.206/25 220.127.116.11/21 18.104.22.168/24 22.214.171.124/24 126.96.36.199/24 188.8.131.52/21 184.108.40.206/24 220.127.116.11/24 18.104.22.168/24 22.214.171.124/25 126.96.36.199/25 188.8.131.52/26
184.108.40.206/25 220.127.116.11/25 18.104.22.168/25 22.214.171.124/25 126.96.36.199/25 188.8.131.52/25 184.108.40.206/25 220.127.116.11/21 18.104.22.168/25 22.214.171.124/26
126.96.36.199/25 188.8.131.52/25 184.108.40.206/25 220.127.116.11/21 18.104.22.168/24 22.214.171.124/25 126.96.36.199/25
The Microsoft Federation Gateway is used with Exchange Online under the following circumstances:
- Federated delegation For more information, see Configure Federated Delegation in the Cloud.
- Hybrid deployments For more information, see Exchange Hybrid Deployment and Migration with Office 365.
The following IP addresses and URLs are used by the Microsoft Federation Gateway.
188.8.131.52/25 184.108.40.206/24 *.microsoftonline-p.com *.live.com *.microsoftonline.com *.microsoftonlinesupport.net
Other services in Microsoft Office 365, for example, Microsoft SharePoint Online, use different IP address ranges and URLs. For more information, see IP addresses and URLs used by Office 365.