Azure News - 2026-07-17

Artificial Intelligence is evolving at unprecedented speed. The challenge for enterprises is no longer building AI solutions—it is engineering AI platforms that can adapt, scale, and govern innovation continuously. Hypervelocity Engineering (HVE) provides the engineering operating model that enables this transformation.

Executive Summary

Artificial Intelligence is transforming how enterprises design and operate digital platforms. Traditional Enterprise Architecture practices—built around static documentation, periodic governance reviews, and manual implementation—are struggling to keep pace with the rapid evolution of AI workloads.

HyperVelocity Engineering (HVE) introduces a disciplined engineering operating model that combines AI-assisted decision making, platform engineering, automation, and continuous governance. When applied to Azure AI Landing Zone, HVE enables architects to evolve from producing architecture documents to continuously engineering secure, governed, and scalable AI platforms.

This article demonstrates how HVE Core principles map naturally to Azure AI Landing Zone and how Enterprise Architects can use RPIR (Research, Plan, Implement, Review) as a continuous architecture lifecycle.

Why Enterprise AI Needs a New Engineering Model

Organizations across every industry are rapidly adopting Generative AI, intelligent agents, and AI-assisted business processes. Yet many enterprise AI initiatives encounter the same obstacles:

• AI projects are developed independently across business units.
• Platform capabilities evolve slower than AI innovation.
• Governance and security become reactive rather than proactive.
• Infrastructure is treated as a one-time deployment instead of a continuously evolving product.
• Engineering teams spend excessive time provisioning environments instead of delivering business value.

Traditional cloud engineering practices were designed for application modernization. Enterprise AI introduces new demands—rapid experimentation, scalable model deployment, secure data access, and continuous compliance. Meeting these demands requires a fundamentally different engineering approach.

Hypervelocity Engineering (HVE) addresses this challenge by enabling organizations to build platforms that evolve at the speed of AI while maintaining enterprise-grade governance, security, and operational excellence.

From Traditional Engineering to Hypervelocity Engineering

Enterprise architecture is shifting from project-centric delivery to platform-centric engineering.

This transformation allows engineering organizations to focus less on repetitive operational tasks and more on innovation.

What is HyperVelocity Engineering?

Hypervelocity Engineering (HVE) is Microsoft's engineering operating model designed to accelerate software and platform delivery through automation, reusable engineering patterns, platform engineering, AI-assisted development, and continuous feedback.

Unlike traditional methodologies, HVE is not another architecture framework or software product. Instead, it defines how engineering organizations operate to deliver secure, governed, and continuously improving solutions.

Its core philosophy is straightforward:

Engineer platforms, automate everything practical, measure continuously, and improve through rapid feedback while keeping humans accountable for critical decisions.

HVE combines several modern engineering disciplines into a unified operating model:

• Platform Engineering
• Infrastructure as Code (IaC)
• Policy as Code
• Security by Design
• AI-assisted engineering
• Continuous observability
• DevSecOps
• Human-in-the-loop governance

Together, these capabilities enable organizations to innovate faster without compromising security or compliance.

Azure AI Landing Zone as the Reference Implementation

Azure AI Landing Zone provides the foundational platform required to deploy enterprise AI workloads securely and consistently.

Typical capabilities include:

• Microsoft Entra ID
• Management Groups
• Azure Policy
• Hub-and-Spoke Networking
• Private Endpoints
• Azure Firewall
• Azure API Management
• Azure AI Foundry
• Azure AI Search
• Azure Kubernetes Service (AKS)
• Azure Monitor
• Defender for Cloud
• Infrastructure as Code (Bicep/Terraform)

HVE provides the engineering operating model that continuously evolves this platform.

The Core Principles of Hypervelocity Engineering

Hypervelocity Engineering is built around six complementary principles.

Outcome-Driven Engineering

Every engineering decision should align with measurable business outcomes rather than technology adoption alone. Success is measured by customer value, not infrastructure deployment.

Platform Engineering

Rather than building infrastructure repeatedly for every project, organizations create reusable, self-service platforms that accelerate application delivery while maintaining consistency.

Automation Everywhere

Automation extends beyond deployments. Infrastructure provisioning, governance, security validation, policy enforcement, testing, and operations should all be automated wherever possible.

Security by Design

Security is integrated into every engineering stage—from identity and networking to deployment pipelines and operational monitoring—reducing risk while improving delivery speed.

AI-Assisted Engineering

AI enhances developer productivity by generating code, documentation, infrastructure templates, architecture recommendations, and testing artifacts. Humans remain responsible for validation and governance.

