Event Recap – Microsoft at the Digital Workplace Conference Australia 2026
July 1, 2026🌍 MGCI Newsletter – July 2026
July 1, 2026
ACA Express Apps are a strong fit for teams that need to ship quickly and can’t afford long platform setup cycles. This includes startups, internal platform teams, and product groups deploying APIs, web apps, or agent endpoints that scale with uneven demand. If the priority is fast path-to-production, predictable wake-up behavior, and minimal infrastructure overhead, this model is likely the right choice.
To put real numbers behind that, I built a live demo that races Express against a Consumption environment on the same app. The measurements below come from that demo, not from a spec sheet.
MicroVMs make cold starts practical
Cold start delays usually come from rebuilding runtime state whenever an app wakes up. ACA Express Apps reduce that overhead with MicroVM-based startup paths built for fast boot and isolation. The result is faster instance readiness without trading off security.
The gap shows up clearly when both apps have scaled all the way to zero. Waking from a genuine cold start, Express comes back in about 1.5 seconds. The same app in a Consumption environment takes about 20 seconds to answer the first request. Both were measured live in the browser, from request to first response.
Disk and memory state restore is the speed multiplier
State restoration skips the app’s internal boot sequence entirely. Instead of replaying the same initialization work on every start, ACA Express Apps can restore disk and memory state so the app starts closer to ready. That reduces time-to-first-request and smooths scale events, especially for framework-heavy workloads. It’s also what lets scale-to-zero stay practical: the app costs nothing while idle, but the wake-up penalty stays in the low single-digit seconds instead of the tens of seconds you’d otherwise pay.
Environmentless changes the deployment experience
Skipping the environment setup completely changes the deployment workflow. Teams can ship the container app without first managing environment sprawl, while still getting the runtime foundations they need. For fast-moving teams, that means less setup overhead and a shorter path to production.
You can see how little there is to fill in. Creating an Express app is a single short form. There is no environment to stand up first.
And once it’s created, the manage view gives you the live URL, status, and the basics you need to operate it.
The numbers, side by side
Everything below was measured on the same container image, in the West Central US region.
| What’s measured | Express | Consumption |
|---|---|---|
| Cold start from zero (request to first response) | ~1.5 s | ~20 s |
| Environment provisioning | ~14 s | ~120 s |
| First-time deploy (environment + app, zero to live URL) | ~52 s | ~166 s |
| App deploy only (environment already exists) | ~30 s | ~30 s |
Express is much faster on the two steps that build infrastructure from scratch: cold start and environment provisioning. Once an environment already exists, the two are about the same. Express isn’t a different app runtime, it’s the same platform with the first-time setup cost stripped down.
Get started
Express is in public preview. You can have a container on a live URL in the time it takes to read this post.
- 📖 Azure Container Apps Express overview — concepts, capabilities, and the current feature support matrix.
- 🚀 Create your first Express app — the CLI commands and portal steps to get an app running.
- 🛠️ New Container Apps portal — create and manage Express apps in the streamlined UI.
- 🧪 Test Express apps locally — validate your container before you deploy.
- ❓ Express FAQ — preview status, limits, regions, and how Express relates to standard Container Apps.
👉 Deploy an Express app · Read the docs · Browse the FAQ
When speed matters, ACA Express is the best tool for deploying containers. It skips the platform setup delays without sacrificing reliability under load.