May 2019 Content Update

[microsoft]

May 2019 Content Update

[DawnmarieDesJardins]

@deltadan
Hi Dan, Please move forward with your suggested updates.

[deltadan]

The following are the recommendations for the BCDR Update:

1. Move the Azure automation from the current version of AzureRM Powershell to AzureAz. This is a natural evolution to keep up with the change in the PowerShell Cmdlets.

2. Move from Availablity Sets for the VMs to Availability Zones - this is a huge leap in protection for the solution. This requirement will be surfaced in the scenario by the customer. Given that their solution is deployed to one region and uses ASR using AZs allowed for an additional level of reliability that is missing from the current version of the solution.
   https://azure.microsoft.com/en-us/updates/disaster-recovery-for-virtual-machines-deployed-in-availability-zones-to-another-region/

3. Replace Traffic Manager for the PaaS solution with Frontdoor. By adding Frontdoor and removing Traffic Manager we add much more capability to the solution for the customer. TM only routes traffic to the POPs based on DNS - with Frontdoor we have more capabilities such as geo-filtering, SSL offload, and WAF rules at a global scale.
   https://docs.microsoft.com/en-us/azure/frontdoor/front-door-overview

[cesarfong]

Review the scripts BCDROnPremPrimarySite.json is throwing error

[DawnmarieDesJardins]

Closing with May 2019 content update merge

[deltadan]

Review the scripts BCDROnPremPrimarySite.json is throwing error

this was resolved with the last PR.