Microsoft 365 network connectivity principles
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/microsoft-365-docs · commit f5fd0c3 · +1 −1 lines · also on GitHub
⋯ 221 unchanged lines
222222
223223
You can approach optimization as an incremental process, applying each method successively. The following table lists key optimization methods in order of their effect on latency and reliability for the largest number of users.
224224
225
−|**Optimization method**|**Description**|**Impact**|
225
+| Optimization method | Description | Impact |
226226
|:-----|:-----|:-----|
227227
|Local DNS resolution and Internet egress <br/> |Provision local DNS servers in each location and ensure that Microsoft 365 connections egress to the Internet as close as possible to the user's location. <br/> | Minimize latency <br/> Improve reliable connectivity to the closest Microsoft 365 entry point <br/> |
228228
|Add regional egress points <br/> |If your corporate network has multiple locations but only one egress point, add regional egress points to enable users to connect to the closest Microsoft 365 entry point. <br/> | Minimize latency <br/> Improve reliable connectivity to the closest Microsoft 365 entry point <br/> |
⋯ 29 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/microsoft-365-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 05:34 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.