Networking Phase-Describe Microsoft 365 apps and services

The Networking phase of a Microsoft 365 deployment is intended to ensure that all clients have sufficient Internet connectivity to access the cloud resources they will require regularly. This is not just a matter of bandwidth, however. The Microsoft Global Network provides endpoints to its cloud services worldwide, and for Microsoft 365 clients to function efficiently, they should have access to the closest possible endpoint.

Many enterprise networks were designed and constructed at a time when the proximity of the Internet connection was not a priority. It was common for Internet traffic at remote sites to be routed over a backbone network to a central location that provided the actual Internet access. This can result in a significant amount of network latency (that is, transmission delays), which can have a negative effect on Microsoft 365 performance.

Microsoft’s Domain Name System (DNS) servers direct client traffic to the nearest endpoint based on their initial connection request. The clients should therefore also utilize a geographically local DNS server for their outbound Internet traffic.

For an enterprise that has a centralized Internet access infrastructure, the organization should take the steps necessary to reroute the Internet traffic so that each client is directed to the Microsoft endpoint that is geographically closest to its location. In a large enterprise with many remote sites, this can be a substantial undertaking that might play a role in deciding whether to adopt Microsoft 365 in the first place.

Microsoft also recommends that enterprise networks avoid using protection mechanisms, such as proxy servers and packet inspection, for Microsoft 365 traffic. The DNS names and IP addresses used by the Microsoft 365 cloud services are well-known, and Microsoft’s own mechanisms already protect the services. Duplicating this protection at the enterprise end can also have a negative effect on Microsoft 365 performance. Bypassing these local protection mechanisms requires browsers, firewalls, and other components to identify Microsoft 365 traffic and process it differently from other types of Internet traffic.