Skip to main content

Microsoft Copilot Managed Runtime

Let agents reach Microsoft 365 Copilot and Copilot Studio agents in your tenant as a registered app.

Connect it with: Service account. Microsoft Copilot Managed Runtime's own documentation: https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/copilot-apis-security-authentication.

What agents can do​

Connect Microsoft Copilot Managed Runtime so the agents working your tasks can reach it. With it connected, they can:

  • Call a Copilot Studio agent your organization built, through the Microsoft 365 Agents SDK, and use its answer in a task.
  • Use the Microsoft Graph application permissions you grant this app alongside Copilot, for example to read the organization's details.

Before you start​

  • A Microsoft 365 tenant with Copilot or Copilot Studio, and a Global Administrator or Privileged Role Administrator to grant admin consent.
  • An app registration for Jaah with the Microsoft Graph application permission Organization.Read.All (what the Test reads), plus the Copilot permissions your tenant offers for app-only access (API permissions > APIs my organization uses > Power Platform API, such as CopilotStudio.Copilots.Invoke), then Grant admin consent.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Microsoft Copilot Managed Runtime​

Jaah connects to Microsoft Copilot Managed Runtime with a service account, not with a sign-in button.

Connect with an API key​

Find each value first:

  • Tenant ID: Microsoft Entra admin center > Entra ID > Overview > Tenant ID, or a domain such as acme.onmicrosoft.com.
  • Client ID: Entra ID > App registrations > New registration (name it Jaah Copilot, single tenant), then the app's Overview > Application (client) ID.
  • Client secret: The app's Certificates & secrets > Client secrets > New client secret: copy the Value column (not the Secret ID) - Entra shows it once.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Microsoft Copilot Managed Runtime card.
  2. Name the secret and choose who can use it.
  3. Fill in Tenant ID, Client ID, Client secret.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Microsoft Copilot Managed Runtime with a service account, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah makes one read-only call to Microsoft Copilot Managed Runtime with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: tenant_id, client_id, client_secret.

Tell the agent in your task description which secret to use, for example “use the Microsoft Copilot Managed Runtime secret org/microsoft-copilot”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Microsoft Copilot Managed Runtime once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Microsoft Copilot Managed Runtime's side too, delete the service account's key in its cloud console.

Limitations​

  • Microsoft documents most Copilot APIs for signed-in users only; app-only (service principal) access to Copilot Studio agents is in preview and must be enabled for your tenant. Check the permissions your tenant offers before relying on it.
  • The Test proves the app and its secret against Microsoft Graph; it does not call Copilot itself, so a missing Copilot permission shows up only when an agent calls it.
  • Client secrets expire (at most 24 months). Add a new secret before the old one expires and select Replace.
  • Agents can do only what the connected Microsoft Copilot Managed Runtime service account and its roles allow.

Troubleshooting​

Test says Microsoft Copilot Managed Runtime rejected the client secret (401)

You copied the Secret ID, or the secret expired (AADSTS7000215). Create a new client secret, copy its Value, and select Replace.

Test says Microsoft Graph refused the organization read (403)

The app lacks Organization.Read.All, or admin consent was not granted. Add it under API permissions > Microsoft Graph > Application permissions and select Grant admin consent.

Agents get 401 or 403 calling a Copilot Studio agent

The app lacks the Copilot invoke permission, the agent is not published, or app-only access is not enabled in your tenant. Add the permission and grant admin consent, then publish the agent.

Still stuck? Select Test and read the result: it names the value Microsoft Copilot Managed Runtime refused and the status it answered.

FAQ​

Does this use a Copilot license?

Calls made through a Copilot Studio agent are billed to your tenant's Copilot Studio capacity, as for any other channel.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Microsoft Copilot Managed Runtime account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.