Getting Started with Copilot Studio: Your PAA & FAQ Guide
What is Microsoft Copilot Studio? Microsoft Copilot Studio is a low-code, graphical tool within the Power Platform used for building and conversational bots. It empowers users, even those without extensive technical backgrounds, to create sophisticated logic and connect to various data sources and services using prebuilt or custom plugins. Is Copilot Studio easy to use for beginners? Yes Copilot Studio is designed to be easy for beginners. You only need to describe the agent you want in plain language to start creating it. The platform uses a graphical, low-code interface that streamlines the process of defining instructions, knowledge sources (like documents), and conversation triggers, making it accessible to most users. What is the difference between Microsoft 365 Copilot and Copilot Studio? Microsoft 365 Copilot is an AI assistant that integrates across Microsoft 365 apps (Word, Excel, Teams, etc.) to enhance productivity. Copilot Studio, conversely, is a development platform used to build customised AI agents that are tailored to specific business goals or data sources. Copilot is the agent you use; Copilot Studio is the tool you use to build or extend agents. Do end-users need a specific license to use a Copilot I create? Yes, licensing for end-users depends on how and where the custom copilot is deployed. While development often requires a Power Platform or Azure subscription deploying the bot across an organization may require specific Copilot licenses for the end-users accessing the agent. Check the official Microsoft licensing documentation for your specific scenario. How can I add SharePoint data as a knowledge source for my Copilot? You can connect your Copilot agent to SharePoint data using the generative answers feature in Copilot Studio. The agent can search documents stored in a SharePoint document library. Be aware that there can sometimes be nuances with how attachments versus core document libraries are indexed, which the community is actively discussing in the forums. We hope this formatted FAQ helps you quickly find the information you need! If you have more questions, please use the discussion board to connect with the community.Introducing Microsoft Agent Factory
Microsoft Agent Factory is a new program designed for organizations that want to move from experimentation to execution faster. With a single plan, organizations can build agents with Work IQ, Fabric IQ, and Foundry IQ using Microsoft Foundry and Copilot Studio. They can also deploy their agents anywhere, including Microsoft 365 Copilot, with no upfront licensing and provisioning required. Eligible organizations can also tap into hands-on engagement from top AI Forward Deployed Engineers (FDEs) and access tailored role-based training to boost AI fluency across teams.ESPC25 – Dublin | Microsoft event guide
ESPC25 | Come curious. Leave inspired. European SharePoint Conference 2025 | Dublin, Ireland | December 1–4, 2025 | SharePointEurope.com. Your guide to ESPC25 Dublin, Ireland, is one of the most dynamic and innovative tech cities in Europe, making it the perfect place for in-person, in-depth learning at the European SharePoint Conference—now simply branded as ESPC25—December 1–4, 2025. As the celebrated Irish writer Edna O’Brien once said, “Hospitality is the cornerstone of the Irish heart.” This spirit of warmth and welcome is sure to be felt throughout your stay in Dublin during ESPC25. You will have the opportunity to learn from experts, network with peers, and discover new technologies that can help you achieve your goals. The event and city have something for everyone: inspiring keynotes, in-depth sessions and workshops, community, art and culture, and many festive moments. Explore powerful new AI capabilities for every role and function: Diving into Microsoft 365, Microsoft 365 Copilot, Power Platform, and more, you’ll discover how Microsoft is transforming the way we work today—and get a firsthand look at the future of work itself. You’ll find content delivered by the world’s best Microsoft 365 and Copilot Studio experts, including many Microsoft leaders and employees from the product teams. In this pre-event guide, we list all the Microsoft-led sessions below so you can prepare for what awaits you alongside community and MVP expert sessions. There will be plenty of opportunities for you to learn, share, and engage: Evening gatherings, the attendee party, and our Innovation Hub with Microsoft product demo stations, a Promptathon, Vibe Coding, a place to network with your peers, a dedicated community space, the Inspire Stage, and 1:1 meeting spaces are all within the Expo Hall alongside all the wonderful event sponsors. The 101 on ESPC25 What: ESPC25 Where: The Convention Centre Dublin, Spencer Dock, North Wall Quay, Dublin 1 D01 T1W6, Ireland When: December 1-4, 2025 (keynotes, sessions, tutorials, workshops, and more) Presenters: 120+ sessions (35+ Microsoft-led), 115+ speakers (MVPs, RDs, Microsoft and community members); check out Microsoft-led keynotes, tutorials, and sessions Cost: From €695 + VAT (one day) to €1645 + VAT (four day) Enjoy an additional €200 discount with our exclusive community discount code: ESPC25COMM Primary social: Join in and follow @ESPC_Community (Twitter) and ESPC (LinkedIn); use hashtag #ESPC25 About ESPC ESPC25 offers you affordable, world-class learning and networking at your fingertips. Join in 120+ sessions covering: Microsoft 365 Copilot, Copilot Studio, AI and agents, SharePoint, Microsoft Viva, Microsoft Teams, Microsoft 365 adoption, governance, admin, intranets, and more. Over the years, ESPC has visited some of the most incredible cities: from the charming streets of Copenhagen and the historic beauty of Berlin to the vibrant culture of Prague, and the dynamic atmosphere of Amsterdam. Even during the COVID-19 pandemic, ESPC kept the excitement alive with engaging online events! The European SharePoint Conference (ESPC), now known simply as ESPC, is one of the largest and most prominent events in Europe dedicated to Microsoft technologies, particularly Microsoft 365 and Azure. It began in 2011 in Berlin, Germany, as a platform for discussing SharePoint and related Microsoft technologies. Over the years, ESPC expanded its scope to include other tools in the Microsoft ecosystem, reflecting the industry's trend toward digital transformation and cloud adoption. ESPC has grown to become the largest independent European event for Microsoft technology users, serving as a crucial knowledge hub and networking space. It continues to play a vital role in educating the tech community on best practices for using SharePoint, Microsoft 365, and Azure to enhance productivity, collaboration, and security in the modern workplace. Review past ESPC events: 2025: Dublin, Ireland 2024: Stockholm, Sweden 2023: Amsterdam, Netherlands 2022: Copenhagen, Denmark 2021: Online (due to COVID-19) 2020: Online (due to COVID-19) 2019: Prague, Czech Republic 2018: Copenhagen, Denmark 2017: Dublin, Ireland 2016: Vienna, Austria 2015: Stockholm, Sweden Review all Microsoft keynotes and sessions below: Start building your schedule today! Microsoft keynotes (All times represented in local Dublin time) Opening keynote: The New Frontier of Work: Copilot, AI, and the Future of Microsoft 365 Jeff Teper, President of Collaborative Apps and Platforms , Microsoft with Miceile Barrett, Zach Rosenfield, Alex Weingard, and Michel Bouman Tuesday, Dec. 2, 9:00–10:00 AM Day one PM keynote: From One to Many: The future of AI is Collaborative Jaime Teevan, Chief Scientist and Technical Fellow, Microsoft Tuesday, Dec. 2, 2:00–3:00 PM Day three keynote: Beyond the Prompt: Building an AI-Resilient Career with Power Skills Heather Cook, Principal Customer Experience PM, Microsoft Karuana Gatimu, Director, Customer Advocacy, Microsoft 365, AI and Agents Thursday, Dec. 4, 9:00–10:00 AM Community keynotes Will AI Become Intelligent? Rafal Lukawiecki, Data Scientist at Tecflix, Ireland Wednesday, Dec. 3, 9:00–10:00 AM Hacker’s Perspective on New Risks: Revising the Cybersecurity Priorities for 2025 Paula Januszkiewicz, Founder and CEO, CQURE Inc. and CQURE Academy Tuesday, Dec. 2, 4:45–5:45 PM Microsoft sessions (All times represented in local Dublin time) Breakout sessions: (60 min, in-person) Latest Innovations in Microsoft 365 Copilot Chat Speaker: Connie Welsh, Bryan Wofford Tuesday, December 2, 2025, 10:15 AM | Session Code T8 What’s new in Copilot Studio Speaker: Antonio Rodriques Tuesday, December 2, 10:15 AM | Session Code T9 SharePoint as the Intelligence Backbone of Copilot Speaker: Zach Rosenfield Tuesday, December 2, 11:45 AM | Session Code T18 IT Excellence in the AI era: Managing Copilot and Agents for Impact and Control Speaker: Ben Summers Tuesday, December 2, 3:15 PM | Session Code T26 AI in Action: Microsoft's Approach to Internal Communications Speakers: Adam Barzel, Anna Pope, Darina Sexton Tuesday, December 2, 3:15 PM | Session Code T27 Woman in Tech & Allies Panel Speaker: Heather Cook, Danielle Moon and Karuana Gatimu Tuesday, December 2, 3:15 PM | Session Code T28 Microsoft Teams: What's New and What's Next Speaker: Alex Weingart Wednesday, December 3, 10:15 AM | Session Code W8 MCP (Model Context Protocol) in action in Microsoft 365 Copilot Speaker: Paolo Pialorsi Wednesday, December 3, 10:15 AM | Session Code W9 Microsoft Teams as Your AI-Driven Work Hub Speaker: Kartik Datwani Wednesday, December 3, 10:15 AM | Session Code W18 Building Intelligent Content Apps for the Copilot Era Speakers: Steve Pucelik, Shreyas Saravanan Wednesday, December 3, 2:00 PM | Session Code W27 OneDrive Updates: Smarter Storage, Seamless Sharing Speakers: Miceile Barrett, Lincoln DeMaris, and Jason Moore Wednesday, December 3, 2:00 PM | Session Code W28 AI Intranet: Creating and Managing High Quality Content on the Intranet of Tomorrow Speaker: Katelyn Helms Wednesday, December 3, 2:00 PM | Session Code W30 AI-Enhanced Planning: Innovations in Planner & Project Manager Agents Speaker: Howard Crow Wednesday, December 3, 3:15 PM | Session Code W38 AI Risk Management: From Oversharing to Strategic Oversight Speakers: Gabriel Tiberiu Damaschin, Nishan DeSilva Wednesday, December 3, 4:45 PM | Session Code W45 Streamlining Core Operations with AI Automation Speaker: Antonio Rodriques Wednesday, December 3, 4:45 PM | Session Code W44 Understanding Copilot Extensibility: a practical guide Speakers: Vesa Juvonen and Paolo Pialorsi Thursday, December 4 ,10:15 AM | Session Code TH8 Agents Among Us – Governance for the Agentic Era Speaker: Sesha Mani Thursday, December 4 ,10:15 AM | Session Code TH 9 Creating AI Agents for People and Platforms Speaker: Nandakishor Basavanthappa Thursday, December 4, 11:45 AM | Session Code TH14 Windows AI: Powering Progress Across the Globe Speaker: Vikas Malekar Thursday, December 4 ,11:45 AM | Session Code TH15 Accelerating Copilot Adoption Across Your Organization Speakers: Karuana Gatimu, Bryan Wofford Thursday, December 4, 11:45 AM | Session Code TH16 True Stories of Copilot in Action Speakers: Connie Welsh, Danielle Moon Thursday, December 4, 2:00 PM | Session Code TH 28 Fireside Insights: Driving Value and Business Growth with AI Speaker: TBA Thursday December 4 15:15 | Session Code TH37 Lightning talks (20 minutes, in person) - Innovation Hub Supercharge Your Projects with Microsoft 365 Community Tools Speaker: Vesa Juvonen Tuesday, December 2, 10:15 AM Building Copilot with community-led engagement Speaker: Anna Pope Tuesday, December 2, 10:40 AM Managing your brand for career management Speaker: Karuana Gatimu (MCAG) Tuesday, December 2, 11:45 AM Empowering Community Builders: MGCI & Communitydays.org Speaker: Heather Cook Tuesday, December 2, 12:05 PM Your Day, Your Way: Personalized AI with OneDrive Speaker: Miceile Barrett Tuesday, December 2, 12:30 PM Security First Powering AI Transformation Speaker: Sesha Mani Tuesday, December 2, 4:45 PM Unlocking SharePoint Advanced Management for Copilot Success Speaker: Michael Holste Tuesday, December 2, 5:10 PM Fast-Tracking Value with the Copilot Success Kit & Scenario Library Speaker: Bryan Wofford Wednesday, December 3, 10:15 AM How to find learning Opportunities Everywhere Speaker: Adam Harmetz Wednesday, December 3, 10:40 AM Copilot readiness & resiliency with Microsoft 365 Backup & Archive Speaker: Kaustubh Chaudhary, Michael Holste Wednesday, December 3, 12:05 PM Unlock SharePoint Embedded integration with Power Platform Connectors Speaker: Steve Pucelik Thursday, December 4, 10:15 AM Microsoft Teams: Day-to-Day AI Speaker: Alex Weingart Thursday, December 4, 10:40 AM Driving Business Value with Copilot Analytics and ROI Measurement Speaker: Manas Kumar Biswas Thursday, December 4,11:45 AM Understanding Copilot APIs Speaker: Paolo Pialori Thursday, December 4, 12:05 PM Migration in Motion: Simplify, Secure, and Scale with Microsoft 365 Speaker: Manas Vishal Lodha Thursday, December 4, 12:30 PM Inspire Track (60 minutes, in person) - Inspire Stage Good Thing We Like Our Copilots CANCELLED: How Your Job Will Evolve in 2026 into AGENTBOSS! Speaker: Dona Sarkar Tuesday, December 2, 10:15 AM | Session Code: Inspire 2 How To Thrive in Your Tech Career: Managing Burnout and Boredom Speaker: Adam Harmetz Wednesday, December 3, 11:45 AM | Session Code: Inspire 6 Managing your brand for career management Speaker: Karuana Gatimu Thursday, December 4, 11:45 AM | Session Code: Inspire 10 Cultivating Trust and Leadership Excellence through Mentorship and Leadership Speaker: Heather Cook Thursday, December 4, 2:00 PM | Session Code: Inspire 11 Innovation Hub and Lightning Talk Theater The Microsoft Innovation Hub at ESPC is a vibrant, multi-zone environment crafted to ignite new ideas, showcase cutting-edge prototypes, and shape the future of Microsoft 365 and Microsoft 365 Copilot. Here, creativity and technology intersect, providing a dedicated space for developers, architects, consultants, and strategists to explore the forefront of innovation. The Innovation Hub is designed to foster collaboration, highlight emerging technologies, and collect real-time insights from the wider Microsoft 365 community. You can meet with Microsoft Product Team members and Microsoft MVPs! You’ll find the Microsoft Innovation Hub in the ESPC Expo Tuesday through Thursday. Each day on the Innovation Stage in Zone 1 you will find Lightning Talks for live demonstrations and peer learning in a compact format. And don't miss the SharePoint 25th Birthday Celebration and the Innovation Awards, Tuesday evening at 5:45 PM. Within Zone 2, you will find Future Tech Demos daily during breaks and lunches. The Microsoft team and MVPs will be on hand to walk you through dynamic demos: Agents/Copilot Studio, Developer, Microsoft 365 Copilot and SharePoint and One Drive. Get connected in the Zone 3 Feedback Loop Lounge and leave your thoughts on our survey for a chance to win daily prizes. And finally, meet in the Zone 4 Ideation Lounge each afternoon for guided workshops including a Promptathon and Vibe Coding activities in an environment specifically designed to encourage creativity and collaborative thinking. This event guide will continue to update as we finalize more of our activations. Stay tuned! Shout out to event leads and community members Sarah McNamara, Kevin Monahan, Ella Murphy, Bridgette Robertson, John, and Sarah G, and the #ESPC25 team for putting together ESPC25, corralling all speakers and content, and for supporting and promoting the knowledge and expertise to promote the world-class Microsoft 365 tech community around the world. Cheers, Heather Last, a glimpse of the ESPC event experience:Who Can Start Discussions On The Copilot Studio User Group?
This Post Is About Who Can Post On The Copilot Studio User Group It Is For Members That Want To Know Who Can Start Discussions On The Copilot Studio User Group Who Can Start Discussions On The Copilot Studio User Group? Group Members That Have Joined The Copilot Studio User Group Can Post About Copilot Studio & Ask Questions About Copilot Studio & Even Discuss About Copilot Studio
Problem Exporting Copilot with Custom Connection
I have a clean environment in which I have created a single solution, "Xero4Copilot", that contains a single agent "Executive Summary". This agent uses a Custom Connector "Odatalink_report", which is created from a tested Swagger file. The Agent uses two endpoints from the connector as tools. The Agent is using the tools well, with no configuration errors. I wanted to clarify the problem before calling for help, hence the clean install and intro. When I export the solution, I get a failure, the GUI gives the same answer, this is the output from PAC CLI: PS C:\Users\mike\Downloads> pac solution export -n Xero4Copilot Connected as email address removed for privacy reasons Connected to... Xero4CopilotDev Starting Solution Export... Microsoft PowerPlatform CLI Version: 1.50.1+gabb74d2 (.NET Framework 4.8.9221.0) Online documentation: https://aka.ms/PowerPlatformCLI Feedback, Suggestions, Issues: https://github.com/microsoft/powerplatform-build-tools/discussions Error: Exporting connection reference mike_executiveSummary.shared_mike-5fodatalink-5freport-5f24577e437a5ff0b6.a4cd806a-ef0b-4680-acf3-34e5b779930f for a custom connector requires the custom connector to be added to a dataverse solution. Please add connector shared_mike-5fodatalink-5freport-5f24577e437a5ff0b6 to a solution and retry. I've tried various adds of components, but this does not really seem to be the problem. I have reduced the problem to a single area of interest: I was wondering if I need to register that Custom Connector or add some metadata. Any thoughts on how to resolve this problem? I've decided to call it a problem and see if it is an issue, haha! TIA MikeWelcome to the Copilot Studio User Group!
🚀 About This Community The Copilot Studio User Group is a virtual community where members share knowledge, experiences, and ideas about using and building with Microsoft Copilot Studio. Our goal is to make Copilot Studio more accessible, collaborative, and fun for everyone — whether you’re experimenting with AI copilots or running automation in your organization. 💡What We’ll Be Doing Here’s what you can expect from our group: 💬 Virtual Chat Events: Join topics-based sessions where members discuss Copilot Studio best practices. 🧩 Community Projects: Collaborate on creative experiments and prototypes. 📢Feature Updates: Stay informed on the latest Microsoft Copilot news. 🤝Member Spotlights: Learn from other community builders and share your own work. 🌍 Why Join Our Events Each virtual event is designed to be interactive you’ll be able to: Ask questions live in chat. Exchange use cases and demos. Network with fellow makers and technologists. Get inspired by what others are building! 🧰 Resources & Tools Here are some links to help you get started: Microsoft Copilot Studio Official Site Copilot Documentation Join The Microsoft Tech Community 💬 Get Involved We’d love your participation! Here’s how to engage: Comment on posts and share your insights. Participate in our chat-based virtual sessions. Share your own tutorials, blog posts, or project ideas with the group. 🌟 Our Commitment This user group follows all Microsoft Tech Community Standards, and Terms Of Use. Our focus is collaboration, inclusion, and respectful discussion. 🙌 Final Note Whether you’re new to Copilot Studio or a seasoned pro, you belong here. let’s build the future of AI collaboration — together.Deployment Guide-Copilot Studio agent with MCP Server exposed by API Management using OAuth 2.0
Introduction In today’s enterprise landscape, enabling AI agents to interact with backend systems securely and at scale is critical. By exposing MCP servers through Azure API Management (APIM), organizations can provide controlled access to these services. When combined with OAuth 2.0 authorization code flow, this setup ensures robust, enterprise-grade security for AI agents built in Copilot Studio—empowering intelligent automation while maintaining strict access governance. Disclaimer & Caveats This article explores how to configure a MCP tool—exposed as a MCP server via APIM—for secure consumption by AI agents built in Copilot Studio. Leveraging the OAuth 2.0 Authorization Code Flow, this setup ensures enterprise-grade security by enabling delegated access without exposing user credentials. With Azure API Management now supporting MCP server capabilities in public preview, developers can expose REST APIs as MCP tools using a standardized JSON-RPC interface. This allows AI agents to invoke backend services securely and scalable, without the need to rebuild existing APIs. Copilot Studio, also in preview for MCP integration, empowers organizations to orchestrate intelligent agents that interact with these tools in real time. While this guide provides a foundational approach, every environment is unique. You can enhance security further by implementing app roles, conditional access policies, and extending your integration logic with custom Python code for advanced scenarios. ⚠️ Note: Both MCP server support in APIM and MCP tool integration in Copilot Studio are currently in public preview. As these platforms evolve rapidly, expect changes and improvements over time. Always refer to the https://learn.microsoft.com/en-us/azure/api-management/export-rest-mcp-server for the latest updates. This article is about consuming remote MCP servers. In Azure, managed identity can also be leveraged for APIM integration. What is Authorization Code Flow? The Authorization Code Flow is designed for applications that can securely store a client secret (like server-side apps). It allows the app to obtain an access token on behalf of the user without exposing their credentials. This flow uses an intermediate authorization code to exchange for tokens, adding an extra layer of security. Steps in the Flow User Authentication The user is redirected to the Authorization Server (In this case: Azure AD) to log in and grant consent. Authorization Code Issued After successful login, the Authorization Server sends an authorization code to the app via the redirect URI. Token Exchange The app sends the authorization code (plus client credentials) to the Token Endpoint to get: Access Token (for API calls) and Refresh Token (to renew access without user interaction) API Access The app uses the Access Token to call protected resources. Below diagram shows the Authorization code flow in detail. Press enter or click to view image in full size Microsoft identity platform and OAuth 2.0 authorization code flow — Microsoft identity platform | Microsoft Learn High Level Architecture Press enter or click to view image in full size This architecture can also be implemented with APIM backend app registration only. However, stay cautious in configuring redirect URIs appropriately. Remote MCP Servers using APIM Architecture APIM exposing Remote MCP servers, enabling AI agents—such as those built in Copilot Studio—to securely access backend services using standardized JSON-RPC interfaces. This integration offers a robust, scalable, and secure way to connect AI tools with enterprise APIs. Key Capabilities: Secure Gateway: APIM acts as an intelligent gateway, handling OAuth 2.0 Authorization Code Flow, authentication, and request routing. Monitoring & Observability: Integration with Azure Log Analytics and Application Insights enables deep visibility into API usage, performance, and errors. Policy Enforcement: APIM’s policy engine allows for custom rules, including token validation, header manipulation, and response transformation. Rate Limiting & Throttling: Built-in support for rate limits, quotas, and IP filtering helps protect backend services from abuse and ensures fair usage. Managed Identity & Entra ID: Secure service-to-service communication is enabled via system-assigned and user-assigned managed identities, with Entra ID handling identity and access management. Flexible Deployment: MCP servers can be hosted in Azure Functions, App Services, or Container Apps, and exposed via APIM with minimal changes to existing APIs. To learn more, visit https://learn.microsoft.com/en-us/samples/azure-samples/remote-mcp-apim-functions-python/remote-mcp-apim-functions-python/ Develop MCP server in VS Code This deployment guide provides sample MCP code written in python for ease of use. It is available on the following GitHub repo. However, you can also use your own MCP server. Clone the following repository and open in VS Code. git clone https://github.com/mafzal786/mcp-server.git Run the following to execute it locally. cd mcp-server uv venv uv sync uv run mcpserver.py Deploy MCP Server as Azure Container App In this deployment guide, MCP server is deployed in Azure Container App. It can also be deployed as Azure App service. Deploy the MCP server in Azure container App by running the following command. It can be deployed by many other various ways such as via VS Code or CI/CD pipeline. AZ Cli is used for simplicity. az containerapp up \ --resource-group <RESOURCE_GROUP_NAME> \ --name streamable-mcp-server2 \ --environment mcp \ --location <REGION> \ --source . Configure Authentication for Azure Container App 1. Sign in Azure portal. Visit the container App in Azure and Click “Authentication” as shown below. Press enter or click to view image in full size For more details, visit the following link: Enable authentication and authorization in Azure Container Apps with Microsoft Entra ID | Microsoft Learn Click Add Identity Provider as shown. 2. Select Microsoft from the drop down and leave everything as is as shown below. 3. This will create a new app registration for the container App. After it is all setup, it will look like as below. As soon as authentication is configured. it will make container app inaccessible except for OAuth. Note: If you have app registration for Azure Container App already configured, use that by selecting "pick an existing app registration in this directory" option. Review App Registration of Container App — Backend Visit App registration and click streamable-mcp-server2 as in this case. Click on Authentication tab. Verify the Redirect URIs. you should see a redirect URL for container app. URI will end with /.auth/login/aad/callback as shown in the green box in the below screenshot. Now click on “Expose an API”. Confirm Application ID URI is configured with scope as shown below. its format is api://<client id> Scope "user_impersonation" is created. Verify API Permission. Make sure you Grant admin consent for your tenant as shown below. More scope can be created depending on the requirement of data access. Note: Make sure to "Grant admin consent" before proceeding to next step. Create App registration for representing APIM API Lauch Azure Portal. Visit App registration. Click New registration. Create a new App registration as shown below. For example, "apim-mcp-backend-api" in this case. Click "Expose an API", configure Application ID URI, and add a scope as shown in the below diagram such as user_impersonation. Click "App roles" and create the following role as shown below. More roles can be created depending on the requirements and case by case basis. Here app roles are created to get the concept around it and how it will be used in APIM inbound policies in the coming sections. Create App Registration for Client App — Copilot Studio In these steps, we will be configuring app registration for the client app, such as copilot studio in this case acting as a client app. This is also mentioned in the “high level architecture” diagram in the earlier section of this article. Lauch Azure Portal. Visit App registration. Click New registration. Create a new App registration. leave the Redirect URL as of now, we will configure it later as it is provided by copilot studio when configuring custom MCP connector. 3. Click on API permission and click “Add a permission”. Click Microsoft Graph and then click “Delegated permissions”. Select email, openid, profile as shown below. 4. Make sure to Grant admin consent and it should look like as below. 5. Create a secret. click “Certificates & secrets”. Create a new client secret by clicking “New client secret”. store the value as it will be masked after some time. if that happens, you can always delete and re-create a new secret. 6. Capture the following as you would need it in configuring MCP tool in Copilot Studio. Client ID from the Overview Tab of app registration. Client secret from “Certificates & secrets” tab. 7. Configure API permissions for APIM API i.e. "apim-mcp-backend-api" in this case. Click “API permissions” tab. Click “Add a permission”. Click on “My APIs” tab as shown below and select "apim-mcp-backend-api". Note: If you don't see the app registration in "My APIs". Go to App registration. Click "Owners". Add your AD account as Owners. 8. Select "Delegated permissions". Then select the permission as shown below. 9. Select the Application permission. Select the App roles created in the apim-mcp-backend-api registration. Such as mcp.read in this case. You MUST “Grant admin consent” as final step. It is very important!!! I can’t emphasize more on that. without it, nothing will work!!! 10. End result of this client app registration should look like as mentioned in the below figure. Configure permissions for Container App registration Lauch Azure Portal. Visit app registration. Select app registration of Azure container app such as streamable-mcp-server2 in this case. Select API permissions. Add the following delegated and application permissions as shown in the below diagram. Note: Don't forget to Grant admin consent. Configure allowed token audience for Container App It defines which audience values (aud claim) in a token are considered valid for your app. When a client app requests an access token from Microsoft Entra ID (Azure AD), the token includes an aud claim that identifies the intended recipient. Your container app will only accept tokens where the aud claim matches one of the values in the Allowed Token Audiences list. This is important as it ensures that only tokens issued for your API or app are accepted and prevents misuse of tokens intended for other resources. This adds extra layer of security. In the Azure Portal, visit Azure Container App. i.e. streamable-mcp-server2. Click on "Authentication" Click "Edit" under identity provider Under "Allowed token audiences", add the application ID URI of "apim-mcp-backend-api". As this will be included as an audience in the access token. Best Practices Only include trusted client app IDs. Avoid using overly broad values like “allow all” (not recommended). Validate tokens using Microsoft libraries (MSAL) or built-in auth features. Configure MCP server in API Management Note: Provisioning an API Management resource is outside the scope of this document. If you do not already have an API Management instance, follow this QuickStart: https://learn.microsoft.com/en-us/azure/api-management/get-started-create-service-instance The following service tiers are available for preview: Classic Basic, Standard, Premium, and Basic v2, Standard v2, Premium v2. For the Classic Basic, Standard, or Premium tiers, you must join the AI Gateway Early Update group to enable MCP server features. Please allow up to 2 hours for the update to take effect. Expose an existing MCP server Follow these steps to expose an existing MCP server is API Management: In the Azure portal, navigate to your API Management instance. In the left-hand menu, under APIs, select MCP servers > + Create MCP server. Select Expose an existing MCP server. In Backend MCP server: Enter the existing MCP server base URL. Example: https://streamable-mcp-serverv2.kdhg489457dslkjgn,.eastus2.azurecontainerapps.io/mcpfor the Microsoft Azure Container App hosting MCP server. In Transport type, Streamable HTTP is selected by default. In New MCP server: Enter a Name the MCP server in API Management. In Base path, enter a route prefix for tools. Example: mcptools Optionally, enter a Description for the MCP server. Select Create. Below diagram shows the MCP servers configured in APIM for reference. Configure policies for MCP server Configure one or more API Management policies to help manage the MCP server. The policies are applied to all API operations exposed as tools in the MCP server and can be used to control access, authentication, and other aspects of the tools. To configure policies for the MCP server: In the Azure portal, navigate to your API Management instance. In the left-hand menu, under APIs, select MCP Servers. Select an MCP server from the list. In the left menu, under MCP, select Policies. In the policy editor, add or edit the policies you want to apply to the MCP server's tools. The policies are defined in XML format. <!-- - Policies are applied in the order they appear. - Position <base/> inside a section to inherit policies from the outer scope. - Comments within policies are not preserved. --> <!-- Add policies as children to the <inbound>, <outbound>, <backend>, and <on-error> elements --> <policies> <!-- Throttle, authorize, validate, cache, or transform the requests --> <inbound> <base /> <set-variable name="accessToken" value="@(context.Request.Headers.GetValueOrDefault("Authorization", "").Replace("Bearer ", ""))" /> <!-- Log the captured access token to the trace logs --> <trace source="Access Token Debug" severity="information"> <message>@("Access Token: " + (string)context.Variables["accessToken"])</message> </trace> <set-variable name="userId" value="@(context.Request.Headers.GetValueOrDefault("Authorization", "Bearer ").Split(' ')[1].AsJwt().Claims["oid"].FirstOrDefault())" /> <set-variable name="userName" value="@(context.Request.Headers.GetValueOrDefault("Authorization", "Bearer ").Split(' ')[1].AsJwt().Claims["name"].FirstOrDefault())" /> <trace source="User Name Debug" severity="information"> <message>@("username: " + (string)context.Variables["userName"])</message> </trace> <set-variable name="scp" value="@(context.Request.Headers.GetValueOrDefault("Authorization", "Bearer ").Split(' ')[1].AsJwt().Claims["scp"].FirstOrDefault())" /> <trace source="Scope Debug" severity="information"> <message>@("scope: " + (string)context.Variables["scp"])</message> </trace> <set-variable name="roles" value="@(context.Request.Headers.GetValueOrDefault("Authorization", "Bearer ").Split(' ')[1].AsJwt().Claims["roles"].FirstOrDefault())" /> <trace source="Role Debug" severity="information"> <message>@("Roles: " + (string)context.Variables["roles"])</message> </trace> <!-- <set-variable name="requestBody" value="@{ return context.Request.Body.As<string>(preserveContent:true); }" /> <trace source="Request Body information" severity="information"> <message>@("Request body: " + (string)context.Variables["requestBody"])</message> </trace> --> <validate-azure-ad-token tenant-id="{{tenant-id}}" header-name="Authorization" failed-validation-httpcode="401" failed-validation-error-message="Unauthorized. Access token is missing or invalid."> <client-application-ids> <application-id>{{client-application-id}}</application-id> </client-application-ids> <audiences> <audience>{{audience}}</audience> </audiences> <required-claims> <claim name="roles" match="any"> <value>mcp.read</value> </claim> </required-claims> </validate-azure-ad-token> </inbound> <!-- Control if and how the requests are forwarded to services --> <backend> <base /> </backend> <!-- Customize the responses --> <outbound> <base /> </outbound> <!-- Handle exceptions and customize error responses --> <on-error> <base /> <trace source="Role Debug" severity="error"> <message>@("username: " + (string)context.Variables["userName"] + " has error in accessing the MCP server, could be auth or role related...")</message> </trace> <return-response> <set-status code="403" reason="Forbidden" /> <set-body> {"error":"Missing required scope or role"} </set-body> </return-response> </on-error> </policies> Note: Update the above inbound policy with the tenant Id, client application id, and audience as per your environment. It is recommended to use APIM "Named values" instead of hard coding inside the policy. To learn more, visit Use named values in Azure API Management policies Configure Diagnostics for APIM In this solution, APIM diagnostics are configured to forward log data to Log Analytics. Testing and validation will be carried out using insights from Log Analytics. Note: Setting up diagnostics is outside the scope of this article. However, you can visit the following link for more information. https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-use-azure-monitor Below diagram shows what Logs are being sent to Log Analytics workspace. MCP Tool configuration in Copilot Studio Lauch copilot studio at https://copilotstudio.microsoft.com/. Configuration of environment and agent is beyond the scope of this article. It is assumed, you already have environment setup and agent has been created. Following link will help you, how to create an agent in copilot studio. Quickstart: Create and deploy an agent — Microsoft Copilot Studio | Microsoft Learn Inside agent configuration, click "Add tool". 3. Click on New tool. 4. Select Model Context Protocol. 5. Provide all relevant information for MCP server. Make sure your server URL ends with your mcp setup. In this case, it is APIM MCP server URL, with base path configured in APIM in the end. Provide server name and server description. Select OAuth 2.0 radio button. 6. Provide the following in the OAuth 2.0 section Client ID of client app registration. In this case, copilot-studio-client as configured earlier. Client secret of copilot-studio-client app registration. Authorization URL: https://login.microsoftonline.com/common/oauth2/v2.0/authorize Token URL template & Refresh URL: https://login.microsoftonline.com/oauth2/v2.0/token Scopes: openid, profile, email — which we selected earlier for Microsoft Azure Graph permissions. Click “Create”. This will provide you Redirect URL. you need to configure the redirect URL in client app registration. In this case, it is copilot-agent-client. Configure Redirect URI in Client App Registration Visit client app registration. i.e. copilot-studio-client. Click Authentication Tab and provide the Web Redirect URIs as shown below. Note: Configure Redirect URIs MUST be configured in app registration. Otherwise, authorization will not complete and sign on will fail. Configure redirect URI in APIM API app registration Also configure apim-mcp-backend-api app registration with the same redirect URI as shown below. Modify MCP connector in PowerApps Now visit the https://make.powerapps.com and open the newly created connector as shown below. Select the security tab and modify the Resource URL with application ID URI of apim-mcp-backend-api configured earlier in app registration for expose an API. Add .default in the scope. Provide the secret of client app registration as it will not let you update the connector. This is extra security measure for updating the connector in Powerapps. Click Update connector. CORS Configuration CORS configuration is a MUST!!! Since our Azure Container App is a remote MCP server with totally different domain or origin. Power Apps and CORS for External Domains — Brief Overview When embedding or integrating Power Apps with external web applications or APIs, Cross-Origin Resource Sharing (CORS) becomes a critical consideration. CORS is a browser security feature that restricts web pages from making requests to a different domain than the one that served the page, unless explicitly allowed. Key Points: Power Apps hosted on *.powerapps.com or within Microsoft 365 domains will block calls to external APIs unless those APIs include the proper CORS headers. The external API must return: Access-Control-Allow-Origin: https://apps.powerapps.com (or * for all origins, though not recommended for production) Access-Control-Allow-Methods: GET, POST, OPTIONS (or as needed) Access-Control-Allow-Headers: Content-Type, Authorization (and any custom headers) If the API requires authentication (e.g., OAuth 2.0), ensure preflight OPTIONS requests are handled correctly. For scenarios where you cannot modify the external API, consider using: Power Automate flows as a proxy Azure API Management or Azure Functions to inject CORS headers Always validate security implications before enabling wide-open CORS. If the CORS are not setup. You will encounter following error in copilot studio after pressing F12 (Browser Developer) CORS policy — blocking the container app Azure container app provides very efficient way of configuring CORS in the Azure portal. Lauch Azure Portal. Visit Azure container app i.e. streamable-mcp-server2 in this case. Click on CORS under Networking section. Configure the following in Allowed Origin Section as shown below. localhost is added to make it work from local laptop, although it is not required for Copilot Studio. 4. Click on “Allowed Method” tab and provide the following. 5. Provide wild card “*” in “Allowed Headers”tab. Although, it is not recommended for production system. it is done for the sake for simplicity. Configure that for added security 6. Click “Apply”. This will configure CORS for remote application. Test the MCP custom connector We are in the final stages of configuring the connector. It is time to test it, if everything is configured correctly and works. Launch the http://make.powerapps.com and click on “Custom connectors”, select your configured connector and click “5. Test” tab as shown below. You will see Selected Connection as blank if you are running it first time. Click “+ New connection” 2. New connection will launch the Authorization flow and browser dialog will pop up for making a request for authorization code. 3. Click “Create”. 4. Complete the login process. This will create a successful connection. 5. Click “Test operation”. If the response is 406 means everything is configured correctly as shown below. Solution validation Add user in Enterprise Application for App roles Roles have been defined under the required claims in the APIM inbound policy and also configured in the apim-mcp-backend-api app registration. As a result, any request from Copilot Studio will be denied if this role is not properly assigned. This role is included in the JWT access token, which we will validate in the following sections. To assign role, perform the following steps. Visit Azure Portal. Visit Enterprise Application. Select APIM backend app registration. In this case for example, apim-mcp-backend-api Click "Users and groups" Select "Add user/group" 5. Select User or Group who should have access to the role. 6. Click "Assign". It will look like as below. Note: Role assignment for users or groups is an important step. If it is not configured, MCP server tests will fail in Copilot studio. Test MCP server in Copilot Studio Lauch copilot studio and click on the Agent you created in earlier steps and click on “Tools tab”. Select your MCP tool as shown the following figure. Make sure it is “Enabled” if you have other tools attached to the same agent, disable them for now for testing. Make sure you have connection available which we created during the testing of custom connector in earlier step. You can also initiate a fresh connection by clicking on the drop down under “Connection” as shown below. Refreshing the tools will show all the tools available in this MCP server. Provide the sample prompt such as “Give me the stock price of tesla”. This will trigger the MCP server and call the respective method to bring the stock price of Tesla. Now try a weather-related question to see more. Now invoking weather forecast tool in the MCP server. APIM Monitoring with Log Analytics We previously configured APIM diagnostic settings to forward log data to Log Analytics. In this section, we’ll review that data, as the inbound policy in APIM sends valuable information to Log Analytics. Run the Kusto query to retrieve data from the last 30 minutes. As shown, the logs capture the APIM API endpoint URL and the backend URL, which corresponds to the Azure Container App endpoint. Scrolling further, we find the TraceRecords section. This contains the information captured by APIM inbound policies and sent to Log Analytics. The figure below illustrates the TraceRecords data. In the inbound policy, we configured it to extract details from the access token—such as the token itself, username, scope, and roles—and forward them to Log Analytics. Now let's capture the access token in the clip board, launch the http://jwt.io which is JSON Web Token (JWT) debugger, and paste the access token in the ENCODED VALUE box as show below. Note the following information. aud: This shows the Application URI ID of apim-mcp-backend-api. which shows access token is requested for that audience. appid: This shows the client Id for copilot-studio-client app registration. You can also see roles and scope. These roles are specified in APIM inbound policy. Note: As you can see, roles are included in access token and if it is not assigned in the enterprise application for "apim-mcp-backend-api", all requests will be denied by APIM inbound policy configured earlier. Perform a test using another Azure AD account that does not have the app role assigned Now, let's try the copilot studio agent by logging in with another account which is not assigned for the "mcp.read" role. Let's, review the below diagram. Logged in as demo and tried to access the MCP tool in copilot studio agent. Request failed with the error "Missing required scope or roles". If you look at it, this is coming from the APIM policy configured earlier in <on-error> Let's review log analytics. As you can see request failed due to inbound APIM policy with 403 error and there is no backend URL. Error is also reported under TraceRecords as we configured it in APIM policy. Now copy the Access token from log analytics and paste it into jwt.io. You can notice in the below diagram, there is no "roles" in the access token, resulting access denied from APIM inbound policy definition to the APIM backend i.e. azure container app. Assign the app role to the demo account Let's assign the "mcp.read" role to the demo account and test if it accesses the tool. Visit Azure Portal, Lauch Enterprise application, and select "apim-mcp-backend-api" as in this example. Click "Users and groups" Click "+ Add user/group" Select demo Click "Select" Click "Assign" End result would look like as shown below. Now, login again as demo. Make sure a new access token is generated. Access token refresh happens after one hours. As you can see in the image below, this time the request is successful after assigning the "mcp.read" app roles. Now let's review the log analytics entries. Let's review the access token in JWT.io. As you can see, roles are included in the access token. Conclusion Exposing the MCP server through Azure API Management (APIM) and integrating it with Copilot Studio agents provides a secure and scalable way to extend enterprise capabilities. By implementing OAuth 2.0, you ensure robust authentication and authorization, protecting sensitive data and maintaining compliance with industry standards. Beyond security, APIM adds significant operational value. With APIM policies, you can monitor traffic, enforce rate limits, and apply fine-grained controls to manage access and performance effectively. This combination of security and governance empowers organizations to innovate confidently while maintaining control and visibility over API usage. In today’s enterprise landscape, leveraging APIM with OAuth 2.0 for MCP integration is not just best practice—it’s a strategic move toward building resilient, secure, and well-governed solutions.
