Merge pull request #111534 from rolyon/rolyon-availability-zones-regions

[Azure Infrastructure] Regions and Availability Zones

Author: v-shils

articles/application-gateway/application-gateway-autoscaling-zone-redundant.md

@@ -18,7 +18,7 @@ The new v2 SKU includes the following enhancements:
 - **Autoscaling**: Application Gateway or WAF deployments under the autoscaling SKU can scale up or down based on changing traffic load patterns. Autoscaling also removes the requirement to choose a deployment size or instance count during provisioning. This SKU offers true elasticity. In the Standard_v2 and WAF_v2 SKU, Application Gateway can operate both in fixed capacity (autoscaling disabled) and in autoscaling enabled mode. Fixed capacity mode is useful for scenarios with consistent and predictable workloads. Autoscaling mode is beneficial in applications that see variance in application traffic.
 - **Zone redundancy**: An Application Gateway or WAF deployment can span multiple Availability Zones, removing the need to provision separate Application Gateway instances in each zone with a Traffic Manager. You can choose a single zone or multiple zones where Application Gateway instances are deployed, which makes it more resilient to zone failure. The backend pool for applications can be similarly distributed across availability zones.
 
-  Zone redundancy is available only where Azure Zones are available. In other regions, all other features are supported. For more information, see [What are Availability Zones in Azure?](../availability-zones/az-overview.md#services-support-by-region)
+  Zone redundancy is available only where Azure Zones are available. In other regions, all other features are supported. For more information, see [Regions and Availability Zones in Azure](../availability-zones/az-overview.md)
 - **Static VIP**: Application Gateway v2 SKU supports the static VIP type exclusively. This ensures that the VIP associated with the application gateway doesn't change for the lifecycle of the deployment, even after a restart.  There isn't a static VIP in v1, so you must use the application gateway URL instead of the IP address for domain name routing to App Services via the application gateway.
 - **Header Rewrite**: Application Gateway allows you to add, remove, or update HTTP request and response headers with v2 SKU. For more information, see [Rewrite HTTP headers with Application Gateway](rewrite-http-headers.md)
 - **Key Vault Integration**: Application Gateway v2 supports integration with Key Vault for server certificates that are attached to HTTPS enabled listeners. For more information, see [TLS termination with Key Vault certificates](key-vault-certs.md).
@@ -170,7 +170,7 @@ The following table compares the features available with each SKU.
 |Billing|Billing scheduled to start on July 1, 2019.|
 |FIPS mode|These are currently not supported.|
 |ILB only mode|This is currently not supported. Public and ILB mode together is supported.|
-|Netwatcher integration|Not supported.|
+|Net watcher integration|Not supported.|
 |Azure Security Center integration|Not yet available.
 
 ## Migrate from v1 to v2

articles/availability-zones/TOC.yml

@@ -8,10 +8,12 @@
   items:
   - name: High availability for Azure applications
     href: https://docs.microsoft.com/azure/architecture/resiliency/high-availability-azure-applications
+  - name: Regions and Availability Zones
+    href: az-overview.md
   - name: Availability Zones Documentation
     items:
-    - name: What are Availability Zones?
-      href: az-overview.md
+    - name: Regions that support Availability Zones
+      href: az-region.md
     - name: Virtual machines
       items:
       - name: Create a Linux VM in an Availability Zone with CLI

articles/availability-zones/az-overview.md

@@ -0,0 +1,57 @@
+---
+title: Regions that support Availability Zones in Azure
+description: To create highly available and resilient applications in Azure, Availability Zones provide physically separate locations you can use to run your resources.
+author: cynthn
+ms.service: azure
+ms.topic: article
+ms.date: 04/27/2020
+ms.author: cynthn
+ms.custom: fasttrack-edit, mvc
+---
+
+# Regions that support Availability Zones in Azure
+
+Availability Zones is a high-availability offering that protects your applications and data from datacenter failures. For more information about Availability Zones, see [Regions and Availability Zones in Azure](az-overview.md).
+
+## Services support by region
+
+This section lists the Azure services and regions that support Availability Zones.
+
+Services that are available in each region, along with upcoming roadmap for availability, can be found at [Products available by region](https://azure.microsoft.com/global-infrastructure/services/).
+
+|                                 |Americas |              |           |           | Europe |              |          |              | Asia Pacific |                 |                |
+|----------------------------|----------|----------|---------|---------|--------------|------------|--------|----------|----------|-------------|-------------|
+|          |Central US|East US|East US 2|West US 2|France Central|North Europe|UK South|West Europe|Japan East|Southeast Asia|Australia East|
+| **Compute**                         |            |              |           |           |                |              |          |             |            |                |                |
+| Linux Virtual Machines          | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓   | ✓       |                |
+| Windows Virtual Machines        | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓   | ✓       |                |
+| Virtual Machine Scale Sets      | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓   | ✓       |                |
+| Azure App Service Environments ILB | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓   | ✓       |                |
+| Azure Kubernetes Service        | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓   | ✓       |                |
+| **Storage**   |            |              |           |           |                |              |          |             |            |                |                |
+| Managed Disks                   | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓   | ✓       |                |
+| Zone-redundant Storage          | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓   | ✓       |                |
+| **Networking**                     |            |              |           |           |                |              |          |             |            |                |                |
+| Standard IP Address        | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓   | ✓       |                |
+| Standard Load Balancer     | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓   | ✓       |                |
+| VPN Gateway            | ✓   |  ✓    | ✓  | ✓  | ✓       | ✓     |  ✓  | ✓    |  ✓   | ✓       |                |
+| ExpressRoute Gateway   | ✓   |  ✓    | ✓  | ✓  | ✓       | ✓     |  ✓  | ✓    |  ✓   | ✓       |                |
+| Application Gateway(V2)    | ✓   |  ✓    | ✓  | ✓  | ✓       | ✓     |  ✓  | ✓    |  ✓   | ✓       |                |
+| Azure Firewall           | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    |  ✓       | ✓       |                |
+| **Databases**                     |            |              |           |           |                |              |          |             |            |                |                |
+| Azure Data Explorer                   | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    | ✓        | ✓       |                |
+| SQL Database                    | ✓   | ✓     | ✓  | ✓(Preview) | ✓       | ✓(Preview)     | ✓ | ✓    | ✓       | ✓       |✓        |
+| Azure Cache for Redis           | ✓   | ✓     | ✓  | ✓  | ✓       | ✓     | ✓ | ✓    |  ✓       | ✓       |                |
+| Azure Cosmos DB                    | ✓   |  ✓  |  ✓ | ✓ |       |     | ✓ |  ✓   |            | ✓       |                |
+| **Analytics**                       |            |              |           |           |                |              |          |             |            |                |                |
+| Event Hubs                      | ✓   |   ✓ | ✓  | ✓  | ✓ | ✓ | ✓ | ✓ | ✓ | ✓       |                |
+| **Integration**                     |            |              |           |           |                |              |          |             |            |                |                |
+| Service Bus (Premium Tier Only) | ✓   |  ✓  | ✓  | ✓  | ✓  | ✓     |✓   | ✓    |✓      | ✓       |                |
+| Event Grid | ✓   |  ✓  | ✓  | ✓  | ✓  | ✓     |✓   | ✓    |✓      | ✓       |                |
+| **Identity**                     |            |              |           |           |                |              |          |             |            |                |                |
+| Azure AD Domain Services | ✓   |  ✓  | ✓  | ✓  | ✓  | ✓     |✓   | ✓    |✓      | ✓       |                |
+
+
+## Next steps
+
+- [Regions and Availability Zones in Azure](az-overview.md)

articles/availability-zones/az-region.md

@@ -126,7 +126,7 @@ Note the following considerations to keep in mind with this release:
 The Event Hubs Standard SKU supports [Availability Zones](../availability-zones/az-overview.md), providing fault-isolated locations within an Azure region. 
 
 > [!NOTE]
-> The Availability Zones support for Azure Event Hubs Standard is only available in [Azure regions](../availability-zones/az-overview.md#services-support-by-region) where availability zones are present.
+> The Availability Zones support for Azure Event Hubs Standard is only available in [Azure regions](../availability-zones/az-region.md) where availability zones are present.
 
 You can enable Availability Zones on new namespaces only, using the Azure portal. Event Hubs does not support migration of existing namespaces. You cannot disable zone redundancy after enabling it on your namespace.
 

articles/event-hubs/event-hubs-geo-dr.md

@@ -35,12 +35,12 @@ You can also associate Azure Firewall to a specific zone just for proximity reas
 
 There's no additional cost for a firewall deployed in an Availability Zone. However, there are additional costs for inbound and outbound data transfers associated with Availability Zones. For more information, see [Bandwidth pricing details](https://azure.microsoft.com/pricing/details/bandwidth/).
 
-Azure Firewall Availability Zones are available in regions that support Availability Zones. For more information, see [What are Availability Zones in Azure?](../availability-zones/az-overview.md#services-support-by-region)
+Azure Firewall Availability Zones are available in regions that support Availability Zones. For more information, see [Regions that support Availability Zones in Azure](../availability-zones/az-region.md)
 
 > [!NOTE]
 > Availability Zones can only be configured during deployment. You can't configure an existing firewall to include Availability Zones.
 
-For more information about Availability Zones, see [What are Availability Zones in Azure?](../availability-zones/az-overview.md)
+For more information about Availability Zones, see [Regions and Availability Zones in Azure](../availability-zones/az-overview.md)
 
 ## Unrestricted cloud scalability
 

articles/firewall/overview.md

@@ -55,7 +55,7 @@ First, create a public Standard load balancer that can balance traffic load over
     |Availability zone| Select **Zone redundant**.    |
      
     >[!NOTE]
-     >Make sure to create your Load Balancer and all resources for it in a location that supports Availability Zones. For more information, see [Regions that support Availability Zones](../availability-zones/az-overview.md#services-support-by-region). 
+     >Make sure to create your Load Balancer and all resources for it in a location that supports Availability Zones. For more information, see [Regions that support Availability Zones](../availability-zones/az-region.md). 
 
 3. In the **Review + create** tab, click **Create**.  
 

articles/load-balancer/tutorial-load-balancer-port-forwarding-portal.md

@@ -137,7 +137,7 @@ Note the following considerations to keep in mind with this release:
 The Service Bus Premium SKU also supports [Availability Zones](../availability-zones/az-overview.md), providing fault-isolated locations within an Azure region.
 
 > [!NOTE]
-> The Availability Zones support for Azure Service Bus Premium is only available in [Azure regions](../availability-zones/az-overview.md#services-support-by-region) where availability zones are present.
+> The Availability Zones support for Azure Service Bus Premium is only available in [Azure regions](../availability-zones/az-region.md) where availability zones are present.
 
 You can enable Availability Zones on new namespaces only, using the Azure portal. Service Bus does not support migration of existing namespaces. You cannot disable zone redundancy after enabling it on your namespace.
 

articles/service-bus-messaging/service-bus-geo-dr.md

@@ -33,7 +33,7 @@ Service Bus Premium supports Geo-disaster recovery, at the namespace level. For
 The Service Bus Premium SKU supports [Availability Zones](../availability-zones/az-overview.md), providing fault-isolated locations within the same Azure region. Service Bus manages three copies of messaging store (1 primary and 2 secondary). Service Bus keeps all the three copies in sync for data and management operations. If the primary copy fails, one of the secondary copies is promoted to primary with no perceived downtime. If the applications see transient disconnects from Service Bus, the retry logic in the SDK will automatically reconnect to Service Bus. 
 
 > [!NOTE]
-> The Availability Zones support for Azure Service Bus Premium is only available in [Azure regions](../availability-zones/az-overview.md#services-support-by-region) where availability zones are present.
+> The Availability Zones support for Azure Service Bus Premium is only available in [Azure regions](../availability-zones/az-region.md) where availability zones are present.
 
 You can enable Availability Zones on new namespaces only, using the Azure portal. Service Bus does not support migration of existing namespaces. You cannot disable zone redundancy after enabling it on your namespace.
 

articles/service-bus-messaging/service-bus-outages-disasters.md

@@ -10,7 +10,7 @@ ms.custom: MVC
 ---
 
 # Move Azure VMs into Availability Zones
-Availability Zones in Azure help protect your applications and data from datacenter failures. Each Availability Zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there’s a minimum of three separate zones in all enabled regions. The physical separation of Availability Zones within a region helps protect applications and data from datacenter failures. With Availability Zones, Azure offers a service-level agreement (SLA) of 99.99% for uptime of virtual machines (VMs). Availability Zones are supported in select regions, as mentioned in [What are Availability Zones in Azure?](https://docs.microsoft.com/azure/availability-zones/az-overview#services-support-by-region).
+Availability Zones in Azure help protect your applications and data from datacenter failures. Each Availability Zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there’s a minimum of three separate zones in all enabled regions. The physical separation of Availability Zones within a region helps protect applications and data from datacenter failures. With Availability Zones, Azure offers a service-level agreement (SLA) of 99.99% for uptime of virtual machines (VMs). Availability Zones are supported in select regions, as mentioned in [Regions that support Availability Zones](https://docs.microsoft.com/azure/availability-zones/az-region).
 
 In a scenario where your VMs are deployed as *single instance* into a specific region, and you want to improve your availability by moving these VMs into an Availability Zone, you can do so by using Azure Site Recovery. This action can further be categorized into:
 
@@ -22,7 +22,7 @@ In a scenario where your VMs are deployed as *single instance* into a specific r
 
 ## Check prerequisites
 
-- Check whether the target region has [support for Availability Zones](https://docs.microsoft.com/azure/availability-zones/az-overview#services-support-by-region). Check that your choice of [source region/target region combination is supported](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-support-matrix#region-support). Make an informed decision on the target region.
+- Check whether the target region has [support for Availability Zones](https://docs.microsoft.com/azure/availability-zones/az-region). Check that your choice of [source region/target region combination is supported](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-support-matrix#region-support). Make an informed decision on the target region.
 - Make sure that you understand the [scenario architecture and components](azure-to-azure-architecture.md).
 - Review the [support limitations and requirements](azure-to-azure-support-matrix.md).
 - Check account permissions. If you just created your free Azure account, you're the admin of your subscription. If you aren't the subscription admin, work with the admin to assign the permissions you need. To enable replication for a VM and eventually copy data to the target by using Azure Site Recovery, you must have:
@@ -80,7 +80,7 @@ The following steps will guide you when using Azure Site Recovery to enable repl
 
 1. In the Azure portal, select **Virtual machines**, and select the VM you want to move into Availability Zones.
 2. In **Operations**, select **Disaster recovery**.
-3. In **Configure disaster recovery** > **Target region**, select the target region to which you'll replicate. Ensure this region [supports](https://docs.microsoft.com/azure/availability-zones/az-overview#services-support-by-region) Availability Zones.
+3. In **Configure disaster recovery** > **Target region**, select the target region to which you'll replicate. Ensure this region [supports](https://docs.microsoft.com/azure/availability-zones/az-region) Availability Zones.
 
     ![Selection of target region](media/azure-vms-to-zones/enable-rep-1.PNG)