B1-series (burstable) VMs are part of the Azure B-family general purpose sizes. If B1 sizes (such as Standard_B1s/B1ms) are not selectable in the portal for a Pay-As-You-Go subscription, the usual causes are:
- The Bv1/B-series in that region are treated as previous-generation or restricted
- The series is not enabled for that subscription/region/zone
To proceed:
- Confirm that B-series is available
- Bv1 sizes are a previous-generation series. For many regions, newer B-family sizes are recommended instead. See the B-family overview to confirm which B-series are available and supported.
- If Bv1/B1 sizes are not listed for the region, select a newer B-family size instead.
- Request access if the series is restricted or zonal-only
- If the B-series appears as restricted or only in specific availability zones, submit a zonal enablement request so the series can be used in the desired zone:
- In the Azure portal, go to Help + support → Create a support request.
- In Describe your issue, type
quotasand select Service and Subscription Limits (quotas). - Set Issue type to Service and Subscription Limits (quotas), choose the correct Subscription, and set Quota type to Compute-VM (cores-vCPUs) subscription limit increases.
- Under Problem details, select Enter details.
- Set Deployment model to Resource Manager.
- Under Choose request types, select Zone access.
- In Request details, choose the Locations (regions) and the requested logical zone(s) where B-series should be enabled.
- Select the B-series VM family you want (for example, the B-series that includes B1 sizes).
- Save, then continue to Review and create and submit the request.
- After approval, B-series should become selectable in that region/zone for the subscription.
- If the B-series appears as restricted or only in specific availability zones, submit a zonal enablement request so the series can be used in the desired zone:
- If still unavailable
- If, after enablement, B1 sizes still do not appear, choose another B-family size that is listed for that region or move the VM deployment to a region where B1/Bv1 is available.
References: