Microsoft 365 Copilot
Microsoft 365 Copilot’s built-in chat runs on Microsoft’s own model, and you cannot redirect it to a gateway, the same way you cannot redirect ChatGPT. That does not mean it is ungovernable: you govern it on the tool plane.
See Connect your harness for the model-plane vs tool-plane distinction.
Tool plane: govern what Copilot does
Section titled “Tool plane: govern what Copilot does”Register TapPass as an MCP server or a connector so Copilot’s tool calls and data reach run through TapPass policy and audit, even though the model stays Microsoft’s. This is the action side, which is where most of the risk lives.
Model plane: use a custom engine agent
Section titled “Model plane: use a custom engine agent”If you want to govern the model itself inside Microsoft 365 Copilot, build a custom engine agent. You own its orchestrator, so you point its model endpoint at TapPass, and it surfaces natively inside Copilot.
| Surface | Model plane | Tool plane |
|---|---|---|
| Built-in Copilot chat | No (model locked) | Yes |
| Custom engine agent in Copilot | Yes | Yes |
Verify
Section titled “Verify”For tool-plane connections, trigger a tool call in Copilot and confirm the tool event is governed in the TapPass console.