Microsoft closed its 2026 fiscal year with a number that would have looked unlikely a few years ago: Azure’s annual revenue passed $100 billion, up 41% from the year before. The company’s finance chief told investors to expect Azure growth near 45% in the current quarter. For a cloud platform already this large, that pace is unusual, and it says something about where enterprise technology spending is actually going.

That growth mostly reflects existing enterprise customers running more workloads through Azure than they were twelve months ago: Copilot deployments, a growing list of agentic AI projects, more data platforms, and a large wave of legacy applications finally getting rebuilt instead of patched. Microsoft’s own commentary points to AI infrastructure demand as a major driver, alongside continued migration of on-premises systems that had been sitting on the roadmap for years.

That second piece, migration, is the one enterprise IT leaders should sit with. A lot of the software still running inside large organisations, especially in finance, insurance, healthcare, and manufacturing, was built on .NET years or decades ago. Azure has always been the default landing zone for that code, since Microsoft built the two to work together from the start. As Azure adoption speeds up, the backlog of .NET applications waiting for a rebuild around Azure-native services grows right along with it.

Cloud capacity is not the limiting factor here. Azure has more regions, more services, and more AI tooling available than most enterprises can work through in a single year’s roadmap. The limiting factor is engineering capacity: teams that understand both the .NET codebase they are moving and the Azure services they are moving it to.

That combination is harder to hire for than it sounds. Job postings asking for .NET developers with real Azure migration experience, not just a certification on a resume, have grown alongside the platform itself, and most internal hiring pipelines were never built to move at cloud-vendor speed. A standard requisition-to-hire cycle for a senior .NET engineer commonly runs two to three months. A quarter where Azure demand jumps 45% does not wait that long.

This is one reason more enterprises are supplementing internal teams with staff augmentation instead of trying to fill every open seat through direct hiring. The model adds engineers who work inside the existing team and report to the existing manager, so a migration already in progress does not stall while a requisition sits open. Full Scale, a staffing firm that places dedicated .NET engineers with U.S. companies, is one example of this approach applied specifically to the .NET-on-Azure gap: engineers who can join an in-flight migration without months of onboarding.

For IT leaders building out their next roadmap, a few things follow directly from Microsoft’s numbers:

• A bigger Azure budget line does not rebuild anything by itself. It needs to be paired with an honest look at who is actually available to do the work.
• Backlogs are likely to grow before they shrink, since AI workloads are adding new demand on top of migration queues that were already full.
• Hiring timelines for specialised cloud and .NET talent are a real constraint on how fast a roadmap can move, not a footnote at the bottom of it.

None of this makes the growth story bad news. A $100 billion cloud platform growing at 41% is evidence that enterprises are finally acting on migrations they had put off for years. But growth at that scale puts pressure somewhere, and right now it is landing on the engineering teams asked to keep up with it.