plugin tool for SAP PRD have Copilot agent make charts for us?

Use Microsoft Copilot Studio’s SAP OData connector—or an HTTP connector for an existing REST/SOAP API—to retrieve SAP PRD data, then return structured results to your Microsoft 365 Copilot agent and render them through a host-tested Adaptive Card, Excel, or Power BI visualization.

There is no single plug-in that automatically turns arbitrary SAP PRD data into charts. The supported implementation depends on how the existing agent was built.

Recommended path: Copilot Studio agent

Copilot Studio provides SAP connectors and can expose an agent through Microsoft 365 Copilot. It supports SAP OData, HTTP/custom connectors, and the SAP ERP connector for BAPI/RFC scenarios.^1^

Prerequisites and ownership

• SAP administrator: Enable a read-only OData service containing the required chart dimensions and measures.
• SAP/BTP or infrastructure administrator: Provide the service base URI and connectivity.
• Copilot Studio maker: Create the connection, action, instructions, and result presentation.
• Security/Entra administrator: Approve authentication, connection policies, and production-data access where required.
• Agent owner/tester: Publish and test the agent with a least-privileged SAP account.

Also verify that the Power Platform environment allows the SAP connector under its data-loss-prevention policies and that the makers can create connections and agents. Licensing and connector availability must be checked for the tenant and environment.

1. Expose SAP PRD safely

Choose the route matching the SAP landscape:

• SAP BTP already in use: Expose and protect the API through SAP API Management, Integration Suite, or an application proxy. Copilot Studio can call it with the SAP OData or HTTP connector. SAP Cloud Connector can forward requests to an SAP system behind a firewall.^2^
• OData behind a corporate firewall without that BTP route: Use an on-premises data gateway.
• Older SAP using BAPI/RFC: Use the on-premises data gateway, SAP Connector for Microsoft .NET, and the SAP ERP connector.^3^

Prefer principal propagation where available so each Copilot user reaches SAP as that user; this preserves SAP authorization boundaries and user-context auditing.^2^

2. Create and validate the SAP OData connection

For the documented Power Automate route:

1. Open Power Automate and create a flow.
2. Add an SAP OData query action.
3. Create the SAP connection.
4. If SAP PRD is behind the firewall, select Data Gateway, then select the configured gateway.
5. Enter the SAP OData base URI supplied by the SAP administrator.
6. Configure a read query that returns chart-ready rows, for example:
   • category or date;
   • numeric value;
   • unit/currency;
   • optional series or grouping.
7. Test the flow and verify that SAP returns only records the test user is authorized to read.

The SAP OData connector supports OData V2, V3, and V4 and can connect to systems including ECC and S/4HANA. ECC or earlier systems require OData endpoints that might not exist out of the box.^4^

3. Add it to the agent

In the existing Copilot Studio agent:

1. Add an action that invokes either:
   • the SAP connector directly; or
   • the tested Power Automate flow when transformation, aggregation, or extra validation is needed.
2. Map agent inputs such as date range, plant, company code, or product to the action inputs.
3. Map the returned category/value rows into the agent output.
4. Add instructions telling the agent to:
   • request missing filters;
   • use only returned SAP data;
   • identify the selected period and unit;
   • provide a table if chart rendering is unavailable.
5. Test with a least-privileged SAP user, verify the SAP audit record is attributed correctly, publish the agent, and test it in the intended Microsoft 365 host.

Chart presentation

Adaptive Card response templates can format API results in a Microsoft 365 Copilot declarative agent, but API plugins must be actions inside a declarative agent; they are not standalone Microsoft 365 Copilot experiences.^5^

This is a separate implementation path from adding a connector or Power Automate action to a Copilot Studio agent. Use it when the current Microsoft 365 agent is a declarative agent with an API plugin, rather than a Copilot Studio agent. The plugin calls the secured SAP-facing API and attaches an Adaptive Card response template.

Chart elements are specifically documented for Teams, including bar, line, pie, donut, gauge, and stacked charts. Host support must therefore be tested in the exact Microsoft 365 Copilot surface being used. Configure a real table or FactSet fallback containing the same values—not merely fallback text—when chart capabilities are unavailable.^6^

For a more reliable, full-featured dashboard experience, use Power BI or pass the structured data to Excel. Access, licensing, embedding, and SAP permissions still need separate validation.

References

1. Copilot Studio with SAP
2. SAP Business Technology Platform with SAP API Management and SAP Cloud Connector
3. On-premises data gateway with access to BAPIs, RFCs, and OData services
4. Get started with the SAP OData Connector
5. Adaptive Card response templates for API plugins for Microsoft 365 Copilot
6. Charts in Adaptive Cards