We build and run Azure DevOps pipelines every day, so we keep an eye on what Microsoft changes underneath them. Most months that’s minor. This month has three changes actually worth knowing about, whether or not you’re changing anything in response.

Managed DevOps Pools can now mix VM sizes

If you’ve used Managed DevOps Pools, you’ll know the pool is normally pinned to a single VM size. That’s fine until that specific size is under regional capacity pressure and your provisioning starts failing or queuing at the worst possible time.

Instance Mix, rolling out this month, lets a single pool define up to five VM sizes instead of one. It’s built on Azure Virtual Machine Scale Sets’ own Instance Mix capability, and the practical effect is simple: if your preferred size isn’t available, the pool can fall back to another one automatically instead of your pipeline just sitting there waiting. For anyone who has had a release blocked by a capacity error at 5pm on a Friday, this is a welcome bit of resilience for free.

Windows ARM64 self-hosted agents: public preview

The Windows ARM64 agent is now in public preview, bringing native ARM64 support to Azure Pipelines self-hosted agents on Windows 11. If you’re evaluating ARM-based hardware for build machines, whether for cost, power efficiency, or just what’s actually available to buy right now, you can finally point Azure Pipelines at it directly rather than running under emulation.

It’s a public preview, so we wouldn’t move a production build fleet onto it this week. But it’s worth a test pool if ARM hardware is on your radar.

A deprecation to check now if you’re on-prem

This one’s a genuine “check this before it bites you” item, not just news. NTLM support is being removed from libcurl, the library Git uses for HTTPS operations, in September 2026. If your Azure DevOps setup is on-prem (Azure DevOps Server, not the cloud service) and your team authenticates Git-over-HTTPS using NTLM, those operations will simply stop working once that change lands.

If that’s you, the fix is straightforward: move affected clients to a Personal Access Token or another supported HTTPS auth method before September, rather than finding out the hard way when a clone or fetch starts failing. If you’re not sure whether this affects you, it’s a five minute check now against a much worse afternoon later.

Also worth watching

A couple of items further out on the Managed DevOps Pools roadmap, both planned for later in 2026: Spot Virtual Machine support (useful for non-time-critical CI/CD jobs, where the cost saving can run up to 90%), and native container agents. Neither is available yet, but both are worth knowing about if you’re planning pipeline infrastructure changes further ahead.

None of this changes what a working pipeline actually needs to do, but it’s exactly the kind of thing we track so the pipelines we hand over stay current rather than quietly rotting. If you’d rather have someone else keep an eye on this and handle it for you, that’s what a support pack is for, or just get in touch if something here affects an environment you’re running.