SharePoint Server 2016 farm Deployment in Azure VM along with Traffic Manager
Many days ago, we had a project on how to build up SharePoint Server 2016 farm in Azure VM along with other resources such as Traffic Manager.
The Requirement from Customer:
- One Domain for the farms
- One main office and two branch offices in the different regions
- The end users only access the content from their own regions when typing the Common URL: http://www.contoso.com
In order to meet the requirements 1 & 2, at the same time, so it doesn't affect the SharePoint performance, we recommended that it is better to deploy three farms in different Azure datacenters. But the critical issue is how to ensure the end user can access the content from their own farm when typing the common URL: http://www.contoso.com.
It took us more than one week to research. Traffic Manager of Azure Resource can meet customer's requirement because geographic of four traffic routing methods can make sure users are directed to specific endpoints based on which geographic location their DNS query originates from.
When a region or a set of regions is assigned to an endpoint, any requests from those regions get routed only to that endpoint. Traffic Manager uses the source IP address of the DNS query to determine the region from which a user is querying from – usually this is the IP address of the local DNS resolver doing the query on behalf of the user.
So, the final design topology is below:
Microsoft Azure Traffic Manager allows you to control how network traffic is distributed to application deployments running in different datacenters. You configure each application deployment as an 'endpoint' in Traffic Manager. When Traffic Manager receives a DNS request, it chooses an available endpoint to return in the DNS response.
According to this project, the endpoints should be configured as follow:
If someone has a good solution, please share it. Much appreciated.