Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
6,307 questions
Why is my disk no longer getting created when using a different VM SKU with my Azure template?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 40%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESL%3C/text%3E%3C/svg%3E)
Seth LeBlanc
5
Reputation points
My company has been using template specs to create VM's in Azure, and the templates are set to use VM SKU's that are no longer available in most regions (specifically the Standard_B1s in this case). So I've been trying to update our templates to include SKU options that are compatible with all/most regions, but when I actually try to deploy a VM using one of the new SKU options (I've tried Standard_B2ts_v2 & Standard_B2ats_v2), I get the error "Your deployment failed - Disk <diskname> is not found".
If I wipe the resource group and recreate in a region where the original SKU's are still compatible, the VM deploys without issue. I've been combing through the template trying to understand how the disk gets generated and what could be causing the error, but I'm not having much luck. When I try to generate a support request, I just get links to various MS documentation as proposed solutions but never an actual option for real tech support.
Any assistance would be greatly appreciated.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 4%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
kobulloc-MSFT 18,966 Reputation points Microsoft Employee2023-10-27T05:49:46.7766667+00:00 Hello, @Seth LeBlanc !
An initial look at this points to an issue with the updated template (usually I would expect to see
SkuNotAvailableorInvalidTemplateDeploymentfor a SKU that's not available). Are you able to share the template here (or email it to us at azcommunity@microsoft.com)? -
Seth LeBlanc 5 Reputation points
2023-10-27T13:56:28.9666667+00:00 Hi @kobulloc-MSFT thanks for responding! I'll email it to you shortly.
-
kobulloc-MSFT 18,966 Reputation points Microsoft Employee
2023-10-31T07:44:39.74+00:00 Quick summary so far: It looks like this may be limited to the Bv2 VMs. Investigating this further.
-
kobulloc-MSFT 18,966 Reputation points Microsoft Employee
2023-11-02T22:44:47.3433333+00:00 Summary so far:
- Are the B1s VMs being retired? There are no retirement announcements for the B series at this time. The A-Series is being retired in August of 2024 (and coincidentally Windows Server 2012/R2 was just retired on Azure which makes deploying Windows Server on a B1s more difficult) however only the A-Series is being retired at this time.
- Standard_D2s_v3 works, why? The B series is unique in that the B1s is available free to student subscriptions whereas the Dv3 series targets enterprise-grade applications, relational databases, and analytics. The Dv3 series is reserved for production workloads.
- Quotas? Usually we see a different error related to quotas, however this is the first thing the virtual machine group mentioned when reviewing this scenario. Let's confirm that you have available quota in the vCPU family and region you are trying to deploy.
-
kobulloc-MSFT 18,966 Reputation points Microsoft Employee
2023-11-04T00:27:34+00:00 Update:
- Quotas appear to be available for both the VM family and the region.
- We are seeing availability errors which is not expected for B1s in South Central US
- In one instance, we've seen an availability error even though the VM does deploy (with errors)
Sign in to comment