Managing Microsoft 365 endpoints

Source history: extracted from the page's source file at a commit; shared includes are not expanded

Settings and overrides named on this page

Registry values, policies and cmdlets the source mentions, with the dated steps that name them. Read the source for the values to set.

• ClientRequestId
• Get-PacFile
• SD-WAN

Requirements, exceptions and scope

• Managing Microsoft 365 endpointsRequirementException1 condition1 passage
• SD-WAN for local branch egress of vital Microsoft 365 network trafficScope1 passage
  SD-WAN
• Use a PAC file for direct routing of vital Microsoft 365 trafficRequirementExceptionScopeRecommendation1 condition4 passages
  Get-PacFileClientRequestId
• Change management for Microsoft 365 IP addresses and URLsRequirementExceptionRecommendationTentative3 conditions1 passage
• Change notification using the Web ServiceRecommendation2 conditions1 passage
• Am I peering appropriately with Microsoft?Recommendation1 passage
• I see network requests to IP addresses not on the published list, do I need to provide access to them?ExceptionRecommendation3 conditions1 passage
• Some Microsoft 365 URLs point to CNAME records instead of A records in the DNS. What do I have to do with the CNAME records?Recommendation1 passage
• I have to have the minimum connectivity possible for Microsoft 365RequirementExceptionRecommendationTentative4 conditions4 passages
• My firewall requires IP Addresses and cannot process URLs. How do I configure it for Microsoft 365?RequirementExceptionRecommendation3 conditions1 passage

Extracted automatically from Microsoft's wording. Confirm dates, conditions and whether they apply to you in the source before acting; a month or quarter is a window, not a day.

How this timeline changed

Changes between ChangeIntel's readings of the page, between commits of its source file where Microsoft publishes it, in Internet Archive copies of pages that keep no other history, and entries from Microsoft's own change log (dated as Microsoft dates them). Edits between readings that neither records are unknown.

1. 20 Jun 2024
   No longer on the page I have to have the minimum connectivity possible for Microsoft 365Microsoft's source, commit 0ddc1a2
2. 20 Jun 2024
   Requirement added I have to have the minimum connectivity possible for Microsoft 365Microsoft's source, commit 0ddc1a2
3. 20 Jun 2024
   Requirement added I have to have the minimum connectivity possible for Microsoft 365Microsoft's source, commit 83ff6b7
4. 20 Jun 2024
   No longer on the page I have to have the minimum connectivity possible for Microsoft 365Microsoft's source, commit 83ff6b7
5. 30 Oct 2023
   Requirement added Change management for Microsoft 365 IP addresses and URLsMicrosoft's source, commit 2d22141
6. 30 Oct 2023
   No longer on the page Change management for Microsoft 365 IP addresses and URLsMicrosoft's source, commit 2d22141
7. 30 Oct 2023
   No longer on the page I have to have the minimum connectivity possible for Microsoft 365Microsoft's source, commit 2d22141
8. 30 Oct 2023
   Requirement added I have to have the minimum connectivity possible for Microsoft 365Microsoft's source, commit 2d22141
9. 30 Oct 2023
   Requirement added My firewall requires IP Addresses and cannot process URLs. How do I configure it for Microsoft 365?Microsoft's source, commit 2d22141
10. 30 Oct 2023
    No longer on the page My firewall requires IP Addresses and cannot process URLs. How do I configure it for Microsoft 365?Microsoft's source, commit 2d22141
11. 30 Oct 2023
    No longer on the page Use a PAC file for direct routing of vital Microsoft 365 trafficMicrosoft's source, commit 2d22141
12. 30 Oct 2023
    Requirement added Use a PAC file for direct routing of vital Microsoft 365 trafficMicrosoft's source, commit 2d22141