Azure Graph & Entra
Read and manage your Microsoft Entra directory - users, groups, apps - through Microsoft Graph as an app.
Connect it with: Service account. Azure Graph & Entra's own documentation: https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-client-creds-grant-flow.
What agents can do
Connect Azure Graph & Entra so the agents working your tasks can reach it. With it connected, they can:
- Look up users, groups and group members in your directory.
- List app registrations and service principals, for example to audit secrets that are about to expire.
- Read sign-in and audit logs to investigate an incident, if you granted AuditLog.Read.All.
- Create users or change group membership, if you granted the matching write permissions.
Before you start
- A Microsoft Entra tenant, and a Privileged Role Administrator or Global Administrator to grant admin consent.
- An app registration for Jaah with the Microsoft Graph application permissions agents need. The Test needs Organization.Read.All; add others, such as User.Read.All or Group.Read.All, for what tasks do. Then select Grant admin consent on the app's API permissions page.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Azure Graph & Entra
Jaah connects to Azure Graph & Entra 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, 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:
- In Jaah, open Secrets, select New, and pick the Azure Graph & Entra card.
- Name the secret and choose who can use it.
- Fill in Tenant ID, Client ID, Client secret.
- 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 Azure Graph & Entra with a service account, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Azure Graph & Entra 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 Azure Graph & Entra secret org/azure-graph”.
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 Azure Graph & Entra 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 Azure Graph & Entra's side too, delete the service account's key in its cloud console.
Limitations
- This is app-only access: agents act as the Jaah app, not as a person, and see everything the granted application permissions allow across the tenant. Grant the least you need.
- Client secrets expire (at most 24 months). Add a new secret before the old one expires and select Replace.
- Mail, calendar and files of individual users are better connected per person with Microsoft 365.
- Agents can do only what the connected Azure Graph & Entra service account and its roles allow.
Troubleshooting
Test says Azure Graph & Entra 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 Azure Graph & Entra rejected the tenant ID or client ID (400)
The tenant or the app does not exist, or they do not belong together (AADSTS90002 or AADSTS700016). Copy both from the same app registration's Overview.
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.
Still stuck? Select Test and read the result: it names the value Azure Graph & Entra refused and the status it answered.
FAQ
How is this different from Azure?
Azure manages cloud resources in a subscription. Azure Graph & Entra reaches your directory and Microsoft 365 data through Microsoft Graph.
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 Azure Graph & Entra account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.