> For the complete documentation index, see [llms.txt](https://docs.meterian.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meterian.io/the-meterian-webapp/advanced-functionalities/sso-configuration/azure-ad.md).

# Azure AD

In this page you can find guidance on how to set up the Azure AD tab in the [SSO configuration](/the-meterian-webapp/advanced-functionalities/sso-configuration.md). Before you start, you need to have registered an application in your Azure AD tenant so that the dashboard can authenticate users against it. The values to enter in the form come from that application's settings.

### Fields

**Name** — a label that identifies this configuration inside Meterian. Only letters, numbers, hyphens and underscores are allowed, and it cannot be changed once saved.

**Tenant ID** — the identifier of the Azure AD tenant that owns the application. You can find it in the Azure portal under "Microsoft Entra ID" → "Overview" as "Tenant ID".

**Client ID** — the application (client) ID of the registered app. In the Azure portal, open the app registration and copy the value listed as "Application (client) ID".

**Client Secret** — a secret created for the same app registration, under "Certificates & secrets". Make sure to copy the secret value at creation time, as Azure will not show it again.

**Scopes** — the OAuth scopes to request when authenticating users. Type each scope and press Space, Enter or comma to add it as a tag. Meterian requires `openid`, `name`, `email` in order to work. The recommendation is to use the `User.Read` claim which provides all the three fields.

<figure><img src="/files/nYr8yBtMPCkQHVC3bNUn" alt=""><figcaption></figcaption></figure>

### After saving

Once the configuration is saved, the "Login URL" section becomes available. Share that URL with the users who should log in via Azure AD — they will be redirected to Microsoft to sign in, and then back into Meterian.

Azure AD does not require any extra attribute mapping: user identity is taken from the standard claims returned by Microsoft.

### Azure AD Teams <a href="#azure-a-d-teams" id="azure-a-d-teams"></a>

{% hint style="warning" %}
**Note:** Azure AD Teams is bound to its own feature flag, separate from the Azure AD SSO flag. It must be enabled on your account before the section appears — contact Meterian support to request it.
{% endhint %}

Once Azure AD SSO is saved, an “Azure AD Teams” section appears below it. This is where you tell Meterian which Azure AD groups grant access to the account and which ones map to your Meterian teams.

The table has two predefined rows that you cannot remove:

* **Everyone** — paste the Azure AD group ID whose members should have access to the Meterian account. Any user authenticated via Azure AD who is not in this group is denied access.
* **Admins** — paste the Azure AD group ID whose members should be Administrators of the Meterian account. Membership of this group is the only way to grant the Administrator role when Azure AD Teams is in use.

Below the predefined rows you can add additional associations: pick a Meterian team from the dropdown, paste the corresponding Azure AD group ID, and click “Add”. Users in that Azure group will be automatically added to the chosen Meterian team when they log in. You can edit or remove these custom associations at any time using the icons in the “Actions” column.

While Azure AD Teams is active, the Teams page displays a notice — “Teams are managed by Azure Active Directory” — and the Administrator role can no longer be assigned manually from the Meterian UI: it is driven entirely by membership of the “Admins” Azure group.

<figure><img src="/files/w45qazGk2ydLnxyLiJ5i" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.meterian.io/the-meterian-webapp/advanced-functionalities/sso-configuration/azure-ad.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.