Continuous Observability and Feedback

Operational insights, telemetry, cost analysis, and user feedback continuously improve future engineering decisions.

Applying RPIR to Enterprise Architecture

Rather than treating architecture as a one-time activity, HVE applies the RPIR cycle continuously.

Instead of ending after deployment, the Review phase feeds directly back into Research, enabling continuous architecture evolution.

Mapping HVE Principles to Azure AI Landing Zone

These principles ensure that governance, security, and operational excellence are embedded throughout the platform lifecycle rather than applied only during reviews.

Reference Architecture Walkthrough

The architecture consists of four logical layers:

1. AI Hub

The AI Hub provides centralized ingress and shared platform services using Azure Application Gateway, Azure Firewall, and Azure API Management. These services enforce security, routing, and governance before requests reach AI workloads.

2. Shared Platform Services

Shared Azure Kubernetes Service (AKS), Azure AI Foundry, and Azure AI Search provide reusable AI capabilities for multiple business units. Centralizing these services improves scalability, operational consistency, and cost efficiency.

3. AI Spoke Environments

Each business unit deploys isolated AI workloads into dedicated spoke environments. Private networking, isolated data stores, and workload-specific resources maintain tenant separation while consuming shared platform capabilities.

4. Platform Governance

Infrastructure as Code, Azure Policy, Microsoft Entra ID, Defender for Cloud, Azure Monitor, and FinOps capabilities operate across every layer to provide continuous governance, security, and operational visibility.

This architecture reflects HVE's platform engineering philosophy by separating shared capabilities from workload-specific implementations while maintaining centralized governance.

Benefits for Enterprise Architects

Adopting HVE alongside Azure AI Landing Zone provides measurable advantages:

• Accelerates architecture delivery through AI-assisted design.
• Standardizes landing zone deployments using reusable platform modules.
• Embeds governance through Policy as Code and Infrastructure as Code.
• Improves security with Zero Trust and continuous compliance validation.
• Enables continuous architecture evolution using the RPIR lifecycle.
• Reduces operational overhead through automation and observability.
• Supports FinOps practices with integrated cost monitoring and optimization.
• Creates auditable architecture decisions through Architecture Decision Records (ADRs).

Rather than replacing architects, HVE allows architects to focus on strategic decisions while AI assists with repetitive engineering activities.

Common Anti-Patterns to Avoid

Organizations should avoid several common pitfalls when adopting enterprise AI:

• Building separate AI platforms for every project
• Treating governance as a post-deployment activity
• Relying on manual infrastructure provisioning
• Operating without continuous telemetry and feedback
• Deploying AI services without standardized platform engineering

Hypervelocity Engineering addresses these anti-patterns by embedding automation, governance, and continuous improvement into the engineering lifecycle.

Design Recommendations

When adopting Hypervelocity Engineering for Azure AI Landing Zones:

• Start with measurable business outcomes rather than technology selection.
• Treat your AI Landing Zone as a reusable platform product.
• Automate infrastructure, security, and governance using Infrastructure as Code and Policy as Code.
• Integrate AI-assisted engineering while maintaining human oversight for architectural decisions.
• Use the RPIR loop to continuously evolve your platform based on operational insights and business feedback.
• Embed security, observability, and FinOps from the outset to support sustainable growth.

Conclusion

Enterprise AI success depends on more than deploying advanced models—it requires an engineering operating model capable of delivering secure, scalable, and continuously evolving platforms.

Hypervelocity Engineering provides that model by combining platform engineering, automation, AI-assisted development, and continuous feedback into a unified approach. When paired with Azure AI Landing Zones, it transforms static infrastructure into a living platform that accelerates innovation while preserving governance, security, and operational excellence.

For enterprise architects, the value is clear: Azure AI Landing Zones establish the foundation, and Hypervelocity Engineering ensures that foundation continuously adapts to changing business needs and the rapid pace of AI innovation.

In the era of enterprise AI, success belongs to organizations that engineer for continuous evolution—not just initial deployment. Hypervelocity Engineering offers the operating model to achieve exactly that.

As cloud services and AI workloads continue to grow, power has become a key constraint in expanding compute capacity. Using available power more efficiently enables Azure to deploy more servers in each datacenter, helping meet growing customer demand while improving sustainability. To address this challenge, Microsoft has taken a vertically integrated approach to infrastructure, co-designing hardware and software to optimize performance and efficiency across the stack.  

