Merge pull request Azure#626 from Azure/canary

Canary

Author: likamrat

docs/azure_jumpstart_hcibox/deployment_az/_index.md

@@ -13,6 +13,8 @@ Azure Bicep is used to deploy HCIBox into your Azure subscription. To deploy, yo
 
 ### Prepare the environment
 
+> **Note:** HCIBox can be deployed in the East US, Australia East, Canada Central and West Europe Azure regions. Deploying in other regions will result in unexpected behavior or failures. It requires 32 ESv5-series vCPUs when deploying with default parameters such as VM series/size. Ensure you have sufficient vCPU quota available in your Azure subscription and the region where you plan to deploy HCIBox. You can use the below Az CLI command to check your vCPU utilization.
+
 - Clone the Arc Jumpstart GitHub repository
 
   ```shell
@@ -29,8 +31,6 @@ Azure Bicep is used to deploy HCIBox into your Azure subscription. To deploy, yo
 
 - Ensure that you have selected the correct subscription you want to deploy HCIBox to by using the *`az account list --query "[?isDefault]"`* command. If you need to adjust the active subscription used by Az CLI, follow [this guidance](https://learn.microsoft.com/cli/azure/manage-azure-subscriptions-azure-cli#change-the-active-subscription).
 
-- **HCIBox requires 32 ESv5-series vCPUs** when deploying with default parameters such as VM series/size. Ensure you have sufficient vCPU quota available in your Azure subscription and the region where you plan to deploy HCIBox. You can use the below Az CLI command to check your vCPU utilization.
-
   ```shell
   az vm list-usage --location <your location> --output table
   ```
@@ -151,8 +151,6 @@ Example parameter-file:
 
   ![Screenshot showing bicep deploying](./bicep_deploying.png)
 
-    > **Note:** HCIBox can be deployed in East US, Australia East, Canada Central and West Europe. Deploying in other regions will result in unexpected behavior or failures.
-
 ## Start post-deployment automation
 
 Once your deployment is complete, you can open the Azure portal and see the initial HCIBox resources inside your resource group. Now you must remote into the *HCIBox-Client* VM to continue the next phase of the deployment. [Continue to learn how to deploy instance in Azure portal](../cloud_deployment/#azure-local-instance-validation-and-deployment-from-the-azure-portal) for the next steps.