Bring company context to a Copilot agent.

The intended connection

The intended integration connects Steer’s authenticated context service to a Copilot Studio agent, which an organisation can publish into Microsoft 365 Copilot. This is a specific agent experience requiring administrator setup. It is not currently available and does not imply that Steer will automatically appear in every Copilot conversation or Office application.

What this can help with

• Intended use: ask a company agent which approved process applies.
• Intended use: retrieve eligible references alongside owner-approved guidance.
• Intended use: use a shared context policy across supported AI destinations.

Register your interest

1. Select Microsoft Copilot when joining the waitlist.
2. Let us know whether your organisation already uses Copilot Studio.
3. We will confirm licensing, administrator setup and tested surfaces before onboarding.

Scope and availability

• Planned; this page is not evidence of a deployed Copilot integration.
• The intended route is a published Copilot Studio agent, not blanket access across all Copilot surfaces.
• User identity, tenant binding, access loss and real agent invocation require end-to-end verification.

Steer is onboarding companies in stages. Join the waitlist to discuss your setup. Read about access and accountability.

What to check before connecting

The route being investigated is Steer’s authenticated MCP service, connected to a Copilot Studio agent, followed by publication and testing in the intended Microsoft 365 Copilot surface. These are separate steps.

• Confirm the organisation’s Copilot Studio licensing, administrator policy and intended publication surface.
• Microsoft documents connecting an existing MCP server using its onboarding wizard or a custom connector. Check transport and authentication compatibility before treating a server as usable.
• Bind the authenticated user to the correct organisation and verify eligible context. A tool argument supplied by a model is not a trustworthy identity.
• Test an ordinary employee question, source updates, access loss and revocation through the published agent. A successful connection alone is insufficient.

Microsoft’s Copilot Studio MCP documentation documents the platform capability; it does not verify Steer availability.

Plan the context, ownership and access

Check permissions and ownership, test source updates and evaluate the connection in a real task.