From 9c4b33191d08bbe1afbba4dc8438665040410b4b Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Mon, 15 Jun 2026 14:05:19 +0200 Subject: [PATCH 01/11] First proposal for Copilto Studio + MCP integration --- .../drawio/copilot-studio+mcp-gateway.drawio | 276 ++++++++++++++++++ .../copilot-studio+mcp-gateway.drawio.svg | 4 + .../11-copilot-studio-with-mcp/readme.md | 201 +++++++++++++ 3 files changed, 481 insertions(+) create mode 100644 docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio create mode 100644 docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg create mode 100644 docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio new file mode 100644 index 0000000000..b67594f40e --- /dev/null +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio @@ -0,0 +1,276 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg new file mode 100644 index 0000000000..a71662157c --- /dev/null +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg @@ -0,0 +1,4 @@ + + + +
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
Network
   
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

 \ No newline at end of file diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md new file mode 100644 index 0000000000..24d2c3b2de --- /dev/null +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md @@ -0,0 +1,201 @@ +--- +id: id-ra0029-1 +slug: /ref-arch/ca1d2a3e/1 +sidebar_position: 1 +title: A2A and MCP for Interoperability +description: >- + Learn how the Agent2Agent (A2A) and Model Context Protocol (MCP) enable a decoupled, interoperable and scalable AI agent ecosystem on SAP BTP. +keywords: + - sap + - ai agents + - a2a + - mcp + - interoperability + - Agent2Agent + - model context protocol + - copilot studio + - microsoft copilot +sidebar_label: A2A and MCP for Interoperability +image: img/ac-soc-med.png +tags: + - agents + - genai + - cap + - aws + - gcp + - azure + - ibm +hide_table_of_contents: false +hide_title: false +toc_min_heading_level: 2 +toc_max_heading_level: 4 +draft: false +unlisted: false +contributors: + - kay-schmitteckert + - hterminasyan +discussion: +last_update: + author: hobru + date: 2026-06-12 +--- + +:::info Disclaimer +The [Agent Gateway](../1-a2a-and-mcp/readme.md#architecture) is not yet generally available (GA). The outlined architecture here shows ways how the integration with Copilot Studio and SAP can be done today. + +::: + +# Microsoft Copilot Studio and the SAP MCP Gateway + +[Microsoft Copilot Studio](https://www.microsoft.com/en-us/microsoft-365-copilot/microsoft-copilot-studio) is Microsoft's low-code platform for building and orchestrating AI agents across Microsoft 365, Teams, and custom channels. +Through the **Model Context Protocol (MCP)**, a Copilot Studio agent can discover and invoke SAP business capabilities as governed tools — without +bespoke point-to-point integration code and without moving SAP data out of its system of record. + +![Copilot Studio and MCP Gateawy](images/copilot-studio+mcp-gateway.drawio.svg) + +If you are new to Copilot Studio, start with the official product documentation: [Microsoft Copilot Studio documentation](https://learn.microsoft.com/en-us/microsoft-copilot-studio/). + +In this pattern, Copilot Studio acts as the **MCP client**, and the **MCP Gateway in SAP Integration Suite** acts as the governed entry point that +exposes SAP APIs, integration flows, and data sources as MCP-compliant tools. Identity flows end-to-end through a trust relationship between **Microsoft Entra ID** and **SAP Cloud Identity Services**, so every tool call runs in the context of the signed-in business user and respects existing SAP authorizations. + +This gives organizations the best of both ecosystems: the conversational reach and authoring experience of Copilot Studio on the front end, and the +enterprise-grade security, governance, and semantic richness of SAP BTP on the back end. + +## Architecture at a Glance + +| Layer | Component | Role | +| --- | --- | --- | +| Front end (Microsoft Azure) | **Copilot Studio agent** | Authors topics/tools, orchestrates the conversation, calls MCP tools at runtime | +| Identity | **Microsoft Entra ID ⇄→ SAP Cloud Identity Services** | Federated trust; issues and exchanges tokens so the user identity propagates into SAP | +| Governance (SAP BTP) | **MCP Gateway in SAP Integration Suite** | Exposes APIs/flows as MCP tools; enforces OIDC auth, rate limiting, payload protection, observability | +| Tools & data | **SAP S/4HANA, SuccessFactors, Concur, Customer Experience, Business Data Cloud, custom MCP servers, third-party APIs** | The authoritative systems the tools act on | + +The Copilot Studio agent connects to the gateway over **MCP using the Streamable HTTP transport** and authenticates with **OAuth 2.0**. The gateway validates the token, applies governance policy, and routes the request to the underlying SAP or non-SAP system. + +## Getting Started + +The integration involves three coordinated configuration steps — one on SAP BTP, one in your identity provider(s), and one in Copilot Studio. + +### Prerequisites + +- An SAP BTP subaccount with **SAP Integration Suite** and the **MCP Gateway** capability enabled. +- The SAP APIs you want to expose available as OData/REST services or integration flows. +- A Microsoft Copilot Studio environment with agent-creation permissions. +- Administrative access to **Microsoft Entra ID** and **SAP Cloud Identity Services** to configure trust and app registrations. + +### Step 1 — Expose your SAP capabilities as MCP tools + +In SAP Integration Suite, use the MCP Gateway to create MCP-compliant tools from your existing APIs and integration flows. Enrich each tool with a clear name and description — the Copilot Studio orchestrator uses this metadata to decide, at runtime, whether a tool is relevant to the user's request. Secure the gateway endpoint with OIDC and apply rate-limiting and payload-protection policies. + +### Step 2 — Establish trust between Entra ID and SAP Cloud Identity Services + +Configure the federation that lets a Microsoft-issued identity be recognized by SAP (covered in detail under [Single Sign-On and Identity +Propagation](#single-sign-on-and-identity-propagation) below). This is what allows the agent to act on behalf of the actual business user rather than a +shared service identity. + +### Step 3 — Connect the MCP server in Copilot Studio + +In your agent's **Tools** page, choose **Add a tool → New tool → Model Context Protocol**. Enter the gateway's server name, description, and URL, then select **OAuth 2.0** as the authentication type. Copilot Studio supports three OAuth setups: + +For step-by-step MCP setup guidance, see: [Connect your agent to an existing MCP server — Microsoft Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent). + +- **Dynamic discovery** — simplest; use when the gateway supports OAuth 2.0 Dynamic Client Registration (DCR) with a discovery endpoint. +- **Dynamic** — DCR without discovery; you supply the endpoints manually. +- **Manual** — you configure all OAuth 2.0 settings explicitly. + +After you add the server, Copilot Studio issues a **callback (redirect) URL**. Register that URL in your identity provider's app registration to complete the OAuth handshake. Once connected, the SAP tools appear in the agent and can be invoked conversationally. + +:::note Transport +Copilot Studio supports the **Streamable HTTP** transport. SSE is deprecated and is no longer supported for MCP after August 2025 — ensure the gateway exposes a Streamable HTTP endpoint. +::: + +## Single Sign-On and Identity Propagation + +Secure, user-context-aware access is the centerpiece of this architecture. The goal is **no shared secrets and no over-privileged service accounts** — each SAP tool call executes with the permissions of the individual signed-in user. + +### How the trust is established + +- **SAP Cloud Identity Services (Identity Authentication, IAS)** is federated with **Microsoft Entra ID** over OIDC. Entra ID typically acts as the + corporate identity provider; IAS brokers the identity into the SAP landscape and maps it to the SAP user. +- In Copilot Studio, the agent authenticates to the MCP Gateway with **OAuth 2.0 Authorization Code Flow**, so a user-delegated access token is obtained interactively when the user first invokes an SAP tool. +- The MCP Gateway validates the token (OIDC), and SAP Cloud Identity Services resolves it to the corresponding SAP identity, after which the underlying system enforces that user's existing roles and authorizations. + +### Why this matters + +- **Least privilege by design** — authorizations already maintained in SAP continue to govern what the agent can read or write. No parallel permission model to build or audit. +- **End-to-end traceability** — actions are attributable to a named user, which supports compliance, audit, and accountability requirements. +- **Single sign-on experience** — users authenticate once with their Microsoft credentials; the federation handles SAP access transparently. + +:::tip +For organizations migrating from SAP Identity Management to Entra ID, this pattern aligns with the joint SAP–Microsoft identity lifecycle reference architecture, reusing the same federation foundation rather than introducing a new one. +::: + +## Scenarios and Use Cases + +The integration shines wherever an employee already works in a Microsoft surface (Teams, Microsoft 365 Copilot, a custom Copilot Studio agent) but needs +authoritative SAP data or actions in the flow of work. + +### Self-service across SAP lines of business + +- **HR & People (SuccessFactors):** "Show my remaining leave balance and submit a vacation request for the last week of July." The agent calls SuccessFactors tools through the gateway under the employee's own identity. +- **Travel & Expense (Concur):** "Create an expense report from these receipts and check the status of my last reimbursement." +- **Procurement & Finance (S/4HANA):** "What's the status of purchase order 4500001234, and who needs to approve it next?" + +### Operational and customer-facing agents + +- **Order-to-cash / customer service (SAP Customer Experience):** A service agent in Teams retrieves order status, delivery dates, and account history without leaving the conversation. +- **Supply chain & logistics:** Surface inventory levels, ASN status, or supplier data from SAP Business Network in a Copilot Studio agent for planners. + +### Insight in the flow of work (SAP Business Data Cloud) + +- "Summarize Q2 revenue variance by region" — the agent grounds its answer in governed SAP analytics data rather than ungoverned exports. + +### Composite, multi-system agents + +Because the gateway can expose SAP **and** non-SAP APIs side by side, a single Copilot Studio agent can orchestrate a process that spans, for example, an +S/4HANA sales order, a Concur travel booking, and a third-party logistics API — all behind one governed MCP entry point. + +### Bridging to the broader SAP agent ecosystem + +For richer multi-agent collaboration, Copilot Studio can interoperate with SAP Joule agents via the **A2A protocol** through the Agent Gateway (once it is available). MCP (tool consumption) and A2A (agent-to-agent delegation) are complementary: use MCP when Copilot Studio needs to *call SAP capabilities as tools*, and A2A when it needs to *delegate a task to a specialized SAP agent*. + +For SAP Joule and Microsoft 365 Copilot integration context, see: [SAP with Microsoft: AI SAP Joule & Microsoft 365 Copilot Integration — Microsoft Learn](https://learn.microsoft.com/en-us/azure/sap/microsoft-ai/joule/joule-copilot-overview). + +## What Makes This Integration Compelling + +- **Open standards, no lock-in.** MCP and OAuth/OIDC are open, widely adopted standards. Tools and agents evolve independently; you are not coupled to a + proprietary connector format. +- **Build once, consume anywhere.** A capability exposed through the MCP Gateway is immediately available to Copilot Studio *and* any other MCP-compliant agent (for example, on Azure AI Foundry, Vertex AI, or Bedrock), maximizing reuse of your integration investment. +- **Governance at the edge.** Authentication, authorization, rate limiting, payload protection, and traffic management are enforced centrally at the gateway — independent of how many agents consume the tools. +- **Observability and adoption insight.** Built-in monitoring, tracing, and analytics show how agents consume tools, supporting compliance reporting and + helping you understand real-world usage. +- **Data stays in SAP.** The agent calls tools and receives scoped results; SAP remains the system of record, and the user's authorizations bound every + interaction. +- **Low-code authoring.** Business teams build and refine agents in Copilot Studio's visual designer, while platform teams retain control of what is exposed and how it is secured. + +### Best Practices + +- Write **precise, action-oriented tool descriptions** in the gateway — the Copilot Studio orchestrator relies on them for accurate tool selection. +- Start with **read-only, high-value scenarios** (status lookups, balances, summaries) to build confidence before enabling write actions (approvals, + submissions). +- **Scope OAuth permissions tightly** and prefer delegated (user) flows over application (service) flows wherever the scenario allows. +- Use the gateway's **rate limiting and payload protection** to guard SAP backends against unbounded agent traffic. +- Validate the **Streamable HTTP** endpoint and token lifetime/refresh behavior in a non-production subaccount first. + +## Simplified Flow + +1. **User request** — A user asks the Copilot Studio agent a question that requires SAP data or an SAP action. +2. **Authentication** — On first use, the agent obtains a user-delegated OAuth 2.0 token; Entra ID and SAP Cloud Identity Services federate the identity into SAP. +3. **Tool discovery & selection** — The orchestrator matches the request to an MCP tool exposed by the SAP MCP Gateway, using the tool's description. +4. **Governed invocation** — The agent calls the tool over MCP (Streamable HTTP). The gateway validates the token, applies governance policy, and routes to the SAP/non-SAP system. +5. **Authorized execution** — The backend executes within the signed-in user's authorizations and returns a scoped result. +6. **Response** — The agent composes and presents the answer to the user in their Microsoft surface. + +## Related Resources + +- [A2A and MCP for Interoperability — SAP Architecture Center](https://architecture.learning.sap.com/docs/ref-arch/ca1d2a3e/1) +- [Microsoft Copilot Studio documentation](https://learn.microsoft.com/en-us/microsoft-copilot-studio/) +- [Connect your agent to an existing MCP server — Microsoft Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent) +- [Create a new MCP server — Microsoft Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-create-new-server) +- [SAP with Microsoft: AI SAP Joule & Microsoft 365 Copilot Integration — Microsoft Learn](https://learn.microsoft.com/en-us/azure/sap/microsoft-ai/joule/joule-copilot-overview) +- [Identity and Access Management with Microsoft Entra and SAP BTP — SAP Community](https://community.sap.com/t5/technology-blog-posts-by-members/identity-and-access-management-with-microsoft-entra-part-i-managing-access/ba-p/13873276) From 36ac13b406706e7c51a71beed043fa45b124ebce Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Mon, 15 Jun 2026 15:22:52 +0200 Subject: [PATCH 02/11] Update readme.md to clarify MCP Gateway integration with Microsoft Copilot Studio - Renamed section title for clarity - Moved description of MCP functionality to improve flow - Added back the diagram for visual reference --- .../drawio/copilot-studio+mcp-gateway.drawio | 76 +++++++++---------- .../copilot-studio+mcp-gateway.drawio.svg | 2 +- .../11-copilot-studio-with-mcp/readme.md | 11 +-- 3 files changed, 44 insertions(+), 45 deletions(-) diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio index b67594f40e..1b172893d8 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio @@ -1,6 +1,6 @@ - + @@ -40,24 +40,6 @@ - - - - - - - - - - - - - - - - - - @@ -82,13 +64,6 @@ - - - - - - - @@ -179,17 +154,6 @@ - - - - - - - - - - - @@ -259,7 +223,7 @@ - + @@ -267,9 +231,43 @@ - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg index a71662157c..73327f7b95 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg @@ -1,4 +1,4 @@ -
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
Network
   
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

 \ No newline at end of file +
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md index 24d2c3b2de..0670e7997e 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md @@ -45,19 +45,20 @@ The [Agent Gateway](../1-a2a-and-mcp/readme.md#architecture) is not yet generall ::: -# Microsoft Copilot Studio and the SAP MCP Gateway +# Microsoft Copilot Studio and the MCP Gateway in SAP Integration Suite [Microsoft Copilot Studio](https://www.microsoft.com/en-us/microsoft-365-copilot/microsoft-copilot-studio) is Microsoft's low-code platform for building and orchestrating AI agents across Microsoft 365, Teams, and custom channels. -Through the **Model Context Protocol (MCP)**, a Copilot Studio agent can discover and invoke SAP business capabilities as governed tools — without -bespoke point-to-point integration code and without moving SAP data out of its system of record. - -![Copilot Studio and MCP Gateawy](images/copilot-studio+mcp-gateway.drawio.svg) If you are new to Copilot Studio, start with the official product documentation: [Microsoft Copilot Studio documentation](https://learn.microsoft.com/en-us/microsoft-copilot-studio/). +Through the **Model Context Protocol (MCP)**, a Copilot Studio agent can discover and invoke SAP business capabilities as governed tools — without +bespoke point-to-point integration code and without moving SAP data out of its system of record. + In this pattern, Copilot Studio acts as the **MCP client**, and the **MCP Gateway in SAP Integration Suite** acts as the governed entry point that exposes SAP APIs, integration flows, and data sources as MCP-compliant tools. Identity flows end-to-end through a trust relationship between **Microsoft Entra ID** and **SAP Cloud Identity Services**, so every tool call runs in the context of the signed-in business user and respects existing SAP authorizations. +![Copilot Studio and MCP Gateawy](images/copilot-studio+mcp-gateway.drawio.svg) + This gives organizations the best of both ecosystems: the conversational reach and authoring experience of Copilot Studio on the front end, and the enterprise-grade security, governance, and semantic richness of SAP BTP on the back end. From e1ee0daf38e21331989255fca07fb9c1d118cfa4 Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Tue, 16 Jun 2026 15:44:42 +0200 Subject: [PATCH 03/11] Refactor code structure for improved readability and maintainability --- .../drawio/copilot-studio+mcp-gateway.drawio | 11 +++++------ .../images/copilot-studio+mcp-gateway.drawio.svg | 2 +- 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio index 1b172893d8..6632357c7a 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio @@ -1,6 +1,6 @@ - + @@ -144,7 +144,7 @@ - + @@ -234,13 +234,12 @@ - + - - + - + diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg index 73327f7b95..50596112df 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg @@ -1,4 +1,4 @@ -
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file +
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file From 57a2cbec1a8c16e7fd6bdd5f3fcc371828309a2b Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Wed, 17 Jun 2026 12:03:56 +0200 Subject: [PATCH 04/11] Refactor code structure for improved readability and maintainability --- .../drawio/copilot-studio+mcp-gateway.drawio | 10 +++++++--- .../images/copilot-studio+mcp-gateway.drawio.svg | 2 +- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio index 6632357c7a..dfc2accc8c 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio @@ -1,6 +1,6 @@ - + @@ -144,7 +144,7 @@ - + @@ -172,6 +172,9 @@ + + + @@ -234,9 +237,10 @@ - + + diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg index 50596112df..e4347aa7e8 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg @@ -1,4 +1,4 @@ -
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file +
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file From 300b2b9c7d035596bbc8e9ad9762ab9966b46405 Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Wed, 17 Jun 2026 12:59:41 +0200 Subject: [PATCH 05/11] Refactor code structure for improved readability and maintainability --- .../drawio/copilot-studio+mcp-gateway.drawio | 3 +-- .../images/copilot-studio+mcp-gateway.drawio.svg | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio index dfc2accc8c..b8df827409 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio @@ -1,6 +1,6 @@ - + @@ -240,7 +240,6 @@ - diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg index e4347aa7e8..8c73f06410 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg @@ -1,4 +1,4 @@ -
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file +
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file From 65e925a86d83c4d962ca1b1302c91890d2ebf9ca Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Thu, 18 Jun 2026 13:37:40 +0200 Subject: [PATCH 06/11] Update title and description for clarity on Microsoft Copilot Studio integration --- .../RA0029/11-copilot-studio-with-mcp/readme.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md index 0670e7997e..1655bd2c1c 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md @@ -2,9 +2,9 @@ id: id-ra0029-1 slug: /ref-arch/ca1d2a3e/1 sidebar_position: 1 -title: A2A and MCP for Interoperability +title: Microsoft Copilot Studio and the MCP Gateway in SAP Integration Suite description: >- - Learn how the Agent2Agent (A2A) and Model Context Protocol (MCP) enable a decoupled, interoperable and scalable AI agent ecosystem on SAP BTP. + Learn how Microsoft Copilot Studio and other Microsoft MCP clients can be connected using the MCP Gateway in SAP Integration Suite. keywords: - sap - ai agents @@ -15,16 +15,12 @@ keywords: - model context protocol - copilot studio - microsoft copilot -sidebar_label: A2A and MCP for Interoperability +sidebar_label: AMicrosoft Copilot Studio and the MCP Gateway in SAP Integration Suite image: img/ac-soc-med.png tags: - agents - genai - - cap - - aws - - gcp - azure - - ibm hide_table_of_contents: false hide_title: false toc_min_heading_level: 2 @@ -37,7 +33,7 @@ contributors: discussion: last_update: author: hobru - date: 2026-06-12 + date: 2026-06-18 --- :::info Disclaimer From 28b12d2d5903fb8925d2d60c2757346eeb6e8190 Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Thu, 18 Jun 2026 13:49:10 +0200 Subject: [PATCH 07/11] Fix sidebar label typo in Copilot Studio documentation --- docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md index 1655bd2c1c..0c7616750f 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md +++ b/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md @@ -15,7 +15,7 @@ keywords: - model context protocol - copilot studio - microsoft copilot -sidebar_label: AMicrosoft Copilot Studio and the MCP Gateway in SAP Integration Suite +sidebar_label: Microsoft Copilot Studio and the MCP Gateway in SAP Integration Suite image: img/ac-soc-med.png tags: - agents From e1cfdec477509ca55a76f37944d7c8b478a24379 Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Thu, 18 Jun 2026 15:27:29 +0200 Subject: [PATCH 08/11] Add documentation for Microsoft Copilot Studio integration with MCP Gateway in SAP Integration Suite --- .../drawio/copilot-studio+mcp-gateway.drawio | 0 .../images/copilot-studio+mcp-gateway.drawio.svg | 0 .../1-copilot-studio-with-mcp}/readme.md | 8 +++----- 3 files changed, 3 insertions(+), 5 deletions(-) rename docs/ref-arch/RA0029/{11-copilot-studio-with-mcp => 10-third-party-mcp-access/1-copilot-studio-with-mcp}/drawio/copilot-studio+mcp-gateway.drawio (100%) rename docs/ref-arch/RA0029/{11-copilot-studio-with-mcp => 10-third-party-mcp-access/1-copilot-studio-with-mcp}/images/copilot-studio+mcp-gateway.drawio.svg (100%) rename docs/ref-arch/RA0029/{11-copilot-studio-with-mcp => 10-third-party-mcp-access/1-copilot-studio-with-mcp}/readme.md (98%) diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio similarity index 100% rename from docs/ref-arch/RA0029/11-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio rename to docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg similarity index 100% rename from docs/ref-arch/RA0029/11-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg rename to docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg diff --git a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md similarity index 98% rename from docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md rename to docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md index 0c7616750f..c73006233a 100644 --- a/docs/ref-arch/RA0029/11-copilot-studio-with-mcp/readme.md +++ b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md @@ -1,6 +1,6 @@ --- -id: id-ra0029-1 -slug: /ref-arch/ca1d2a3e/1 +id: id-ra0029-10-1 +slug: /ref-arch/ca1d2a3e/10/1 sidebar_position: 1 title: Microsoft Copilot Studio and the MCP Gateway in SAP Integration Suite description: >- @@ -69,7 +69,7 @@ enterprise-grade security, governance, and semantic richness of SAP BTP on the b The Copilot Studio agent connects to the gateway over **MCP using the Streamable HTTP transport** and authenticates with **OAuth 2.0**. The gateway validates the token, applies governance policy, and routes the request to the underlying SAP or non-SAP system. -## Getting Started +## Configuration and architecture overview The integration involves three coordinated configuration steps — one on SAP BTP, one in your identity provider(s), and one in Copilot Studio. @@ -166,8 +166,6 @@ For SAP Joule and Microsoft 365 Copilot integration context, see: [SAP with Micr - **Governance at the edge.** Authentication, authorization, rate limiting, payload protection, and traffic management are enforced centrally at the gateway — independent of how many agents consume the tools. - **Observability and adoption insight.** Built-in monitoring, tracing, and analytics show how agents consume tools, supporting compliance reporting and helping you understand real-world usage. -- **Data stays in SAP.** The agent calls tools and receives scoped results; SAP remains the system of record, and the user's authorizations bound every - interaction. - **Low-code authoring.** Business teams build and refine agents in Copilot Studio's visual designer, while platform teams retain control of what is exposed and how it is secured. ### Best Practices From 87b49aa4338a461b3fe94748be2465d4a55f08ef Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Tue, 23 Jun 2026 21:38:46 +0200 Subject: [PATCH 09/11] Refactor MCP setup instructions for clarity and conciseness in documentation --- .../1-copilot-studio-with-mcp/readme.md | 29 ++++--------------- 1 file changed, 5 insertions(+), 24 deletions(-) diff --git a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md index c73006233a..89546d88da 100644 --- a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md +++ b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md @@ -80,27 +80,8 @@ The integration involves three coordinated configuration steps — one on SAP BT - A Microsoft Copilot Studio environment with agent-creation permissions. - Administrative access to **Microsoft Entra ID** and **SAP Cloud Identity Services** to configure trust and app registrations. -### Step 1 — Expose your SAP capabilities as MCP tools - -In SAP Integration Suite, use the MCP Gateway to create MCP-compliant tools from your existing APIs and integration flows. Enrich each tool with a clear name and description — the Copilot Studio orchestrator uses this metadata to decide, at runtime, whether a tool is relevant to the user's request. Secure the gateway endpoint with OIDC and apply rate-limiting and payload-protection policies. - -### Step 2 — Establish trust between Entra ID and SAP Cloud Identity Services - -Configure the federation that lets a Microsoft-issued identity be recognized by SAP (covered in detail under [Single Sign-On and Identity -Propagation](#single-sign-on-and-identity-propagation) below). This is what allows the agent to act on behalf of the actual business user rather than a -shared service identity. - -### Step 3 — Connect the MCP server in Copilot Studio - -In your agent's **Tools** page, choose **Add a tool → New tool → Model Context Protocol**. Enter the gateway's server name, description, and URL, then select **OAuth 2.0** as the authentication type. Copilot Studio supports three OAuth setups: - For step-by-step MCP setup guidance, see: [Connect your agent to an existing MCP server — Microsoft Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent). -- **Dynamic discovery** — simplest; use when the gateway supports OAuth 2.0 Dynamic Client Registration (DCR) with a discovery endpoint. -- **Dynamic** — DCR without discovery; you supply the endpoints manually. -- **Manual** — you configure all OAuth 2.0 settings explicitly. - -After you add the server, Copilot Studio issues a **callback (redirect) URL**. Register that URL in your identity provider's app registration to complete the OAuth handshake. Once connected, the SAP tools appear in the agent and can be invoked conversationally. :::note Transport Copilot Studio supports the **Streamable HTTP** transport. SSE is deprecated and is no longer supported for MCP after August 2025 — ensure the gateway exposes a Streamable HTTP endpoint. @@ -134,14 +115,14 @@ authoritative SAP data or actions in the flow of work. ### Self-service across SAP lines of business -- **HR & People (SuccessFactors):** "Show my remaining leave balance and submit a vacation request for the last week of July." The agent calls SuccessFactors tools through the gateway under the employee's own identity. -- **Travel & Expense (Concur):** "Create an expense report from these receipts and check the status of my last reimbursement." -- **Procurement & Finance (S/4HANA):** "What's the status of purchase order 4500001234, and who needs to approve it next?" +- **HR & People:** "Show my remaining leave balance and submit a vacation request for the last week of July." The agent calls the SAP tools through the gateway under the employee's own identity. +- **Travel & Expense:** "Create an expense report from these receipts and check the status of my last reimbursement." +- **Procurement & Finance:** "What's the status of purchase order 4500001234, and who needs to approve it next?" ### Operational and customer-facing agents -- **Order-to-cash / customer service (SAP Customer Experience):** A service agent in Teams retrieves order status, delivery dates, and account history without leaving the conversation. -- **Supply chain & logistics:** Surface inventory levels, ASN status, or supplier data from SAP Business Network in a Copilot Studio agent for planners. +- **Order-to-cash / customer service:** A service agent in Teams retrieves order status, delivery dates, and account history without leaving the conversation. +- **Supply chain & logistics:** Surface inventory levels, ASN status, or supplier data in a Copilot Studio agent for planners. ### Insight in the flow of work (SAP Business Data Cloud) From 129186418e82a9f487b51b6598c20b7ac2865960 Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Tue, 23 Jun 2026 21:39:06 +0200 Subject: [PATCH 10/11] Refactor code structure for improved readability and maintainability --- .../drawio/copilot-studio+mcp-gateway.drawio | 49 ++++++++----------- .../copilot-studio+mcp-gateway.drawio.svg | 2 +- 2 files changed, 21 insertions(+), 30 deletions(-) diff --git a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio index b8df827409..6bcb213f4f 100644 --- a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio +++ b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/drawio/copilot-studio+mcp-gateway.drawio @@ -16,6 +16,16 @@ + + + + + + + + + + @@ -144,16 +154,6 @@ - - - - - - - - - - @@ -226,24 +226,15 @@ - - - - - - - - - - - - + - + + + - - + + @@ -264,11 +255,11 @@ - - + + - - + + diff --git a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg index 8c73f06410..fcd3a2127f 100644 --- a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg +++ b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg @@ -1,4 +1,4 @@ -
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file +
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file From aa48647576df6ee3488fec2321b567364b65ef1a Mon Sep 17 00:00:00 2001 From: Holger Bruchelt Date: Thu, 25 Jun 2026 15:40:41 +0200 Subject: [PATCH 11/11] Add contributor and update links in Copilot Studio MCP integration documentation - Added 'hobru' as a contributor in the readme file. - Updated the link to the Agent Gateway documentation for clarity. - Corrected the image path for the Copilot Studio and MCP Gateway diagram. --- .../images/copilot-studio+mcp-gateway.drawio.svg | 4 ---- .../1-copilot-studio-with-mcp/readme.md | 7 +++---- 2 files changed, 3 insertions(+), 8 deletions(-) delete mode 100644 docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg diff --git a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg deleted file mode 100644 index fcd3a2127f..0000000000 --- a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/images/copilot-studio+mcp-gateway.drawio.svg +++ /dev/null @@ -1,4 +0,0 @@ - - - -
Subaccount
BTP
Microsoft Azure

SAP S/4HANA

SAP Cloud and On-Premise Solutions

SAP SuccessFactors

SAP Business 

Networks

SAP Customer Experience
SAP Concur
SAP Business
Data Cloud
MCP Gateway
in SAP Integration Suite
 SAP CloudIdentity Services
TRUST
TRUST

ODATA / REST

Joule Studio

MCP builder

Custom MCPs

Agent & Tool

Gateway

Custom Agents

Managed MCPs

MCP

ODATA / REST

Custom-built 

Joule Agents

TRUST
Microsoft Entra ID

Microsoft AI 

others


Microsoft AI Foundry


Microsoft Azure


Copilot Studio

Azure API Management

MCP Server

API

Network
   

MCP

MCP

 \ No newline at end of file diff --git a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md index 89546d88da..7fc459bb7a 100644 --- a/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md +++ b/docs/ref-arch/RA0029/10-third-party-mcp-access/1-copilot-studio-with-mcp/readme.md @@ -30,6 +30,7 @@ unlisted: false contributors: - kay-schmitteckert - hterminasyan + - hobru discussion: last_update: author: hobru @@ -37,12 +38,10 @@ last_update: --- :::info Disclaimer -The [Agent Gateway](../1-a2a-and-mcp/readme.md#architecture) is not yet generally available (GA). The outlined architecture here shows ways how the integration with Copilot Studio and SAP can be done today. +The [Agent Gateway](../../1-a2a-and-mcp/readme.md#architecture) is not yet generally available (GA). The outlined architecture here shows ways how the integration with Copilot Studio and SAP can be done today. ::: -# Microsoft Copilot Studio and the MCP Gateway in SAP Integration Suite - [Microsoft Copilot Studio](https://www.microsoft.com/en-us/microsoft-365-copilot/microsoft-copilot-studio) is Microsoft's low-code platform for building and orchestrating AI agents across Microsoft 365, Teams, and custom channels. If you are new to Copilot Studio, start with the official product documentation: [Microsoft Copilot Studio documentation](https://learn.microsoft.com/en-us/microsoft-copilot-studio/). @@ -53,7 +52,7 @@ bespoke point-to-point integration code and without moving SAP data out of its s In this pattern, Copilot Studio acts as the **MCP client**, and the **MCP Gateway in SAP Integration Suite** acts as the governed entry point that exposes SAP APIs, integration flows, and data sources as MCP-compliant tools. Identity flows end-to-end through a trust relationship between **Microsoft Entra ID** and **SAP Cloud Identity Services**, so every tool call runs in the context of the signed-in business user and respects existing SAP authorizations. -![Copilot Studio and MCP Gateawy](images/copilot-studio+mcp-gateway.drawio.svg) +![drawio](drawio/copilot-studio+mcp-gateway.drawio) This gives organizations the best of both ecosystems: the conversational reach and authoring experience of Copilot Studio on the front end, and the enterprise-grade security, governance, and semantic richness of SAP BTP on the back end.