Azure Developer CLI in 2026: JMESPath Queries, Slot Deployments & Real Surprises

⏱️ 6 min read📅 26 March 2026

Back in 2022, if you’d asked me whether I thought the Azure Developer CLI (azd) would morph into a genuinely indispensable toolkit, I probably would’ve just shrugged and mumbled something about “another Microsoft experiment.” Here we are—February 2026. Well… it’s honestly taken a few wild turns. Let’s not bore each other with bullet-point changelogs; let’s dig into what these updates actually mean when your pipeline is on fire, deadlines are breathing down your neck, and some poor junior is frantically slacking you for help.

JMESPath Query Support: JSON Without the Painkillers

I can’t count how many times—usually somewhere between midnight and “shouldn’t-you-be-sleeping o’clock”—I’ve sat glaring at an avalanche of azd output, desperately trying to isolate one tiny value for a glue script. Sure, jq can slice through JSON like butter… until you realize half your team forgot to install it or can’t recall its syntax unless they’re caffeinated enough to see sounds. This month? Surprise! The azd crew tossed us native JMESPath querying via --query. Didn’t see that coming.

This isn’t theory—I watched it save our skins last Wednesday at Logosoft HQ (not making this up). We were churning out infrastructure reports for an e-commerce client who wants everything exported as JSON but loathes manual anything. Out of nowhere my teammate pipes up: “Can we do this filtering inside azd?” Ten minutes later he had exactly the resource group names needed—zero sidecar tools, zero shell gymnastics.

“The new –query flag lets you filter and transform JSON output from any azd command using JMESPath expressions—right from the terminal.”

I’m not going to pretend JMESPath is always friendly—it’s definitely got its own flavor of weirdness if you grew up on grep/cut/sed—but once you muscle through that initial awkward phase? Your scripts suddenly get ten times cleaner. That said… don’t expect poetic error messages when your expression stumbles (ask me about my afternoon lost hunting a typo). If you want more nerdy comparison fodder with recent Azure CLI AI features, have a look here:
Azure CLI’s New AI Agent Logs: Real Debugging Without the Portal Headache.

💡 Note: It gets better—JMESPath now filters message-type outputs too! Yep, even those chatty logs or oddball results.

No-Hassle App Service Deployment Slots — Did I Dream This?

Açık konuşayım, This next bit caught me off guard—in a good way for once. App Service deployment slots have been around forever but getting azd to play nicely used to require clunky scripts or post-deploy arm-twisting that never felt right. Suddenly? Just point at your slot and deploy; it works without any extra dance moves.

I gave this feature a whirl two weeks ago in my dev sandbox fully expecting chaos (“something will break”). But guess what? It didn’t flinch—not even when pushed from VS Code straight through azd with no portal clickfest or ARM template voodoo involved.

Still, nothing is ever perfect first try—tried orchestrating blue/green swaps after deployment? The swap step itself isn’t automated yet as of v1.23.x; still needs either scripting elbow grease or clicking around manually for now. Don’t underestimate how much smoother things could be if that last mile was covered automatically! For my ranting take on why slot swaps matter more than people admit:
Azure Developer CLI’s App Service Slot Swap: Why I’m Actually Excited.

The Flags Nobody Tells You About Until You Need Them

You know what else quietly made life easier? New --subscription and --location flags added directly onto azd provision, azd up, etc. Sounds boring until your client changes their mind three times in one sprint about which subscription should host prod.

Saves sanity: No need fiddling with global configs every time there’s another region/sub flip-flop.
Cuts mistakes: Point commands precisely where they need to go instead of crossing fingers before hitting enter.
Makes CI/CD less explosive:If you’ve lived through shared pipelines overwriting each other (like we did during Istanbul banking migration last month), you’ll understand why I cheered out loud.

The Extension Game Steps Up (With Some Twists)

