Uploaded August 2026 | Updated September 2026, 2 weeks ago
An enterprise agent becomes genuinely useful when it can act on business systems. It also becomes significantly more dangerous if those integrations are not governed correctly.
In this session, we will connect our Microsoft Foundry agent to real enterprise capabilities using Azure API Management, Azure Logic Apps, Azure Functions, Azure Service Bus, OpenAPI tools, and Model Context Protocol servers.
The agent will create an incident ticket, initiate an approval workflow, invoke a protected business API, submit a long-running remediation command, and report the final result back to the user. Rather than allowing the model direct access to backend systems, we will introduce a governed integration layer with typed tool contracts, authentication, authorization, rate limiting, schema validation, retries, and centralized logging.
We will also compare the roles of OpenAPI tools, MCP servers, Logic Apps actions, Azure Functions, and asynchronous messaging. Managed identities and Microsoft Entra ID will be used to eliminate embedded API keys and apply least-privilege access across the solution.
By the end of the session, attendees will understand how to give agents meaningful enterprise capabilities without bypassing security, integration governance, or operational controls. Key topics: Microsoft Foundry tools OpenAPI and Model Context Protocol Azure API Management as an AI gateway Azure Logic Apps agent actions Azure Functions Azure Service Bus Managed identity and Microsoft Entra ID Secure and asynchronous tool execution.
----------------------------------------------------------------------------
This session is a part of a series, learn more here! [https://aka.ms/ProBadgeSeries-TY](https://aka.ms/ProBadgeSeries-TY)
[eventID:27509]
An enterprise agent becomes genuinely useful when it can act on business systems. It also becomes significantly more dangerous if those integrations are not governed correctly.
In this session, we will connect our Microsoft Foundry agent to real enterprise capabilities using Azure API Management, Azure Logic Apps, Azure Functions, Azure Service Bus, OpenAPI tools, and Model Context Protocol servers.
The agent will create an incident ticket, initiate an approval workflow, invoke a protected business API, submit a long-running remediation command, and report the final result back to the user. Rather than allowing the model direct access to backend systems, we will introduce a governed integration layer with typed tool contracts, authentication, authorization, rate limiting, schema validation, retries, and centralized logging.
We will also compare the roles of OpenAPI tools, MCP servers, Logic Apps actions, Azure Functions, and asynchronous messaging. Managed identities and Microsoft Entra ID will be used to eliminate embedded API keys and apply least-privilege access across the solution.
By the end of the session, attendees will understand how to give agents meaningful enterprise capabilities without bypassing security, integration governance, or operational controls. Key topics: Microsoft Foundry tools OpenAPI and Model Context Protocol Azure API Management as an AI gateway Azure Logic Apps agent actions Azure Functions Azure Service Bus Managed identity and Microsoft Entra ID Secure and asynchronous tool execution.
----------------------------------------------------------------------------
This session is a part of a series, learn more here! [https://aka.ms/ProBadgeSeries-TY](https://aka.ms/ProBadgeSeries-TY)
[eventID:27509]
