Microsoft recommends the following principles to achieve optimal Microsoft 365 connectivity and performance. In essence, this means that even though Microsoft 365 tenant data may be stored in a specific geographic location, Microsoft 365 experience for that tenant remains distributed, and can be present in very close (network) proximity to every end-user location that the tenant has. To achieve the best results, the principles outlined in this document should be looked at from the scale-out (not scale-up) point of view, focusing on optimizing connectivity to the nearest point of presence in the Microsoft Global Network, not to the geographic location of the Microsoft 365 tenant. In the majority of cases, the best user experience is achieved by allowing the customer network to route user requests to the closest Microsoft 365 service entry point, rather than connecting to Microsoft 365 through an egress point in a central location or region.įor most customers, Microsoft 365 users are distributed across many locations. The user experience with Microsoft 365 (including performance, reliability, and other important quality characteristics) involves connectivity through highly distributed service front doors that are scaled out across hundreds of Microsoft locations worldwide. The location of the target Microsoft 365 tenant is important to understand the locality of where customer data is stored within the cloud, but the user experience with Microsoft 365 doesn't involve connecting directly to disks containing the data. One of the most significant architectural features of Microsoft 365 (that is often missed or misinterpreted by network architects) is that it is a truly global distributed service, in the context of how users connect to it. These principles and architecture patterns for connectivity are typical for many other SaaS clouds and at the same time being different from the typical deployment models of Platform-as-a-Service and Infrastructure-as-a-Service clouds, such as Microsoft Azure. While specific Microsoft 365 applications may have their unique features as it applies to customer network and connectivity to the cloud, they all share some key principals, goals, and architecture patterns. Microsoft 365 is a distributed Software-as-a-Service (SaaS) cloud that provides productivity and collaboration scenarios through a diverse set of micro-services and applications, such as Exchange Online, SharePoint Online, Skype for Business Online, Microsoft Teams, Exchange Online Protection, Office in a browser, and many others. The Microsoft 365 connectivity test, a new tool for testing basic connectivity to Microsoft 365.Incremental optimization options for Microsoft 365 traffic.Comparing network perimeter security with endpoint security.New Office 365 endpoint categories and optimization guidance.The Office 365 Endpoints web service, which allows network administrators to consume a structured list of endpoints for use in network optimization.
Updated Microsoft 365 connectivity principles and strategies for optimizing network traffic and the end-user experience.Microsoft 365 architecture as it applies to customer connectivity to the cloud.You can ensure the best Microsoft 365 performance and reliability by understanding and implementing key optimization guidelines. Without optimization, traffic between users and SaaS applications is subject to latency introduced by packet inspection, network hairpins, inadvertent connections to geographically distant endpoints and other factors. The traditional model assumes that users will access applications and data from inside the corporate network perimeter, over WAN links from branch offices, or remotely over VPN connections.Īdoption of SaaS applications like Microsoft 365 moves some combination of services and data outside the network perimeter. Traditional enterprise networks are designed primarily to provide users access to applications and data hosted in company operated datacenters with strong perimeter security. This article will help you understand the most recent guidance for securely optimizing Microsoft 365 network connectivity. This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.īefore you begin planning your network for Microsoft 365 network connectivity, it is important to understand the connectivity principles for securely managing Microsoft 365 traffic and getting the best possible performance.
0 kommentar(er)
