Merge pull request #113027 from MikeDodaro/disasterRecovery

Add section to document per PR 112111, story 1709722

Author: PMEds28

articles/spring-cloud/disaster-recovery.md

@@ -26,4 +26,34 @@ Ensuring high availability and protection from disasters requires that you deplo
 
 [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md) provides DNS-based traffic load-balancing and can distribute network traffic across multiple regions.  Use Azure Traffic Manager to direct customers to the closest Azure Spring Cloud service instance to them.  For best performance and redundancy, direct all application traffic through Azure Traffic Manager before sending it to your Azure Spring Cloud service.
 
-If you have Azure Spring Cloud applications in multiple regions, use Azure Traffic Manager to control the flow of traffic to your applications in each regions.  Define an Azure Traffic Manager endpoint for each service using the service IP. Customers should connect to an Azure Traffic Manager DNS name pointing to the Azure Spring Cloud service.  Azure Traffic Manager load balances traffic across the defined endpoints.  If a disaster strikes a data center, Azure Traffic Manager will direct traffic from that region to its pair, ensuring service continuity.
+If you have Azure Spring Cloud applications in multiple regions, use Azure Traffic Manager to control the flow of traffic to your applications in each region.  Define an Azure Traffic Manager endpoint for each service using the service IP. Customers should connect to an Azure Traffic Manager DNS name pointing to the Azure Spring Cloud service.  Azure Traffic Manager load balances traffic across the defined endpoints.  If a disaster strikes a data center, Azure Traffic Manager will direct traffic from that region to its pair, ensuring service continuity.
+
+## Create Azure Traffic Manager for Azure Spring Cloud
+
+1. Create Azure Spring Cloud in two different regions.
+You will need two service instances of Azure Spring Cloud deployed in two different regions (East US and West Europe). Launch an existing Azure Spring Cloud application using the Azure portal to create two service instances. Each will serve as primary and fail-over endpoint for Traffic. 
+
+**Two service instances info:**
+
+| Service Name | Location | Application |
+|--|--|--|
+| service-sample-a | East US | gateway / auth-service / account-service |
+| service-sample-b | West Europe | gateway / auth-service / account-service |
+
+2. Set up Custom Domain for Service
+Follow [Custom Domain Document](/articles/spring-cloud/spring-cloud-tutorial-custom-domain.md) to set up custom domain for these two existing service instances. After successful set up, both service instances will bind to custom domain: bcdr-test.contoso.com
+
+3. Create a traffic manager and two endpoints: [Create a Traffic Manager profile using the Azure portal](https://docs.microsoft.com/azure/traffic-manager/quickstart-create-traffic-manager-profile).
+
+Here is the traffic manager profile:
+* Traffic Manager DNS Name: http://asc-bcdr.trafficmanager.net
+* Endpoint Profiles: 
+
+| Profile | Type | Target | Priority | Custom Header Settings |
+|--|--|--|--|--|
+| Endpoint A Profile | External Endpoint | service-sample-a.asc-test.net | 1 | host: bcdr-test.contoso.com |
+| Endpoint B Profile | External Endpoint | service-sample-b.asc-test.net | 2 | host: bcdr-test.contoso.com |
+
+4. Create a CNAME record in DNS Zone: bcdr-test.contoso.com CNAME asc-bcdr.trafficmanager.net. 
+
+5. Now, the environment is completely set up. Customers should be able to access the app via: bcdr-test.contoso.com