Update Cloud Guide to reflect Azure IaaS support

src/cloud/architecture/pro-architecture.md

@@ -119,7 +119,7 @@ The three gateways map to the three servers in your Production environment clust
 
 ### Backup and disaster recovery
 
-Your Pro plan backup and recovery approach uses a high-availability architecture combined with full-system backups. We replicate each Project—all data, code, and assets—across three separate AWS Availability Zones, each zone with a separate data center.
+Your Pro plan backup and recovery approach uses a high-availability architecture combined with full-system backups. We replicate each Project—all data, code, and assets—across three separate AWS or Azure Availability Zones, each zone with a separate data center.
 
 In addition to the redundancy of the high-availability architecture, {{site.data.var.ece}} provides
 incremental backups, which include the file system and the database, every hour for the last 24 hours of operation. After the

src/cloud/bk-cloud.md

@@ -17,7 +17,9 @@ Think of the {{site.data.var.ece}} as five functional layers, as shown here:
 
 ![Cloud Stack]
 
-Amazon Web Services (AWS) powers the underlying Infrastructure as a Service (IaaS) for {{site.data.var.ece}}. Each {{site.data.var.ece}} plan provides a PaaS Integration environment for developing, testing, and integrating services, see [{{site.data.var.ece}} architecture]({{ site.baseurl }}/cloud/architecture/cloud-architecture.html) for a comparison and additional features. New Relic provides granular visibility into the site performance. [Fastly]({{ site.baseurl }}/cloud/cdn/cloud-fastly.html) caches site assets and, as customers access the site and stores, loads the cached assets fast. The [Fastly Image Optimization]({{ site.baseurl }}/cloud/cdn/fastly-image-optimization.html) (IO) offloads image processing and resizing load, freeing servers to process orders and conversions efficiently.
+Amazon Web Services (AWS) powers the underlying Infrastructure as a Service (IaaS) for {{site.data.var.ece}}. For {{site.data.var.ece}} Pro projects, you can choose either AWS or Microsoft Azure for IaaS support.
+
+Each {{site.data.var.ece}} plan provides a PaaS Integration environment for developing, testing, and integrating services, see [{{site.data.var.ece}} architecture]({{ site.baseurl }}/cloud/architecture/cloud-architecture.html) for a comparison and additional features. New Relic provides granular visibility into the site performance. [Fastly]({{ site.baseurl }}/cloud/cdn/cloud-fastly.html) caches site assets and, as customers access the site and stores, loads the cached assets fast. The [Fastly Image Optimization]({{ site.baseurl }}/cloud/cdn/fastly-image-optimization.html) (IO) offloads image processing and resizing load, freeing servers to process orders and conversions efficiently.
 <!-- Also, the Fastly Web Application Firewall (WAF) prevents malicious traffic and other OWASP Top 10 threats from affecting the site. -->
 
 ## {{site.data.var.ct}} package

src/cloud/cdn/configure-fastly.md

@@ -148,10 +148,10 @@ To review the backend settings configuration:
 
    ![Modify the backend]({{ site.baseurl }}/common/images/cloud/cloud_fastly-backend.png){:width="600px"}
 
-1. Select the **Shield** location (or datacenter) closest to your AWS region.
-   For example, if Staging is on the west coast of the United States (us-west-1), select the `sjc-ca-us` Fastly shield location. This is the POP that provides caching services.
+1. Select the **Shield** location (or datacenter) closest to your Cloud service region.
+   For example, if your project is hosted on AWS, Staging is on the west coast of the United States (us-west-1), select the `sjc-ca-us` Fastly shield location. This is the POP that provides caching services.
 
-   The following list shows which Fastly shield locations to use based an AWS region:
+   The following list shows which Fastly shield locations to use based on AWS regions:
 
    -  ap-east-1 => hongkong-hk
    -  ap-northeast-1 => tyo-tokyo-jp, hnd-tokyo-jp