Continuous improvement comes to Microsoft Foundry

const currentTheme =
localStorage.getItem(‘blogInABoxCurrentTheme’) ||
(window.matchMedia(‘(prefers-color-scheme: dark)’).matches ? ‘dark’ : ‘light’);

// Modify player theme based on localStorage value.
let options = {“autoplay”:false,”hideControls”:null,”language”:”en-us”,”loop”:false,”partnerName”:”cloud-blogs”,”poster”:”https://cdn-dynmedia-1.microsoft.com/is/image/microsoftcorp/1307367-microsoftfoundry2_tbmnl_en-us?wid=1280″,”title”:”1307367-microsoftfoundry2″,”sources”:[{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftfoundry2-0x1080-6439k”,”type”:”video/mp4″,”quality”:”HQ”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftfoundry2-0x720-3266k”,”type”:”video/mp4″,”quality”:”HD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftfoundry2-0x540-2160k”,”type”:”video/mp4″,”quality”:”SD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftfoundry2-0x360-958k”,”type”:”video/mp4″,”quality”:”LO”}]};

if (currentTheme) {
options.playButtonTheme = currentTheme;
}

document.addEventListener(‘DOMContentLoaded’, () => {
ump(“ump-6aff12b3acce5″, options);
});

New models ship every few weeks, and your customers ask questions no one planned for. The agents that learn from all of it pull ahead. That’s continuous improvement, and today at Microsoft Ignite we’re bringing it to Microsoft Foundry. To unlock it, you need an end-to-end system where you build agents, give them context, run them, govern them, and improve them over time.

And as part of the new Microsoft IQ, Foundry accomplishes two things that only Microsoft can deliver: your unique intelligence stays your advantage, and your agents keep getting better the longer they run.

Out of the box, an AI model is exactly the same for you as it is for anyone else. Three things help you improve your agents as your teams accomplish real work.

Agents on Foundry get better the more you use them. Foundry lets you feed agent traces and user input back into the system, creating a continuous learning loop that improves the performance of the system over time.

Foundry looks across every run for ways to make your agents better. The system finds and tests improvements; shows you how each one trades off across quality, speed, and cost; and then you decide what ships.

Foundry provides a range of other capabilities that allow you to improve progressively, from lightweight skill improvements to agent configuration, all the way to training model weights using your data.

Underneath it all, you have GitHub, where you build your agents, and Foundry, where you run and supervise them as they continuously improve. And they both run on Azure as one system that operates on a global scale.

See what’s new in Foundry today

GitHub: Building intelligent agents

Before you improve an agent, you need to build it. Say you want an agent to automate your supply chain processes, and you want that agent to be available in Teams—where your team already works. Just explain what you’re trying to do in clear, everyday language, and GitHub Copilot writes most, if not all, of the code. And with GitHub Copilot Fusion under the hood, it routes and orchestrates models while you’re building, so you don’t have to. That means you get the right model for the job, while balancing performance, latency, and cost.

Foundry: Running and continuously improving agents at scale

Once you’ve built your agent, you need a place to run it, govern it, and improve it for all your teams, in every region, alongside hundreds or thousands of other agents.

With more than 11,000 models, from OpenAI and Anthropic to Meta, Mistral, open source, our own Microsoft AI (MAI) models, and more, Foundry lets you do just that. And you don’t have to choose just one or be locked into a single model provider. Foundry’s model router sends simple requests to small, fast models and more complicated asks to larger, state-of-the-art models, so you spend less on tokens, time, and compute. Our testing shows that using Foundry’s model router can save you up to 65% compared with sending everything to the frontier.

When your agent runs in Foundry, it has an identity. Entra Agent ID and Foundry guardrails give the agent only the access it needs, and sensitive actions keep a human in the loop as required by your business. And your organization stays in control at every step. You set the standard, every change is tested against evidence, and your team decides what reaches production. Agent controls in Foundry Safety extend that oversight to the runtime. For agents built in Foundry and, in the future, outside it, this means checking an agent’s behavior against the guardrail policies you set as it runs.

ignite session: The trust foundation…

Watch now ↗

Run agents with the orchestration layer of your choice. Foundry Agent Service runs agents built with your preferred framework and harness through hosted agents, which now handle more concurrent sessions at once (in general availability [GA]) and start faster (in preview). And for teams that would rather have the harness managed for them, the Microsoft Copilot harness (now in preview) has built-in capabilities like reusable skills and sub-agents. Fashable, an AI-native fashion company, is using voice agents (now in GA) and the Microsoft Copilot harness to make design and sourcing more conversational and agent powered.

Watch the Microsoft Mechanics episode about the Microsoft Copilot harness

Foundry learns from how your teams use your agents, evaluates every change against your own standard of what “good” looks like, and helps you make each agent better. Agents learn from their own past work and your experts’ feedback, and those lessons become new skills, evaluations, and more. That’s how your agents, and the system around them, keep getting better.

How continuous improvement works

Continuous improvement in Foundry follows four steps, repeated, so each pass builds on the last: Establish, Identify, Optimize, then Validate and repeat.

Establish: You decide what good looks like

Improvement starts with a clear standard. In Foundry, that standard lives in evaluations, which are automated tests that score an agent’s responses against criteria you choose. Rubric evaluators let you write those criteria for your own business, like a checklist your best expert would use, and they now cover safety as well as quality (in preview).

Your people know quality better than any metric, and their feedback turns a capable agent into an expert on your business. Every time an agent runs, Foundry logs a trace: a step-by-step record of what the agent was asked, what it did, and how it answered. With annotations on traces (now in preview), experts review real conversations and mark what worked, what didn’t, and what the agent should have done instead. Those annotated traces become evaluation datasets (in preview), built from real usage rather than hypothetical test cases. From those datasets, Foundry can generate a rubric for each test case, so your experts’ judgment becomes part of how every future version of the agent is scored.

You can then lock in your best set of test cases as a golden dataset (in preview). Think of it as the answer key: the benchmark each new version has to beat.

Identify: Find areas where your agent can improve

Your customers shouldn’t be the first to tell you something broke. Traces show how an agent really behaves, including where things go wrong, but there are far too many to read on your own. Insights (now in GA) groups the problems that keep recurring, shows the evidence, and points to a likely cause, so teams fix what affects the most people first. And your teams can bring the same visibility to agents built outside Foundry with LangGraph, LangChain, and CrewAI (now in GA).

Optimize: Make a good agent better

Agent optimizer turns what you’ve learned into a better agent, whether you’re fixing a repeated mistake or raising the bar on an agent that already performs well. It improves an agent’s instructions, skills, and model choice and tests every candidate change against your evaluations before anything ships. And while it recommends the strongest candidate, your team decides which change to ship—and nothing changes in production until you apply it. Agent optimizer builds on prompt optimization and Foundry’s model router (both already available), with new ways to improve an agent:

Sending insights to agent optimizer (now in preview) turns a problem found in production into a fix in one step. Pick a recurring issue in insights, send it to agent optimizer, and get candidate fixes tested against your evaluations.

Skill optimization (now in preview) helps agents learn from experience. Agent optimizer reviews an agent’s past work and the feedback your experts left, finds the mistakes it keeps repeating and the approaches that worked, and turns those lessons into new or improved skills for similar situations. Skills are versioned, so you can roll back or reuse a proven skill in other agents, and you choose when to adopt it.

Cost optimization (now in preview) finds cost-efficient ways to run your agent, like using a smaller model, without compromising on quality.

Managed Training (previously called managed fine-tuning) lets you train models on your own data. Docusign, which already cut AI processing costs by 90% with fine-tuned models in Foundry, is now fine-tuning MAI models with Managed Training to read agreements.

Programmed Training (now in preview) lets your engineers write their own training recipes in Python while Foundry runs them on serverless GPUs. Heidi, an AI care partner for clinicians, used Programmed Training to post-train an open-weight model for clinical notes that matches a widely used frontier model on its clinical quality metrics, at an estimated 87% lower cost per note.

Alaska Airlines put continuous improvement in Foundry to work. They explored how fine-tuning MAI-Code-2-Flash could assist trained personnel in classifying aircraft maintenance reports by ATA code, with qualified employees retaining responsibility for review and final decisions. In Alaska’s classification evaluation, the model scored 81.2% out of the box and 91.1% after tuning, outperforming GPT-6 Astra and GPT-6.1 Sol at a fraction of the cost.

Try Agent Optimizer

Validate and repeat: Prove the improvement

Every improvement should be something you can prove. When you compare a new version of an agent with your current one, Foundry runs statistical tests on the results, so you can see whether a difference is real or just noise. Teams can build the same check into the release pipeline their developers already use, in GitHub Actions or Azure DevOps, so nothing ships until it clears your quality bar.

Continuous evaluation (already available in Foundry) samples live traffic and scores it with the same evaluators you set at the start, to check that an improvement holds up with real users in production. Scheduled evaluations rerun your golden dataset, and scheduled red-team scans keep testing for new risks. Each agent’s monitoring dashboard shows quality, safety, latency, and token usage in one view, and alerts flag when scores slip.

When something does slip, whether from a model update, a change in your business, or a new type of request, that signal becomes the next insight, and the loop starts again. The version you just shipped becomes the new baseline, so every round starts from your best agent to date.

ignite session: The Foundry improvement loop

Watch now ↗

Customers are already putting this loop to work, including NTT DATA, which is sharing its story at Ignite (BRK249). NTT DATA is applying a continuous improvement loop to its program-management agent, using observability, evaluations, and optimization to identify issues and systematically improve quality. The team is validating the approach as it prepares to scale the agent across more than 1,000 internal projects, showing how continuous improvement can help maintain agent quality at enterprise scale.

const currentTheme =
localStorage.getItem(‘blogInABoxCurrentTheme’) ||
(window.matchMedia(‘(prefers-color-scheme: dark)’).matches ? ‘dark’ : ‘light’);

// Modify player theme based on localStorage value.
let options = {“autoplay”:false,”hideControls”:null,”language”:”en-us”,”loop”:false,”partnerName”:”cloud-blogs”,”poster”:”https://cdn-dynmedia-1.microsoft.com/is/image/microsoftcorp/1307367-microsoftxnttdata_tbmnl_en-us?wid=1280″,”title”:”1307367-microsoftxnttdata”,”sources”:[{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftxnttdata-0x1080-6439k”,”type”:”video/mp4″,”quality”:”HQ”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftxnttdata-0x720-3266k”,”type”:”video/mp4″,”quality”:”HD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftxnttdata-0x540-2160k”,”type”:”video/mp4″,”quality”:”SD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftxnttdata-0x360-958k”,”type”:”video/mp4″,”quality”:”LO”}],”ccFiles”:[{“url”:”https://azure.microsoft.com/en-us/blog/wp-json/bloginabox/v1/get-captions?url=https%3A%2F%2Fwww.microsoft.com%2Fcontent%2Fdam%2Fmicrosoft%2Fbade%2Fvideos%2Fproducts-and-services%2Fen-us%2Fazure%2F1307367-microsoftxnttdata%2F1307367-microsoftxnttdata_cc_en-us.ttml”,”locale”:”en-us”,”ccType”:”TTML”}],”downloadableFiles”:[{“url”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftxnttdata_transcript_en-us”,”locale”:”en-us”,”mediaType”:”transcript”},{“url”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307367-microsoftxnttdata_audio_en-us”,”locale”:”en-us”,”mediaType”:”audio”}]};

if (currentTheme) {
options.playButtonTheme = currentTheme;
}

document.addEventListener(‘DOMContentLoaded’, () => {
ump(“ump-6aff12b3af011″, options);
});

Agents that increase your advantage

An agent becomes an expert when it understands your business: how your people work, your organization’s institutional knowledge, and what “good” looks like—in your specific business context. Microsoft IQ grounds agents in your company’s data, know-how, and tools through a context layer you own, built from the IT investments you’ve already made. Your agents start with years of experience, and everything they learn in Foundry adds to it. That value accrues to you and stays in your business.

We believe AI should increase your advantage. And with continuous improvement in Foundry, those gains compound over time.

Try Agent Optimizer

Read about new models

Learn about Microsoft IQ

Also announced at Microsoft Ignite

Voice agents (now in GA) let people talk to an agent the way they would talk to a colleague, by phone or in an app.

Microsoft 365 accounts for agents (in preview) let agents work inside the same tools your people use.

Deploying hosted agents to Azure Kubernetes Service is coming soon (in preview).

Updates to Toolboxes and browser automation connect agents to more tools and workflows.

Cost in Microsoft Foundry (now in preview) gives you one view of spend across agents, models, and tools, with a forecast and month-end report on the assets driving the most cost.

New Microsoft AI models for coding, security, and creative work are available, plus partner models through fal and Baseten on Foundry.

Microsoft-Decision-1.1 is now generally available in Foundry and also available to be used as a judge in Foundry Evaluations to measure performance, quality, and safety.

If you’re attending Microsoft Ignite 2026, or watching on demand later, check out these sessions:

BRK240 – Build and scale the next generation of AI agents in Microsoft Foundry

BRK249 – From traces to better agents: The Foundry improvement loop

BRK251 – Agents in production: From issue detection to continuous improvement

BRK242 – Build your self-improving AI Platform with Microsoft Foundry

BRK244 – Voice agents in Microsoft Foundry: Prototype to production in 45 mins

BRK247 – Token economics: Get more from your production AI budget

BRK252 – Turn your data into AI advantage with Training in Microsoft Foundry

BRK312 – The trust foundation for the next era of intelligence

Learn. Adapt. Improve.

Use Microsoft Foundry to learn from agent feedback, evaluate changes, and continuously improve performance.

Start building

The post Continuous improvement comes to Microsoft Foundry appeared first on Microsoft Azure Blog.
Quelle: Azure

Azure Cobalt 200 VMs now available, proven on real workloads and built for the agentic era

Today at Microsoft Ignite 2026, we’re announcing the general availability of Azure Cobalt 200-based virtual machines (VMs). Cobalt 200 VMs deliver up to 50% better performance than Cobalt 100 and are now available in 14 regions, expanding to 23 regions by the end of 2026. Built for cloud-native, data-intensive, and agentic AI workloads, Cobalt 200 VMs will represent a significant share of new Azure Compute capacity beginning in 2027.

Explore Cobalt 200 VM sizes and deployment guidance

For customers like Amadeus, Databricks, InMobi, OpenAI, and Snowflake, Cobalt 200 VMs deliver improved performance and efficiency over Cobalt 100 VMs. As a result, customers can deliver faster search results, more responsive database queries, and run their services at higher utilization with fewer cores.

Cobalt 200’s performance and efficiency gains reflect our systems approach to infrastructure design, which co-optimizes silicon, software, networking, power, and rack infrastructure. Cobalt 200 VMs are also designed for agentic AI workflows, including agent sandboxes, file search, code compilation, and tool execution, where higher per-core performance can help reduce latency.

As customer need for high-performance and low-latency compute increases, we’re adding new virtual machine types to bring the price-performance benefits of Cobalt to additional workloads:

Mpsv4 for high memory workloads.

Lpsv5 for workloads needing fast access to large datasets.

With Microsoft Azure Boost included in every Cobalt 200 VM, customers get the latest accelerated network and remote storage performance in Microsoft Azure.

const currentTheme =
localStorage.getItem(‘blogInABoxCurrentTheme’) ||
(window.matchMedia(‘(prefers-color-scheme: dark)’).matches ? ‘dark’ : ‘light’);

// Modify player theme based on localStorage value.
let options = {“autoplay”:false,”hideControls”:null,”language”:”en-us”,”loop”:false,”partnerName”:”cloud-blogs”,”poster”:”https://cdn-dynmedia-1.microsoft.com/is/image/microsoftcorp/1309848-cobalt_tbmnl_en-us?wid=1280″,”title”:”1309848-cobalt”,”sources”:[{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1309848-cobalt-0x1080-6439k”,”type”:”video/mp4″,”quality”:”HQ”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1309848-cobalt-0x720-3266k”,”type”:”video/mp4″,”quality”:”HD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1309848-cobalt-0x540-2160k”,”type”:”video/mp4″,”quality”:”SD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1309848-cobalt-0x360-958k”,”type”:”video/mp4″,”quality”:”LO”}],”ccFiles”:[{“url”:”https://azure.microsoft.com/en-us/blog/wp-json/bloginabox/v1/get-captions?url=https%3A%2F%2Fwww.microsoft.com%2Fcontent%2Fdam%2Fmicrosoft%2Fbade%2Fvideos%2Fproducts-and-services%2Fen-us%2Fazure%2F1309848-cobalt%2F1309848-cobalt_cc_en-us.ttml”,”locale”:”en-us”,”ccType”:”TTML”}],”downloadableFiles”:[{“url”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1309848-cobalt_transcript_en-us”,”locale”:”en-us”,”mediaType”:”transcript”},{“url”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1309848-cobalt_audio_en-us”,”locale”:”en-us”,”mediaType”:”audio”}]};

if (currentTheme) {
options.playButtonTheme = currentTheme;
}

document.addEventListener(‘DOMContentLoaded’, () => {
ump(“ump-6aff12b3a6720″, options);
});

Proven on critical customer workloads

Our benchmarking for Cobalt 200 VMs showed significant performance increases for a wide variety of workloads. We observed up to 1.5 times increased performance for web serving workloads, up to 1.6 times for Java-based workloads, up to 1.5 times for AI agent tool execution workloads, and 1.9 times for database workloads over Cobalt 100.

We’ve seen these results translate into real-world improvements as our customers bring Cobalt 200 VMs to their own workloads.

See what customers are saying about Cobalt 200 VMs

Cobalt has helped us sustain ChatGPT’s growth. Cobalt 100 gave us more CPU capacity when we needed it. By the time we tested Cobalt 200, our services already ran on ARM, so we could compare the same ChatGPT workloads on both generations. We saw higher throughput and lower latency on Cobalt 200. That means we can serve more users with the same number of cores, and they spend less time waiting for ChatGPT to start responding.
—Vadim Filanovsky, Member of Technical Staff, OpenAI

Genie, the data-smart AI coworker, puts answers in front of business users in plain language, and those answers depend on fast, efficient compute underneath. Azure Cobalt helps us deliver that. Azure Databricks serverless compute on Cobalt starts faster and runs more efficiently, so customers spend less time waiting and more time acting on their data. Cobalt 200 raises the bar again, and as we bring more of Azure Databricks onto it, Genie questions, SQL queries, and data pipelines get faster.
—Vinod Marur, SVP Engineering, Databricks

Snowflake has grown with Arm on Azure, from the first Arm-based v5 VMs to Cobalt 100 and now Cobalt 200. Each generation has brought real performance and efficiency gains for our workloads, and those gains help us give our customers an even better experience. We’re proud to partner with Microsoft on what comes next for Cobalt and excited to see Cobalt 200 reach general availability.
—Murray Stokely, Distinguished Engineer, Snowflake

Performance at scale is at the heart of how Amadeus serves the travel industry. In our benchmark lab, Azure Cobalt 200 improved flight search throughput by more than 30% compared with Cobalt 100, a performance gain that exceeded our expectations.
—Luc Choubert, VP Engineering, Amadeus

We tested our ad-serving workloads on Cobalt 200 and saw clear performance and efficiency improvements. In addition to traditional workload patterns, we run high-throughput local neural network inference using SIMD, with each 32-core machine processing approximately 50,000 inferences per second. At the scale of a large fleet, these per-machine efficiency gains compound significantly, making Cobalt 200 particularly compelling for our workloads.
—Sudheer Bhat, Principal Engineer, InMobi

Partner endorsements

Microsoft’s continued investment in Cobalt demonstrates the value of building cloud infrastructure on Arm. Our collaboration on Cobalt 200 brings together Arm Neoverse CSS V3 and Microsoft’s custom silicon innovation to deliver the high performance and efficiency needed for everything from enterprise applications to agentic AI.
—Mohamed Awad, EVP, Cloud AI, Arm

Cobalt 200 VMs bring the performance and efficiency that agentic AI and data workloads need in production. Ubuntu supports Arm as a first-class architecture, so teams deploy Ubuntu on Cobalt 200 VMs the way they already do across Azure. Ubuntu Pro keeps those systems patched and supported for the long term. On Ubuntu 26.04 LTS, that includes Kernel Livepatch, which applies high and critical kernel fixes on Arm-based VMs without a reboot.
—Cindy Goldberg, VP, Cloud and Silicon Partnerships, Canonical

Improving efficiency at Microsoft scale

Microsoft products and services, including Azure Database for PostgreSQL, Azure DevOps, Azure SQL, Microsoft 365, XBOX, and more, run on Cobalt VMs for increased performance, improved efficiency, and cost savings at scale.

Accelerating cloud database workloads

Cobalt 200 was designed to deliver high-performance for database workloads, and at Microsoft Build 2026, we announced the availability of Azure Database for PostgreSQL on Cobalt 200. Cobalt 200 VMs provide scalable performance, memory capacity, and local storage needed to accelerate Azure Database for PostgreSQL.

Advancing custom silicon development

Microsoft’s silicon engineers run EDA workloads for design verification, physical implementation, and sign-off, and they benchmarked many of those workloads on Cobalt 200 VMs. The team reported increased performance and efficiency with Cobalt 200, with performance between 1.3 and 4.15 times over Cobalt 100. The increased performance allows the team to run more test cases in the same amount of time, supporting the development of more advanced Maia and Cobalt silicon.

Speeding up developer workflows

Every second counts when developers are waiting on a build. Cobalt 200 VMs allow GitHub Actions larger Arm runners to finish jobs noticeably faster than on Cobalt 100. Across the millions of workflows run every day, those gains add up to faster feedback for developers and more efficient use of compute.

Gaming

XBOX evaluated Cobalt 200 VMs on its web service and caching layer, the behind-the-scenes building blocks that help players sign in, see what their friends are playing and jump into games more quickly. Running natively on Arm, XBOX achieved improved performance and efficiency compared to their current infrastructure, a jump that matters in gaming for delivering fast and reliable gameplay.

Scaling media processing

The media processing service running video for Microsoft Teams observed 1.65 times the performance on Cobalt 200 compared with Cobalt 100, allowing them to further optimize their capacity needs to serve customers. Testing also showed linear scaling across Cobalt 200 physical cores, with vCPU utilization reaching up to 90% while serving traffic.

Compute designed for agents, powered by custom systems

Modern AI applications have evolved from simple inference-based chat interfaces to complex reasoning and agentic systems requiring high-performance compute infrastructure paired with AI acceleration. Cobalt 200 is optimized from the lowest levels of the silicon to the overall rack and system architecture for the demands of agentic compute.

Azure Cobalt 200 server board

At the center of every Cobalt 200 VM is the Cobalt 200 system-on-chip (SoC). Built on TSMC’s advanced 3nm process technology to deliver optimal performance and efficiency, the Cobalt 200 SoC brings together 132 Arm Neoverse V3 cores, with a multi-chipset architecture, and advanced packaging.

Compute: Each vCPU is a full physical core, with 3MB of private L2 cache, and 192 MB of system-level cache, helping provide consistent performance under load while keeping recently accessed data close to the core.

Memory: Cobalt 200 features a custom memory controller with 12 channels of DDR5 and enables memory encryption by default with negligible latency.

Networking and storage: Cobalt 200 VMs include the latest version of Azure Boost, moving networking and storage processing off the host, delivering up to 15% higher network bandwidth, 20% higher remote storage IOPS, and 10% higher remote storage throughput compared with Cobalt 100.

Security: Every Cobalt 200 server includes the Azure Integrated HSM which protects the server hardware from unauthorized intrusion and enables protected encryption key storage for hosted workloads.

Acceleration: Integrated compression and cryptography accelerators enable Microsoft workloads to reduce CPU consumption by offloading common tasks to specialized low-power silicon. On-chip accelerators will help reduce Azure SQL backup times by up to 2.5 times while minimizing disruption to the live workload.

Expanding choice and control

Predictable performance or peak performance. Cobalt 200 VMs support two processor modes.

Deterministic Mode runs cores at a consistent 3.2 GHz.

Opportunistic Mode can boost cores up to 3.6 GHz when power and thermal headroom allow—delivering up to 12% more performance at the expense of some frequency variability.

Different customers have different needs. Deterministic Mode suits distributed data and analytics clusters which run at the pace of their slowest node, and services with tight performance targets. Opportunistic Mode suits web and API services, transaction processing, and media workloads, where speed matters more than consistency.

Use the ProcessorMode setting to choose deterministic or opportunistic mode when you create a VM or later through the Azure portal, Microsoft Azure CLI, PowerShell, or Azure Resource Manager and Biceptemplates.

Cobalt 200 VM sizes and workload options

More shapes for more workloads. Cobalt 200 VMs are available in five VM series, across general purpose, memory-optimized, high-memory, and storage-optimized families. Cobalt 200 adds two new VM families for Arm-based compute on Azure:

High-memory Mpsv4—with 16 GiB of memory per vCPU for large in-memory databases, ERP systems, large caches, and memory-intensive analytics.

Storage-optimized Lpsv5—with large local NVMe storage and up to 23 TB per VM for data staging, search and indexing, and databases that need fast local storage.

VM seriesvCPUsMemory per vCPUMax memoryLocal NVMe storageMax network bandwidthMax remote storage throughputBest-fit workloadsGeneral purpose: Dplsv7 and Dpldsv71 to 1282 GiB256 GiBDpldsv7: up to 7,040 GiBUp to 85 GbpsUp to 70 GbpsMicroservices, small databases, caches, gaming servers, media encoding, and other non-memory-intensive scale-out workloadsGeneral purpose: Dpsv7 and Dpdsv71 to 1284 GiB512 GiBDpdsv7: up to 7,040 GiBUp to 85 GbpsUp to 70 GbpsWeb and application servers, agentic AI services (agent orchestration, tool sandboxes), small to medium databases, caches, and scale-out enterprise workloads.Memory optimized: Epsv7 and Epdsv71 to 1288 GiB1,024 GiBEpdsv7: up to 7,040 GiBUp to 85 GbpsUp to 70 GbpsLarge relational and NoSQL databases, in-memory caches (Redis, Memcached), vector search and agent memory stores for agentic AI, real-time analytics, memory-intensive EDA(New) High-memory optimized: Mpsv4 and Mpdsv41 to 84,12816 GiB1,388 GiBMpdsv4: up to 7,040 GiBUp to 85 GbpsUp to 70 GbpsLarge in-memory databases, ERP systems, caching layers, large-scale vector search for agentic AI, memory-intensive analytics(New) Storage optimized: Lpsv51 to 1288 GiB1,024 GiBEvery size, up to 23 TB Up to 85 GbpsUp to 70 GbpsAI training data preparation and staging, databases needing local storage, big data analytics, search and index engines

Regional availability: Cobalt 200 VMs are generally available today in 14 Azure regions: Australia East, Canada Central, Central US, East US, East US 2, Indonesia Central, Italy North, Korea Central, South Central US, Spain Central, Sweden Central, UK South, West US 2, and West US 3. Availability will expand to 23 regions by the end of 2026.

For the latest regional availability, see Products Available by Region.

Get started with Azure Cobalt 200 VMs

Cobalt 200 is the next chapter of Arm-based compute on Azure, delivering our highest-performing and leading price-performance general purpose VMs.

Getting started is simple—workloads already running on Cobalt 100 can easily move to Cobalt 200 VMs where they need the additional performance, larger VM sizes, or new VM families.

The Arm software ecosystem has matured alongside our infrastructure. Cobalt 200 VMs are supported by popular Linux distributions, Azure Kubernetes Service (AKS), and multiple deployment and containerization frameworks.

Cobalt 200 currently supports the following operating systems:

AlmaLinuxOracle LinuxSUSE Linux Enterprise ServerAzure LinuxRed Hat Enterprise LinuxUbuntuDebianRocky LinuxWindows 11 Client

You can deploy Cobalt 200 VMs with the Azure portal, SDKs, APIs, PowerShell, and the Azure CLI, and use them with Virtual Machine Scale Sets and as AKS node pools.

Build with Cobalt today

Learn about Cobalt 200 VM sizes and deployment guidance.

Learn about Azure Compute VM pricing.

Join us at our Microsoft Ignite 2026 session BRK440. Cobalt 200: Delivering Azure’s best performance and efficiency.

Learn more about Microsoft Azure infrastructure, from silicon to systems.

Learn about Arm64-based computing in the cloud from Arm.

Linux server software for Arm, with recommended versions, in the Software Ecosystem Dashboard for Arm.

Windows server software for Arm, with recommended versions, in the Software Ecosystem Dashboard for Arm.

Learn about Linux readiness for Cobalt 200 from Canonical.

For additional questions, contact Azure support or your Microsoft account team.

Azure Cobalt 200 VMs

The leading price-performance general-purpose VMs in the Microsoft Azure fleet.

Discover more

The post Azure Cobalt 200 VMs now available, proven on real workloads and built for the agentic era appeared first on Microsoft Azure Blog.
Quelle: Azure

Microsoft and Oracle bring agentic AI into flow of enterprise work

This blog is co-authored by Arpan Shah, SVP of Oracle Databases and Muneer Mirza, VP of Multicloud at Oracle Cloud Infrastructure (OCI).

Today at Microsoft Ignite, we’re bringing agentic AI into the flow of enterprise work. Our new integrations let AI agents reason across Oracle’s business-critical data—from finance and supply chain to HR and customer operations—and the work context Microsoft Work IQ understands across meetings, email, documents, and Teams. Customers can access this combined intelligence through Excel, Teams, and Microsoft Copilot. Built on Oracle AI Database@Azure, the integrations help businesses turn trusted enterprise data into insights and actions, with the choice, security, and performance mission-critical workloads demand.

Learn more about Oracle on Azure

With Oracle AI Database@Azure, Oracle and Microsoft have helped customers modernize critical workloads to improve application performance and unlock more value from their enterprise data, by bringing databases closer to applications and connecting enterprise data with Microsoft AI. Oracle AI Database@Azure now spans 33 Azure regions, more than on any other hyperscaler, delivering the performance and flexibility customers need.

At Oracle AI World 2026, we announced new capabilities for Oracle AI Database@Azure including FedRAMP Class D certification coming soon for US Government and public-sector workloads, and Proximity Placement Groups (PPGs) that enable customers to place their database closer to applications—resulting in approximately 50% lower VM-to-Exadata network round-trip latency than deployments without PPG alignment. Now, at Microsoft Ignite 2026, we’re building on that momentum.

For IT operations: Monitoring and trust at every layer

Today, we’re announcing limited preview of Azure Workload Center for Oracle, bringing each workload’s architecture, resources, and dependencies together through a construct called a Workload Virtual Instance (WVI). This significantly reduces the complexity and resources required to manage solutions at the individual component level. Integrations across the Workload Virtual Instance, Azure Monitor Health Models, and the Microsoft Azure Copilot Run Oracle agent connect monitoring signals across application, database, and infrastructure layers.

This operational visibility is complemented by agent access controls: Oracle AI Database@Azure supports Microsoft Entra authentication and Oracle Deep Data Security, helping agents stay within users’ existing permissions while database calls run through the managed model context protocol (MCP) server and activity remains auditable across your Oracle database estate.

For example, after business users report poor performance from an order processing application, an admin must quickly diagnose and fix the problem. The admin signs in with their existing Microsoft Entra identity and uses Azure Workload Center for Oracle to get a unified view of workload health including signals across the infrastructure, database, and application layers while Copilot provides a summary highlighting where to focus.

The admin uses a natural-language prompt to initiate a coordinated investigation involving multiple agents, each with Oracle data access limited by their identify profile. Database calls from the agents run through the managed MCP server, and every action is captured for audit. Working together, the agents synthesize their findings into a single operational conclusion for the admin.

For end users: Oracle data in the flow of work

Business users need insights from Oracle data, but they often need assistance from someone more technical to extract, format, and deliver it.

The new Oracle AI Database plug-in for Excel, available today, lets users connect Excel directly to Oracle Database, pull trusted data into the worksheet, and reason over it with Copilot without leaving the spreadsheet. No export, no manual preparation, no ticket to IT.

Together, Microsoft and Oracle are bringing intelligence to the workflows that run the business: giving analysts, planners and controllers the power to understand margin changes, analyze shifts in demand, resolve reconciliation issues, and act on supply chain disruptions. Copilot analyzes Oracle transaction data and enriches it with context from Work IQ, drawn from meetings, email, documents and Teams, to identify exceptions, draft an explanation, and prepare a governed action plan for review. Rather than another dashboard, or disconnected chatbot, this is AI in the flow of work, grounded in systems of record maintained in Oracle AI Database.

For developers: Build trusted agents quickly, from prototype to production

Pilots are easy; production is hard. Real processes span multiple data sources, call for several specialized agents, and demand answers a business can stand behind. Developers can build agents that connect to Oracle AI Database using Microsoft Foundry with Managed Model Context Protocol (MCP) servers and A2A protocol.

MCP servers enable governed access from Azure agents to Oracle AI Database, whether it runs in Oracle Cloud Infrastructure or as Oracle AI Database@Azure, through approved SQL and PL/SQL operations, tools, and predefined reports. Application roles determine which tools each user or group can use, so agents never reach beyond what IT has sanctioned, and AI comes to the data rather than the data being copied out to AI. These integrations make Oracle AI Database a first-class source of knowledge, memory, and data for agents built in Microsoft Foundry.

For example, a developer builds a sales intelligence application involving an agent retrieving account and order data from Oracle AI Database through MCP, a product agent identifying cross-sell opportunities, and a finance agent weighing in on account health. Through coordinated activity across these agents, the sales intelligence team receives a concise sales brief through an API.

In another scenario, a customer service agent, grounded through Foundry IQ, can answer questions about a policy or an account with supporting citations, and recall the customer history from Oracle-backed memory, retrieve similar past interactions, and responds with context.

Get started with Microsoft Foundry

Experience it all at Microsoft Ignite

Visit Oracle booth #6163 at Microsoft Ignite to see demos, attend an in-booth theater session, and meet with an Oracle specialist to discuss your specific requirements.

Register for Microsoft’s Breakout session BRK435 on combining workload intelligence and AI-ops. Check out Oracle’s event resource page to learn more and be sure to register for the Oracle Theater session THRSP1082 for more information on Azure Workload Center for Oracle.

Oracle on Azure

Migrate Oracle workloads and unlock AI-powered innovation with Azure services.

Learn more

The post Microsoft and Oracle bring agentic AI into flow of enterprise work appeared first on Microsoft Azure Blog.
Quelle: Azure

Introducing Azure Catalyst agentic modernization and new AI infrastructure innovations

As AI continues to reshape how every business builds, operates, and competes, it is rapidly emerging as the defining workload in the cloud. This new class of agents, more demanding, complex, and dynamic than anything before them, is rewriting the rules of cloud infrastructure. Reasoning across multi-agent systems, drawing on rich context, acting in real time, and running continuously, they ask more of every layer of the platform beneath them. This week, we’re introducing innovations across Microsoft Azure that set a new standard for how the cloud powers AI: expanded AI core capabilities in Azure to build what’s next, and Azure Catalyst, an intelligent agent-led solution to modernize the apps, data, and infrastructure that already run the business.

For years, we have been reengineering every layer of Azure for the unique demands of AI and proving it on the world’s most advanced AI workloads, from leading frontier models to our own GitHub Copilot, Microsoft Teams, and Microsoft 365. That work has forged Azure into a single, co-engineered system, with models, silicon, and cloud infrastructure tuned as one and value compounding at every layer. This week, we take that even further.

Explore Microsoft Azure

New capabilities across isolated execution, agent networking, context management, and inference efficiency deliver faster, more secure agents with better unit economics. Every innovation rests on an open foundation, giving customers the freedom to run open models and open systems everywhere they operate. There is a wave of new AI applications scaling in production, and years of existing apps and data are moving to the cloud, becoming AI-ready. Azure was built for this moment.

Of everything we’re announcing this week, three areas matter most:

Building the next generation of AI applications. Silicon, compute, storage, and networking work as one system across Azure for inference, training, and agents. A new connected path from Microsoft Foundry to Azure Kubernetes Service (AKS) gives you choice in how and where you run AI.

Modernizing apps and data with agents. Azure Catalyst uses AI agents to modernize applications, data, and infrastructure in a fraction of the time and cost of traditional methods, turning decades of technical debt into the fastest path to AI.

Extending AI wherever you operate. Azure Local, flex nodes for AKS and Microsoft Foundry extend AI across cloud and distributed environments, governed through Azure Arc. Windows Server 2028, now in public preview, and Windows PCs, bring AI closer to applications, data, and users, providing the choice to meet workload-specific data, performance, regulatory, and cost needs.

Build and run the next generation of AI applications

Microsoft Foundry and AKS are at the center of how you build and run AI from Foundry’s managed experience, to the deep customization of AKS across models, runtimes, performance, security, and infrastructure.

The connected path between them runs from building AI applications and agents to running them at scale. Open-weight models and agents move seamlessly from Foundry to AKS clusters, deployed from cloud to edge, with consistent infrastructure, security policies, and governance.

Learn more about Azure Kubernetes Service (AKS)

Underneath these experiences, AI applications are challenging infrastructure in new ways: writing and executing code autonomously, connecting dynamically to multiple agents, models, tools, and data, and carrying context across long-running tasks. We’re advancing the infrastructure to meet each of these demands:

Isolation and confidentiality. With the Agent Sandbox extension for AKS, agent-generated code runs in secure, managed sandboxes with virtual machine (VM)-level isolation for every session, pre-warmed pools for fast startup, and a serverless option with no infrastructure to manage. Azure confidential computing extends protection to sensitive data and workloads while in use.

Agent networking and security. With Agent Grid, agents securely connect to other agents, models, tools, data, and Azure services through authenticated, encrypted connections. Identity-driven policies and default-deny network isolation control how agents communicate and what resources they can access.

Context and state. Long-context, long-running agents reuse processed prompt context instead of recomputing it on the GPU, so long tasks run faster and cost less. That cached context stays durable and controlled, by you, in your Azure tenant.

And we’re making Azure itself more intelligent, building in new workload-aware capabilities that combine deep context for what each AI application requires with what only the platform delivers: GPU and VM performance, topology, and real-time availability across the fleet. AKS AI Manager translates what each model needs into the right infrastructure, placing each deployment where the fleet has the GPU capacity to serve it best. The result is a cloud that makes every AI workload perform better, with faster responses, better economics, and optimal placement decisions.

And across all of this, we’re extending our commitment to open-source, giving you transparency and access to the best innovation shaped by the community. Kubernetes, vLLM, and Ray, together with flex nodes for AKS in preview, bring greater flexibility from development through production, including supported GPU environments beyond Azure. You have the freedom to build on the best model, use the right framework, and run where your business needs it.

We’re already seeing what’s possible with these innovations. Rockwell Automation is using AI in its factories to help engineers diagnose equipment issues and investigate product failures. As these applications move into production, Rockwell wants to build on what works and bring those approaches to other facilities:

Running our factory-level AI applications on Azure gives us one foundation for different AI workloads in production. When something works in one plant, we can adapt it for the next instead of starting over.
—Justin Litherland, Vice President, Enterprise Program Management, IT, Rockwell Automation

Within our own teams, Microsoft 365 engineering built COSMIC, a shared platform on AKS, to help them ship faster with built-in security, compliance, and reliability. Making infrastructure easier to run matters for developers. COSMIC handles infrastructure centrally so developers can focus on customer experiences rather than Kubernetes operations. What we learn as our own customer continues to shape future Azure capabilities for you.

To go deeper at Microsoft Ignite, check out these sessions:

BRK420: Deploy and run Microsoft Foundry models and agents on Kubernetes

BRK448: Run secure agent loops in production with isolated sandboxes at scale

BRK429: The evolution of Azure infrastructure for AI models, apps, and agents

Learn more about Microsoft Foundry

Modernize applications and data with Azure Catalyst

The need to modernize is universal. But with developers stretched thin, custom code and deep running dependencies, progress often stalls and the backlog keeps growing. Decades of technical debt adds security exposure, cost and complexity, while disconnected tools create friction from assessment to execution.

Agents in Azure Catalyst change that, analyzing legacy code, mapping dependencies, and planning and executing with precision. Work that once took months or years can now be done in weeks or even days, even with limited resources and skills, making it possible to modernize systems that were previously out of reach.

Learn more about Azure Catalyst

The results are real: 1.4 million applications modernized, with businesses like Levi Strauss modernizing its enterprise systems and deploying more than 1,000 agents across them.

Azure Catalyst modernizes end to end—across applications, data, and infrastructure in one solution—delivered in the tools hundreds of millions of developers and IT professionals already use. Here’s what sets it apart:

One connected experience

Azure Catalyst connects IT teams and developers across an end-to-end process from discovery to design and execution. New capabilities add rich estate insights, AI-powered application discovery, modernization strategy and cost comparisons, and AI-generated migration waves. Execution spans applications, containers, storage, networking, and databases, and builds on existing coverage for Java and .NET modernization and migration support for VMware, Hyper-V, and physical servers.

Tailored to your business

Governance rulebooks and bring-your-own-model support let you set the standards, guardrails, and models agents follow, so plans fit your architecture, priorities, and security requirements. Reusable runbooks and skills make what works repeatable, so every project meets your exact standards.

Secure from the start

Outdated applications and data increase security exposure. Azure Catalyst works with Microsoft Security to find, prioritize, and eliminate vulnerabilities end to end. Together they scan and rank risk, prioritize actions by severity and exposure, and flag vulnerable code and databases for modernization. Through GitHub Copilot you can quickly remediate vulnerabilities as applications are modernized, fixing them once and shipping as both modern and hardened.

Ready for AI

Azure Catalyst works in GitHub Copilot to help teams understand the business logic and dependencies of complex applications and upgrade those apps to run on Azure’s managed services. These upgrades make it easier to connect apps to AI workflows. New previews support modernizing applications and databases together and migrating from BizTalk to Azure Logic Apps. And because Azure Catalyst is built for Azure, it optimizes performance, security, and economics along the way.

const currentTheme =
localStorage.getItem(‘blogInABoxCurrentTheme’) ||
(window.matchMedia(‘(prefers-color-scheme: dark)’).matches ? ‘dark’ : ‘light’);

// Modify player theme based on localStorage value.
let options = {“autoplay”:false,”hideControls”:null,”language”:”en-us”,”loop”:false,”partnerName”:”cloud-blogs”,”poster”:”https://cdn-dynmedia-1.microsoft.com/is/image/microsoftcorp/1307382-azurecatalyst_tbmnl_en-us?wid=1280″,”title”:”1307382-azurecatalyst”,”sources”:[{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307382-azurecatalyst-0x1080-6439k”,”type”:”video/mp4″,”quality”:”HQ”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307382-azurecatalyst-0x720-3266k”,”type”:”video/mp4″,”quality”:”HD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307382-azurecatalyst-0x540-2160k”,”type”:”video/mp4″,”quality”:”SD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307382-azurecatalyst-0x360-958k”,”type”:”video/mp4″,”quality”:”LO”}]};

if (currentTheme) {
options.playButtonTheme = currentTheme;
}

document.addEventListener(‘DOMContentLoaded’, () => {
ump(“ump-6aff12b39cdf3″, options);
});

Microsoft is customer zero for agent-led modernization, putting the same agentic tooling in Azure Catalyst across our estate. Microsoft Quantum and Xbox achieved 80% faster app modernization, while Intune upgraded a key library 75% faster than anticipated. GitHub ported the GitHub Copilot agentic harness—800,000 lines of production code—from TypeScript to Rust. By using these technologies ourselves, we learn firsthand what it takes to modernize complex, production-scale systems, from targeted fixes to large-scale code transformation, and apply those lessons to help you modernize your own environment.

For a full breakdown, read the Azure Catalyst announcement blog. To go deeper at Microsoft Ignite, check out these sessions:

BRK412: Rethink modernization end to end with agents

BRK409: Modernize faster with AI-powered discovery, planning, and execution

BRK410: Accelerating Java, .NET, and database modernization with agents

Read more about Azure Catalyst in this blog

Run AI across cloud, edge, and devices

Across cloud, enterprise infrastructure, edge, physical systems, and personal devices, we’re giving you the power to run AI where your business needs it. Azure Local and flex nodes for AKS extend cloud infrastructure and Kubernetes compute into distributed environments, while extending Microsoft Foundry across these environments. Azure Arc provides consistent infrastructure management and governance end to end. New at Microsoft Ignite, Windows Server 2028 enables AI inference alongside business-critical applications and data, while Windows PCs bring intelligence directly to the devices where people work through local processing. Together, you compose the right infrastructure for each AI workload to best meet data, performance, regulatory, and cost requirements.

For a full breakdown, read the Windows Server 2028 blog. To go deeper at Microsoft Ignite, check out these sessions:

BRK418: What’s new and what’s next for Windows Server

BRK442: Build sovereign AI with Azure Local and Foundry Local

Read more about Windows Server 2028 in this blog

Innovate on an open foundation for what comes next

The architecture decisions you make today will carry your business for the next decade. Our job is to ensure the systems you depend on now can evolve into an AI-powered future, and that everything you build next runs on an open, co-engineered platform with choice over your models and where your workloads run. The real test of everything we’re introducing is how these solutions perform in your environment. We’ll keep listening and building alongside you.

This week, I’m looking forward to Mark Russinovich, Chief Technology Officer (CTO), Deputy Chief Information Security Officer (dCISO), and Technical Fellow, Microsoft Azure and Pavan Davuluri, Executive Vice President, Windows and Devices, discussing why Azure and Windows are the foundation for mission-critical AI, from datacenters to the edge to a billion devices, at INV643: AI infrastructure from cloud to edge. We’d love to see you there.

Microsoft Azure

Azure unifies infrastructure, data, applications, and AI on a trusted cloud platform to accelerate innovation and scale AI with confidence.

Learn more

The post Introducing Azure Catalyst agentic modernization and new AI infrastructure innovations appeared first on Microsoft Azure Blog.
Quelle: Azure

Microsoft Ignite 2026: What’s new in Azure, the platform purpose-built for AI

Azure at Microsoft Ignite 2026: The headlines

Azure AI core: AI on infrastructure you control.

Azure Cobalt 200: Our highest-performing general-purpose virtual machines (VMs).

Azure Catalyst: Agent-led modernization from plan to code.

Agentic cloud operations: Agents that keep your cloud running well.

Azure HorizonDB and Fabric HorizonDB: PostgreSQL for AI apps and analytics.

Fabric apps: Governed apps built on trusted data.

Microsoft IQ: Context for every agent.

Over the past year, my conversations with customers have changed. A year ago, the question was which model to choose. Now it’s how to put agents to work on the processes that run the business, and how to trust them to do it.

With the same frontier models available to everyone, the advantage comes from what no one else has: your context. It’s how your business runs, what your people know, and the systems and data you’ve spent years building. That’s your IQ. It’s your intellectual property, so it should stay yours, and it should work wherever your people and agents do. Our job is to make every layer beneath your agents better, from the infrastructure that runs them and the estate they act on to the apps they power and the business context that tells them how your company works.

Azure is the foundation of Frontier Transformation. We engineer Azure as one system, so the knowledge an agent needs stays governed and the security you use to protect your people extends to the agents acting for them. And because we’re evolving the open, cloud-native platform you already rely on, you don’t have to start over.

See what Azure can do for your business

As Satya Nadella shared at Microsoft Build in June, we added more datacenter capacity in 18 months than in Azure’s first decade. Combined with more regions than any other cloud provider, you can scale your AI workloads globally with confidence as demand grows.

This week at Microsoft Ignite, we’re sharing what’s new across every layer of the platform. New capabilities spanning compute, storage, and networking let you run AI at scale with the control of your own infrastructure, without having to build, secure, and operate all of it yourself. Azure Catalyst brings agent-led modernization together in one experience from estate to code.

PostgreSQL now has two homes at Microsoft: Azure HorizonDB, generally available for mission-critical scale, and the new Fabric HorizonDB, which connects your PostgreSQL apps to analytics and AI. And Fabric apps, now generally available, let your teams turn trusted enterprise data into working apps.

We’re also introducing Microsoft IQ, the enterprise context management platform that helps you build your own IQ and put it to work in every app and agent. It also gives your teams a path on Azure to build, run, and continuously improve those agents.

Run AI at scale with the control you choose

It starts with the infrastructure that runs your agents. As they take on real work, you should be able to run them on your terms, with your choice of models, your data, and where they run. That control lets you find the right balance of performance and cost for each workload and adapt as models and needs change.

But control comes with real work and risk. Platform teams end up assembling and operating much of the AI stack themselves and stretching GPUs to keep up with shifting demand. Agents that reach models, tools, and data and run code on their own open new security gaps, putting sensitive data at risk.

Teams want the control of running their own AI infrastructure without taking on all the manual toil of building, securing, and operating it.

Building the AI core on Azure

That’s what we’re bringing to Azure. New capabilities across compute, storage, and networking come together as one AI foundation, so you keep control of your models and workloads while Azure takes on the work underneath. Build AI with Microsoft Foundry in a fully managed experience and run it at scale with Azure Kubernetes Service (AKS) when you need more control over performance, security, and cost.

Ignite session: AI infrastructure from cloud to Edge

Watch now ↗

Azure sets up and tunes the infrastructure for you, so your teams spend less time on configuration and more time moving models and agents into production. Workloads are placed based on available capacity, so your GPU investment goes further as demand grows. Security is enforced centrally across agents, models, and tools, giving security teams consistent controls wherever agents run. And because it’s built on open-source projects, your workloads stay portable, including to your own servers outside Azure, keeping your options open as your needs change.

The result is AI that scales with your business, on infrastructure you control.

To hear how organizations are operating AI at scale, join Mark Russinovich and Pavan Davuluri in the innovation session “AI Infrastructure from cloud to edge.”

Strengthening every layer of your AI estate with Azure Cobalt 200

Agents reason, make decisions, and run continuously, and that’s reshaping what cloud infrastructure needs to deliver. That’s why we design Azure as one system, from silicon to servers to services. We pair our own Maia and Cobalt chips with the latest from NVIDIA and AMD, so every workload runs on the right silicon for the job. Our strategy focuses on building performance, efficiency, and security into every layer. The result is AI that’s faster and more economical to run at scale, on a roadmap you can plan around.

Ignite session: cobalt 200…

Watch now ↗

Azure Cobalt 200 virtual machines, our highest-performing general-purpose VMs, are now generally available. Designed from the ground up for scale-out, cloud native, and agentic AI workloads, these VMs deliver up to 50% better CPU performance compared to our Cobalt 100 VMs. Together with Maia, they give you an infrastructure you can plan around.

Read about the latest Azure Cobalt updates in this blog

Agent-led modernization and operations, from estate to code

Agents are only as useful as the systems they can act on. Much of what makes your company unique is built into your applications and databases and years of business logic your teams rely on. Modernizing puts existing apps and data to work in new AI-powered experiences, helps teams ship faster, and lowers the cost and risk of running older systems, creating a more adaptable foundation for growth.

Getting there isn’t easy. Modernizing can mean mapping complex systems and changing code that few people fully understand. Keeping the estate running well means sorting through constant signals with little knowledge on what matters most. And as agents take on more of that work, teams need to let them act while keeping the oversight your business requires.

That’s why we’re bringing agents to both, from estate to code. Azure Catalyst helps you modernize applications, code, and databases from plan to execution. And new capabilities in Azure Copilot, Azure SRE Agent, and Azure Monitor help keep your cloud and databases running well, with people in control.

Modernize for AI with Azure Catalyst

Azure Catalyst is a new unified experience for agentic modernization. It brings discovery, planning, migration, modernization, and code intelligence together, so IT teams and developers work from the same plan across infrastructure, applications, and data. Azure Catalyst modernizes the technology you already have into a foundation for AI, putting the business logic in your existing applications to work in new AI-powered experiences and agentic business processes.

Ignite session: rethink modernization…

Watch now ↗

For IT teams, Azure Catalyst agent extends from migration planning into deeper modernization and execution. For developers, GitHub Copilot modernization carries that plan into code in the tools they already use, with agent governance rulebooks and bring-your-own-model support that customizes your modernization project to the specifications of each business. And Azure Catalyst delivers a deeper understanding of how enterprise applications work, so teams can assess the impact of changes, modernize faster, and find where legacy processes could be reimagined with AI.

Ignite session: modernize faster with ai…

Watch now ↗

Modernization can also close security gaps. End-of-support runtimes, unpatched dependencies, and aging code widen your threat surface. Azure Catalyst works with Microsoft Security to fix that: Microsoft Perception and MDASH rank vulnerabilities across your estate and code, Azure Catalyst identifies vulnerable code and databases to modernize first, and GitHub Copilot turns those findings into fixes in the same pass. Each app comes out more secure than it went in.

const currentTheme =
localStorage.getItem(‘blogInABoxCurrentTheme’) ||
(window.matchMedia(‘(prefers-color-scheme: dark)’).matches ? ‘dark’ : ‘light’);

// Modify player theme based on localStorage value.
let options = {“autoplay”:false,”hideControls”:null,”language”:”en-us”,”loop”:false,”partnerName”:”cloud-blogs”,”poster”:”https://cdn-dynmedia-1.microsoft.com/is/image/microsoftcorp/1307382-azurecatalyst_tbmnl_en-us?wid=1280″,”title”:”1307382-azurecatalyst”,”sources”:[{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307382-azurecatalyst-0x1080-6439k”,”type”:”video/mp4″,”quality”:”HQ”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307382-azurecatalyst-0x720-3266k”,”type”:”video/mp4″,”quality”:”HD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307382-azurecatalyst-0x540-2160k”,”type”:”video/mp4″,”quality”:”SD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1307382-azurecatalyst-0x360-958k”,”type”:”video/mp4″,”quality”:”LO”}],”ccFiles”:[{“url”:”https://azure.microsoft.com/en-us/blog/wp-json/bloginabox/v1/get-captions?url=https%3A%2F%2Fwww.microsoft.com%2Fcontent%2Fdam%2Fmicrosoft%2Fbade%2Fvideos%2Fproducts-and-services%2Fen-us%2Fazure%2F1307382-azurecatalyst%2F1307382-azurecatalyst_cc_en-us.ttml”,”locale”:”en-us”,”ccType”:”TTML”}]};

if (currentTheme) {
options.playButtonTheme = currentTheme;
}

document.addEventListener(‘DOMContentLoaded’, () => {
ump(“ump-6aff12b3a1941″, options);
});

Learn more about Azure AI foundation and Azure Catalyst in this blog

Keep your cloud running well with agentic operations

As applications scale across hybrid infrastructure, microservices, and AI workloads, leading organizations are moving to operating models where insight flows directly into action. That’s the idea behind agentic operations: AI agents, guided by your intent, continuously observe, reason, and help take action across the cloud lifecycle. Signals feed coordinated workflows that improve performance, cost, and reliability as systems run, with people kept in control.

At Microsoft Ignite, we’re bringing that model to more of your estate. Azure Copilot‘s deployment agent, now generally available, helps you go from requirements described in natural language to deployed cloud workloads. You can even extend agentic operations to Oracle and SAP with Azure Workload Center, now in limited preview.

Ignite session: put ai agents to work…

Watch now ↗

Azure SRE Agent brings agentic operations into secure production environments, with new enterprise controls in preview, while Microsoft Entra Agent ID and Agent 365 give central teams a consistent way to discover, govern, and audit agents throughout their lifecycle. We’re also giving agents richer data and understanding so they can detect issues earlier, diagnose problems faster, and take more effective action. Azure Monitor health models, now generally available, give agents a real-time view of your application architecture and business priorities, so they can recommend fixes.

const currentTheme =
localStorage.getItem(‘blogInABoxCurrentTheme’) ||
(window.matchMedia(‘(prefers-color-scheme: dark)’).matches ? ‘dark’ : ‘light’);

// Modify player theme based on localStorage value.
let options = {“autoplay”:false,”hideControls”:null,”language”:”en-us”,”loop”:false,”partnerName”:”cloud-blogs”,”poster”:”https://cdn-dynmedia-1.microsoft.com/is/image/microsoftcorp/1306765-agenticoperations_tbmnl_en-us?wid=1280″,”title”:”1306765-agenticoperations”,”sources”:[{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-agenticoperations-0x1080-6439k”,”type”:”video/mp4″,”quality”:”HQ”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-agenticoperations-0x720-3266k”,”type”:”video/mp4″,”quality”:”HD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-agenticoperations-0x540-2160k”,”type”:”video/mp4″,”quality”:”SD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-agenticoperations-0x360-958k”,”type”:”video/mp4″,”quality”:”LO”}],”ccFiles”:[{“url”:”https://azure.microsoft.com/en-us/blog/wp-json/bloginabox/v1/get-captions?url=https%3A%2F%2Fwww.microsoft.com%2Fcontent%2Fdam%2Fmicrosoft%2Fbade%2Fvideos%2Fproducts-and-services%2Fen-us%2Fazure%2F1306765-agenticoperations%2F1306765-agenticoperations_cc_en-us.ttml”,”locale”:”en-us”,”ccType”:”TTML”}],”downloadableFiles”:[{“url”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-agenticoperations_transcript_en-us”,”locale”:”en-us”,”mediaType”:”transcript”},{“url”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-agenticoperations_audio_en-us”,”locale”:”en-us”,”mediaType”:”audio”}]};

if (currentTheme) {
options.playButtonTheme = currentTheme;
}

document.addEventListener(‘DOMContentLoaded’, () => {
ump(“ump-6aff12b3a1ea4″, options);
});

Learn more about agentic operations in this blog

Build the next generation of AI apps

Then there are the apps your agents power, where business data becomes business value. The question for every organization is how quickly it can move from idea to an app the entire business can rely on. Today, the people building AI apps span the whole organization. Developers are creating mission-critical systems and new apps with agents, while teams across the business are describing the app they need in Copilot. Each needs something different from the platform, but every app needs to connect to business data and run under governance IT can trust.

We’re building one foundation for all of them, and it starts with PostgreSQL, the database of choice for a growing share of developers. With Azure HorizonDB and Fabric HorizonDB, you can run PostgreSQL wherever your apps need it, from mission-critical systems to analytics and AI. Fabric apps builds on that foundation, so teams can turn business data into working apps, whether they start in code or in conversation.

Power your AI apps with PostgreSQL on Azure HorizonDB and Fabric HorizonDB

The apps developers build now reason over data, call models, and act for users, so the database underneath has to bring transactions, vectors, and AI together at mission-critical scale. Azure HorizonDB, now generally available, is a fully managed, PostgreSQL-compatible database built for that work. It delivers millisecond latency with built-in vector indexing, so your apps can find, reason over, and act on data in one place. Enterprise-grade security comes built in, and developers can work in tools they already know, including GitHub Copilot and Visual Studio Code.

ignite session: data foundations for modern apps…

Watch now ↗

We’re also extending the power of PostgreSQL directly into Microsoft Fabric. Fabric HorizonDB, now in public preview, brings a serverless, Fabric-native PostgreSQL experience alongside SQL database in Fabric and Cosmos DB in Fabric. By bringing operational databases, analytics, and AI together on a unified, governed platform, developers can build intelligent applications with less data movement and complexity. Fabric HorizonDB will also serve as the PostgreSQL backend for Fabric apps.

const currentTheme =
localStorage.getItem(‘blogInABoxCurrentTheme’) ||
(window.matchMedia(‘(prefers-color-scheme: dark)’).matches ? ‘dark’ : ‘light’);

// Modify player theme based on localStorage value.
let options = {“autoplay”:false,”hideControls”:null,”language”:”en-us”,”loop”:false,”partnerName”:”cloud-blogs”,”poster”:”https://cdn-dynmedia-1.microsoft.com/is/image/microsoftcorp/1306765-horizondbvs_tbmnl_en-us?wid=1280″,”title”:”1306765-horizondbvs”,”sources”:[{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-horizondbvs-0x1080-6439k”,”type”:”video/mp4″,”quality”:”HQ”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-horizondbvs-0x720-3266k”,”type”:”video/mp4″,”quality”:”HD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-horizondbvs-0x540-2160k”,”type”:”video/mp4″,”quality”:”SD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-horizondbvs-0x360-958k”,”type”:”video/mp4″,”quality”:”LO”}],”ccFiles”:[{“url”:”https://azure.microsoft.com/en-us/blog/wp-json/bloginabox/v1/get-captions?url=https%3A%2F%2Fwww.microsoft.com%2Fcontent%2Fdam%2Fmicrosoft%2Fbade%2Fvideos%2Fproducts-and-services%2Fen-us%2Fazure%2F1306765-horizondbvs%2F1306765-horizondbvs_cc_en-us.ttml”,”locale”:”en-us”,”ccType”:”TTML”}],”downloadableFiles”:[{“url”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-horizondbvs_audio_en-us”,”locale”:”en-us”,”mediaType”:”audio”}]};

if (currentTheme) {
options.playButtonTheme = currentTheme;
}

document.addEventListener(‘DOMContentLoaded’, () => {
ump(“ump-6aff12b3a265b”, options);
});

To simplify database management across environments, Database Hub in Fabric is now generally available. It provides a unified experience to discover, monitor, and manage databases across Azure, on-premises environments, and Fabric, with Fabric Copilot highlighting what needs attention.

Read the latest Microsoft Databases announcements in this blog

Turn ideas into governed enterprise-ready apps with Fabric apps, now generally available

Great ideas for apps come from every corner of the business, and with Copilot, people can build one in minutes. But taking it from prototype to production on trusted data remains the biggest hurdle. Fabric apps, now generally available, bring together the backend services applications need with direct access to trusted data in Fabric, built-in security, and enterprise governance. Developers and coding agents build in code with open-source tools, and Fabric provisions everything from databases to authentication, with no infrastructure to manage. This makes it easier to turn ideas into enterprise-ready applications that can scale across the organization.

ignite session: build like a startup…

Watch now ↗

We’re also extending Fabric’s role as the data foundation for AI-powered applications. With the new Microsoft Copilot integration, now in Frontier public preview, anyone can describe the app they need and bring it to life, with the option to use Fabric as a ready-to-use data backend providing databases, storage, and data APIs. We’re also introducing Copilot Credits as a new usage-based billing option for Microsoft Fabric, providing greater flexibility alongside existing capacity-based options.

Power BI creators can now build more than static reports. With a new agentic app creation experience in Power BI Desktop, now in preview, they can turn their existing semantic models into interactive apps that capture input, update data, and support operational workflows.

Learn more about Fabric apps in the Ignite Microsoft Fabric blog

Ground every agent in your business context with Microsoft IQ

Most organizations already have the knowledge their agents need. It lives in the semantic models your analysts built in Power BI, the documents and procedures your teams rely on, the conversations happening across Microsoft 365, and the systems of record you run every day, like SAP and Oracle. The problem is that it’s scattered, so every new agent starts from zero and every team rebuilds the same context.

That’s why we’re introducing Microsoft IQ, the enterprise context management platform for building your organization’s IQ. It brings together Work IQ, Fabric IQ, Foundry IQ, Web IQ, and more than 350 connectors, so the knowledge your agents need is captured once, governed in one place, and reused by every agent and app.

At the heart of Microsoft IQ are new business plugins, now available as part of the Frontier program. Business plugins turn what your teams know into trusted context, skills, and tools that anyone across the business can reuse. Take a supply chain disruption. A business plugin can tell an agent to use the components and orders semantic model in Fabric IQ to find the affected orders, the supplier contracts in Foundry IQ to check late-delivery terms, and Work IQ to find who owns the decision. Your domain experts write it once, and every agent across the organization inherits it.

Teams can also reuse proven evaluations across agents instead of rebuilding them. The foundation underneath Microsoft IQ brings Microsoft Foundry and Microsoft Fabric together in one path, built on Azure, to build, run, and continuously improve agents. And Agent 365 gives IT one place to observe, govern, and secure them.

ignite session: Harnessing Your IQ…

Watch now ↗

Your IQ stays yours, and it isn’t locked into one assistant. The same context and business plugins reach your agents wherever they run, in Microsoft Copilot, GitHub Copilot, Microsoft Foundry, and assistants such as Claude and ChatGPT, through model context protocol (MCP) and APIs. Your permissions and governance go with it. Agents can also draw on the business context in your systems of record, like SAP and Oracle, so they work from the data your teams already rely on. Learn more about Oracle’s latest integrations with Microsoft IQ.

See how the Australian Energy Market Operator uses Microsoft IQ to help keep Australia’s power grid secure:

const currentTheme =
localStorage.getItem(‘blogInABoxCurrentTheme’) ||
(window.matchMedia(‘(prefers-color-scheme: dark)’).matches ? ‘dark’ : ‘light’);

// Modify player theme based on localStorage value.
let options = {“autoplay”:false,”hideControls”:null,”language”:”en-us”,”loop”:false,”partnerName”:”cloud-blogs”,”poster”:”https://cdn-dynmedia-1.microsoft.com/is/image/microsoftcorp/1306765-microsoftiq_tbmnl_en-us?wid=1280″,”title”:”1306765-microsoftiq”,”sources”:[{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-microsoftiq-0x1080-6439k”,”type”:”video/mp4″,”quality”:”HQ”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-microsoftiq-0x720-3266k”,”type”:”video/mp4″,”quality”:”HD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-microsoftiq-0x540-2160k”,”type”:”video/mp4″,”quality”:”SD”},{“src”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-microsoftiq-0x360-958k”,”type”:”video/mp4″,”quality”:”LO”}],”ccFiles”:[{“url”:”https://azure.microsoft.com/en-us/blog/wp-json/bloginabox/v1/get-captions?url=https%3A%2F%2Fwww.microsoft.com%2Fcontent%2Fdam%2Fmicrosoft%2Fbade%2Fvideos%2Fproducts-and-services%2Fen-us%2Fazure%2F1306765-microsoftiq%2F1306765-microsoftiq_cc_en-us.ttml”,”locale”:”en-us”,”ccType”:”TTML”}],”downloadableFiles”:[{“url”:”https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/1306765-microsoftiq_transcript_en-us”,”locale”:”en-us”,”mediaType”:”transcript”}]};

if (currentTheme) {
options.playButtonTheme = currentTheme;
}

document.addEventListener(‘DOMContentLoaded’, () => {
ump(“ump-6aff12b3a337e”, options);
});

Nearly 60,000 customers already use Microsoft IQ today. And because every agent builds on the same context, each one you add makes the next one better.

Learn more about Microsoft IQ in this blog

Experience these innovations at Microsoft Ignite

Every agent you build is only as good as what it knows about your business. That’s why we’re making sure your IQ, the context that makes your company unique, is available to your agents across every layer of Azure, with governance and security built in. It stays yours, and its value grows with everything you build on it. To learn more about Microsoft IQ, I encourage you to join my Microsoft Ignite session, “Harnessing Your IQ with a continuously improving agent platform,” in person or online at no cost, or watch the recording afterward.

For a closer look at all the innovation we are bringing to Azure, explore the full list of sessions on the Microsoft Ignite session catalog.

Explore Azure at Microsoft Ignite

See how Azure Catalyst, Azure HorizonDB, and other Azure innovations help you modernize your estate and build AI apps.

See all sessions

The post Microsoft Ignite 2026: What’s new in Azure, the platform purpose-built for AI appeared first on Microsoft Azure Blog.
Quelle: Azure

Meet the New Docker: Built to Run on Trust

Evolving an iconic brand for the agentic era

Today, Docker is officially launching its new brand, and I’m excited to tell you what it’s all about and why we think now is the time for change.

Let’s start with the big picture. We’re living through a transformative moment: for Docker, for developers, for the industry, and quite possibly, for humanity itself. AI is creating possibilities that would have sounded like science fiction not long ago.

But it’s also forcing the industry to confront an almost existential question: how do we harness all that power and intelligence without compromising security, governance, or control? Or, put more simply: how do we get to a point where we can actually trust agents?

That one seemingly simple yet infinitely complex question is why we’re here today, introducing you to a new Docker. 

A new Docker, but a familiar story. 

We’ve been here before

Ok, not exactly here, but once upon a time, a decade or so ago, the tech industry was at a similar inflection point. Digital transformation was the term du jour, promising a new way of engaging customers and powering the global economy. There was one big constraint, though: teams needed a better way to build, ship, and run software consistently across any environment. 

Enter a company you might have heard of: Docker. 

Together with all of you, Docker built the standard trusted by millions of developers. For over a decade, developers have relied on us to make software portable, open, reproducible, and secure. Docker turned the frustration of “Well, it works on my machine!” into the assurance that “Yes, it works everywhere.”

Today, of course, the challenge confronting us is new and evolving, and we all need to evolve with it. We cannot simply continue to do what we’ve always done and expect to succeed in this new era. That applies to business leaders, developers, tech companies, everyone. It certainly applies to Docker. That’s what this rebrand is about: evolving to meet the moment for our customers.

What isn’t changing

Let me be unequivocal: this is not about leaving Docker’s legacy or heritage behind. We’ve spent more than a decade earning your trust. This is about building on that foundation, not replacing it.

The qualities you value us for aren’t changing. We’re still committed to openness and industry collaboration. We’re still, and always will be, developer-first. We’re still fanatical about simplicity, and about showing up everywhere you need us. 

On the product front, the containers you know and love aren’t going anywhere. Containers still play a huge role in the software development lifecycle. As long as that’s the case, Docker will continue leading the way.  

Containers weren’t designed for agents 

Agents have introduced a new problem. Containers isolate workloads. But agents aren’t workloads. Agents are actors. 

Agents make their own decisions about what to run, what to access, and what to change. Developers and enterprises need solutions built specifically to isolate and govern them, so they can give those agents real autonomy without giving up control. 

Docker’s next chapter is about delivering exactly that: security, isolation, and governance, so we can all trust agents to do meaningful work without feeling like we’re always one step from catastrophe.

Run on trust 

In case I haven’t made it blindingly obvious yet, the new Docker is all about trust.

Trust Docker because our track record speaks for itself. Trust Docker because we’re proven, neutral, and secure. Trust Docker because it’s pretty darn clear you can’t trust the agents to manage themselves. 

Trust us because we have a software supply chain that is already the standard for building securely. Trust us because nobody isolates agents where they run better than we do. Trust us because we’re taking a comprehensive approach to improving governance and minimizing risk across the entire enterprise. 

Trust Docker because we’re not egotistical enough to think we can solve a challenge this big alone. Trust us because everything about our history, our heritage, and our actions over the past year tells you we’ll partner with the smartest and build alongside the best, and not create vendor lock-in. 

Most of all, trust Docker because we’re not just talking the talk. We’ve got the goods to back it up: trusted supply chain for your agents to build from, trusted runtime to isolate your agents, and a trusted ecosystem to ensure all the layers of trust are covered, whether made by Docker or not.

A whale of an evolution

As our product team innovated to meet the moment and our messaging in the market began to shift, one thing became clear: the speed and scale of evolution happening inside Docker called for an equally momentous evolution on the outside. Something that makes it unmistakably clear that it’s a new day for Docker. Something that says and shows, loud and clear, for all the world to see, that Docker is not just about containers anymore. 

Something big. 

Something, dare I say, whale sized. 

I’m talking, of course, about our beloved Moby. 

If you know Docker, then you know Moby, and if Docker is evolving, Moby should too. The only question was to how and to what extent? We looked at a lot of whales, folks. (I may or may not have been seeing whales in my sleep.) Ultimately, with the help of our friends at the strategic brand transformation company, Motto, we landed on a new Moby for the new Docker.

Watch Moby’s transformation here:

In many ways, Moby is a microcosm for Docker and the changes we’re making: the Moby you love and trust, evolved for a new era. Just as the new Docker is no longer singularly defined by containers, neither is the new Moby.

Come take a look around

We’ve got lots to show you. Poke around our new website. Find and engage with the new Docker brand on social media. And if you want to see what trust in the agentic era looks like in practice, try Docker Sandboxes and Docker AI Governance. We’d love to hear what you think.

Wherever this new era takes us, Docker will always honor and cherish the trust you continue to place in us. Now, let’s go build what’s next.

Quelle: https://blog.docker.com/feed/

Docker patches Java4Shell and the NGINX HTTP/2 with Docker Hardened Images

OpenJDK and Oracle disclosed Java4Shell (CVE-2026-114938) on November 17, and NGINX released fixes for two HTTP/2 flaws the next day. Docker began publishing fixed images for both in the Docker Hardened Images (DHI) catalog starting that same day. 

What we know about Java4Shell is that it’s a memory-corruption bug in the Java runtime that can let an attacker with no credentials run code inside a Java application. Many container images contain a Java runtime, including application images that bundle their own, so it affects teams well beyond the ones that write Java.

Docker Hardened Images are the trusted foundation your applications should run on, because a flaw in the runtime inside an image is fixed only when that image is rebuilt, and Docker rebuilds its hardened images as soon as upstream fixes become available. Fixed images for the Amazon Corretto, SapMachine and Azul Zulu runtimes and for NGINX are in the catalog today, with Eclipse Temurin following as soon as Adoptium completes its fixed builds.

TL;DR

Affected: Java 17.0.6 and later, including Java 21, 25, 26 and 27, from every OpenJDK vendor.

Only on some hardware: the bug is reachable only when the JVM runs on an x86-64 CPU with AVX-512 VBMI. The same image can be exposed on one host and not on another.

Fixes are arriving vendor by vendor. Corretto, SapMachine and Zulu builds in DHI are fixed. Temurin, which many DHI application images use, is not released yet.

Check the version the runtime reports. A tag or a recent rebuild date does not tell you which Java build is inside an image. java -version does.

Until your image runs a fixed build, start Java with -XX:-UseBASE64Intrinsics. Set it yourself and check that it took effect. Make sure it reaches every JVM, not only the first one. The second half of this post shows how.

The NGINX HTTP/2 flaws are fixed in the catalog. The Docker Hardened Images for NGINX are rebuilt on NGINX 1.30.7 and 1.31.9. Pull the image again, or move a pinned tag to one of those versions, and redeploy.

What the vulnerability is

To decode Base64 quickly, the HotSpot JVM uses a hand-written routine built on AVX-512 instructions. That routine miscalculates a length when the input ends in unexpected padding and writes up to 62 bytes past the end of a buffer on the Java heap. Calif, the researchers who found it, turned that into heap disclosure and remote code execution.

They demonstrated code execution before authentication against default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and after authentication against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. They note there is no universal exploit: each application needs its own, and they have not published those. As of November 18 there are no public reports of exploitation in the wild.

Oracle rates the issue 8.1 (High) under CVSS 3.1. The researchers rate it 9.2 (Critical) under CVSS 4.0. CISA has issued an alert urging immediate patching.

How to find out if you’re exposed

Java version. The JVM is 17.0.6 or later and does not yet include the fix. The fixed OpenJDK versions are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Vendors add their own suffixes, but in the builds we checked, the build string printed by java -version contains one of those four numbers when the runtime is fixed.

CPU. The host is x86-64 and supports AVX-512 VBMI: Intel Xeon from Ice Lake onward, AMD EPYC and Ryzen from Zen 4 onward. ARM64 hosts are not affected.

Reachability. Data an attacker controls reaches Java’s Base64 decoder. That includes Authorization headers, tokens, SAML messages and file uploads. A Java client that opens a TLS connection to a malicious server is also in scope. For anything that accepts network input, assume this is true.

All three of these must be true

To check a host’s CPU, run this on the host or Kubernetes node. Hardened runtime images have no shell, so it will not run inside the container.

grep -m1 ‘^flags’ /proc/cpuinfo | tr ‘ ‘ ‘n’ | grep -E ‘^(avx512f|avx512bw|avx512vbmi|bmi2)$’

The host is affected if all four flags are printed.

Two other ways to check, for when a shell on the node is hard to get.

Ask the JVM. This works in hardened images:

docker run –rm –entrypoint java <image> -XX:+PrintFlagsFinal -version | grep -w UseAVX

UseAVX = 3 means the JVM is using AVX-512 on that host. Treat the host as affected until the full check says otherwise. A value of 0 to 2 means AVX-512 is not in use. On ARM64 nothing is printed. The answer applies only to the host the command ran on.

Ask Kubernetes. kubectl get nodes -L kubernetes.io/arch,node.kubernetes.io/instance-type shows the architecture and instance type of every node. If you run Node Feature Discovery, nodes with the instruction set carry the label feature.node.kubernetes.io/cpu-cpuid.AVX512VBMI=true.

Check build runners and CI workers as well. They run Java, and they talk to the network.

Ask the JVM. This works in hardened images:

docker run –rm –entrypoint java <image> -XX:+PrintFlagsFinal -version | grep -w UseAVX

UseAVX = 3 means the JVM is using AVX-512 on that host. Treat the host as affected until the full check says otherwise. A value of 0 to 2 means AVX-512 is not in use. On ARM64 nothing is printed. The answer applies only to the host the command ran on.

Ask Kubernetes. kubectl get nodes -L kubernetes.io/arch,node.kubernetes.io/instance-type shows the architecture and instance type of every node. If you run Node Feature Discovery, nodes with the instruction set carry the label feature.node.kubernetes.io/cpu-cpuid.AVX512VBMI=true.

Check build runners and CI workers as well. They run Java, and they talk to the network.

Where Docker Hardened Images stand

Java runtime in DHI

DHI status

Amazon Corretto 17, 21, 25, 27

Fixed. The published images report 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4.

SapMachine 21, 25, 27

Fixed. The published images report 21.0.13.1+2, 25.0.5.1+2 and 27.0.1.1+4.

Azul Zulu 17, 21, 25, 27

Fixed. The published Zulu images we checked report 17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2 and 27.0.1.1+4.

Eclipse Temurin 17, 21, 25, 27

Waiting for Adoptium to complete its release. On November 18 Adoptium had published 27.0.1.1+4 for x86-64 Linux only. 17.0.21.1, 21.0.13.1 and 25.0.5.1 were still in testing. Adoptium tracks progress in adoptium/temurin#326. Our published images still report 17.0.21+9, 21.0.13+9, 25.0.5+8 and 27.0.1.0.2+1, which are vulnerable.

Java 26 (any vendor)

Java 26 reached end of support in September 2026, so no fix is expected from any vendor, and it is not among the fixed lines in the OpenJDK advisory. If you run it, treat it as affected and keep the flag set. We recommend moving to Java 25 or updating to Java 27. If you cannot migrate yet, ask us whether Extended Lifecycle Support can cover your version. It is the Docker Hardened Images Enterprise add-on for software past its upstream end of life.

Java 8 and 11

Not affected by this CVE and no action is needed for it. The same November update fixes other issues in these lines, so update when new images arrive.

Application images that bundle Java, such as Keycloak, Jenkins, Kafka, Elasticsearch and Solr

They follow the bundled runtime, which for many of them is Temurin, and they are rebuilt once the runtime they use is fixed. Until then, set the flag yourself.

Set the mitigation flag yourself on every JVM that is still waiting for a fixed runtime, and check what each image already sets before you do. Treat the flag as a stopgap, because a JVM is protected only if the flag reaches it when it starts, and a deployment setting or a start script can override it or drop it. A fixed runtime is the only thing that closes the issue, so move to the fixed image as soon as it is published.

Next Steps:

If you are not running Docker Hardened Images yet

The CPU check and the mitigation flag in the steps below apply to any image that runs a HotSpot-based OpenJDK build. The version strings in this post come from Docker Hardened Images, so for an image from another source, confirm the fixed build in that source’s advisory.

The fixed build can only come from whoever builds your image, because the Java runtime and the system packages your application runs on come from the image underneath it. That dependency is why a hardened image is a necessary step toward a trusted software supply chain. With Docker Hardened Images, tracking each vendor’s fix and rebuilding on it is work Docker does for you. The images are minimal and secure by default, and they are built to serve as a trusted and verifiable upstream for your builds. You can move a service onto one by following the migration guide.

If you have Docker Hardened Images deployed

1. Find the Java in your deployments, by version. Look for DHI Java runtime images, DHI application images that bundle Java, and your own images built on either. Include JVMs you add in your own layers. Ask each runtime for its version. This works on hardened images, which have no shell:docker run –rm –entrypoint java <image> -versionCompare the result with the fixed versions above. Temurin-21.0.13+9 is vulnerable. Corretto-21.0.13.1.2 is fixed.Do not rely on a vulnerability scan alone for this. The public vulnerability databases were still incomplete for this CVE on November 18.

Set the flag. For most deployments, set JAVA_TOOL_OPTIONS on the container:docker run -e JAVA_TOOL_OPTIONS=”-XX:-UseBASE64Intrinsics” <your-image>env:  – name: JAVA_TOOL_OPTIONS    value: “-XX:-UseBASE64Intrinsics”Three cases need more care, and the next section covers them: images that already set Java option variables (our FIPS images do), environments that also run Java 8, and anything that starts more than one JVM.Prefer this flag to -XX:UseAVX=2, the other published mitigation. UseAVX does not exist on ARM64, and a JVM given it there will not start. Applications that decode very large volumes of Base64 may run slower with the flag. Test before a wide rollout.The flag addresses this CVE only. The same OpenJDK release fixes nine other CVEs, including two rated 7.4 that affect every Java line from 8 to 27. Only the fixed image addresses those.

Restart, then verify. The flag is read only at JVM startup. It cannot be changed in a running JVM, so every JVM has to be restarted. Then look for this line in the container log:Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics

Check your CPUs, and keep checking. Run the CPU command on every node pool. A cluster with mixed instance types can schedule the same pod onto an affected node tomorrow. If any node in a pool is affected, treat the workload as affected.

Reduce exposure. Restrict network access to Java services that do not need to be public, starting with identity, CI/CD and collaboration systems. The researchers note that a proxy which buffers whole request bodies gets in the way of some of their exploits but not all of them, so do not count on it.

Watch for crashes, and think about secrets. A failed attempt can crash the JVM. In the container log a crash starts like this:# A fatal error has been detected by the Java Runtime Environment:##  SIGSEGV (0xb) at pc=0x…, pid=1, tid=…The JVM also writes a report named hs_err_pid<pid>.log inside the container. That file is gone when the container is replaced, which in Kubernetes happens straight away. To keep it, point -XX:ErrorFile at a mounted volume. The malformed input is also rejected with an IllegalArgumentException, so a burst of Base64 decoding errors in an application’s log is worth a look. Neither signal is reliable, and a service that stays up is not proof that nothing happened.The researchers could read the Java heap before they could run code. If you have reason to believe an exposed JVM on affected hardware was attacked, treat the keys, tokens and passwords it held as disclosed, and rotate them.

Making the flag reach every JVM

A container often runs more than one JVM, for example when a build tool forks a JVM for tests, an application server starts helper processes or a CI agent starts a JVM for every build step. The flag protects only the JVMs that receive it, and the variable most people reach for first is JAVA_OPTS, which Java does not read at all.

Where you put the flag

What reads it

Child JVMs get it?

Watch out for

JAVA_TOOL_OPTIONS

The JVM itself, however it is started. Includes javac, keytool and other JDK tools.

Yes, through the inherited environment

A Java 8 JVM that sees it refuses to start. Some DHI FIPS images already set this variable.

JDK_JAVA_OPTIONS

Only the java launcher, Java 9 and later

Yes, when the child is started with java

Not read by javac, keytool or other JDK tools. DHI FIPS images set it. Java 8 ignores it.

The java command line

That one JVM

No

Nothing downstream inherits it.

JAVA_OPTS, JENKINS_JAVA_OPTS, MAVEN_OPTS, ES_JAVA_OPTS and similar

A start script, which copies the value onto one java command line

No

Each script has its own rules. If nothing in the image reads the variable, it does nothing.

Five rules follow from that table. We tested each on DHI images.

JAVA_OPTS only works where a script reads it. With JAVA_OPTS=”-XX:-UseBASE64Intrinsics” set and a plain java command, the intrinsic stays on. No warning is printed.

A flag on the command line stops at that process. We started a JVM with the flag on its command line and had it start a second JVM. The child ran with the intrinsic on. With JAVA_TOOL_OPTIONS or JDK_JAVA_OPTIONS in the environment, the child ran with it off. A child started with a cleared environment gets nothing, whichever variable you use.

Check what the image already sets before you set anything. In Docker and Kubernetes, your value replaces the image’s value. It is not appended.

docker inspect –format ‘{{range .Config.Env}}{{println .}}{{end}}’ <image>   | grep -E ‘^(JAVA_TOOL_OPTIONS|JDK_JAVA_OPTIONS)=’

Our FIPS images use these variables to configure the FIPS provider. dhi.io/eclipse-temurin:21-fips sets both. When we replaced its JDK_JAVA_OPTIONS with only the flag, the JVM started normally, but the org.bouncycastle.fips.approved_only property was gone. Nothing warned us. If the command prints a value, copy it and add the flag at the end:

env:  – name: JDK_JAVA_OPTIONS    value: “<the existing value from the image> -XX:-UseBASE64Intrinsics”

Not every FIPS image uses the same variables, so run the check for each image.

Keep JAVA_TOOL_OPTIONS away from Java 8. Java 8 is not affected and does not know the flag:

Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64IntrinsicsUnrecognized VM option ‘UseBASE64Intrinsics’Error: Could not create the Java Virtual Machine.

Adding -XX:+IgnoreUnrecognizedVMOptions to the variable does not help on Java 8. Where Java 8 shares an environment with a newer Java, either scope the variable to the containers that need it or use JDK_JAVA_OPTIONS, which Java 8 ignores. Java 11 accepts the flag, so it is harmless there.

Verify the process, not the environment. Running java -XX:+PrintFlagsFinal -version inside a container starts a new JVM. It tells you what the environment gives a new JVM, not what the JVM already serving traffic was started with. For the running process, use the startup log line. JDK_JAVA_OPTIONS prints one too, starting with NOTE: Picked up. In an image that includes the JDK you can also ask the process directly:

jcmd <pid> VM.flags | tr ‘ ‘ ‘n’ | grep UseBASE64Intrinsics

The answer must be -XX:-UseBASE64Intrinsics. If the flag reached the JVM through an environment variable, it will not show in the process’s command line, so ps is not a reliable check.

Some applications discard these variables on purpose. Elasticsearch’s start script, for example, ignores JAVA_TOOL_OPTIONS and expects ES_JAVA_OPTS. Check your application’s documentation.

When the fixed images arrive

Pull the new image and redeploy. Four things catch people out:

The tag may not change. dhi.io/amazoncorretto:21.0.13 now reports the fixed Corretto-21.0.13.1.2, a newer build than the tag name suggests. A tag cannot tell you which build you are running. java -version can.

Kubernetes may not pull. With imagePullPolicy: IfNotPresent, the default for every tag except latest, a node that already holds the old image under that tag keeps using it, even after a restart. Deploy by digest, or set the policy to Always for this rollout.

Mirrors lag. If you copy DHI into your own registry, the fix arrives when your mirror next syncs.

Your own images need a rebuild. An image built FROM a DHI Java image keeps the old runtime until you rebuild and redeploy it.

Then confirm with java -version that what is running reports a fixed build. After that, remove the flag from every place you set it.

The NGINX HTTP/2 flaws are fixed in the same catalog

The day after Java4Shell, NGINX released fixes for two memory errors in the way it handles HTTP/2 connections, tracked as CVE-2026-123007 and CVE-2026-123633. A crafted request can crash a worker process, and where an attacker gets past the operating system’s memory protections it can run code inside that worker. Both flaws need HTTP/2 to be enabled on the server, and the same releases fix other NGINX issues that do not depend on HTTP/2, so update either way.

The Docker Hardened Images for NGINX were rebuilt on NGINX 1.30.7 and 1.31.9 and published on November 18, the same day as the upstream release. To patch, pull the image again and redeploy, and move any tag pinned to an older exact version to a fixed one. nginx -v prints the version, and the fixed ones are 1.30.7 and 1.31.9. The notes on pull policy, mirrors and your own images in the section above apply to NGINX images in the same way.

Who does what

The vulnerable code is in the Java runtime inside the image, and if you are using DHI, shipping the fix becomes our job. Whether that code can be reached in your deployment depends on things an image cannot see: the CPU it is scheduled onto, the options you start it with, the processes it starts, and the traffic you send it.

With Docker Hardened Images, Docker will

Without Docker Hardened Images

Track every Java vendor and ship fixed runtimes in DHI as soon as they are released

Track every Java vendor yourself and rebuild your base images on each fixed runtime

Tell you which images are fixed and which are still waiting

Find out from each vendor which of its builds are fixed

Tell you what we know, and update this post

Follow the OpenJDK, Oracle and vendor advisories as they change

Three jobs stay with you whichever image you run.

Pull the fixed images, redeploy, and confirm the Java version that is actually running.

Make sure the flag is set on every JVM that is still waiting for a fixed runtime.

Know which CPUs your workloads run on, control what can reach your Java services, and patch the JVMs you add yourself.

So how many more bullets are you willing to dodge?

It was only four weeks ago that the news was PHP2Shell and the eMudhra certificate compromise. Calif, the security research team that found Java4Shell and helped find PHP2Shell, says it used AI to find this flaw in about an hour and that the whole effort cost less than $200 in tokens. When a flaw like this can be found and weaponized at that price, it is reasonable to expect more of them.

If you lead a team or answer for how your organization builds and ships software, the questions after a week like this one are whether you were exposed and how quickly you can prove you were not. It is imperative to have a trusted foundation in place before the next flaw appears, and Docker Hardened Images is that foundation to adopt. This week Docker began publishing fixed Java and NGINX images to the catalog within a day of each disclosure, with the images still waiting listed in the status table above. Each image ships with a signed SBOM and SLSA Build Level 3 provenance, so you have a record of what it contains and how it was built.

The Docker Hardened Images catalog is free and open source under Apache 2.0, and moving one of your services onto a hardened image typically means changing one line in its Dockerfile. If you are not building on Docker Hardened Images yet, start today.
Quelle: https://blog.docker.com/feed/

AWS Elemental MediaTailor adds Dynamic Avail Sizing for live HLS

AWS Elemental MediaTailor now supports Dynamic Avail Sizing, which reduces the slate viewers see when ad breaks, also called avails, in live HLS streams go unfilled. MediaTailor is a server-side ad insertion and channel assembly service that personalizes ads in live and on-demand video streams.
When the ad decision server returns fewer ads than a break allows, dynamic avail sizing omits the unfilled time and resumes programming early instead of showing slate. To keep playback continuous, MediaTailor holds back a configurable reserve of content behind the live edge and draws on it when a break ends early. When the reserve runs low, MediaTailor requests extra ad time in later breaks to refill it. Free ad-supported streaming TV (FAST) channel operators can use dynamic avail sizing to keep viewers watching programming instead of filler content.
Customers turn on dynamic avail sizing for each playback session by adding query parameters to the session initialization URL, with no change to their playback configuration. To learn more, see Dynamic avail sizing in the AWS Elemental MediaTailor User Guide.
Quelle: aws.amazon.com

Amazon IVS Real-Time Streaming now provides a Linux broadcast SDK

The Amazon Interactive Video Service (Amazon IVS) Linux broadcast SDK is now available for IVS Real-Time Streaming. Applications running on Linux can join an IVS stage, receive audio from participants, and send audio back to the stage in real time. The SDK provides a C API and Go language bindings.
The Linux broadcast SDK is ideal for AI applications that enrich live streams by processing audio, such as transcription, translation, and content moderation, as well as voice agents that converse with participants.
Amazon IVS is a managed live streaming solution designed to make low-latency or real-time video available to viewers around the world. Visit the AWS Region table for a full list of AWS Regions where the Amazon IVS console and APIs for control and creation of video streams are available.
To learn more, see IVS Broadcast SDK: Linux Guide.
Quelle: aws.amazon.com

AWS Transform combines migration assessment and planning in one experience

AWS Transform for migrations now combines migration assessment and migration planning into a single migration job. Previously, you ran separate jobs to build a total cost of ownership (TCO) business case and to plan your migration. With this launch, you upload your on-premises inventory once and use it for both assessment and planning, in any order.
After you upload your inventory data, you can estimate your AWS costs and build a business case, group your infrastructure into applications and plan migration waves, or do both. You can rerun either workflow as your data improves. For example, build a business case first and then plan waves from the same inventory, or plan your waves first and then estimate the cost of a single wave. Because assessment and planning share one inventory, your business case and migration plan stay consistent without moving data between jobs. After you finalize your plan and assessment, you can continue in the same job to migrate your networks, deploy landing zones, and migrate servers, storage, and containers.
This newest release is available in all AWS Regions where AWS Transform is offered. To learn more about migrating with AWS Transform, visit the product page and documentation.
Quelle: aws.amazon.com