In Microsoft 365 Copilot, users can't add Diri themselves. Your Microsoft 365 administrator builds a Diri agent in Copilot Studio once and publishes it to Microsoft 365 Copilot and Teams. Each user then opens the agent and signs in to Diri with their own account, and works as themselves.
Bring your own AI must be activated for your organisation first: see Getting started. We are happy to go through the setup with your Microsoft 365 administrator; contact support@cyrigo.com.
EnforcementUsageCredits./mcp, for example https://app.diri.ai/mcp.Diri. If Copilot Studio offers to build it by chatting, fill in the form instead.DiriDiri risk and compliance system: reads registers and exports data, and proposes imports and suggestions that a person reviews and publishes in Diri.https://app.diri.ai/mcpNo token or key is entered anywhere. Each person who uses the agent signs in to Diri with their own account, and Copilot renews the sign-in itself.
In Copilot Studio's test pane, ask: "Where am I working in Diri?" The agent should call Diri and name your organisation and module.
A user opens the Diri agent in Microsoft 365 Copilot or Teams and asks it something. The first time, the agent shows a sign-in card: the user signs in to Diri with their own account and approves the connection. Diri's approval page says where the agent will work (the organisation the user has open in Diri), which registers it may read, whether it may propose changes for review and make suggestions, and that what it reads is processed by Microsoft under your organisation's agreement with them.
Paste this into the agent's Instructions. It is deliberately short: when the agent starts, Diri gives it the full and current working method, so the agent stays up to date when Diri changes.
You help the user work with Diri, their risk and compliance system, through the Diri tools. You act as the user, in the organisation and module they have open in Diri. Nothing you send reaches a register until a person publishes it in Diri.
1. In every conversation, call diri_start before anything else, and tell the user which organisation and module you are working in.
2. diri_start returns the working method (workingMethod.text). Follow it exactly for the whole conversation; it takes precedence over these instructions.
3. Before you review data or propose anything, read the guide with diri_guide, topics 0, 4, 5 and 6.
4. When diri_start lists a playbook for the task, read it with diri_playbook and follow it.
5. Submit only what the user has agreed to. Never say something is in Diri until diri_read_import reports it as "published"; a person publishes, you cannot.
6. When Diri refuses a call, tell the user its message and what they can do about it.
7. Answer in the user's language; diri_whoami says which.| What you see | What to do |
|---|---|
EnforcementUsageCredits in the test pane or in Teams |
The environment has no Copilot Credits. Allocate capacity or link a pay-as-you-go plan in the Power Platform admin centre, or test with a user who has a Microsoft 365 Copilot licence in Teams. |
| Copilot Studio hangs on "Creating connection" | Microsoft's connector service can't reach Diri, usually because the environment is outside the regions Diri accepts. Contact support@cyrigo.com with the environment's region. |
| After signing in, the Diri window shows Diri's start page | The sign-in ran in its own window and is done. Go back to the Copilot Studio window, where the connection appears. |
| The tool can't be added, or is blocked | Your environment's data policy blocks custom connectors. Your Power Platform administrator can allow them for the environment. |
| Diri refuses the sign-in: pilot, AI access off, or this kind of AI client not allowed | See Getting started. The message says which step is missing. |
| The agent doesn't know about something new in Diri | Refresh the Diri tool in Copilot Studio. |