agents
370 TopicsAzure AI Gateway is now generally available: Ship faster, stay in control
Today at Microsoft Ignite 2026, we're announcing the general availability of Azure AI Gateway, a fully managed Azure service that lets you set up a single, controlled path from your AI applications and agents to models and tools across providers. Developers build with the models and tools they choose, and platform teams manage access, enforce policies, control costs, and monitor usage from one place, without operating gateway infrastructure. Azure AI Gateway, previously in public preview as the AI Gateway tier of Azure API Management, is now a standalone product optimized for governing access to AI models and tools, with a roadmap focused entirely on AI. You can use it by itself with any app or agent, or together with Microsoft Foundry, where you build and run agents, and Microsoft Agent 365, where you manage them. Azure AI Gateway is available today in 17 Azure regions. To make it easy to get started, it offers a freemium, per-use pricing model with 10,000 free requests per gateway each month. Paid billing begins January 1, 2027. See the Regions and pricing section below for details. Why enterprise AI needs a unified governance layer Enterprise AI has moved beyond one app calling one model. Organizations use models from several providers, build agents that act through enterprise tools, and scale AI across teams. When each app manages its own credentials, routing, safety, and usage limits, governance becomes fragmented. Developers struggle to find approved models and tools, and platform teams can't see who is using what, what it costs, or which policies apply. Azure AI Gateway lets you move those controls out of individual apps and into one place, where they apply consistently to every app and agent you connect. How Azure AI Gateway works Apps and agents you connect call the gateway instead of calling each model or tool directly. On every request, the gateway authenticates the caller with Microsoft Entra ID or a gateway access key, enforces access rules and your policies, routes the request to the right model or tool, and records telemetry. Figure 1. Azure AI Gateway sits between callers and backends, governing every request that passes through it. What you can do with Azure AI Gateway Build with models and tools across providers Any model, one name: Use models from Microsoft Foundry, Azure OpenAI, OpenAI, Anthropic, Amazon Bedrock, Google Vertex AI, or any OpenAI-compatible endpoint. Apps call each model by an alias you define, so you can switch models without changing app code. Routing and failover: Route by priority, weight, or custom conditions, with configurable failover, or let Model Router (preview) choose by cost or quality. Consolidated tools: Federate MCP servers and turn OpenAPI specs, connectors, and API Management APIs into MCP tools. Multiple MCP spec versions are supported, including the latest (July 2026). The APIs you know: Call models through an OpenAI-compatible API or the Anthropic Messages API and connect agents to tools from any MCP client. Govern and observe AI interactions Access with Entra ID: Built-in roles control who can use models and tools. Provider keys and tool credentials never reach app code. Safety on every prompt: Screen prompts and responses with Azure AI Content Safety. Only approved tools: Curate and block tools at the gateway, or through Microsoft Agent 365 policies. Protection from poisoned tools (preview): Through the Microsoft Agent 365 integration, Microsoft Defender and Microsoft Purview inspect tool calls and results and block threats before an agent acts. Delegated identity: With on-behalf-of (OBO) authentication, tools act with the signed-in user’s own permissions. Every call on record: Record the caller, target, tokens, and outcome of each model and tool call, trace each call to its agent, and export the data over OpenTelemetry to Application Insights, Datadog, Splunk, Grafana Cloud, or any OTLP endpoint. Private by design: Private Link (preview) for inbound calls, VNet integration (preview) for private backends, IP filtering, and managed identity. Control AI spend as adoption scales See who spends what: Track tokens and estimated cost by user, team, app, agent, provider. Enforced budgets: Cost limits stop new requests once estimated spend reaches a budget. Fair sharing: Token and request limits keep one caller from crowding out the rest. Discover, build, and operate in your existing workflow Coding agent plugin: Developers find approved models and tools and connect their apps from their coding agent. Portal, CLI, Bicep, and REST API: Configure in the portal or with the CLI, then deploy the same setup as code from your CI/CD pipelines with Bicep or the REST API. See Azure AI Gateway in action From connecting models and MCP tools to securing access, controlling costs, and monitoring AI traffic, this demo shows how Azure AI Gateway helps you run AI applications with confidence. Extend AI governance across your Microsoft ecosystem Already using Microsoft Foundry, Microsoft Agent 365, or Azure API Management? Azure AI Gateway works with all three. Microsoft Foundry: Foundry has governance built in for its resources and projects. When AI spreads across teams, Foundry resources, subscriptions, and other providers, the gateway adds a shared layer on top. In a hub-and-spoke model, the gateway is the hub: a central platform team sets the rules once, and developers keep building in their Foundry projects, the spokes, using approved models and tools without managing credentials. Projects can share one deployment, including PTU, and fail over to another Foundry resource or provider. Foundry prompt agents can use gateway models through a model connection (preview), without code changes. Microsoft Agent 365: Agent 365 discovers the gateway’s MCP servers and lets you set tool policies. The gateway enforces those policies, alongside its own, on every tool call, with added threat protection (preview) from Defender and Purview. Regions and pricing Azure AI Gateway is available today in 17 Azure regions: East US, East US 2, East US 2 EUAP, West US, West US 2, Central US, North Central US, South Central US, Canada East, West Europe, North Europe, UK South, France Central, Sweden Central, Australia East, Japan East, and Southeast Asia. Azure AI Gateway offers a freemium, per-use pricing model with 10,000 free requests per gateway each month. Paid billing begins January 1, 2027. Monthly gateway requests Service fee Additional request charges Up to 10,000 Free None More than 10,000, up to 10 million $500 per month, per gateway, billed hourly None (includes 10 million requests) More than 10 million $500 per month, per gateway, billed hourly $20 per additional million requests, billed in increments of 10,000 requests Prices are in US dollars and may vary by region. Exact regional prices will be available when billing begins. Get started with Azure AI Gateway Create a gateway at ai.gateway.azure.com. It’s ready in about a minute and free to start. Then: Connect an existing model and give it an alias. Expose the MCP tools your agents need. Give your team access with an AI Gateway role. Set a cost limit. Point your app or agent at the gateway. Or start from your coding agent. Install the Azure AI Gateway plugin, and it finds approved models and tools and connects your app for you. Explore the documentation and quickstarts at ai.gateway.azure.com/docs.6.2KViews1like1CommentWhat’s new in Logic Apps Automation at Ignite 2026
Build like a startup. Ship like an enterprise. That's the idea behind Logic Apps Automation launched in Public Preview earlier this year. This Ignite preview refresh moves both halves forward. To build faster, you get templates, a refreshed designer, new built-in connectors for Azure automation, AI models that are ready to use with no deployment, and Decision actions that turn judgment calls into typed answers your workflow can act on. To ship with confidence, you get virtual network support, a re-platformed hosting environment that makes environments and apps faster to create, shareable templates that become your team's approved patterns, and availability in most Azure public region over the coming weeks. Here's what's new. New built-in connectors for Azure automation Automating Azure operations usually means connecting several systems: where your code lives, how it ships, how work is tracked, and how your Azure environment is behaving. This Ignite, Logic Apps adds a new set of built-in connectors for these systems: GitHub, Azure DevOps Pipelines, Azure DevOps Repos, Azure DevOps Boards, Azure Monitor Logs, Azure Resource Graph and Azure Advisor. Together they let a single workflow cover the full loop. It can respond to an event in your environment, look up the affected resources, check recommendations, open or update the right work item, kick off a pipeline and keep the code-review process moving. You can sign in with managed identity, OAuth or a personal access token, so you can pick what fits your security setup. Many of these connectors include triggers, so automation can start from an event instead of a schedule. Here are a few of the scenarios they make possible. Work tracking and planning with Azure DevOps Boards Route and assign new work items as they're created Monitor SLAs every time a work item is updated Code and delivery with agents with GitHub, Azure DevOps Repos and Azure DevOps Pipelines Triage new issues and suggest or open a fix as a pull request with an agent Review new pull requests automatically Kick off pipelines as part of the same workflow Azure operations and governance with Azure Monitor Logs, Azure Resource Graph and Azure Advisor Find affected resources and query logs when something needs attention Act on best-practice recommendations as they appear Together, these make Logic Apps Automation a central place to automate how you run, govern and improve your Azure estate. Because they run directly within the Logic Apps runtime, built-in connectors are generally faster and have fewer limits than managed connectors. More are coming soon, including Azure Events, Azure Key Vault, Microsoft Defender, Azure Policy, Azure Health and Azure Billing. Explore the template catalog and go from idea to workflow in minutes You don't need to start from scratch. Logic Apps Automation includes a growing catalog of ready-made templates that cover the full range of automation, from integration and business process workflows to agentic scenarios with AI agents and proven design patterns you can build on. For Azure automation, templates cover scenarios such as triaging new GitHub issues with an agent, reviewing incoming pull requests automatically, creating Azure DevOps work items from incoming events and tracking SLAs as work items change. Every template is a fully editable workflow, so you can start from a proven pattern and then add your own steps, approvals or AI agents as your needs grow. The catalog is now available in the Logic Apps Automation portal, where you can browse every template without signing in and explore what's possible before you commit to anything. When you find one you want to use, just choose your environment and app, and the workflow is created for you, ready to connect your accounts and run. Coming soon, you'll be able to maintain your own template library, giving your organization a single place to discover, publish and manage its approved templates. Turn any workflow run into a shareable template Templates aren't limited to the ones Microsoft ships. You can now generate a template directly from a run. When a workflow works well, one click turns it into a reusable template. From there you choose how far to share it. You can share it within your team or organization, where colleagues can import it and use it like any other template. Or you can check it into the public Logic Apps templates GitHub repository so it appears in the public gallery for the wider community. Teams can package proven automation patterns once and reuse them everywhere, and organizations can use templates to bring their development guidelines and best practices into every new workflow from the start. Coming soon, you'll be able to maintain your own template library, giving your organization a single place to discover, publish and manage its approved templates. Managed AI models: bring AI into your automation, with no setup Adding AI to a workflow used to mean provisioning a model resource, deploying a model and managing keys and quotas before you could build anything. With Managed AI Models, Logic Apps provides the large language models for you, so your agents can use them right away. There's nothing to provision, deploy or maintain. Pick a model and start building. Managed models work with both types of agents in Logic Apps. Workflow Agents are simple, declarative agents that you define directly in your workflow, which makes them a good fit for tasks like triaging GitHub issues or summarizing Azure Monitor findings. Managed Agents are for more advanced scenarios. They give you a pluggable harness and model choice, plus a sandbox for running code in isolation, so agents can safely analyze data, generate scripts or test fixes without touching your production environment. Decision actions Many automation steps come down to a judgment call: is this alert actionable, which team should own this issue, how severe is this incident? Decision actions, now in public preview, handle these questions with three native actions. Yes/No, Choice and Score each return a typed answer with a confidence value that your workflow can act on right away. The actions are powered by the built-in Microsoft-Decision-1 model, so there's no model to deploy and no output to parse. You'll find them under AI and agents in the designer. Read the full announcement here. Region availability Logic Apps Automation is already live in a set of initial regions, and starting at Ignite we're rolling it out to most Azure public regions. The rollout will take couple of weeks, so if it isn't in your region yet, check back over the coming days. Network isolation with virtual network support Automation that works across your Azure estate often needs to reach resources that aren't open to the internet. Logic Apps Automation now supports virtual network (VNet) integration. You can connect an environment to your virtual network, and all outbound calls from your workflows then go through it. That covers everything that runs in the environment, including all built-in connectors, agents and workflow actions, so your automation can run entirely inside your network. It can reach private databases, internal APIs and locked-down Azure resources while meeting your organization's network and compliance requirements. Setup is a single toggle. When you create an environment, choose your subscription, resource group and region, turn on Use a virtual network and pick a subnet from the list. That's it: the environment's traffic now goes through your VNet. Choose the subnet carefully, because it can't be attached, changed or removed after the environment is created. For more advanced configuration, you can also create the environment in the Azure portal. Private endpoint support for inbound traffic is next on the roadmap. Faster from the first click: a re-platformed foundation Logic Apps Automation moves to a new hosting platform built on Azure's lightweight, microVM-based compute with sub second cold start times. Before, each environment brought up its own dedicated infrastructure before you could build anything. Now environments and apps run on pre-provisioned regional capacity, so creating an environment and an app takes only a few seconds, down from a few minutes, and you go from sign-in to your first workflow almost immediately. The lighter-weight foundation also means each app uses fewer resources, and future platform improvements reach you without any changes on your side. Environments you've already created will keep running until they're migrated to the new platform. If you want the benefits sooner, you can recreate an environment to move it to the new platform right away. A refreshed designer Based on your feedback during the preview, we’ve redesigned the Logic Apps Automation designer to make workflows easier to understand, edit, test, and troubleshoot. Clearer canvas: a consistent visual style, labeled branches you can collapse, horizontal or vertical layouts, and canvas search. Agents in one view: each agent appears with its tools and selected model, and you can choose a Microsoft-managed model. Faster editing: copy, paste, or group several steps at once, and references update automatically when you rename a step. Easier configuration: individual Parse JSON properties show up as dynamic content, and inputs accept JavaScript expressions. Test before publishing: use test data and draft app settings to run supported drafts without touching your published workflow. Better monitoring: see the branch each run took, inspect loops one iteration at a time, and view retry history and analytics. Read the full walkthrough: From canvas to run: a better Logic Apps Automation experience Get started Logic Apps Automation is in preview today. Here's how to get started: Learn the basics. The documentation includes a three-minute overview video and a quickstart that walks you through creating your first environment and workflow. Start from a template. Browse the template gallery, pick a scenario that matches your needs and make it your own. Share your feedback. Try it on a real workflow and tell us what works and what's missing via Automation Feature Request. Your feedback shapes what we build next.442Views0likes0CommentsAnnouncing Decision APIs as actions in Azure Logic Apps
Today at Microsoft Ignite 2026, we're announcing the public preview of Decision actions powered by decision models in Logic Apps Automation. Three new built-in actions, Yes/No, Choice, and Score, let a workflow ask a focused question about any content and get back a typed answer it can act on right away. The actions and the Microsoft-Decision-1 model behind them are fully managed, so there's no model to deploy, no output format to prompt for, and no response to parse. Many steps in a business process come down to a judgment call. Is this message a refund request? Which team should handle this ticket? How severe is this alert? Until now, you had two options: write rigid rules, or call a general-purpose large language model, prompt it for a format, and parse the text it returns. Decision actions give you a third option, designed for exactly these questions. Background: Decision models AI applications and agents make many small judgments in the course of their work. These judgments generally take one of three forms: Yes-or-no checks, such as whether an email is spam, whether a customer wants to cancel a subscription, or whether a job application meets the minimum qualifications. Selections from a known set, such as which language a message is written in, which expense category a receipt belongs to, or which product a customer is asking about. Ratings on an ordered scale, such as how positive a product review is, how closely a student’s answer matches the answer key, or how formal the tone of a draft is. These judgments have typically been handled by general-purpose generative models, which return free-form text that the application must then interpret, even though the set of valid answers is known in advance. Decision models are designed for these tasks. Each request supplies the content to evaluate and one or more questions, and each question declares its answer type: the probability that a condition is true, a selection from a fixed set of options, or a score on an ordered scale. This approach offers two advantages over generative models. Typed responses. Every response follows the schema the caller defines. A probability is always a number between 0 and 1, a selection is always one of the options supplied, and a score always falls within the defined scale. Applications can use the answer directly, without output-format instructions in the prompt and without parsing or validation code. Token efficiency. Because the model returns a value rather than text, each answer is a single output token instead of a paragraph. Requests are also smaller, because they don't need formatting instructions or examples of the expected output, and a single request can answer several questions about the same input. This category of model is new. Microsoft introduced Microsoft-Decision-1 in the Microsoft Foundry model catalog on October 9, 2026, in public preview, and several other providers have released comparable models in recent weeks. Microsoft-Decision-1 is intended for classification, routing, evaluation, and workflow control. It accepts text input and is priced at $0.042 per million input tokens, with no charge for output. Why decision models matter for AI Automation A common pattern in Logic Apps today uses a chat completion action to classify content, a Compose or Parse JSON action to normalize the response, and a Switch or condition action to route on the result. Decision actions replace the first two steps of that pattern. You define the answer options in the action itself, the response is constrained to those options, and every answer carries a probability that downstream actions can evaluate. Three actions, one for each kind of question Yes/No Yes/No answers whether a condition is true, which makes it a good fit for gates and checks such as refund requests, spam, or a missing purchase order number. It returns the probability that the answer is yes, which you compare with a threshold in a Condition action. For example, ask "Is the customer asking for a refund?" and send high-probability messages to the refunds queue. Choice Choice picks the one option from your list that fits best. Use it for routing and classification when the categories have no natural order, such as support teams, document types, or review topics. It returns the selected option, a probability for each option, and an overall confidence value, so you can point a Switch action at the result. Include an Other option so that input that fits none of your categories isn't forced into the wrong one. Score Score places the input on an ordered scale you define, such as low to high urgency, severity, or negative to positive sentiment. It returns a probability-weighted score across your levels, along with a confidence value and per-level probabilities, so a result can fall between two levels. A mixed product review, for example, can land between Neutral and Positive, which gives you a finer reading than a single label. How it works in the designer Decision actions appear under AI and agents in the designer. Every Decision action takes the same three inputs: State: the content to evaluate, as text or JSON. This value usually comes from the trigger or an earlier step, such as a ticket body or the output of a previous action. Question or instructions: what you want the model to decide, such as "Is the customer asking for a refund?" You can also add rules here, such as how to break a tie. Options or levels: for Choice, a stable key and a short description for each option. For Score, the levels in order from lowest to highest. For Yes/No, you can optionally describe what yes and no mean. The outputs appear as dynamic content, so you can branch on them with the actions you already use. Each answer, its probability, and its token usage are recorded in run history, so you have a clear record of how every item was handled and cost is visible from the first run. What you can build Any step that turns on a judgment call is a candidate. You can use one action on its own or combine all three on the same input, so a workflow can gate, route, and prioritize in a single pass. Scenario Yes/No Choice Score Customer support triage Is the customer asking for a refund? Which team should handle this: Billing, Shipping, Technical support, or Account access? How urgent is this ticket? Review analysis Does the customer ask for a reply or replacement? Is the review mainly about product quality, delivery, price, or service? How positive is this review overall? Bug report triage Does the report include steps to reproduce? Which product area does it affect? How severe is the impact on users? Lead qualification Is this a genuine inquiry from a potential customer? Which product are they most interested in? How ready are they to buy? Content moderation Does the post share someone's personal contact information? What kind of issue does it have, if any? How serious is the problem? Designed for human oversight Decision actions help you automate judgment calls responsibly. Every answer includes a probability or confidence value, so you can send low-confidence results to a person or a review queue instead of acting on a guess. Run history records each question, answer, and probability, which gives your team an auditable record of how the workflow reached each outcome. Get started Decision actions are available today in public preview in Logic Apps Automation. The quickest way to start is from a template. We've published templates that show each action in a complete workflow. Find them in the Logic Apps template gallery - Templates | Logic Apps Automation To build your own workflow instead: In the workflow designer, add an action, and then look under AI and agents for Yes/No, Choice, or Score. Specify the state, the question, and the options or levels. Add a Condition or Switch action that uses the result. We'd love to hear what you build and what you'd like to see next. Share your feedback or request a feature here251Views0likes0CommentsWhat's new with Web IQ: Ignite 2026 edition
Web IQ’s Ignite 2026 updates bring broader Azure availability, lower pricing, and new ways to ground AI agents. Auto and Auto Advanced simplify retrieval with cited evidence, while Weather, Places, Commerce in private preview, and health-aware ranking support real-world tasks. Scopes and Zero Query Logging give enterprises more control over sources and query privacy.Bring-your-own image and Azure Cosmos DB MCP server in Connector Namespace hosted MCP (preview)
We're excited to announce two new capabilities for hosted MCP servers in Azure Connector Namespace, now available in public preview: Bring-your-own container image (BYO image): Deploy your custom MCP servers without managing the underlying hosting infrastructure. Azure Cosmos DB MCP server: Deploy a prebuilt MCP server from the catalog to give AI agents access to your Azure Cosmos DB for NoSQL data. These additions give developers more flexibility to bring MCP servers to Azure, whether you're building custom tools for your agents or connecting them to existing services. Both capabilities are available in public preview in select Azure regions. Hosted MCP servers As AI agents become more capable, they increasingly need access to external tools and data through MCP servers. However, hosting MCP servers remotely introduces operational complexity. Beyond deploying the server, developers need to provision compute, configure authentication, manage scaling, and monitor the server. The hosted MCP servers capability in Connector Namespace simplify this experience by providing a managed hosting experience. The namespace handles: Infrastructure and scaling: Provision and manage the compute required to run your MCP server. Authentication and access control: Secure MCP endpoints with Microsoft Entra ID authentication and access policies. Monitoring: Integrate with Application Insights to monitor server activity and troubleshoot issues. Server lifecycle: Manage deployed MCP servers as resources within your connector namespace. This lets developers focus on making tools available to their agents rather than operating the infrastructure behind them. With the latest preview updates, you can now bring your own MCP server implementation or choose the prebuilt Azure Cosmos DB server from the catalog. Bring-your-own container image to host custom MCP servers Previously, hosted MCP servers were limited to prebuilt servers available in the Azure Connector Namespace catalog. With the BYO image support, you can now deploy your own MCP server implementation using the same managed hosting experience. This is particularly useful when you want to: Reuse existing MCP servers: Bring an MCP server you've already built or packaged as a container image to Azure. Expose custom tools: Make proprietary APIs, internal systems, or business-specific capabilities accessible to AI agents. Avoid managing hosting infrastructure: Focus on developing and maintaining your server implementation while Azure Connector Namespace manages the underlying runtime. How it works The experience follows the same approach as deploying a prebuilt hosted MCP server. In Azure Connector Namespace portal, select Bring your own MCP server in the MCP catalog, then provide a few configuration details. Click Create, and Connector Namespace takes care of deploying and hosting your server: Once deployed, your custom MCP server benefits from the same hosting capabilities as catalog servers, including authentication, access control, scaling, and monitoring. You retain control over your MCP server's code, tools, and dependencies, while the platform manages the hosting infrastructure. Ready-to-deploy Azure Cosmos DB MCP server We're also expanding the hosted MCP server catalog with a new Azure Cosmos DB MCP server for NoSQL. The prebuilt server enables AI agents to interact with data stored in Azure Cosmos DB through MCP tools. Agents can: Discover databases and containers: Explore available databases and containers in Azure Cosmos DB. Understand data structures: Discover the structure of documents to understand the available data. Retrieve and query data: Access documents and query data stored in Azure Cosmos DB for NoSQL. In Azure Connector Namespace portal, open the MCP server catalog and find the Cosmos DB MCP Server under the Hosted catagory. Provide your database's endpoint and create the server. References Hosted MCP in Connector Namespace Hosted MCP developer guide What is Azure Connector Namespace Summary Whether you want to host your own MCP server or quickly connect AI agents to MCP servers, Azure Connector Namespace provides a managed way to bring MCP tools to your applications. Try out the new capabilities and share your feedback! We'd love to hear about the MCP servers you're building and what you'd like to see next.90Views0likes0CommentsAzure API Management Applications feature now available in public preview to all customers
We are excited to announce that the Applications feature in Azure API Management is now available in public preview to all customers, with no sign-up or registration required. Applications introduce a streamlined, application-centric approach to managing API consumption, helping organizations simplify application onboarding, enable identity-based authentication, and manage access to APIs through Azure API Management. With this public preview, customers can explore and use the Applications feature in supported Azure API Management tiers without enrolling in a preview program or requesting access. Simplifying how applications consume APIs As organizations expand their API ecosystems, managing access for different applications, services, and development teams becomes increasingly important. Traditionally, API providers have relied on API subscriptions and subscription keys to manage access to APIs. While subscription keys provide a straightforward mechanism for identifying and controlling API consumption, enterprise applications increasingly use Microsoft Entra ID and OAuth 2.0 for secure, identity-based authentication. Organizations also need a consistent way to understand which applications consume their APIs, manage application access to API products, and simplify onboarding for application developers. The Applications feature in Azure API Management addresses these needs by introducing an application-level abstraction for API consumption. Rather than managing API access solely through subscriptions, API providers can register consuming applications, associate them with API products, and configure Microsoft Entra ID integration to support secure application authentication. This provides a more structured approach to managing API consumers while building on the existing API Management product model. What are Applications in Azure API Management? Applications represent software applications or services that consume APIs published through Azure API Management. An application can be associated with API products, which group APIs and provide a logical boundary for managing API access. With Applications, API providers can: Register API-consuming applications: Create and manage application records directly in Azure API Management, establishing a centralized inventory of applications consuming APIs. Associate applications with API products: Define which API products an application is authorized to consume, simplifying access management across related APIs. Integrate with Microsoft Entra ID: Use Microsoft Entra ID and OAuth 2.0 client credentials to support secure, identity-based authentication for machine-to-machine API communication. Manage application access centrally: Organize application registrations and their associated API products within Azure API Management, reducing the complexity of managing API consumers across multiple APIs. Applications complement the existing API Management capabilities for publishing, securing, and governing APIs, providing an additional application-centric experience for API providers and consumers. Key benefits of the Applications feature 1. Simplify application onboarding Onboarding a new application to consume enterprise APIs can involve multiple steps, including identifying the required APIs, configuring access permissions, and establishing authentication credentials. With Applications, API providers can register consuming applications directly in Azure API Management and associate them with the appropriate API products. This creates a consistent process for organizing application access and reduces the need to manage API consumption independently for every API. 2. Enable secure, identity-based API access Modern enterprise applications increasingly use OAuth 2.0 and Microsoft Entra ID for authentication rather than relying exclusively on shared API keys. Applications support integration with Microsoft Entra ID, enabling API providers to use OAuth 2.0 client credentials for application-to-application authentication. This is particularly valuable for backend services, automated workloads, and other machine-to-machine scenarios where applications access APIs without interactive user sign-in. By using Microsoft Entra ID, organizations can align API authentication with their existing enterprise identity infrastructure and security practices. 3. Streamline API authorization through products Azure API Management products provide a convenient way to group related APIs and make them available to consumers. With Applications, API providers can associate consuming applications with specific products, creating a centralized model for organizing application access. For example, an organization might publish separate products for customer information, order management, and inventory services. Different applications can be associated with the products they need, making it easier to organize API consumption according to business requirements. Combined with appropriate gateway authorization policies, this approach helps organizations manage which applications can access their APIs. 4. Improve visibility and governance of API consumers As API adoption grows, organizations need better visibility into the applications that depend on their APIs. Applications provide a centralized representation of API consumers and their relationships with API products. This helps API providers maintain a clearer inventory of consuming applications, understand application dependencies, and manage API access as applications evolve. The application-centric model also provides a foundation for more consistent governance across enterprise API ecosystems. 5. Improve the developer experience Developers consuming enterprise APIs often need to navigate multiple onboarding processes, authentication configurations, and access requirements. Applications provide a more organized approach by bringing application registration and API product associations into Azure API Management. This helps simplify the experience for application developers while giving API providers a consistent mechanism for managing access to their published APIs. How Applications work Consider an organization exposing APIs for order processing, inventory management, and customer information through Azure API Management. A backend application needs access to the order processing and inventory APIs. Using the Applications feature, the API provider can follow this workflow: Register the consuming application: Create an application record in Azure API Management to represent the backend service. Associate API products: Associate the application with the API products containing the order processing and inventory APIs. Configure application identity: Integrate the application with Microsoft Entra ID and configure OAuth 2.0 client credentials authentication. Obtain an access token: The consuming application requests an OAuth 2.0 access token from Microsoft Entra ID using its configured credentials. Call the APIs: The application sends API requests through Azure API Management, including the access token. Validate and enforce access: Azure API Management validates the token and applies the configured authorization policies before forwarding authorized requests to the backend APIs. This approach combines application registration, product-based access organization, and identity-based authentication to provide a structured model for API consumption. Public preview now open to all customers The Applications feature was previously available through a limited public preview that required customers to register for access. Starting now, the public preview is open to all customers in supported Azure API Management tiers, without any sign-up or registration requirement. Customers can explore the feature, register consuming applications, configure product associations, and evaluate Microsoft Entra ID integration directly in their API Management environments. This expanded availability enables more organizations to evaluate application-centric API access management and provide feedback as we continue to evolve the experience. Get started with Applications To start using the Applications feature: Open your Azure API Management instance in the Azure portal. Navigate to the Applications experience. Register an application that will consume your APIs. Associate the application with the appropriate API products. Configure Microsoft Entra ID integration and the required authentication and authorization policies. Test API access using the application's identity. For detailed configuration steps, supported tiers, and feature requirements, refer to the official documentation. Get started with Applications in Azure API Management Looking ahead Applications represent an important step toward simplifying how organizations onboard, secure, and govern API consumers in Azure API Management. By introducing an application-centric model alongside existing API products and policies, Azure API Management helps organizations move toward more structured, identity-based API consumption. We encourage customers to explore the public preview, evaluate Applications in their API environments, and share feedback to help shape future improvements. Learn more: Azure API Management Applications documentationConnector Namespace is generally available:
A connector namespace is one Azure resource that hosts connections, triggers, connector operations, and MCP server configurations. You create a connection once, then use it from Azure Functions, Foundry agents, Azure Container Apps sandboxes, or your own app. Same 1,400+ connectors you know from Logic Apps and Power Platform. This post is the index. The main GA features each get their own deep dive, and I'll link them here as they go live. What's new Feature What you get Deep dive On-behalf-of (OBO) authentication for MCP connectors Set an MCP connector to Per-user authentication and every tool call runs as the signed-in user, not through a shared connection. The namespace creates one connection per user on first use, for any connector that supports OAuth sign-in. An agent that searches SharePoint for an employee sees only the files that employee can open, and the downstream system's audit trail shows the real user. Read the deep dive Custom connectors and custom MCP servers Bring your own APIs and MCP servers into the namespace, next to the managed catalog. Your internal order API or a partner's MCP server gets the same connection management and identity handling as Salesforce or ServiceNow, and your agents call it the same way. Read the deep dive Polling triggers Set a trigger configuration's delivery mode to Polling and your code pulls events from the namespace when it has capacity, instead of the namespace pushing them to a callback endpoint. There's no inbound endpoint to open, and access comes from an access policy on the connection, not a key. A function that processes new SQL orders can sit behind private endpoints and work through a burst at its own pace without flooding the fulfilment system behind it. Azure Functions consumes polling triggers today, through the Connector trigger in public preview. Read the deep dive Bring-your-own server image in Hosted MCP (public preview) Host your custom MCP servers without operational and management burden - just bring the container image, and let the namespace handle deployment, manage underlying compute, server lifecycle, authentication/authorization, scaling, and more. Read the deep dive GA also includes two platform updates: Managed identity end to end. Use an Azure managed identity as the authentication option for connectors that support it, configured the same way in Bicep and in the portal. For those connectors, your deployment pipeline stands up a namespace and its connections with no client secrets to store, rotate, or leak. New public regions. Create namespaces in more Azure regions: [Add region list]. Run your namespace in the same region as your compute and your data, and meet data residency requirements. We'll keep adding regions after GA based on partner and customer demand. What's next GA doesn't cover everything. Here's what's still coming, so you can plan around it: Observability. Diagnostic logs, Azure Monitor usage metrics, and an OpenTelemetry (OTel) export destination with shared correlation IDs for end-to-end tracing. Virtual network (VNet) integration. Inbound Private Link, and outbound VNet integration with customer-controlled DNS and egress. This is what lets connectors reach private and on-premises systems. Get started Portal: connectors.azure.com Documentation: Create a connector namespace Public preview announcement: aka.ms/connector-namespace/blog If you built on the preview, try the GA features and tell me what still keeps you out of production. That list shapes what we build after observability and VNet. File issues and requests at GitHub Issues.279Views0likes0CommentsRun MCP tools as the signed-in user: on-behalf-of authentication in Connector Namespace
What is on-behalf-of authentication OBO is a standard Microsoft Entra ID OAuth 2.0 flow. A service receives a user's token, exchanges it for a new token for a downstream API, and that new token still represents the same user. In Connector Namespace, you turn it on per MCP connector (a set of connector operations exposed as Model Context Protocol tools) by setting its authentication mode to OnBehalfOfUser. In the portal, this option is called Per-user authentication. From then on: There's no shared connection. The first time a user calls a tool, the namespace creates a connection for that user and that MCP connector. The user signs in to the connector once. Later calls reuse their connection. Connector credentials stay in the namespace. Your app never sees them. Developer connection (default) On-behalf-of user Runs as The connection owner The user calling the tool Connections One, shared by every caller One per user, created on first use What the agent can reach Everything the owner can reach Only what that user can reach Why it matters An agent that reads files or tickets for an employee should see only what that employee can see. With OBO, it does, because every call runs with the user's own permissions in the downstream system. OBO uses delegated permissions, so it never gives a user access they don't already have. That changes three things for you: No shared service account. Nothing in your namespace holds broad access on behalf of everyone. Actions belong to real people. The downstream system sees the user, not a service account, so its audit trail stays meaningful. Access is yours to pull. Remove an app or user from the MCP connector's access policies and their calls stop. Targets: where OBO applies OBO targets connector-backed MCP connectors that use Per-user authentication (OnBehalfOfUser in the API and CLI). It works with any managed connector that supports OAuth sign-in, such as SharePoint Online and Office 365 Outlook. Connectors that don't support OAuth can't use this mode. Two details shape your design: Each OBO MCP connector wraps exactly one connector. Need SharePoint and Outlook? Create two MCP connectors. Every call needs two matches: an Application access policy for the calling app, and a User or Group policy for the signed-in user. Permissions on a connection don't count toward this check. Hosted MCP servers have their own OBO mode with an admin app registration. That's a separate post. Prerequisites You need four things before the walkthrough. The first two are one-time tenant setup, usually done by an Entra admin. A connector namespace. Plus Owner or Contributor on it. See Create a connector namespace. The Azure API Connections enterprise application in your tenant. This is a Microsoft first-party app, not an Azure resource you deploy. It represents the namespace runtime in Entra ID (application ID fe053c5f-3692-4f14-aef2-ee34fc081cae, audience https://apihub.azure.com). Check whether your tenant already has it: az login --tenant "<tenant-id>" az ad sp show --id fe053c5f-3692-4f14-aef2-ee34fc081cae If it's missing, an Entra Application Administrator or Cloud Application Administrator creates it: az ad sp create --id fe053c5f-3692-4f14-aef2-ee34fc081cae These identifiers are for Azure public cloud. Verify the app ID and audience before you use another cloud. An app registration for your agent or app. This is the caller. It must be a confidential client (secret, certificate, or federated credential) in the same tenant as your users. Public clients and app-only tokens don't qualify. In its API permissions: Select Add a permission, then APIs my organization uses, and search for Azure API Connections (or the application ID above). Select Delegated permissions, then Runtime.All (scope ID 6c3012bf-22c1-4bb5-959b-dff738314144). Select Grant admin consent for your tenant. You will also need The users or groups who'll use the agent. You need their object IDs from the Microsoft Entra admin center. Walkthrough: an agent that only sees your files The scenario: an HR policy agent that searches SharePoint document libraries. Two employees ask the same question. Each gets answers only from files they can open. Step 1: Create the MCP connector Open your namespace in the portal at connectors.azure.com and select MCP Connectors. Create a new MCP connector, pick the SharePoint Online connector and select an existing connector or create a new one Under authentication, select Per-user authentication. Under tools select the tools you want to expose. Get file content Get file metadata Get file properties List folder List root folder The portal uses your own sign-in to read the connector's operations while it builds the tools. At runtime, each user gets their own connection. Pick the mode carefully. It's fixed once set. To switch modes, you recreate the MCP connector. Step 2: Add access policies In the MCP connector, select Access Policies, then + Add Access Policy, and add two policies: Application, with your app registration's client ID and tenant ID. User or Group, with the object ID and tenant ID. Watch the IDs. Applications use the client (application) ID, users and groups use the object ID, and swapping them gets the policy rejected. Step 3: Get a delegated token in your app Your agent backend already receives a user token for its own API. Exchange it with MSAL's on-behalf-of flow for the Runtime.All scope: var app = ConfidentialClientApplicationBuilder .Create(clientId) .WithClientSecret(clientSecret) // or a certificate or federated credential .WithAuthority($"https://login.microsoftonline.com/{tenantId}") .Build(); var result = await app .AcquireTokenOnBehalfOf( new[] { "https://apihub.azure.com/Runtime.All" }, new UserAssertion(incomingUserToken)) .ExecuteAsync(); If your app signs the user in directly, request the same scope during sign-in instead. Either way, the token should have audience https://apihub.azure.com and scope Runtime.All. Step 4: Call the MCP endpoint Copy the MCP endpoint URL from the MCP connector's overview. Don't build it from the resource name. Send the token as a bearer token: POST <mcp-endpoint-url> Authorization: Bearer <delegated-token> Content-Type: application/json {"jsonrpc":"2.0","id":"1","method":"tools/list","params":{}} Step 5: Handle first-time consent The first time a user calls a tool, they haven't connected to SharePoint yet. The response is HTTP 200 with a JSON-RPC error: {"jsonrpc":"2.0","id":"<request-id>","error":{"code":-32001,"message":"<consent-required-message>","data":{"url":"<consent-url>","connectorName":"sharepointonline","connectionId":"<connection-id>"}}} Show the user a sign-in action that opens error.data.url , then retry the call. Don't treat HTTP 200 as success on its own. If your MCP client supports URL elicitation, turn on consent elicitation in the MCP connector settings and you'll get an elicitation/create request instead. Before you build: what to know One connector per MCP connector. Group tools by connector. Same-tenant users only. Guest and cross-tenant users aren't supported yet. Consent is per user, per connector. Design your client for the consent response from day one. Feedback I want to know where this breaks for you. Point it at the connector your agent depends on most, run it as two different users, and tell me what you see. File issues and requests at GitHub Issues. That list decides what we build next. Portal: connectors.azure.com GA announcement: aka.ms/connector-namespace/ga/blog134Views0likes0Comments