ai agents
233 TopicsFinOps in Microsoft Foundry: see your token spend, hit your quality bar for less, and set limits
An end-to-end walkthrough of FinOps for AI in Microsoft Foundry: plan what an agent should cost, see where the spend goes, find out why it changed, hit your quality bar for less, and set limits.241Views0likes0CommentsFoundry IQ: now managed for you in every Foundry project
Foundry IQ: Now managed for you in every Foundry project Building AI agents that can answer questions from your documents just got simpler. Today we're announcing that every Microsoft Foundry project will include a managed Foundry IQ resource. Create knowledge bases and ground agents directly from your project, with no separate Foundry IQ (Azure AI Search) service to provision or manage. With a managed Foundry IQ resource, it's easier to connect your agent to a knowledge base and activate market-leading agentic retrieval, ingestion, content security, indexing, and source connections within your Foundry agent-building experience. You choose the content; Foundry IQ manages the underlying grounding infrastructure. Request access to the Foundry Managed Knowledge preview. We're starting with limited preview access and plan to roll out managed Foundry IQ to all Microsoft Foundry projects in December 2026. How it works Start with an eligible project and permissions to create a knowledge base and access the content you want to use. Step 1: Open Knowledge in your Foundry project and select Create a knowledge base. In the configuration pane, use the Managed by Foundry resource and enter a name for your knowledge base. Step 2: Select Upload files to add your files as a knowledge source. Foundry IQ processes the uploaded content and prepares it for retrieval through a searchable index. Once the knowledge source status changes to Active, save the knowledge base. You can also connect a knowledge source supported by the managed preview. For supported file formats, upload limits, and processing details, see Create a file knowledge source. Find evidence across documents with agentic retrieval With model-based query planning enabled, Foundry IQ can break a complex question into focused searches, run them in parallel, and bring the relevant passages together for the agent. For example, asking "How do our Q3 sales in Europe compare with our Q2 forecast?" may require retrieving actual sales results, forecast assumptions, and regional performance data from different documents. Foundry IQ can plan and execute focused searches across those sources to gather the evidence needed for a grounded response. Source references let users check where the answer came from. Learn how agentic retrieval works. Use microsoft-retriever-1 out of the box for fast, low-cost retrieval, or bring your own supported model to tune the trade-off between latency, cost, and answer quality. Different workloads may benefit from different models depending on query complexity, retrieval requirements, and performance goals. Ground your agent and test its answers From the saved knowledge base, select Add to an agent. In the agent playground, ask a question that draws on multiple files and open a citation to check that the source supports the answer. Then try a question answered by one document and another the documents can't answer. For the latter, check that the agent acknowledges the gap. Choose how to run Foundry IQ Use a managed Foundry IQ resource when you want to create a knowledge base in your project and have Foundry manage the search infrastructure. Bring your own Foundry IQ (Azure AI Search) resource when you want to reuse existing search indexes or indexing pipelines, define custom index schemas, or control the search resource configuration directly. Supported knowledge sources and configuration options vary by setup. Get started Request access to private preview and try grounding an agent with a set of documents you know well. Additional resources: Open Microsoft Foundry Explore Azure AI Search knowledge sources Connect a knowledge base backed by your own Azure AI Search resource to Foundry Agent Service Use the Foundry IQ skill with an AI coding agent See Azure AI Search pricing for bring-your-own resources75Views0likes0CommentsVoice agents in Microsoft Foundry Agent Service now generally available
People want to talk to AI as naturally as they talk to each other, with instant responses in their preferred language and voices that sounds Human-like. For organizations, this opens a new way to serve customers, with conversations that feel personal at any scale. Voice agents in Microsoft Foundry Agent Service, now generally available, give teams one enterprise-grade platform to build, deploy, operate and continuously improve those experiences. Over the past year, Microsoft has made significant strides in bringing this vision to life. At Ignite 2025, Voice Live API became generally available, giving developers a unified API for natural, real-time voice conversations with any AI agent. At Build 2026, we introduced Voice Live integration with Microsoft Foundry prompt agents and hosted agents, making it easier to build voice-enabled AI experiences. Today’s release brings together advanced speech capabilities and comprehensive agent lifecycle management in a unified, enterprise-grade platform. Developers can now build, deploy, operate, and continuously optimize intelligent, speech-to-speech conversational agents, accelerating the journey from prototype to production. We're also announcing significant advancements to Speech in Microsoft Foundry: more accurate speech recognition, more natural and expressive voices, and expanded choices across languages, voices, and avatars. Together, these innovations empower organizations to create richer, more human-like voice experiences for customers around the world. Voice agents in Microsoft Foundry Agent Service Voice agents in Microsoft Foundry Agent Service are now generally available. It's an enterprise-grade platform for developers to build Speech to speech conversational voice agents by providing the leading Speech capabilities and supporting the full agent's lifecycle — from building and deployment to operations and continuous optimization. Loading Medius video… The general availability of voice agents in Microsoft Foundry Agent Service introduces a comprehensive set of capabilities designed to help developers build more natural, intelligent, and reliable voice experiences, while simplifying development and operations at enterprise scale. End-to-end voice agent lifecycle management Going beyond model APIs, Voice Agent builds on the Microsoft Foundry agent platform to help developers build, deploy, and operate enterprise-ready voice agents through a unified platform. Build and connect: Developers can create voice agents in minutes, connect them to enterprise knowledge through Foundry IQ, and integrate with rich tools through server-side MCP and client-side function calling, apply guardrails to help keep conversations safe and aligned with business policies, with private-network support for supported enterprise resources and integrations—helping teams control access to sensitive systems and data. Observe, evaluate, and improve: Built-in voice-native tracing, monitoring, and evaluation make conversations inspectable and quality measurable. For example, if a customer experiences a slow response during a billing inquiry, developers can inspect the turn-by-turn trace to determine whether the delay came from speech recognition, the model, a billing-system tool call, or speech synthesis—and replay the conversation when transcript and audio capture are enabled. Connect to existing channels with easy setup: Deploy voice agents on the web using audio or text input / output or connect them to existing telephony and contact-center infrastructure—including Teams Phone, Twilio, and Genesys—without rebuilding your customer experience. Bring AI-powered conversations to the channels customers already use, while managing agents through a unified platform. More natural, expressive, and intelligent voice conversations Deliver engaging, real-time conversations with greater flexibility in speech models and voices. Expanded choice of speech-to-speech models: Alongside existing GPT Realtime models, we’re introducing new options for more natural voice conversations, giving enterprises greater flexibility to balance conversational experience, agentic capabilities, and cost. GPT Live 1: Delivers full-duplex, highly natural, fluid conversations—from follow-up questions to complex, multi-step requests. Beyond delegating to specialized models, it can route tasks to Foundry prompt agents, and hosted agents across agent platforms, bringing their specialized knowledge, tools, and workflows into the conversation without breaking its flow. This lets enterprises combine an engaging voice experience with agents that handle work behind the scenes, for experiences where conversational richness and task completion both matter. Microsoft Realtime Flash 1: Combines low-cost serving with competitive conversational quality and agentic capabilities across typical voice-agent domains, including customer support, appointment scheduling, and routine service requests. It supports experiences where agents need to understand customer intent, sustain a natural conversation, and use tools to take action—not simply answer questions. Its cost-efficient approach helps enterprises move beyond small pilots toward the economics required for millions of calls per day, keeping operating costs manageable as adoption grows. The model is now in preview with Voice Live Lite tier pricing, offering an affordable path to scaling voice automation. Below is our internal test result on τ³-Voice benchmark. Microsoft Realtime Flash 1 achieved the highest reported average score in internal testing: 70.9 versus GPT-realtime-2.1’s 63.7—a 7.2-point improvement. Gains were strongest in telecom (+16.6 points) and retail (+3.5 points), while airline performance was lower (−6.0 points). Against GPT-realtime-2.1-Mini, the average improved by 39.2 points. More expressive voices: New HD V3 voices bring natural, real-time speech with greater expressiveness, optimized for customer service scenarios. Expanded language coverage includes English, Chinese, Filipino, Indonesian, Malay, and Indic languages. Developers can also control speaking styles and expressions using simple instruction tags, without learning complex markup languages. Enhanced conversation quality: Improved noise suppression helps voice agents stay focused on the primary speaker, reducing interference from television audio and background voices. Combined with more accurate turn-taking and end-of-speech detection, azure_semantic_vad v2 helps distinguish genuine interruptions from brief acknowledgments and speech directed at others—reducing unnecessary interruptions and premature responses for smoother, more natural full-duplex conversations than previous version. Below table reports our test results on Full-Duplex-Bench v1.5, a public benchmark that tests how a voice model behaves when someone else talks while it is speaking. Each column is the share of test cases where the model did the right thing (0 to 1). The total score is the plain average of the four columns. As you can see, the total score improved from 46.3% to 72.2%, a 25.9-percentage-point gain, with the largest improvements in handling speech directed at others and background voices. Customized voice and avatar experiences Create differentiated, branded experiences through customizable voices and avatars. Organizations can use their own data to develop custom voices that reflect their brand identity. We're also introducing VASA-2 Photo Avatar, which transforms a single photo into a lifelike, upper-body talking avatar. Building on VASA-1, VASA-2 delivers more natural movements and greater control over facial expressions, enabling richer and more engaging visual conversations. Flexible multi-agent orchestration for complex voice agents experiences Voice agents can seamlessly collaborate with Foundry prompt agents and hosted agents through flexible multi-agent patterns. Developers can choose the architecture that best fits their applications: Delegation to sub-agents: Voice agents handle real-time conversations while delegating complex reasoning and specialized tasks to backend agents. This keeps voice interactions responsive and low latency without sacrificing reasoning capabilities. Inline sub-agents: Developers can orchestrate multiple specialized voice agents in a graph-based workflow, each with its own instructions, tools, and voice. Agents can seamlessly transition between tasks during a conversation, improving accuracy, controllability, and cost efficiency. Hosted agents as conversation engines: Voice agents manage real-time speech input and output while communicating with hosted agents through bidirectional text streaming. This allows developers to preserve existing agent logic while adding advanced conversational voice capabilities. Together, these patterns make it easier to build sophisticated voice experiences that combine real-time responsiveness with powerful reasoning and enterprise workflows. Simplified development and enterprise integration Accelerate voice agent development with a streamlined developer experience and ready-to-use integrations. Unified developer tooling: Azure Developer CLI (AZD) and GitHub Copilot support help developers quickly build, test, and deploy voice agents using familiar development workflows. Ready-to-use templates: More than 40 industry-specific agent templates accelerate development across customer support and other business scenarios. Native telephony integration: Built-in Session Initiation Protocol (SIP) support enables voice agents to connect directly with existing contact center and telephony infrastructure, making it easier to bring AI-powered conversations into established customer service workflows. Since the public preview launch, thousands of customers have adopted voice agents across a wide range of scenarios, including customer service, automotive, education, human resources, personal assistants, public services, and more. Hear from customers already building voice agents in Foundry: "As a leading airline, Gulf Air is proud to work with Microsoft to advance how we use AI across our business. Through our collaboration, we have migrated and enhanced our existing voice agents in Microsoft Foundry, bringing voice, enterprise knowledge and intelligent tools together in a more integrated experience. This enables us to innovate faster and deliver even better experiences for our teams and customers." Ahmed AbdulJalil Ebranhim, Manager, Digital Innovation & Process Management, Gulf Air “The Hera companion is a voice agent built on Microsoft Foundry. What began as a proof of concept is now an operational experience. Anyone can talk to Hera: she listens and answers in real time. And she doesn’t just answer, she acts. Ask for a tour, and she turns the spacecraft to show you. Switch to Italian halfway through, and she keeps going. But a great voice isn’t enough; she has to be right. With voice agents in Foundry, Foundry IQ grounding and safety controls come together in one place, so every answer is grounded in ESA’s own mission knowledge and checked against Microsoft’s safety controls and our own rules." Daniele Montemaggiori, IT Cloud Services Architect, European Space Agency (ESA) "We tested multiple AI vendors and voice pipelines, and none delivered the customer experience we wanted. Voice agents in Microsoft Foundry finally made AI calls feel like a conversation instead of a phone tree - callers can interrupt, pause to think and speak naturally, and the agent keeps up. With a regional bank customer, our AI agent now handles 30% of calls from end to end. When a caller needs a person, it hands off to a human expert in Microsoft Teams on the same call, with full context." Matt Landis, CEO & Founder, Landis Technologies What’s new in Speech in Microsoft Foundry - More accurate, natural speech models Beyond powering voice agents described above, customers use Speech in Microsoft Foundry for live captions, meeting and call transcription and translation, voiceover for videos and e-learning, and reading content aloud. At Ignite 2026, we are making it more accurate, more natural and offering more choice across three core capabilities: speech to text, text to speech and avatars, and speech translation. Speech to text: understand more languages, faster and more accurately Speech to text converts streaming and file-based audio into high-quality transcripts for voice agents, live captions, contact center analytics, and meeting transcription. These scenarios increasingly involve many languages, speakers who switch languages mid-conversation, and large volumes of recorded audio. Our latest updates, all now generally available, address these needs across real-time transcription, Fast Transcription, and containers. Real-time transcription now offers native multilingual recognition across 50+ languages, with more on the way, so you no longer have to specify the language up front. Results arrive in about 100 milliseconds, with availability in select regions. Multichannel support transcribes two audio channels, such as agent and customer, separately and detects the language on each. For single-language audio, post-stream refinement now spans all language locales. To learn more, see our latest blogs on multichannel transcription and multilingual transcription. Fast Transcription and LLM Speech are now faster than ever, processing audio at a 100+ speed factor across 100+ multilingual languages, including expanded Indic language support. Mixed-language audio can now be transcribed in a single call. LLM Speech ranks among the leaders on Hugging Face's Open ASR Leaderboard and holds the top spot on the multilingual leaderboard, underscoring its quality across languages. Read more in our latest blog post. Microsoft AI's MAI-Transcribe-2 is now available as an additional model option. On-Prem Containers now support Fast Transcription, letting you transcribe audio files on-premises with GPU inference through the same API you use in the cloud. Learn more Text to speech (TTS) and TTS avatar: more natural voices, more choice, more lifelike avatars Microsoft text to speech voices and avatars power many scenarios beyond voice agents mentioned in section 1 above. In addition, natural and expressive voices are required for voiceover, e-learning and read-aloud content, and other apps need voices that sound clear and engaging. At Ignite 2026, we are delivering two updates: a better and broader set of Neural HD standard voices, and the new VASA-2 photo avatar. New update for Neural HD standard voices: Besides the Neural HD v3 voices enhancement covered in voice agent scenario, we also extend our Neural HD standard voice offering with the Partner Voices (Public Preview), which brings HD voices built by partners such as DataoceanAI and Telus into Microsoft Foundry. Partner voices give customers more choices to find the right one for both their voice agents and content creation scenarios. Locale Voice Name Sample Script Audio Link En-CA TTS-354-F1 Oh no, I completely understand how that must feel—it can be really frustrating when things don’t go the way you expect. But don’t worry, you’re not alone. I’ll be with you every step of the way and make sure we get this sorted out quickly. Let’s take it one step at a time, okay? Ko-KR TTS-038 모두 50대 이상 중년층 고객이 가장 많이 증가한 것으로 나타 났다. Zh-CN TTS-373-F231 哎呀,我不是故意让你失望的!这样吧:如果你想要古怪又有趣、充满笑声的体验,就去看蓝人乐团。如果你想要令人惊叹又充满魔力的表演,太阳马戏团是最佳选择。两者都会让你的第一次约会难忘,所以无论选择哪一个都不会错。 New VASA-2 photo avatar (Public Preview): Avatar brings a face to voice agent and empowers content creation scenarios such as marketing video or training materials. VASA-2 photo avatar is specially designed to enrich the voice agent experience to be more engaged and personal. In Ignite 2026, we bring VASA-2 turns a single photo into a lifelike, upper-body talking avatar, an important upgrade from the talking head of VASA-1. It also moves more naturally and gives you more control over facial expressions to fit your scenario. Learn more. Speech translation: talk across languages in your own voice Language should not stand between people. Live Interpreter API, our real-time speech-to-speech translation service, now runs on a new LLM-based model that translates speech while people are still talking. Breakthrough translation quality: 30% fewer translation errors than the previous production model. Fast response: Translates end to end in under 3 seconds, on par with professional human interpreters. Your voice in every language: With Personal Voice, Live Interpreter API keeps the speaker's voice, style and tone in each language, so conversations feel natural and personal. Learn more Customers are already using Live Interpreter for contact center agent assist, on phones and smart devices such as earbuds and AI glasses, and in international meetings. Get started today Build voice agents: Getting started only takes a few steps: Open the Microsoft Foundry portal go to Build, Agents and New agent, select “Voice”. Choose a voice-optimized model and configure your agent's instructions. Connect knowledge sources and tools as needed for your scenario. Test conversations directly in the built-in voice playground. Deploy to your desired channels and monitor performance using built-in observability and evaluation capabilities. Explore Speech in Microsoft Foundry. Use the Speech playgrounds in Microsoft Foundry Portal to try Speech transcription, voices, avatars and Speech translation. When you’re ready to integrate speech into an application, start with the Speech SDK and Speech in Microsoft Foundry documentation.161Views0likes0CommentsYour Agents Are Running. But Are They Safe and Compliant?
An AI agent can perform perfectly and still violate your organization’s policies. Picture an enterprise running hundreds of agents across customer service, financial transactions, and internal workflows. Every operational dashboard looks healthy: tasks are completing and targets are being met. But are those agents using approved models? Accessing only authorized tools? Running the required safety protections? And when one violates a requirement, can an administrator tell which policy failed, which asset is affected, and what to change? An operationally healthy fleet isn’t necessarily a safe or compliant one. As organizations move from experimenting with individual agents to running AI across business-critical operations, it’s no longer enough to define policies and trust each team to implement them. Enterprises need to enforce the controls that matter at runtime, verify those controls actually work, and confirm, across the fleet, that they’re in place. That’s what Microsoft Foundry Safety brings together. It’s the home for the capabilities that keep agents inside the boundaries you set: Foundry Guardrails: safety controls a developer configures and Foundry applies at runtime. agent controls: the managed policy engine underneath Guardrails, enforcing deterministic rules, classifiers, and LLM-based judgments across frameworks and clouds. Safety Rubric Evaluators: spec-driven evaluations that measure whether a control actually holds, before and after you ship. AI Red Teaming Agent: adversarial probing that finds failures before an attacker does. Compliance dashboard: the new experience that confirms, across your entire fleet, that these controls are assigned, in place, and holding. Each of these has its own story. Governing hundreds or thousands of agents is a different challenge than building one. The new Manage experience in Microsoft Foundry brings fleet inventory, operational telemetry, cost, and compliance into a single view. The Foundry Governance blog walks through Fleet, Operations, and Cost in depth. This post, however, focuses on the capabilities that tells you whether your fleet is safe and compliant. Compliance: from requirements to action At the center of this experience is Foundry Manage → Compliance, bringing together relevant governance signals from Azure Policy, Microsoft Defender for Cloud, and Microsoft Purview. Four complementary views help administrators investigate their AI estate: Compliance view What it helps answer Policy Which organizational policies apply, and where are violations occurring? Asset Is a particular agent, model deployment, or toolbox compliant? Security posture Which security recommendations require attention? Data security & governance What Purview coverage and data-security findings are relevant to my AI assets? Understand compliance from the policy or the asset Administrators and developers come to Compliance with different questions. An administrator may start with an organization-wide requirement and ask which resources violate it, across a subscription or resource group. A developer is more likely to start with a particular agent and ask which policy it failed, why, and what needs to change. The Policy and Asset views support these complementary workflows. Through its integration with Azure Policy, Microsoft Foundry brings organizational governance into the context of your AI estate. Administrators can define and assign policies at the appropriate scope, review compliance status, identify violating assets, and investigate policy requirements. These capabilities span model deployments, agent configurations, tools, network egress, and safety controls, as outlined below: Policy category What organizations can govern Models Restrict deployments to approved models or publishers and enforce model eligibility requirements, such as excluding preview models. Agents Govern approved agent types and trusted Hosted Agent container images. Tools Govern tool usage and connections, including approved tool types, MCP endpoints, and connectors. Network egress Control which outbound destinations hosted agents are permitted to access. Safety controls Establish requirements for safety guardrails, such as harmful-content filtering, jailbreak protection, indirect-attack protection, and custom controls. For example, an organization might establish a policy restricting AI deployments to an approved set of models. In Manage → Compliance → Policy, an administrator can review the assigned policy, examine its scope and configured parameters, understand whether it is compliant, and identify the exact model deployments that violate the requirement. They can also inspect the policy definition, enforcement effect, and available evaluation details to understand why an asset is noncompliant. For changes to assignments or exemptions, Foundry links to the relevant Azure Policy management experience. Audit and Deny provide different levels of control. Audit identifies noncompliant resources without blocking operations. Where supported, Deny prevents new noncompliant create or update operations, while existing resources that violate the policy remain flagged until remediated. The effects available depend on the specific policy definition. This gives administrators a clearer view of not just which policies exist, but where they apply, how they are configured, and which resources require attention. The Asset view provides the complementary perspective. Starting from a flagged customer-support agent, a developer or administrator can examine the relevant policy evaluations and identify the cause: perhaps a disallowed model deployment or a missing required protection. The agent may be operating successfully from an application perspective while remaining noncompliant. Operational health and policy compliance are not the same thing. And knowing a violation exists is only useful if you can act on it. Foundry connects the affected asset to the requirement and the relevant management experience, helping teams determine whether to update a configuration, enable a protection, or follow an Azure Policy workflow. From compliance requirements to safety controls enforced at runtime Configuration compliance is essential, but agents introduce another challenge: an agent can be configured correctly and still attempt an action that violates a business rule. Imagine a financial-services agent offering a new credit product to a customer who has disclosed financial hardship, or an agent attempting a transaction above its authorized limit. These are runtime behavioral requirements that depend on what the agent is doing in the moment. That's why we're bringing more flexible safety controls into the Foundry developer experience. Define safety controls once. Apply them automatically at runtime. With Microsoft Foundry Guardrails, developers can configure safety controls through Build → Guardrails or programmatically through the API. These controls include supported built-in safety protections, such as harmful-content filtering and prompt-attack protection. The architecture is also evolving to support more expressive organization-specific requirements through deterministic business rules and LLM-based judgments. Once a guardrail policy is configured and assigned to a supported agent, Foundry automatically applies its supported controls at runtime. Developers don't need to build a separate policy-evaluation and enforcement integration for the supported Foundry-hosted execution path. The runtime invokes the applicable protections at supported intervention points and applies their decisions as part of execution. Behind this experience are our investments in the open-source Agent Control Specification (ACS), Agent Hooks, and the managed agent controls service. Agent Hooks defines where the runtime can intervene; ACS defines the policy evaluation contract; the managed service evaluates supported policies; and the Foundry runtime enforces the returned decisions. For example, consider an insurance agent processing a policyholder's request to change a beneficiary. An organization might want to require verified identity context before the update, use an LLM judge to detect possible coercion requiring escalation, and apply built-in classifiers to relevant content risks. These are illustrative policy patterns, with availability depending on the supported controls and intervention points. Developers define the boundaries. Foundry handles runtime application of assigned, supported guardrails. Azure Policy complements this experience by establishing and auditing supported organizational requirements; an Azure Policy assignment is not a prerequisite for a properly assigned guardrail to operate at runtime. For more on the underlying architecture and cross-framework integration, see agent controls announcement. Check that the control actually works: Safety Rubric Evaluators Enforcing a control and verifying it holds are two different things. Safety Rubric Evaluators (preview), built on our open-source ASSERT work, turn a plain-language safety policy plus your agent’s own definition and traces into a structured set of Allowed and Disallowed behaviors, then score conversations on two independent metrics, whether the agent did something disallowed, and whether it refused something legitimate. Measuring those separately matters: the easiest way to drive unsafe outputs to zero is to make an agent refuse everything ambiguous, and a single blended score would hide that over-refusal. Teams can generate a rubric from a policy, review and version it in the Evaluator Catalog, and re-run it before and after a mitigation to confirm a fix reduced risk without breaking legitimate user workflows. Together, the pieces form a loop: Guardrails and agent controls enforce policy at runtime, Safety Rubric Evaluators and AI Red Teaming measure whether it holds, and Compliance confirms coverage across the fleet. (Read the Safety Rubric Evaluators deep dive →) Security and data governance belong in the same view Compliance doesn't stop at resource policies and runtime guardrails. An AI resource can meet its configuration requirements and still have security weaknesses or data-exposure risks. Security posture: Microsoft Defender for Cloud The Security posture view surfaces relevant Defender for Cloud recommendations for supported resources. For example, an administrator may discover a recommendation to disable local key-based authentication on a Foundry resource, see which AI resource is affected, and navigate to Defender for deeper investigation and remediation. Data security and governance: Microsoft Purview The Data security & governance view brings relevant Microsoft Purview information into Foundry, including supported coverage information, agent interactions, and prioritized data-security findings. As agents retrieve documents and process sensitive records, administrators can investigate relevant data-protection signals in the context of their AI estate, then use Purview for specialized management and remediation. From compliance signals to action An administrator may begin in Fleet or the Policy view to assess an organization-wide requirement, identify noncompliant assets, and navigate to Azure Policy for an assignment change or exemption. A developer may begin with an agent in the Asset view, inspect the specific violation, and update its model, tool configuration, or guardrails. Both benefit from seeing the requirement and the affected asset in the same Foundry management experience. If an agent is experiencing errors or elevated latency, Operations provides relevant telemetry. If the concern is infrastructure security, teams can investigate in Defender. If it involves sensitive enterprise information, Purview provides its specialized data-security workflows. These systems retain distinct responsibilities for policy evaluation, runtime enforcement, and evidence. What changes is that teams no longer have to begin their investigations with disconnected information scattered across multiple systems. Foundry connects the AI assets organizations build with the policies, protections, and governance insights they need to operate them responsibly. Get started Building an agent that works is only the beginning. The next challenge is building an AI fleet your organization can confidently operate and govern. With Microsoft Foundry Safety, we’re bringing the capabilities that keep agents safe into one place: Guardrails and agent controls to enforce policy at runtime, Safety Rubric Evaluators and AI Red Teaming to verify it holds, and the new Compliance experience to confirm coverage across the fleet. Together with the broader Manage experience — fleet inventory, operational monitoring, and cost — these help organizations move from defining policies to enforcing, verifying, and confirming them. Ready to explore? Start in Microsoft Foundry: Manage your AI fleet: Discover your agents, models, and other AI assets across supported scopes, and understand fleet-level activity and health. Explore Compliance: Navigate to Manage → Compliance to investigate organizational policies, noncompliant assets, security recommendations, and data-governance insights. Understand Azure Policy: Learn how to establish organizational requirements, manage policy assignments, and review compliance results. Configure runtime safety with Foundry Guardrails: Navigate to Build → Guardrails or use the supported API to define and assign safety controls that Foundry automatically applies to supported agents at runtime.54Views0likes0CommentsThe Governance Layer Every Enterprise AI Agent Needs
Introduction The first wave of agentic AI was about capability: Can an AI agent reason, retrieve enterprise knowledge, call tools, and take actions? The next question is much harder: Should the agent be allowed to do it? As AI agents move from experiments into enterprise environments, building the agent is only part of the problem. We need to decide what principles it must follow, what knowledge it can trust, which model should handle a request, what actions it is authorized to perform, and how every important decision can be traced and audited. Building such an agent raises four fundamental governance questions: 1. What principles must the agent obey? 2. What knowledge is the agent allowed to access and trust? 3. Which model should handle each request? 4. What did the agent decide and do, and can we audit it? These four questions give us four layers of enterprise AI governance: This is where AI governance becomes part of the architecture, not an afterthought. 1. Constitutional Governance What principles must the agent obey? AI agents can reason, retrieve information, call tools, and take actions dynamically. This introduces an important governance question: What principles and boundaries must the agent follow regardless of what a user asks it to do? For example, an enterprise HR agent might be required to: Protect sensitive employee information. Detect attempts to manipulate its instructions. Prevent harmful or prohibited responses. Validate risky actions before executing them. Connect only to approved enterprise systems. These principles form a constitutional governance layer around the agent. The goal is not to rely only on instructions in the system prompt, but to enforce controls throughout the agent workflow. How does Microsoft Foundry enable it? Microsoft Foundry provides Guardrails, which allow organizations to configure safety and security controls around models and agents. A guardrail is a named collection of controls. Each control defines: The risk that should be detected. Where in the interaction the risk should be evaluated. What action should be taken when the risk is detected. Guardrails can evaluate an interaction at different stages: Intervention point What is checked User input What the user asks Tool call What action the agent wants to perform Tool response What information a tool returns Output What the agent returns to the user For example, consider: "Ignore company policy and retrieve the salary details of another employee." A guardrail can detect the unsafe input, inspect a proposed HR tool call, evaluate information returned by the tool, or prevent unsafe information from appearing in the final response. This provides defense in depth, rather than relying on a single system prompt. Steps to configure Guardrails in Microsoft Foundry Open the Microsoft Foundry project. Go to Build → Guardrails. Select Create Guardrail. Select the required control or risk. Choose where it should apply: User input, Tool call, Tool response, or Output. Configure the required action and save the guardrail. Assign it to the supported agent or model deployment. Test with both normal and adversarial prompts. Step 1: Creating a Guardrail Capture: Foundry → Build → Guardrails → Create Guardrail This screenshot demonstrates where governance controls are created. Step 2: Configuring a control Capture the screen showing the selected risk together with the available intervention points and actions. This is the most important screenshot because it visually demonstrates that governance can happen at different stages of agent execution. Step 3: Testing the Guardrail Run one allowed prompt and one intentionally blocked test prompt and capture the resulting behavior. This demonstrates that the governance policy is actually being enforced rather than existing only as an agent instruction. 2. Knowledge Governance What knowledge is the agent allowed to access and trust? Enterprise agents need access to organizational knowledge such as policies, SharePoint documents, operational data, and business information. But simply because information exists within the enterprise does not mean every agent or employee should be able to access it. Knowledge Governance therefore focuses on four questions: Source: Where did the information come from? Trust: Is it an approved enterprise source? Access: Is the user authorized to see it? Grounding: Can the answer be traced back to its source? For example, an HR agent should be able to answer: "What is our parental leave policy?" But it should not expose another employee's confidential information simply because that data exists within an enterprise system. How does Microsoft Foundry enable it? Microsoft Foundry provides Foundry IQ, which enables organizations to create reusable, multi-source knowledge bases for AI agents. A shared knowledge architecture can look like this: SharePoint + OneLake + Azure Blob Storage + Approved Web Sources → Foundry IQ Knowledge Base → HR Agent / IT Agent / Finance Agent Instead of every agent maintaining a separate retrieval pipeline, multiple agents can use a shared knowledge base. Foundry IQ uses Azure AI Search for indexing and retrieval and supports agentic retrieval across configured knowledge sources. More importantly for governance, it can support permission-aware retrieval using capabilities such as Microsoft Entra identity, ACLs, query-time authorization, and Microsoft Purview sensitivity labels for supported sources. This means the knowledge base can be shared while the information returned still depends on what the requesting user is authorized to access. Foundry IQ can also return citations to the source content, helping users verify where an agent's answer originated. Steps to create a shared knowledge base Open your Microsoft Foundry project and go to Build → Knowledge. Create or connect an Azure AI Search resource. Create a Knowledge Base and add the required knowledge sources. Configure the required retrieval settings and access controls. In Azure AI Search, go to Access control (IAM) → Add role assignment and assign Search Index Data Reader to the Foundry project/resource managed identity. Go to Agents and connect the Knowledge Base to the required agent. Test the agent and verify that the response is grounded in the expected source with citations. Step 1: Build → Knowledge showing the Knowledge Base and connected sources. Step 2: The Knowledge Base connected to an agent and adding the permissions Step 3: An agent response showing the retrieved answer and source citations. Key takeaway: Knowledge Governance is not simply about giving an agent more data. It is about giving the agent access to the right knowledge, for the right user, from trusted sources, with traceability back to the source. 3. Model Governance Which model should handle each request? Model Governance determines which AI models an organization allows its agents to use, how models are selected for different tasks, and how their performance is evaluated over time. Not every enterprise request requires the same level of intelligence. A simple question such as "What are the office working hours?" does not require the same reasoning capability as "Compare these three financial reports and identify potential inconsistencies." Using the most powerful model for every request can increase operational costs and response latency. Conversely, using a smaller model for complex reasoning tasks could affect response quality. Model Governance therefore focuses on finding the right balance between: Capability: Is the model capable of handling the task? Quality: Does it produce accurate and reliable responses? Cost: Is the model economically viable at scale? Performance: Does it meet the required latency and throughput? Compliance: Is the model approved for the organization's data and workload requirements? It also establishes a controlled set of models that agents are permitted to use, rather than allowing unrestricted model selection. How does Microsoft Foundry enable it? Microsoft Foundry provides a model catalogue, model deployment options, routing capabilities, and evaluation tools to help organizations manage model selection and performance. 1. Microsoft Foundry Model Catalogue The Foundry Model Catalogue provides a centralized place to explore available models from Microsoft and other providers. Organizations can compare models based on their capabilities, supported modalities, benchmarks, and deployment options. For example, an enterprise might maintain an approved model pool containing: A smaller model for simple employee queries. A more capable model for document summarization. A reasoning-oriented model for complex multi-step tasks. This creates a controlled model selection process before models are made available to agents. Steps to use the Model Catalog 1. On the overview page of Microsoft Foundry, Select Explore Models. 2. Search for the model that you're looking for in the search bar. 2. Microsoft Foundry Model Router One of the most interesting capabilities here is Model Router. Instead of manually writing routing logic for every incoming request, Model Router analyzes the request context and dynamically selects an appropriate model from the configured model pool. For example: Employee request Routing decision "What are the office timings?" A smaller, faster model "Summarize the leave policy." A capable general-purpose model "Compare multiple policies and identify exceptions." A more capable reasoning model Model Router supports different routing approaches that prioritize cost, balanced performance, or quality. It can also be used with Foundry Agent Service, where model selection can happen independently for individual requests within a conversation. This means the same conversation does not necessarily need to use the same model for every turn. Steps to implement model router through Microsoft Foundry 1. In Model catalog, search for model-router 2. Choose Custom settings 3. Select the routing mode 4. Deploy the model router and navigate to the playground to test. In the images below, I have tried three prompts. Each of these prompts are being handled by different models. 3. Model Evaluations Selecting a model based on its published benchmarks is not enough. Organizations need to evaluate how it performs against their actual business requirements. Microsoft Foundry Evaluations allows teams to assess models and agents using test datasets and predefined or custom evaluators. For example, an organization can create a dataset of HR-related questions and expected answers, then compare candidate models based on: Answer relevance. Accuracy and groundedness. Response quality. Safety. Latency and token consumption. These evaluations help determine whether a model is suitable for a particular workload before it is approved for production. Steps to run a Model Evaluation in Microsoft Foundry 1. Open your Foundry project. Select Evaluations on the navigation bar on the left. 2. Select Create and choose Model as the evaluation target. 3. Choose an existing dataset or create one containing test questions, reference context, and expected answers. 4. Select evaluators such as Relevance, Groundedness, Coherence, and Fluency. 5. Configure the evaluation, review the settings, and submit the run. 6. Once completed, inspect the aggregate scores and individual evaluation results. An important distinction: The evaluated model vs. the evaluator model In AI evaluations, two different models may be involved: Target model: The model being evaluated. It generates responses to the test questions. Evaluator (Judge) model: A separate model that assesses the generated responses against evaluation criteria such as relevance, groundedness, and quality. For example, an organization might evaluate GPT-4o-mini using a GPT-4.1 deployment as the evaluation judge. The target model generates the answer, while the judge model assesses how well that answer meets the expected criteria. Not every evaluator requires a judge model. Some evaluators use code-based metrics, while others use AI-assisted evaluation and require a configured judge model. 4. Continuous Evaluation and Optimization Model governance does not end once a model is deployed. Organizations need to continuously monitor AI performance, identify quality regressions, and optimize their solutions based on observed behavior. Microsoft Foundry provides a monitoring dashboard that helps teams track agent activity, execution performance, token consumption, and operational trends. Steps to monitor and optimize AI agents in Microsoft Foundry Deploy an AI agent and enable tracing so that its interactions and execution details can be captured. Generate sample interactions through the agent playground or application. Navigate to Monitor > Overview in your Foundry project. Select the relevant time range and review metrics such as agent runs, token usage, estimated cost, and operational performance. Compare trends across different time periods to identify changes in usage, performance, or failures. Use the observations to optimize prompts, model selection, and Model Router configurations where applicable. For example, if an agent experiences increased latency or consistently consumes more tokens than expected, engineering teams can investigate its execution traces and optimize the underlying model or orchestration strategy. This creates a feedback loop where observed performance and evaluation results drive ongoing optimization. If quality drops for certain request types, adjust Model Router's configuration to route those to a more capable model. 4. Decision Governance What did the agent decide and do, and can we audit it? Decision Governance focuses on making an AI agent's execution, decisions, and actions observable, measurable, and accountable. Unlike traditional applications, AI agents can make context-dependent decisions, select tools, retrieve information, and execute multi-step workflows. This introduces an important enterprise challenge: knowing what happened during an interaction is not always as straightforward as checking an application log. Consider an employee asking an IT support agent to raise a service request. The agent might: Interpret the employee's request. Identify the appropriate IT support category. Select the relevant API or tool. Invoke the API to create a ticket. Receive a response from the ITSM system. Confirm the result to the employee. Now imagine that the agent creates a duplicate ticket or assigns the request to the wrong department. The organization needs to investigate: What did the employee ask? Which model handled the request? What information did the agent retrieve? Which tool did it invoke? Was the action authorized? What was the final outcome? Decision Governance ensures that these interactions can be investigated, evaluated, and audited. How does Microsoft Foundry enable it? 1. Agent Tracing Microsoft Foundry provides tracing capabilities to capture the execution flow of an AI agent. Tracing helps organizations understand what happens during an agent interaction, including: User inputs and agent responses. Model invocations. Tool calls and tool responses. Execution duration and latency. Token consumption. Errors and failed operations. For example, if an agent fails to create an IT ticket, developers can inspect the trace to determine whether the issue occurred during model execution, tool selection, API invocation, or the external system's response. Foundry integrates tracing with Azure Monitor Application Insights. Steps to inspect agent execution traces in Microsoft Foundry Open your Foundry project and navigate to Create > Agents. Create an agent or open an existing agent. Configure the tracing connection with Azure Application Insights if it hasn't already been enabled. Open the agent playground and submit a test request that triggers the agent's response or tool invocation. Navigate to Observe > Traces (or the Traces view associated with your agent, depending on the portal experience). Select the latest interaction and expand its trace spans to inspect model invocations, tool calls, inputs, outputs, execution duration, and errors. Use the trace details to identify where failures or unexpected behavior occurred. 2. Evaluations Tracing helps us understand what happened. Evaluations help us determine whether the agent performed well. Microsoft Foundry Evaluations can assess the quality, safety, and reliability of agent interactions. For example, an organization can evaluate: Evaluation area What it checks Task completion Did the agent successfully complete the requested task? Tool selection Did it invoke the correct tool? Answer relevance Did it address the employee's request? Groundedness Was its response supported by retrieved information? Safety Did it follow the required safety boundaries? These evaluations can be performed during development and against production traces to identify recurring issues and improve agent behavior. Steps to evaluate agents in Microsoft Foundry The evaluation process is similar to the Model Evaluation workflow described in the previous section. The key difference is that, instead of selecting Model as the evaluation target, select Agent to evaluate the agent's responses and behavior. Follow the same steps to select your dataset, configure the appropriate evaluators, run the evaluation, and inspect the results. 3. Monitoring with Azure Monitor and Application Insights An agent's behavior needs to be monitored continuously after deployment. Microsoft Foundry integrates with Azure Monitor and Application Insights to provide visibility into operational and performance metrics. Organizations can monitor: Request volumes. Response latency. Token consumption. Failure rates. Agent execution performance. Quality and safety metrics where configured. For example, if the HR agent suddenly starts experiencing increased latency or a higher failure rate, monitoring helps engineering teams identify and investigate the issue. Organizations can also configure alerts to respond to operational or quality problems. Steps to evaluate monitor in Microsoft Foundry The monitoring process is similar to the workflow described in the previous section. The key difference is that, instead of monitoring model-level performance, the focus shifts to agent-level execution and behavior. 4. Decision and Audit Ledger This is where we introduce an additional application-level component. Foundry tracing provides technical execution visibility, but enterprises may also need a structured record of important business decisions and actions. This can be implemented as a decision or audit ledger within the application architecture. For example, whenever the agent creates an IT support ticket, the application can record: Audit field Example Interaction ID INT-10245 User identity Authenticated employee Agent version IT-Agent v1.2 Requested action Create IT ticket Authorization Approved Tool invoked CreateTicket API Execution result Successful Transaction reference INC-20451 Timestamp Execution timestamp This record can be stored in an appropriate enterprise audit datastore and integrated with the organization's existing logging and compliance systems. The important distinction is: Tracing captures how the agent executed a task. Evaluations measure whether the agent performed the task correctly. Monitoring identifies operational and behavioral issues. The audit ledger records important business actions, authorization outcomes, and transaction references. Microsoft Purview and other enterprise compliance tools can complement this architecture by providing additional data governance, auditing, and protection capabilities where configured. Steps to implement a Decision and Audit Ledger Unlike tracing and evaluations, Foundry does not provide a built-in business audit ledger. However, you can use Foundry's tool-calling capabilities along with Azure Storage Table to implement one. Implementing a Decision and Audit Ledger using Azure Storage Table An AI agent may interact with enterprise systems and execute business-critical actions, such as creating support tickets, approving requests or updating employee records. Organizations need a way to track these actions and establish accountability. For this demonstration, Azure Storage Table is used as a lightweight audit datastore. A Storage Account is created, followed by an AgentAuditLedger table to store details of agent-initiated business actions. A Python FastAPI backend acts as the application-level control layer. It receives the requested action, validates the user's authorization, executes the business operation and automatically writes an audit record to Azure Storage Table. Each record captures information such as the user's identity, agent version, requested action, authorization decision, tool invoked, execution result, transaction reference and timestamp. For the demonstration, an IT support ticket creation scenario is simulated. When an authorized employee requests a ticket, the backend executes the operation and records the successful transaction. Unauthorized requests are rejected and their authorization failures are also recorded. This demonstrates how an application-level audit ledger can provide traceability and accountability for actions performed through AI agents. Key takeaway: Microsoft Foundry provides the agent orchestration and tool-calling capabilities, while the application backend implements authorization, business-action execution and audit logging. Azure Storage Table provides the persistence layer for maintaining these records. Create an Azure Storage Account through the Azure portal. Navigate to Storage Browser > Tables and create a table named AgentAuditLedger. Define the audit record structure using fields such as Interaction ID, User Identity, Agent Version, Requested Action, Authorization, Tool Invoked, Execution Result, Transaction Reference, and Timestamp. Implement a backend using Python (FastAPI) to receive tool requests, validate user authorization, and execute the corresponding business action. The backend acts as the execution layer between the Microsoft Foundry agent and the enterprise systems. It receives tool requests, validates user authorization, executes the requested business operation, and automatically records the outcome for auditing. For this implementation, I developed a Python-based backend using FastAPI and the Azure Data Tables SDK. The implementation includes: API endpoint: Exposes a /create-ticket endpoint to receive requests from the agent. Authorization: Validates the requesting user's identity before executing the business operation. Business execution: Simulates IT ticket creation for authorized requests. Audit logging: Automatically records both successful and rejected requests in the Azure Storage Table AgentAuditLedger. Microsoft Entra authentication: Uses DefaultAzureCredential to securely authenticate the backend with Azure Storage. GitHub Repository: https://github.com/higopika/agent-audit-backend The repository contains the complete Python implementation, dependencies, and instructions to run and test the backend locally Run the backend locally, open the Swagger UI at 127.0.0.1:8000/docs, expand POST /create-ticket, and execute a request with user_identity and issue to confirm a 200 response with status: "Successful" and a generated ticket_id. Open Storage browser > Tables > AgentAuditLedger in the Azure portal to review the logged entities and confirm both Approved and Denied requests were recorded with their PartitionKey, RowKey, Timestamp, and Authorization outcome. Host the application in a web app in Azure App Service Instance. On the Deployment tab, enable Continuous deployment, connect the higopika/agent-audit-backend GitHub repository on the master branch. Enable the App Service's system-assigned managed identity and assign it the Storage Table Data Contributor role on the Storage Account through IAM. Configure your storage endpoint Name Value AZURE_STORAGE_TABLE_ENDPOINT https://YOUR_STORAGE_ACCOUNT.table.core.windows.net After deployment, the App Service overview confirms the app is live at its default domain (agent-audit-backend-34525-....azurewebsites.net), and browsing to /docs confirms the FastAPI /create-ticket endpoint is reachable and ready for testing. In Microsoft Foundry, create an agent and configure a custom function or tool (for example, CreateITTicket) that allows it to request business actions. In the IT-Governance-Agent playground, add a new tool, select OpenAPI as the tool type, name it CreateITTicket, create a new connection targeting the backend's /create-ticket endpoint, and paste the OpenAPI 3.0 schema to complete the tool configuration. { "openapi": "3.0.1", "info": { "title": "IT Ticket Management API", "version": "1.0.0", "description": "API for creating IT support tickets through the backend." }, "servers": [ { "url": "https://agent-audit-backend-34525-hbadaeame5hdhegb.centralindia-01.azurewebsites.net/" } ], "paths": { "/create-ticket": { "post": { "operationId": "create_ticket", "summary": "Create an IT support ticket", "description": "Submits an IT issue to the backend. The backend validates the user's authorization, creates a ticket if authorized, and records the outcome in Azure Storage for auditing.", "requestBody": { "required": true, "content": { "application/json": { "schema": { "type": "object", "properties": { "user_identity": { "type": "string", "description": "Email address of the employee requesting the ticket." }, "issue": { "type": "string", "description": "Description of the IT issue." } }, "required": [ "user_identity", "issue" ] } } } }, "responses": { "200": { "description": "Ticket created successfully", "content": { "application/json": { "schema": { "type": "object", "properties": { "status": { "type": "string" }, "ticket_id": { "type": "string" } } } } } }, "403": { "description": "User is not authorized" }, "422": { "description": "Invalid request" }, "500": { "description": "Internal server error" } } } } } } 7. Test the agent by triggering an action and verify that the corresponding audit record appears in the Azure Storage Table. Triggering an IT ticket request in the IT-Governance-Agent playground creates the ticket successfully, and the new entry appears immediately in the AgentAuditLedger table in Storage Browser with an Approved authorization outcome. Get Started Ready to apply these governance patterns to your own AI agents? Try it yourself Create and test a Guardrail in Microsoft Foundry. Build a Foundry IQ Knowledge Base and connect it to an agent. Experiment with Model Router to explore different model-routing strategies. Clone the audit ledger sample used in this article and adapt it to your own business-action workflow. Go deeper Guardrails and controls in Microsoft Foundry Configure Guardrails in Microsoft Foundry Foundry IQ overview Connect agents to Foundry IQ Model Router in Microsoft Foundry Monitor agents in Microsoft Foundry Decision and Audit Ledger sample Conclusion Building an enterprise AI agent is no longer just a question of what it can do. It's a question of what it's allowed to do, what it can trust, which model should answer, and whether every decision can be traced back and explained. The four governance layers covered here work together rather than in isolation. Constitutional governance defines the boundaries an agent must respect regardless of what it's asked. Knowledge governance ensures the agent draws only from trusted, access-controlled sources. Model governance balances capability, cost, and quality across the models an agent relies on. Decision governance closes the loop, making the agent's actions observable, evaluable, and auditable. Microsoft Foundry brings these layers together through Guardrails, Foundry IQ, the model catalogue and Model Router, Evaluations, and native tracing integrated with Azure Monitor. Where Foundry's built-in capabilities stop, such as a structured business audit ledger, an application-level component like the one demonstrated here with Azure Storage Table closes the gap. As agents take on more consequential, enterprise-critical work, governance can't be bolted on after deployment. It has to be designed into the architecture from the start, so every principle enforced, every source trusted, every model selected, and every action taken can withstand scrutiny.118Views0likes0CommentsFoundry IQ SharePoint (indexed) knowledge source is now generally available
At Ignite, the SharePoint (indexed) knowledge source in Foundry IQ is generally available. It brings SharePoint document libraries, lists, and pages into agent grounding, with SharePoint permissions applied at retrieval time. Semantic chunking, image descriptions, document-level access controls, private ingestion, and cross-tenant customer-managed keys are also now GA.115Views0likes0CommentsFrom Agents to Digital Coworkers with Foundry autonomous agents
We are already building agents that reason, retrieve knowledge, call tools, and execute multistep workflows. Some assist people directly. Others run in the background. Increasingly, multiple agents collaborate to get a job done. So what makes a Foundry autonomous agents different? Is it another form of automation? Another autonomous agent? An agent with more tools, better memory, or a task that runs longer? Those capabilities can exist in other agents too. "The more important shift is from an agent that performs work to a digital coworker with its own identity, a standing role in the organization, and a manager accountable for its operation." That changes more than what the agent can do. It changes the operating model around it. A different class, not just a more capable agent We often describe agents by how they are implemented: prompts, custom code, tools, skills, orchestration, models, or managed runtimes. We also describe them by what they can do: reason, plan, remember, retrieve information, use tools, or act autonomously. Foundry autonomous agents introduce another useful distinction: "Who is acting?" Microsoft Learn overview describes three agent types: Agent type Who acts? Where it fits Assistive agent An agent acting on behalf of a signed-in user, within that user's permissions Personal assistance, such as preparing a meeting brief Background service agent An agent using its own app-only permissions, without an agent user account Backend automation, such as responding to an infrastructure alert Foundry autonomous agents An agent with both an agent identity and an agent user account, acting as itself in Microsoft 365 A digital coworker coordinating work with a team These three agent types also represent different operating models for how agents participate in an organization. Autonomy alone does not define a Foundry autonomous agent. The more important distinction is that a Foundry autonomous agent can operate under its own organizational identity rather than inheriting a user's identity to perform its work. That distinction becomes particularly important when an agent moves from helping an individual complete a task to taking on an ongoing responsibility for a team. Its own place in the organization hierarchy Every Foundry agent has a Microsoft Entra agent identity. A Foundry autonomous agent additionally has an Entra agent user account. The two serve different purposes. The agent identity secures the infrastructure and resources used to run the Foundry autonomous agent. The agent user account gives the digital coworker its presence in Microsoft 365 and a place within the organization. This introduces a different collaboration model. Instead of interacting with software that always operates through someone else's identity, a team can work with a digital coworker under its own name. Authorized actions can be associated with that account rather than whichever teammate happens to be signed in. This is particularly valuable in two scenarios: Group work, where there is no obvious person whose identity the agent should borrow. Event-driven work, where the agent may need to respond even when no person is actively signed in. The important distinction is that this is not simply a background service with more automation. The Foundry autonomous agent becomes an organizational participant in Microsoft 365, with its own identity, defined responsibilities, and a manager accountable for its operation. Build once, hire multiple times The second major difference is the developer and deployment model. With Foundry autonomous agent, developers publish a blueprint that teams can use to create their own instances. Think of the blueprint as defining the digital role: Its purpose and instructions, Capabilities and tools, Expected behavior, Supporting platform infrastructure, And the technical boundaries within which its instances operate. Each hired instance then has its own identity, agent user account, assignment, and independently granted access. Imagine a Release Manager blueprint that knows how to track commitments, generate summaries, and work with project information. One team can hire an instance for its release work. Another can hire an instance for a different program. Both digital coworkers share the underlying implementation. They do not automatically share access to each other's business resources. Capability belongs to the blueprint. Business access belongs to the instance. That separation is essential. Adding a SharePoint tool does not automatically grant access to a SharePoint site. Likewise, administrative consent to an API capability does not, by itself, authorize access to every business resource behind it. This allows organizations to reuse a blueprint without hard-coding one team's projects, credentials, or data into the shared implementation. From an agent endpoint to a digital team member The third difference is how people work with the agent over time. A traditional agent experience often starts with an interaction: Ask a question. Invoke a workflow. Get a response. A digital coworker can instead have a standing responsibility that continues across individual interactions. Consider a digital Workstream Manager. Its job is not simply to answer questions about a project. Its responsibility might be to maintain visibility into commitments and outstanding work. A teammate asks it to track a proposal review. The digital coworker records the owner and expected date. Later, the manager asks what remains open, and the digital coworker prepares a workstream summary from the work it has been tracking. The reviewed Workstream Manager sample provides a concrete starting point for exploring this model: persistent work items, manager-controlled teammate access, on-demand summaries, and Microsoft 365 tools for authorized information sources. The important idea here is continuity of responsibility. Instead of treating every interaction as an isolated request, the digital coworker performs a defined role across the team's work. An agent can complete a request. A digital coworker can hold a bounded responsibility over time. Accountability Matters as Much as Autonomy Autonomy gets much of the attention in conversations about AI agents. But as agents become organizational participants, accountability becomes equally important. The Foundry autonomous agent makes this operating model explicit. Different organizational roles participate at different stages: Developers build, publish, and evolve the blueprint and its agent behavior. Azure administrators help provision and govern the supporting Azure resources. Identity and Microsoft 365 administrators review the permissions and organizational access the agents require. Hiring managers hire and onboard instances for their teams. Managers oversee those instances within their assigned responsibilities. Tenant administrators and security teams maintain governance across the broader agent estate. Onboarding establishes the practical boundaries of a particular digital coworker: who can interact with it, which conversations or events it responds to, whom it can communicate with, which resources it can access, and which information sources can ground its work. The manager then oversees that instance while developers continue improving the shared blueprint and administrators govern the broader fleet. This is more than assigning an owner to a software deployment. The manager is accountable for whether the digital coworker should continue performing its role, whether its scope should change, and when it should stop operating. That leads to an important design principle: Autonomy should increase only when identity, authorization, observability, and accountability increase with it. Building the Coworker Is Only Half the Architecture Microsoft Foundry provides the pro-code path for building the behavior of these digital coworkers: custom agent logic, model integration, tools, persistence, orchestration, and evaluation. But building the agent is only part of the architecture. Enterprise adoption also requires controls around identity, permissions, inventory, security, compliance, monitoring, and lifecycle management. Microsoft Agent 365 complements the development model by providing enterprise controls around the agent estate and integrating with capabilities across Microsoft Entra, Defender, and Purview. This distinction matters because designing an effective digital coworker is not only about deciding what it can do. We also need to determine: Who it is, What it can access, Who manages it, Where it can operate, How its activity is observed, and when its authority should end. Network isolation, permissions, data boundaries, telemetry, evaluation, and lifecycle controls therefore become architectural concerns, not afterthoughts. The goal is to control not only how the digital coworker works, but also where, for whom, and under whose authority it works. Start With a Role, Not with Autonomy Foundry autonomous agent can support individuals, teams, and broader organizational processes. But organizations should not start by asking: How autonomous can we make this agent? A more useful question is: What responsibility could we give a digital coworker that has a clear purpose, bounded access, measurable outcomes, and a named manager? Start with one role. Give it explicit responsibilities. Define what it can and cannot access. Determine what requires human approval. Establish how its manager will observe, coach, and eventually offboard it. Then expand its responsibilities and autonomy as confidence grows. The move from agents to digital coworkers is not about making every agent autonomous. It is about giving the right agents a defined identity, a bounded responsibility, and a place in how an organization gets work done. Get Started If you are exploring Foundry autonomous agent, a practical path is: 1. Clone the repository and open the sample folder. These PowerShell commands select the source snapshot reviewed for this article: git clone https://github.com/microsoft-foundry/foundry-samples.git Set-Location foundry-samples git checkout f960ccb05b003fa274e9b5903f9d39ac1228eb65 Set-Location samples\python\autopilot-agents\hello-world Follow the Hello World README for Python 3.11 or later locally, PowerShell 7, Azure CLI 2.80 or later, Azure Developer CLI 1.32 or later, and the azure.ai.agents extension 1.0.0-beta.16 or later. The declared hosted runtime is Python 3.13. Keep the parent autopilot-agents\scripts directory: provisioning and session updates use shared helpers. Before provisioning, confirm a supported hosted-agent region, a Responses-compatible model with quota, resource-management permissions, and Foundry project access. Arrange a tenant administrator for blueprint approval. Sign-in and provisioning do not grant the developer missing permissions; Microsoft 365 licensing and tenant app policies are separate items that would need to be addressed. 2. Define the behavior in Python In Hello World's agent\app.py, the message handler calls the configured model through the Foundry project. This is an excerpt from its existing respond function, not a standalone application: if context.activity.text: response = await project.get_openai_client().responses.create( model=os.environ["AZURE_AI_MODEL_DEPLOYMENT_NAME"], input=context.activity.text, ) await send_reply(context, response.output_text) The same file constructs ActivityAgentServerHost with digital_worker=True and registers the Teams handlers. The preview SDK provides the activity-message endpoint, readiness endpoint, hosting, and storage lifecycle. Setting that flag selects the Autopilot identity model; it does not define a useful role or grant business-data access. For richer behavior, the sibling samples separate the responsibilities: File, relative to autonomous agents What it implements hello-world\agent\activity_routing.py Selects supported direct, group, and tagged channel messages foundry-toolbox\agent\toolbox.py Discovers and validates allowed tools; uses Microsoft Agent Framework to handle model-selected calls meeting-assistant\agent\app.py Registers meeting handlers and obtains Work IQ tokens using agent-user authorization meeting-assistant\agent\meeting_lifecycle.py Coordinates meeting start, end, transcript readiness, and persisted occurrence state meeting-assistant\agent\meeting_analysis.py Extracts explicit agenda items and validates structured closure classifications and evidence references 3. Separate deployment configuration from tool configuration Deployment and tool definitions have different jobs. Hello World's azure.yaml describes the hosted service and Microsoft 365 publication. Selected fields are shown below; retain the complete source file when deploying: services: hello-world-autopilot: host: azure.ai.agent project: . language: python codeConfiguration: runtime: python_3_13 entryPoint: main.py kind: hosted protocols: - protocol: activity version: 2.0.0 activity: digitalWorkerType: m365 publish: publishScope: tenant canRespondWithoutMention: true appVersion: 1.0.0 agentDisplayName: Hello World Autopilot The full file includes descriptions, developer and privacy URLs, environment settings, and resource sizing. Review the publication metadata before using it for your organization. canRespondWithoutMention is a publication setting, not a replacement for routing logic: Hello World still requires mentions for channel messages. For a concrete tool manifest, Foundry Toolbox supplies this separate toolbox.yaml: name: public-docs description: Microsoft Learn documentation and Bing-backed public web search. tools: - type: mcp server_label: learn server_url: https://learn.microsoft.com/api/mcp allowed_tools: - microsoft_docs_search - microsoft_docs_fetch - microsoft_code_sample_search require_approval: never - type: web_search name: web_search description: Search the public web for current information with source links. Microsoft Agent Framework discovers those functions and handles model-selected calls. The sample validates a read-only tool allowlist; require_approval: never is specific to this public-information example, not a recommendation for tools that write or access sensitive data. When deploying that sibling sample, follow its README to install azure.ai.toolboxes, create public-docs from toolbox.yaml, and save its MCP endpoint as TOOLBOX_ENDPOINT before azd deploy. Merely adding the YAML file does not create or connect a Toolbox. Public Web Search incurs additional charges and has separate data-handling boundaries; use public questions only. Meeting Assistant uses a different connection: Work IQ MCP, with the delegated WorkIQAgent.Ask permission declared in its azure.yaml and agent-user authorization configured at runtime. Follow its README for the newer agent extension requirement, 1.0.0-beta.18 or later, and a model supporting structured outputs. It also needs tenant consent, transcript API access, applicable licensing, and a Work IQ spending policy. 4. Package and deploy the Python code directly After completing the Hello World README's setup, run the following from its folder containing azure.yaml: $tenantId = "<tenant-id>" az login --tenant $tenantId azd auth login --tenant-id $tenantId azd env new my-hello-world azd provision azd deploy azd ai agent show This agent will also show up in Microsoft Foundry Portal 5. Publish the blueprint, then approve and hire an instance Review Hello World's activity.publish metadata, then submit the deployed agent to Microsoft 365: azd ai agent publish Deployment, publication, approval, and hiring are separate steps. An AI Administrator or Global Administrator approves the requested blueprint in the Microsoft 365 admin center and verifies its presence in the Agent 365 registry. A licensed user can then create an instance in Teams through Apps > Agents for your team, subject to tenant app policies. For Hello World, start with a direct message: "Say hello and tell me what you can help with." Check group-chat delivery and tagged channel messages separately. For Meeting Assistant, use synthetic meeting data to check agenda extraction, event delivery, transcript access, and evidence quality; its behavior is not a Hello World feature. For code-only changes, run azd deploy again. Existing sessions can remain on an older sandbox; the sample provides an explicit update helper: References New to autonomous agent? Start with the overview. Focus on the identity model and the distinction between a reusable blueprint and a hired instance. Ready to build? Start with the Python Hello World walkthrough. Deploy the code, inspect the hosted agent in Foundry, publish the blueprint, obtain approval, and create an instance in Teams. Then choose Foundry Toolbox for public-information grounding or Meeting Assistant for an event-driven team responsibility. Use each sample's own README and configuration together; their tools and prerequisites differ. Planning governance? Review the lifecycle and Agent 365 integration guide. Identify the Azure administrator, developer, tenant approver, and instance manager before deployment. Check current regional support, permissions, and licensing; the autonomous agent quickstart currently requires Frontier enrollment and an available Agent 365 Frontier license for each hired instance. What is an autopilot in Microsoft Foundry? - agent types, identity, blueprints, and collaboration patterns. Autopilot lifecycle in Microsoft Foundry - roles, hiring, onboarding, and accountability. Microsoft Agent 365 integration with Foundry - governance integration and hosted-agent telemetry requirements. Microsoft Agent 365 overview - product name, capabilities, and current product availability. Build your first autopilot - current prerequisites and documented publishing flow. foundry-samples/samples/python/foundry-autopilot-agent at main · microsoft-foundry/foundry-samples Happy Reading!50Views0likes0CommentsMicrosoft Retriever 1 brings sub-second agentic retrieval to Foundry IQ
Microsoft Retriever 1 is an agentic search model trained by Microsoft and now in preview in Foundry IQ. It cuts typical knowledge base retrieval latency by more than 6x, raises search evidence recall by 8–11 points, and lets agents use a third fewer input tokens. It needs no provisioning or reindexing.330Views1like1Comment