AegisAI
Why Copilot first

The platform with the gravity.

Microsoft is shipping Copilot into Word, Excel, Teams, Outlook, Power BI, Dynamics, and the Power Platform. By the time SAP API Policy 4.2026a hits, Copilot will be the dominant AI agent reaching for SAP data inside enterprise tenants. The Copilot Studio connector is therefore the highest-leverage integration AegisAI ships — one connector, every Microsoft surface.

Setup

Three steps. Fifteen minutes.

1. Register in Entra ID

App registration with redirect URI https://global.consent.azure-apim.net/redirect/aegisai, a client secret, and an exposed scope query.execute. So the user's token is what reaches AegisAI — not the bot's.

2. Import the connector

Power Platform → Custom Connectors → New → Import an OpenAPI file. Upload connector-swagger.json from samples/connectors/copilot-studio/. Paste your Entra IDs into the Security tab.

3. Wire the topic

Copilot Studio → your copilot → Topics → Add → From file → upload topics/ask-aegisai.yaml. Trigger phrases are pre-filled. Publish and test in the chat pane.

What's in the kit

Three files in samples/connectors/copilot-studio/.

FilePurpose
README.mdSetup walkthrough with the exact Entra ID and Power Platform steps.
connector-swagger.jsonSwagger 2.0 ready to import into Power Platform's custom connector wizard. Pre-shaped for the vnd.microsoft.copilot+json response.
topics/ask-aegisai.yamlA Copilot Studio topic that fires the connector and renders the response as an adaptive card. Trigger phrases included.
The single most important thing

Don't let Copilot use a service principal.

Copilot Studio's default for Custom Connectors is to authenticate with a service principal. Do not pick that option for AegisAI. If you do, every request looks like the bot, no request is attributable to a human, and AegisAI's identity-propagation guarantees collapse to "the bot did it."

The OAuth 2.0 + delegated permission setup in README.md ensures Copilot forwards the signed-in user's Entra ID token. Verify it: hit /api/audit/tail after a query and confirm the sub field is the user's UPN, not the bot's app id.

Want a live walkthrough?

We'll join your tenant for a 30-minute screenshare and stand the whole thing up with you.

Book a screenshare