SAP–Power Platform Integration Architect

An SAP + Microsoft architect in your Copilot Studio agent. Describe your landscape or upload a requirements document, and get a clear, sourced recommendation for the three questions that come up in almost every SAP + Microsoft conversation:

What you get

1. An answer straight away. No questionnaire first: the agent uses what you wrote and uploaded, fills the gaps with sensible assumptions, and says openly which assumption could change the recommendation.
2. An HTML architecture report, attached to the reply: summary, positioning table, data-flow and identity-flow diagrams, facts and assumptions, alternatives, prerequisites by role, implementation steps, risks, open questions, and sources. It opens in any browser and can be shared as-is.
3. A “Refine this answer” template at the end of every reply, pre-filled with the values the agent used. Copy it, correct what’s wrong (“not sure” is fine), send it back, and you get a What changed summary, an updated recommendation and a new version of the report.

Before you start

• A Copilot Studio agent on the GitHub Copilot harness. Skills are available on that harness.
• Code execution and file uploads available to the agent (code execution is native on the GitHub Copilot harness). The report is generated by a small Python script that uses only the standard library: nothing to install.
• Recommended: web search or the Microsoft Learn MCP server as a tool. With it, the agent checks the Microsoft Learn and SAP Architecture Center pages that change most often before answering. Without it, the agent uses its built-in baseline and says so in the report.
• Recommended: Microsoft Entra ID authentication on the agent.

Set it up

1. Download the bundle (.zip) from this page.

2. In Copilot Studio, open your agent → Build → Skills → Add skill → Upload a skill, and upload the .zip as is (don’t unzip it).

3. Optional: under Tools, add web search or the Microsoft Learn MCP server.

4. Optional: add these lines to the agent’s instructions:

   You are an architecture advisor for organizations that run SAP and Microsoft technologies.
   For questions about SAP with Power Platform, Copilot Studio, Microsoft 365 Copilot, SAP Joule,
   SAP BTP, Fiori or extensibility, use the sap-power-platform-integration-architect skill.
   State assumptions instead of asking questions first. Answer in the user's language.

5. Optional: add suggested prompts, for example “Joule or Copilot Studio — which should we use?”, “How do we connect SAP to a Copilot Studio agent?”, “Fiori or Power Apps for this app?”.

6. Test it in the preview pane with one of the prompts below.

Try it

• “We run S/4HANA on RISE in Azure and want a Copilot Studio agent in Teams to approve purchase orders with each user’s own SAP permissions. What’s the best way?”
• “We already have Joule. Why would we also need Copilot Studio, and can they work together?”
• “Fiori or Power Apps for a mobile goods-receipt app used by warehouse staff?”
• “Our ECC system only has custom Z-BAPIs. A canvas app needs to create maintenance notifications.”
• Upload sap-landscape.docx and ask: “Propose the integration architecture for these use cases.”

What an answer looks like

Recommended: SAP OData connector through Azure API Management (confidence: medium) Why: SAP runs on RISE in Azure, so API Management reaches it over virtual network peering without an extra proxy · approvals must respect each user’s SAP authorizations · your team already runs Azure. Flow: Copilot Studio agent in Teams → SAP OData connector → Azure API Management → S/4HANA Identity: Entra ID user → API Management exchanges the token for SAML → SAP named user Alternatives: SAP BTP with Cloud Connector, if BTP becomes your API front door Before you build: activate the purchase order OData service (SAP Basis) · SAML trust (SAP Basis) · app registrations (Entra admin) · API Management in a peered network (Azure admin) · data loss prevention policy for the SAP connector (Power Platform admin) Assumptions: released OData APIs exist (assumed) — if only BAPIs exist, the recommendation changes to the SAP ERP connector through the on-premises data gateway. Report: po-approvals-in-teams-v1.html attached · baseline 2026-10-21

Refine this answer — lines marked (assumed) are my main guesses; correct any line and send it back:

SAP system: S/4HANA on RISE (given)                          [ECC | S/4HANA on-prem | RISE/private cloud | S/4HANA Cloud public]
Interfaces available: released OData APIs (assumed)          [standard BAPI/RFC | custom Z-RFC | OData | SOAP | SAP GUI only | not sure]
Already in place: none (assumed)                             [data gateway | Azure API Mgmt | BTP + Cloud Connector | Integration Suite | none]
Entra ID ↔ SAP Cloud Identity Services: not sure (assumed)   [trust exists | no | planned | not sure]
Anything else:

What’s covered

• Nine connection patterns:
  • SAP ERP connector through the on-premises data gateway
  • SAP OData connector through the gateway
  • SAP OData connector through Azure API Management
  • SAP BTP with Cloud Connector
  • SAP MCP Gateway on SAP Integration Suite
  • custom connector through API Management
  • Azure Logic Apps (IDocs, events, high volume)
  • Power Automate desktop with SAP GUI (as a bridge)
  • analytics connectors
• Single sign-on chains: Kerberos and certificates for the SAP ERP connector, Entra ID → API Management → SAML, and Entra ID federated with SAP Cloud Identity Services with principal propagation.
• Assistants: the ready-made Joule ↔ Microsoft Copilot integration, Copilot Studio agents calling SAP, delegating to Joule agents (agent-to-agent), handoff from Microsoft’s Employee Self-Service agent, Joule Studio, and Copilot Studio agents embedded in the Fiori launchpad or SAP Build Work Zone.
• Where to extend: key-user extensibility, ABAP Cloud, SAP Build and SAP BTP, Power Platform, RPA, and SAP’s clean-core approach (released vs classic APIs).
• Accelerators when they fit, such as the SAP Procurement template for Power Platform.

Keeping it current

The guidance is anchored to dated Microsoft Learn, SAP Help and SAP Architecture Center sources (baseline 2026-10-21). Pages that change often — authentication options, preview/GA status, Joule integration scope, agent-to-agent availability — are flagged, and the agent re-checks them at runtime when it has web search or the Microsoft Learn MCP server. Every report states whether it was checked live or uses the baseline.

What it won’t do

• No licensing, pricing or legal advice. Questions about SAP’s API policy, indirect access, or comparing SAP and Microsoft licences are referred to your SAP and Microsoft account teams.
• No connection to your systems. It doesn’t reach or test SAP, Azure or Power Platform; every step must be validated by your SAP Basis, security and Power Platform admins.
• No invented API names. Suggested SAP services or BAPIs are labelled “verify in SAP Business Accelerator Hub / with SAP Basis”.
• No vendor bias. Joule, SAP Build and Fiori are presented with their strengths, and the answer often combines SAP and Microsoft options.

Privacy

• Don’t upload documents you’re not allowed to share with your agent.
• If an uploaded document contains passwords, keys or connection strings, the agent leaves them out of the answer and the report and tells you.
• The report is a single self-contained HTML file with no scripts and no external calls.

Troubleshooting

Under the hood

Key sources

• Copilot Studio with SAP
• About SAP with Microsoft AI
• Joule and Microsoft Copilot integration
• Power Platform and SAP connection options
• SAP and Power Platform architecture workflow
• SAP Architecture Center