With Azure Cobalt CPUs, Microsoft introduced an industry-first per-virtual machine (VM) power monitoring and capping capability, developed from the ground up and deployed in Azure. Bringing this capability into production required hardware/software co-design across the Azure stack, spanning silicon and firmware, virtualization, server agents, VM placement systems, and datacenter power management infrastructure. By managing power at the granularity of individual VMs, Azure can preserve performance for critical workloads while improving overall infrastructure efficiency. 

The Need for Fine-Grained Power Management to Enhance Efficiency 

A widely adopted strategy for improving datacenter power efficiency is oversubscription — adding more servers within the same power budget to harvest the unutilized power and relying on power capping when power draw exceeds the limit. However, conventional hardware-based capping applies uniform CPU throttling across all cores. While this ensures power safety, it degrades performance for all VMs, including critical customer-facing workloads. This limitation restricts how aggressively Azure can oversubscribe power, since higher oversubscription levels cause more frequent and severe throttling, thereby degrading customer workload performance. 

To address these limitations, Azure initially introduced software-only per-VM power capping. This system uses VM metadata and workload predictions to selectively throttle non-critical VMs (e.g., non-production workloads, batch jobs) through a userspace Azure agent, helping protect the performance of customer-facing production applications; the figure below shows the criteria used for determining each VM’s priority.  However, software-based throttling is slow since it relies on fixed frequency change steps in a feedback loop that struggles to converge quickly. 

Hardware/Software Co-design for Per-VM Power Management on Cobalt 

Building our own CPUs enabled Microsoft to extend software-only per-VM power capping into a more effective hardware/software co-design, with per-VM power monitoring and management built directly into Cobalt from the ground up. This industry-first capability, now deployed in Azure, preserves performance for critical customer workloads while enabling up to 20% more power oversubscription on Cobalt 200.

In our implementation, the software provides VM identifiers (IDs) and each VM’s priority to the hardware. The hypervisor communicates a VM’s ID and priority to the hardware on VM core scheduling. CPU firmware uses VM priorities to maximize performance within a power budget. When power consumption exceeds the limit, it reduces power draw in priority order by lowering the voltage and frequency (DVFS) of each VM's cores. Since VM to core assignments can change due to context switches (at milliseconds scale), the firmware samples VM priorities of cores and re-evaluates power and core frequency every millisecond. The below figure illustrates the evolution of Azure's power management approach, from conventional hardware capping to per-VM (workload-aware) power management on Cobalt.

Furthermore, the firmware uses the programmed IDs to monitor per-VM power and frequency. This telemetry is used to understand the throttling experienced by VMs, build VM power models, and support energy/carbon reporting. 

Real-World Impact  

• Co-designed per-VM power capping on Cobalt provides up to 24% higher performance than software-only capping under the same power budget, based on SPEC CPU Integer benchmarks. Cobalt provides the best (100%) performance for the top 5 priorities while the software-based approach can only do so for the top priority. Overall, Cobalt provides 2 – 24% higher performance.

• Prioritized capping on Cobalt 200 provides up to 20% more power oversubscription for the evaluated scenarios while preserving performance of critical VMs. It allows a 35% reduction in power with no performance impact to the critical VMs whereas no prioritization only allows a reduction of 15%. Azure can choose power savings between 15 to 35% based on tolerable performance impact to the non-critical VMs.

These results demonstrate that per-VM power management on Cobalt 200 helps preserve performance for critical workloads while improving efficiency. By applying power limits more selectively, Azure can use power more effectively — deploying more servers within its existing datacenter footprint to meet growing customer compute demand and improve sustainability.

End-to-End Integration across the Azure Stack 

The figure below shows the end-to-end architecture for per-VM power management on Cobalt and highlights the hardware and software enhancements across the Azure stack. The VM scheduler places VMs in racks with available power and live migrates VMs from constrained racks using workload criticality and measured VM power. The node agent provides each VM’s ID and priority to the hypervisor, which tags the VM’s cores during scheduling. Each VM's ID enables per-VM telemetry, while its priority guides power management decisions. The per-VM telemetry is sent to Resource Central for building and refining prediction models. Finally, the power manager monitors power consumption across server groups, such as racks and rows. When a power limit is reached, it signals servers to reduce usage. The Cobalt CPU on each server then uses VM priorities to selectively throttle lower-priority workloads, preserving performance for critical applications while maintaining power safety.

Looking Ahead 

This work exemplifies the power of hardware/software co-design in cloud infrastructure and is a consequence of deep collaboration across many hardware and software teams within Microsoft. As cloud workloads continue to evolve, innovations like co-designed per-VM power management will be essential to balance performance, efficiency, and sustainability.