A shorter one this week: one genuinely useful pipeline change, and a correction to something we said in last month’s roundup.

Call Azure DevOps REST APIs without a workaround service connection

Released in Sprint 277, the InvokeRESTAPI@1 task now supports an Azure DevOps service connection directly:

- task: InvokeRESTAPI@1
  inputs:
    connectionType: 'connectedServiceNameAzureDevOps'
    serviceConnection: '<your-azure-devops-service-connection>'
    method: 'GET'
    urlSuffix: '<organization>/<project>/_apis/build/builds?api-version=7.1'

If you’ve ever wanted a pipeline to call Azure DevOps’s own REST API, checking another pipeline’s status, querying work items, that kind of thing, the previous options were a generic service connection with a PAT you had to create and remember to rotate, or an ARM service connection that wasn’t really built for this. Now connectionType: connectedServiceNameAzureDevOps just points at a service connection you’ve probably already got. One less credential to manage, which is one less thing that can quietly expire and break a pipeline six months from now.

Instance Mix quietly slips from July to August

In July we wrote that Managed DevOps Pools’ Instance Mix feature, letting a single pool define up to five VM sizes instead of one, was “rolling out this month.” That was accurate at the time, based on what Microsoft’s own roadmap said. This week that same roadmap page was updated, and Instance Mix is now listed as planned for August 2026 instead of July.

It’s a minor slip, not a cancellation, but it’s a useful reminder: “coming this month” on a vendor roadmap is a plan, not a release. We’d rather flag a correction like this than have you go looking for a feature that quietly moved a month to the right.

Also this week

Azure DevOps’ Remote MCP Server picked up Enterprise Live Migration tooling in preview, aimed at organizations migrating Azure DevOps repositories to GitHub Enterprise Cloud. Niche if that’s not your situation, worth knowing about if it is.

That’s it for this week. If you’d rather not track any of this yourself, that’s exactly what a support pack is for, and if something here affects an environment you’re running, get in touch.