Operation could not be completed as it results in exceeding approved standardBSFamily Cores quota.

Products

• VMware Tanzu Platform

Issue/Introduction

 Ops manager 3.0.39 update is failing with vmcreation issue. In the error output provided by the customer it has the following.

"Operation could not be completed as it results in exceeding approved standardBSFamily Cores quota. Additional details - Deployment Model: Resource Manager, Location: northcentralus, Current Limit: 10, Current Usage: 10, Additional Required: 2, (Minimum) New Limit Required: 12.

Resolution

Customer experiences vmcreation issue failed with the following errors because of quota limit is reached. Please request quota increase in your Azure account.

"Operation could not be completed as it results in exceeding approved standardBSFamily Cores quota. Additional details - Deployment Model: Resource Manager, Location: northcentralus, Current Limit: 10, Current Usage: 10, Additional Required: 2, (Minimum) New Limit Required: 12.

After increasing the resource quota, customer has followed the below steps to migrate unmanaged to managed disks. customer is still seeing the disks under storage account after migrating the disks. 
Migrating from Storage Accounts to Managed Disks on Azure

The migration won't remove the unmanaged disk automatically.

When customer trying to upgrade the opsman version to 3.0.40 but customer is seeing the below errors on azure platform. 

Failed to retrieve image alias doc 'https://raw.githubusercontent.com/Azure/azure-rest-api-specs/main/arm-compute/quickstart-templates/aliases.json'. Error: 'ConnectionError'. Use local copy instead.

Regarding this warning Failed to retrieve image alias doc 'https://raw.githubusercontent.com/Azure/azure-rest-api-specs/main/arm-compute/quickstart-templates/aliases.json'. Error: 'ConnectionError'. Use local copy instead.

From the Microsoft docs, it is a quickstart template to discover resources to deploy, this is related to Azure though not the platform. If you want more details you would need to reach out Azure

While performing the apply changes, customer saw the following erros
Values for request parameters are invalid: encryption.keyvaultproperties.keyversion.
It is failing to create the stemcell because the keyversion field is missing