Menu
-->![Microsoft Support And Recovery Assistant For Office 365 Mac Microsoft Support And Recovery Assistant For Office 365 Mac](/uploads/1/2/6/4/126469474/626968241.jpg)
![Microsoft Support And Recovery Assistant For Office 365 Mac Microsoft Support And Recovery Assistant For Office 365 Mac](/uploads/1/2/6/4/126469474/629302677.png)
Some network endpoints were previously published and have not been included in the Office 365 IP Address and URL Web Service. The web service scope is network endpoints that are required for connectivity from a user of Office 365 across an enterprise perimeter network. This currently does not include:
Outlook for Windows, Outlook for Mac, Outlook apps for Apple or Android, Outlook.com? Since Office 365 isn’t software (it’s the marketing name for a group of Microsoft software and services) how do you know if it’ll help? Turns out it’ll help with some of those if you’re using Office 365 hosted mail (Exchange Online). 2019-12-2 The Microsoft Support and Recovery Assistant (SaRA) uses advanced diagnostics to report known problems and details about your Microsoft Outlook configuration. Reported problems are linked to public-facing documentation (usually a Microsoft Knowledge Base article) for possible fixes. Mar 26, 2020 Fortunately, Support and Recovery Assistant finds and helps you fix most issues with Outlook or Office 365. As a first step in troubleshooting email delivery problems for Office 365 for business, we recommend that you download and run Microsoft Support and Recovery Assistant on the affected machine. Sep 06, 2019 To troubleshoot Office 365 issues when signing in to Skype for Business, you can use the Microsoft Support and Recovery Assistant (SaRA). This tool can help you automatically diagnose and fix a range of known issues related to signing in to Skype for Business. We announced the availability of ‘Office 365 Support and Recovery Assistant’ a couple of months ago here. Introducing Engineering Blog for 'Microsoft Office.
![Microsoft Support And Recovery Assistant For Office 365 Mac Microsoft Support And Recovery Assistant For Office 365 Mac](/uploads/1/2/6/4/126469474/626968241.jpg)
- Network connectivity that may be required from a Microsoft datacenter to a customer network (inbound hybrid server network traffic).
- Network connectivity from servers on a customer network across the enterprise perimeter (outbound server network traffic).
- Uncommon scenarios for network connectivity requirements from a user.
- DNS resolution connectivity requirement (not listed below).
- Internet Explorer or Microsoft Edge Trusted Sites.
Microsoft Support And Recovery Assistant For Office 365 Mac Download
![Microsoft Support And Recovery Assistant For Office 365 Mac Microsoft Support And Recovery Assistant For Office 365 Mac](/uploads/1/2/6/4/126469474/629302677.png)
Microsoft autoupdate mac download not working. Where is the microsoft user data folder mac. Apart from DNS, these are all optional for most customers unless you need the specific scenario that is described.
Row | Purpose | Destination | Type | |
1 | Import Service for PST and file ingestion | Refer to the Import Service for additional requirements. | Uncommon outbound scenario | |
2 | Microsoft Support and Recovery Assistant for Office 365 | https://autodiscover.outlook.com https://officecdn.microsoft.com https://api.diagnostics.office.com https://apibasic.diagnostics.office.com https://autodiscover-s.outlook.com https://cloudcheckenabler.azurewebsites.net https://dcs-staging.azure-api.net https://login.live.com https://login.microsoftonline.com https://login.windows.net https://o365diagtelemetry.trafficmanager.net https://odc.officeapps.live.com https://offcatedge.azureedge.net https://officeapps.live.com https://outlook.office365.com https://outlookdiagnostics.azureedge.net | Outbound server traffic | |
3 | Azure AD Connect (w/SSO option) – WinRM & remote PowerShell | Customer STS environment (AD FS Server and AD FS Proxy) | TCP ports 80 & 443 | Inbound server traffic | |
4 | STS such as AD FS Proxy server(s) (for federated customers only) | Customer STS (such as AD FS Proxy) | Ports TCP 443 or TCP 49443 w/ClientTLS | Inbound server traffic | |
5 | Exchange Online Unified Messaging/SBC integration | Bidirectional between on-premises Session Border Controller and *.um.outlook.com | Outbound server only traffic | |
6 | Mailbox Migration. When mailbox migration is initiated from on-premises Exchange Hybrid to Office 365, Office 365 will connect to your published Exchange Web Services (EWS)/Mailbox Replication Services (MRS) server. If you need the NAT IP addresses used by Exchange Online servers to restrict inbound connections from specific source IP ranges, they are listed in Office 365 URL & IP ranges under the 'Exchange Online' service area. Care should be taken to ensure that access to published EWS endpoints like OWA is not impacted by ensuring the MRS proxy resolves to a separate FQDN and public IP address before restricting TCP 443 connections from specific source IP ranges. | Customer on-premises EWS/MRS Proxy TCP port 443 | Inbound server traffic | |
7 | Exchange Hybrid co-existence functions such as Free/Busy sharing. | Customer on-premises Exchange server | Inbound server traffic | |
8 | Exchange Hybrid proxy authentication | Customer on-premises STS | Inbound server traffic | |
9 | Used to configure Exchange Hybrid, using the Exchange Hybrid Configuration Wizard Note: These endpoints are only required to configure Exchange hybrid | domains.live.com on TCP ports 80 & 443, only required for Exchange 2010 SP3 Hybrid Configuration Wizard GCC High, DoD IP addresses: 40.118.209.192/32; 168.62.190.41/32 Worldwide Commercial & GCC: *.store.core.windows.net; asl.configure.office.com; mshrcstorageprod.blob.core.windows.net; tds.configure.office.com; mshybridservice.trafficmanager.net | Outbound server only traffic | |
10 | The AutoDetect service is used in Exchange Hybrid scenarios with Hybrid Modern Authentication with Outlook for iOS and Android*.acompli.net *.outlookmobile.com *.outlookmobile.us 52.125.128.0/20 52.127.96.0/23 | Customer on-premises Exchange server on TCP 443 | Inbound server traffic | |
11 | Skype for Business in Office 2016 includes video based screen sharing which uses UDP ports. Prior Skype for Business clients in Office 2013 and earlier used RDP over TCP port 443. | TCP port 443 open to 52.112.0.0/14 | Skype for Business older client versions in Office 2013 and earlier | |
12 | Skype for Business hybrid on-premises server connectivity to Skype for Business Online | 13.107.64.0/18, 52.112.0.0/14 UDP ports 50,000-59,999 TCP ports 50,000-59,999; 5061 | Skype for Business on-premises server outbound connectivity | |
13 | Cloud PSTN with on-premises hybrid connectivity requires network connectivity open to the on-premises hosts. For more details about Skype for Business Online hybrid configurations | See Plan hybrid connectivity between Skype for Business Server and Office 365 | Skype for Business on-premises hybrid inbound | |
14 | Authentication and identity FQDNs The FQDN secure.aadcdn.microsoftonline-p.com needs to be in your client's Internet Explorer (IE) or Edge Trusted Sites Zone to function. | Trusted Sites | ||
15 | Microsoft Teams FQDNs If you are using Internet Explorer or Microsoft Edge, you need to enable first and third-party cookies and add the FQDNs for Teams to your Trusted Sites. This is in addition to the suite-wide FQDNs, CDNs, and telemetry listed in row 14. See Known issues for Microsoft Teams for more information. | Trusted Sites | ||
16 | SharePoint Online and OneDrive for Business FQDNs All '.sharepoint.com' FQDNs with '<tenant>' in the FQDN need to be in your client's IE or Edge Trusted Sites Zone to function. In addition to the suite-wide FQDNs, CDNs, and telemetry listed in row 14, you'll need to also add these endpoints. | Trusted Sites | ||
17 | Yammer Yammer is only available in the browser and requires the authenticated user to be passed through a proxy. All Yammer FQDNs need to be in your client's IE or Edge Trusted Sites Zone to function. | Trusted Sites | ||
18 | Use Azure AD Connect to sync on-premises user accounts to Azure AD. | See Hybrid Identity Required Ports and Protocols, Troubleshoot Azure AD connectivity, and Azure AD Connect Health Agent Installation. | Outbound server only traffic | |
19 | Microsoft Stream (needs the Azure AD user token). Office 365 Worldwide (including GCC) | *.cloudapp.net *.api.microsoftstream.com *.notification.api.microsoftstream.com amp.azure.net api.microsoftstream.com az416426.vo.msecnd.net s0.assets-yammer.com vortex.data.microsoft.com web.microsoftstream.com TCP port 443 | Inbound server traffic | |
20 | Use MFA server for multifactor authentication requests, both new installations of the server and setting it up with Active Directory Domain Services (AD DS). | See Getting started with the Azure Multi-Factor Authentication Server. | Outbound server only traffic | |
21 | Microsoft Graph Change Notifications | Developers can leverage change notifications to subscribe to events in the Microsoft Graph. | *.cloudapp.net 104.43.130.21, 137.116.169.230, 13.79.38.63, 104.214.39.228, Public Cloud: 168.63.250.205, 52.161.9.202, 40.68.103.62, 13.89.60.223, 23.100.95.104, 40.113.95.219, 104.214.32.10, 168.63.237.145, 52.161.110.176, 52.174.177.183 Microsoft Cloud for US Government: 52.244.231.173, 52.238.76.151, 52.244.250.211, 52.238.78.108 Microsoft Cloud Germany: 51.4.231.136, 51.5.243.223, 51.4.226.154, 51.5.244.215 Microsoft Cloud China operated by 21Vianet: 139.219.15.33, 42.159.154.223, 42.159.88.79, 42.159.155.77 TCP port 443 Note: Developers can specify different ports when creating the subscriptions. | Inbound server traffic |