Azure

GPT-5.5 in Microsoft Foundry for Enterprise AI

3 min read

Summary

Microsoft is making OpenAI GPT-5.5 generally available in Microsoft Foundry, giving Azure customers a new frontier model designed for long-context reasoning, agentic execution, and lower token usage. The update matters for enterprises because Foundry adds the security, governance, identity, and deployment controls needed to run production AI agents at scale.

Need help with Azure?Talk to an Expert

Introduction

Microsoft is bringing OpenAI's GPT-5.5 to Microsoft Foundry, expanding Azure's enterprise AI platform with a model built for more reliable reasoning, agent execution, and production-scale efficiency. For IT leaders, developers, and platform teams, the bigger story is not just model access—it is the ability to operationalize advanced AI with governance, identity, and security built in.

What's new with GPT-5.5 in Microsoft Foundry

GPT-5.5 becomes generally available in Microsoft Foundry, alongside a premium GPT-5.5 Pro option for more demanding workloads.

Key improvements highlighted by Microsoft include:

  • Deeper long-context reasoning for large documents, codebases, and multi-session work
  • More reliable agentic execution for multi-step tasks and professional workflows
  • Improved computer-use accuracy when interacting with software interfaces
  • Better token efficiency to reduce cost and latency at scale
  • Stronger support for coding, research, document creation, and analysis

Microsoft positions GPT-5.5 for scenarios where precision matters, including software engineering, DevOps, legal, health sciences, and professional services.

Why Foundry matters for enterprises

Microsoft Foundry is the platform layer that helps organizations move from AI experiments to governed production use. Rather than just exposing a model endpoint, Foundry provides:

  • Enterprise-grade security, compliance, and governance
  • Broad model choice and interoperable agent frameworks
  • Integration with enterprise systems and productivity tools
  • Easier evaluation, deployment, and scaling of new models

Microsoft also emphasized Foundry Agent Service as the operating environment for running agents at scale. Hosted agents can run in isolated sandboxes with:

  • A persistent filesystem
  • A distinct Microsoft Entra identity
  • Scale-to-zero pricing
  • Support for frameworks such as LangGraph, OpenAI Agents SDK, Claude Agent SDK, Microsoft Agent Framework, and GitHub Copilot SDK

Pricing at a glance

Microsoft published token pricing for both models:

  • GPT-5.5: $5/M input, $0.50/M cached input, $30/M output
  • GPT-5.5 Pro: $30/M input, $3/M cached input, $180/M output

Impact on IT administrators and platform teams

For Azure and AI platform admins, this release means more choices for production AI workloads without giving up enterprise controls. Teams can standardize how agents are deployed, secured, and managed while supporting multiple frameworks and identities through Foundry.

Developers also benefit from a clearer path to production, especially for use cases involving coding assistants, research agents, and workflow automation.

Next steps

If your organization is already testing AI agents on Azure, now is the time to:

  • Evaluate GPT-5.5 for high-precision workflows
  • Review Foundry Agent Service for secure hosted agent deployment
  • Compare token costs against current model usage
  • Validate governance, identity, and compliance requirements before wider rollout

For enterprises moving beyond pilots, GPT-5.5 in Microsoft Foundry looks like a significant step toward scalable, governed agentic AI in production.

Need help with Azure?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

AzureMicrosoft FoundryGPT-5.5AI agentsenterprise AI

Related Posts

Azure

SQL Server on Azure Local GA for Edge and Sovereign

Microsoft has announced general availability of SQL Server on Azure Local for both connected and disconnected environments. The release gives organizations a consistent way to run mission-critical SQL Server workloads close to their data, while supporting Azure Arc management, existing licensing benefits, and local AI scenarios with Foundry Local in preview.

Azure

Microsoft Fabric 2026: Copilot and Power BI Updates

At FabCon and SQLCon 2026, Microsoft announced new Microsoft Fabric and SQL innovations focused on grounding Copilot and agents in trusted enterprise data. Highlights include Fabric IQ integration with Microsoft Copilot, agentic app creation in Power BI Desktop, Fabric Apps enhancements, and new observability and database management capabilities.

Azure

Azure VM Lifecycle Policy: New Stages for Modernization

Microsoft has introduced a clearer Azure Virtual Machine lifecycle policy to help customers plan infrastructure transitions with more transparency and predictability. The new framework defines Current, Extended, End of Life, and Retired stages for key VM families, along with guidance, availability expectations, and modernization tools for affected workloads.

Azure

Microsoft Foundry Adds Voice Agents and GPT-6

Microsoft Foundry has expanded its AI agent platform with broader model choice, native voice agents, and tools for continuous optimization. The update gives Azure teams more flexibility to evaluate frontier models like GPT-6 and Claude Opus 5.5, build multilingual voice experiences, and improve agent quality, latency, and cost over time.

Azure

Claude Opus 5.5 in Microsoft Foundry for AI Agents

Microsoft Foundry now offers Claude Opus 5.5, Anthropic’s latest model aimed at long-running coding, knowledge work, and agent-based workflows. The update matters to Azure teams because it adds adaptive reasoning, clearer agent communication, and new capabilities for managing long-context tasks in production.

Azure

Azure Resilience Drift: Why Diagrams Are Not Enough

Microsoft is urging organizations to treat resilience as a continuously validated operational capability, not a one-time architecture exercise. The article highlights how configuration drift, AI dependencies, and untested failover paths can undermine resilient designs even when architecture diagrams still look correct.