Office 365 Connectivity Guidance: Part 3

3. Unhindered access to the endpoints required. The next principle is to get your traffic to Microsoft as unhindered as possible, this means minimising the work done on the traffic or ensuring any work done doesn’t cause an impact to that traffic. When moving to the cloud it’s worth having a rethink about how you…

0

Office 365 Connectivity Guidance: Part 4

4. Local DNS resolution Finally, local DNS resolution is a necessity to ensure Microsoft can connect your clients to resources based on their location. Many cloud services use this method, for example, we currently use Geo DNS for Exchange Online to connect your clients to the nearest front-end server for the service. I’ve covered this…

1

Office 365 Connectivity Guidance: Part 2

2. Localized network egress as close to the user as possible To enable your user’s traffic to take full advantage of Microsoft’s global network, ideally, we’d want their traffic to egress locally and thus peer onto Microsoft’s network as quickly and as closely as possible. However, backhauling to a centralized internet egress is common for…

0