Skip to main content

Azure

Manage Azure resources in one subscription with a Microsoft Entra service principal.

Connect it with: Service account. Azure's own documentation: https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal.

What agents can do​

Connect Azure so the agents working your tasks can reach it. With it connected, they can:

  • Inspect resources, resource groups and deployments in the subscription.
  • Read logs and metrics to investigate an incident.
  • Create or change resources with the Azure CLI or an SDK, if the role you assigned allows it.

Before you start​

  • An Azure subscription, and permission to register an app in Microsoft Entra ID and assign it a role on the subscription (Owner or User Access Administrator).
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Azure​

Jaah connects to Azure with a service account, not with a sign-in button.

Connect with an API key​

Find each value first:

  • Tenant ID: Azure portal > Microsoft Entra ID > Overview > Tenant ID, or a domain such as acme.onmicrosoft.com.
  • Client ID: Microsoft Entra ID > App registrations > New registration (name it Jaah), 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) - Azure shows it once.
  • Subscription ID: Azure portal > Subscriptions > the subscription > Overview > Subscription ID. Then Access control (IAM) > Add role assignment: give the app the role agents need, such as Reader or Contributor.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Azure card.
  2. Name the secret and choose who can use it.
  3. Fill in Tenant ID, Client ID, Client secret, Subscription ID.
  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 Azure 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 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, subscription_id.

Tell the agent in your task description which secret to use, for example “use the Azure secret org/azure”.

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 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's side too, delete the service account's key in its cloud console.

Limitations​

  • Azure has no sign-in button for apps like Jaah: you connect with a service principal's client secret.
  • Agents get exactly the role you assign on the subscription. Reader keeps them read-only.
  • Client secrets expire (6 to 24 months is typical). Add a new secret before the old one expires and select Replace.
  • Agents can do only what the connected Azure service account and its roles allow.

Troubleshooting​

Test says Azure refused the credentials: AADSTS7000215 Invalid client secret provided

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

Test says the app cannot read the subscription

The app has no role on that subscription. Add one under Subscriptions > Access control (IAM) > Add role assignment.

Test says AADSTS700016 application not found in the directory

The client ID and tenant ID do not belong together. Copy both from the same app registration's Overview.

Still stuck? Select Test and read the result: it names the value Azure refused and the status it answered.

FAQ​

Can one secret reach several subscriptions?

The Test checks the subscription you enter. The app can hold roles on others too, and agents can reach them with the same secret.

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 account?

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