If dev containers are part of your daily grind—maybe Codespaces/Docker stuff—the new auto-extension installer might sound almost magical compared to old setup routines. Pop extensions into config and watch them appear as soon as the container fires up; no more yak-shaving post-build tasks!

Murat (from our DevOps squad) tried this during Logosoft Hackathon Day last Friday—and his jaw nearly hit the floor when all three custom extensions just… showed up ready-to-go sans fussing around afterward.

BUT—and yeah, there always seems to be one—you absolutely must set requiredAzdVersion correctly now or risk total silence while things fail behind the scenes (learned that lesson painfully myself). More than once someone wondered why their extension wasn’t loading only to find out they’d mistyped a version spec by one measly digit!

Pitfalls With Extensions Nobody Warns You About Yet…

If you ship internal extensions? Update docs ASAP with accurate requiredAzdVersion—or expect angry pings late Sunday night before release freeze.
If you’re rolling back azd versions mid-project (…it happens), double-check compatibility BEFORE demos blow up Monday morning.
No UI warning if blocked by version mismatches—all errors dump into console spam juniors rarely notice while scrolling past test runs!

The Hidden Gems That Quietly Save Your Sanity (AI Agents & Remote Builds)

Şahsen, I’ll admit—I treated most “AI agent support” press releases like vaporware until recently myself. But here comes something refreshingly concrete built right in now: automatic detection of coding agents so batch jobs stop hanging endlessly waiting for prompts nobody will answer except maybe Clippy circa ’98. Azure SDK March 2026 Release: Surprises, Frustrations, and What Actually Matters yazımızda da bu konuya değinmiştik. Azure MCP Server Meets PyPI: Real Python Support, Finally! yazımızda da bu konuya değinmiştik.

This change paid off big time during our Foundry PoC rollout in January—we shaved ten minutes per run because automation stopped tripping over confirmation dialogs meant only for humans sitting at keyboards sipping tea!

💡 Note: On Azure Functions Flex Consumption plans—you can toggle remoteBuild so Node.js/.NET SDK installs aren’t needed locally anymore; let Azure handle build steps itself!

Bugs Zapped… But Ghostty Still Lurks?

I’ll end on this—a bugfix parade marched through lately (finally fixed arrow keys inside Ghostty emulator among others), but little quirks persist especially if ancient dotfiles lurk in .bashrc/.zshrc land waiting patiently since Ubuntu Trusty days.

This echoes an issue from earlier this year—a junior stuck debugging bizarre escape sequences every time he pressed arrows on an old VM… only for us all to discover his shell defaulted stubbornly back into Ghostty mode after an OS patch derailed xterm settings overnight! These fixes show someone cares about edge cases besides VS Code fans with shiny new Macs—which frankly surprised me in a good way.

The Takeaway & Where There’s Room To Grow Next Month…

The February ’26 batch brings real developer-friendly momentum—not least thanks to those JMESPath queries making automation scripts less ugly everywhere complex data wrangling hides out-of-sight.
Slot deployments finally feel official-ish rather than glued together… though swap orchestration has miles left before I’d trust it alone late Friday afternoons!

If automation is daily life: Try those new flags today—they genuinely cut down fat-finger mistakes.
If containers/devboxes rule your workflow: Let extensions install themselves…but eyeball version requirements until tooling matures further!
If AI agent news sounded irrelevant before: You may be shocked which flaky pipeline headaches simply disappear behind-the-scenes soon enough…

At day’s end — none of these features will win innovation awards solo…but stitched together they push azd closer toward being genuinely essential rather than “just another utility”. Now let’s wait and see what fun surprises drop next month!

Keen on more gritty takes—including rough edges Microsoft skipped smoothing over?
Check my deep dive:
Azure SDK February 2026 Update – Surprising Wins & Annoyances.
Have war stories or fresh pain points yourself?
Drop them below—I promise I’ll read every single one over strong Turkish coffee!

Source: Azure Developer CLI (azd) – February 2026: JMESPath Queries & Deployment Slots