Advisory TRV3-YHG: does the 31 July 2026 restriction affect VM creation within existing approved quota?

Tom 20 Reputation points
2026-07-28T22:27:24.9633333+00:00

We received Service Health advisory TRV3-YHG on subscription 7befd81f-de40-4672-8b39-2bd880189764 https://app.azure.com/h/TRV3-YHG/7be764 . Two statements appear to conflict for our workload:

  • "new deployments ... will not be approved" vs
  • "does not affect: Existing deployments operating within Capacity currently allocated."

The advisory also states that this will take effect July 31, 2026. With full deprecation of these VM SKUs on July 31, 2028.

Our usage is highly ephemeral, where we may need to allocate ~1000-2000 'Standard_B1s' VMs within a few hours, and keep them running for several days before deleting them. We operate in the West US 2 region.

Our quota is Standard BS Family vCPUs = 3000.

  1. On 1 August 2026, will Standard_B1s VM creation in West US 2 still succeed on this subscription while we remain within our existing 3000-vCPU quota? Or will we potentially see an increase in allocation failures, due to restricted capacity?
  2. We need to know whether our existing Standard_B1s launches will keep working, or if we need to perform critical priority work to migrate them to a new instance type.

Thanks,

Tom Petit Staff Software Engineer @ CMDnCTRL Security

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments
Answer accepted by question author
TP 163.2K Reputation points Volunteer Moderator
2026-07-29T09:09:48.1633333+00:00

Hi Tom,

Adding to what Vinodh247-1375 has written.

I recommend you assume the worst (for your own safety) and thus modify your deployment pipelines, quota, etc., to use newer VM series. I've been trying to get clarification since you asked your question.

In the advisory, it has "will not be approved", whereas in the documentation, it has "might not approve". And what, precisely, is meant by "capacity expansion requests"? For example, if you have an existing Deallocated v1-v4 VM and you attempt to start it, that would seem to be an attempted expansion of your allocated capacity, so if you interpret the advisory text strictly, it "will not be approved".

I'm not saying they will actually enforce the text in this way, rather, I'm saying depending on how it is interpreted, they could.

Also, if you try to create new VMs, even though you have plenty of available quota, if you interpret the advisory text strictly these "new deployments" "will not be approved".

On the other hand, the sentence "Quota already approved in existing subscriptions for these VM series will not be affected." could lead you to believe that you may be able to create new VMs (assuming capacity is available) so long as you have available quota.

The above are not the only questions/scenarios that I have come up with in regards to this issue, but you get the idea. The documentation and advisory do not match each other, and the text is not precise enough for you to know what will or will not be approved or occur under real world circumstances, in my opinion.

Documentation was published on July 16th, advisory around the same, I received email sent on July 24th, so to me this is short notice.

Previous-generation VM size series capacity limitations and migration guidance

https://learn.microsoft.com/en-us/azure/virtual-machines/migration/sizes/previous-gen-series-capacity-limitations

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Was this answer helpful?

1 person found this answer helpful.

2 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Tom 20 Reputation points
    2026-07-29T20:46:22.86+00:00

    Upon submitting a support ticket, we received the following answer:

    “New deployments will not be approved” means that after July 31, 2026 any VM creation request for Standard_B1s in West US 2 will be rejected—even if you previously ran B1s VMs. “Existing deployments operating within capacity currently allocated” refers only to the VM instances that are running or allocated at the moment the retirement restriction takes effect. Deleting and recreating or scaling above that count is treated as a new deployment and is blocked. Ephemeral workflows that deallocate and then reallocate VMs dynamically will hit that block if they exceed the capacity that was allocated before the cutoff date.

    So it seems that the answer is that at least for ephemeral use cases like our, where our usage is extremely dynamic, we cannot continue to use the retired VM series.

    Was this answer helpful?

    0 comments
  2. Vinodh247-1375 44,716 Reputation points Volunteer Moderator
    2026-07-29T07:44:48.8766667+00:00

    Hi ,

    Thanks for reaching out to Microsoft Q&A.

    not guaranteed to keep working reliably.

    “Existing deployments within allocated capacity” means VMs that are already running are safe, but it does not guarantee future allocations, even if you are within your 3000 vCPU quota. After 31 July 2026, new VM creations (including your burst scaling of B1s) can be throttled, deprioritised, or fail due to capacity restrictions in West US 2, because the SKU is moving toward retirement and no new capacity is being approved.

    Given your pattern (rapidly spinning up 1000 to 2000 VM's), you should expect increasing allocation failures over time and should plan migration to a supported SKU (ex: B series successor or alternative burstable/general-purpose VM) rather than relying on current behaviour.

    Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.