OCPBUGS-16610: Updated UPI info in Azure account limits module

Author: dfitzmau

modules/installation-about-custom-azure-vnet.adoc

@@ -45,6 +45,12 @@ Your VNet must meet the following characteristics:
 
 You must provide two subnets within your VNet, one for the control plane machines and one for the compute machines. Because Azure distributes machines in different availability zones within the region that you specify, your cluster will have high availability by default.
 
+[NOTE]
+====
+By default, if you specify availability zones in the `install-config.yaml` file, the installation program distributes the control plane machines and the compute machines across link:https://azure.microsoft.com/en-us/global-infrastructure/availability-zones/[these availability zones]
+within link:https://azure.microsoft.com/en-us/global-infrastructure/regions[a region]. To ensure high availability for your cluster, select a region with at least three availability zones. If your region contains fewer than three availability zones, the installation program places more than one control plane machine in the available zones.
+====
+
 To ensure that the subnets that you provide are suitable, the installation program confirms the following data:
 
 * All the specified subnets exist.

modules/installation-azure-limits.adoc

@@ -109,17 +109,6 @@ To deploy more worker nodes, enable autoscaling, deploy large workloads, or use
 a different instance type, you must further increase the vCPU limit for your
 account to ensure that your cluster can deploy the machines that you require.
 
-ifndef::ash[]
-By default, the installation program distributes control plane and compute machines across
-link:https://azure.microsoft.com/en-us/global-infrastructure/availability-zones/[all availability zones]
-within
-link:https://azure.microsoft.com/en-us/global-infrastructure/regions[a region].
-To ensure high availability for your cluster, select a region with at least
-three availability zones. If your region contains fewer than three availability
-zones, the installation program places more than one control plane machine in the
-available zones.
-endif::ash[]
-
 ifndef::ash[]
 |OS Disk
 |7

modules/installation-configuration-parameters.adoc

@@ -1068,7 +1068,13 @@ ifdef::azure[]
 [id="installation-configuration-parameters-additional-azure_{context}"]
 == Additional Azure configuration parameters
 
-Additional Azure configuration parameters are described in the following table:
+Additional Azure configuration parameters are described in the following table.
+
+[NOTE]
+====
+By default, if you specify availability zones in the `install-config.yaml` file, the installation program distributes the control plane machines and the compute machines across link:https://azure.microsoft.com/en-us/global-infrastructure/availability-zones/[these availability zones]
+within link:https://azure.microsoft.com/en-us/global-infrastructure/regions[a region]. To ensure high availability for your cluster, select a region with at least three availability zones. If your region contains fewer than three availability zones, the installation program places more than one control plane machine in the available zones.
+====
 
 .Additional Azure parameters
 [cols=".^2,.^3a,.^3a",options="header"]

modules/installation-creating-azure-control-plane.adoc

@@ -20,13 +20,14 @@ You must create the control plane machines in Microsoft {cp} for your cluster
 to use. One way to create these machines is to modify the provided Azure
 Resource Manager (ARM) template.
 
+ifdef::azure[]
 [NOTE]
 ====
-If you do not use the provided ARM template to create your control plane
-machines, you must review the provided information and manually create the
-infrastructure. If your cluster does not initialize correctly, you might have to
-contact Red Hat support with your installation logs.
+By default, Microsoft {cp} places control plane machines and compute machines in a pre-set availability zone. You can manually set an availability zone for a compute node or control plane node. To do this, modify a vendor's Azure Resource Manager (ARM) template by specifying each of your availability zones in the `zones` parameter of the virtual machine resource.
 ====
+endif::azure[]
+
+If you do not use the provided ARM template to create your control plane machines, you must review the provided information and manually create the infrastructure. If your cluster does not initialize correctly, consider contacting Red Hat support with your installation logs.
 
 .Prerequisites
 

modules/installation-creating-azure-worker.adoc

@@ -33,13 +33,14 @@ In this example, you manually launch one instance by using the Azure Resource
 Manager (ARM) template. Additional instances can be launched by including
 additional resources of type `06_workers.json` in the file.
 
+ifdef::azure[]
 [NOTE]
 ====
-If you do not use the provided ARM template to create your worker machines, you
-must review the provided information and manually create the infrastructure. If
-your cluster does not initialize correctly, you might have to contact Red Hat
-support with your installation logs.
+By default, Microsoft {cp} places control plane machines and compute machines in a pre-set availability zone. You can manually set an availability zone for a compute node or control plane node. To do this, modify a vendor's ARM template by specifying each of your availability zones in the `zones` parameter of the virtual machine resource.
 ====
+endif::azure[]
+
+If you do not use the provided ARM template to create your control plane machines, you must review the provided information and manually create the infrastructure. If your cluster does not initialize correctly, consider contacting Red Hat support with your installation logs.
 
 .Prerequisites