As a developer, I can deploy Azure service to support a multi-region infrastructure

[James-Nance]

Description

As a developer, I can deploy Azure services to support a multi-region infrastructure

This should incorporate a simple Terraform manifest that references:

1x Bedrock/Traffic Manager profile

Region 1 1xColbalt/App Gateway 1xCobalt/App Service 1xCobalt/Service Plan 1xColbalt/API Management 1xBedrock/Backend 1xBedrock/Vnet module - Will require two subnets: 1. app gateway 2. APIM. 1xBedrock/Traffic Manager Public Endpoint module - this should reference the traffic manager profile

Region 2 1xColbalt/App Gateway 1xCobalt/App Service 1xCobalt/Service Plan 1xColbalt/API Management 1xBedrock/Backend 1xBedrock/Vnet module - Will require two subnets: 1. app gateway 2. APIM. 1xBedrock/Traffic Manager Public Endpoint module - this should reference the traffic manager profile

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

• [ ] Screen shot of Azure services running in Azure Portal
• [ ] test/reference "Hello World" web app is accessible
• [ ] …

Also, here are a few points that need to be addressed:

1. Should use Terraform
2. Should contain any variables for Azure services

Resources

Tasks

Stories are intended to be completed in a single sprint; if task breakdown creates addition work then team should discuss promoting the Story to an Epic. Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)

Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)

Assignee should break down work into tasks here