> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector.md).

# Microsoft Entra ID Connector

Version 1.1.0 · Vendor: equipme · Module: `equipme.microsoft.entraid`

The Microsoft Entra ID connector lets your workflows manage Microsoft's identity and access platform, formerly Azure Active Directory. It covers the everyday administration work — users, groups, devices, licenses, directory roles and app registrations — and adds a family of monitors that watch your tenant for you: expiring app secrets, inactive accounts, missing MFA registration and more.

{% hint style="info" %}
equipme talks to Microsoft Entra ID in three different places. This section is about the **workflow connector**, which writes into Entra from your flows.

If you are looking for importing employees into equipme from Entra, see HR-Sync. If you are looking for signing in to equipme with Entra credentials, see Single Sign-On.
{% endhint %}

#### Setting up the connection

The connector uses OAuth2 with Microsoft sign-in and delegated permissions. The first time you use one of its components, you are asked to sign in with a Microsoft account.

Three things are worth knowing before you start:

**The account matters.** Delegated permissions never widen what an account is allowed to do. The account you sign in with needs the matching Entra ID role for the task — User Administrator for user management, Cloud Application Administrator for app registrations, and so on.

**Each component asks only for what it needs.** Components request their own scopes, so the first use of a new component may require signing in again and confirming admin consent.

**If you see "Insufficient privileges to complete the operation",** the connection was authorised before the component you are now using existed. Disconnect the connection in the flow, sign in again and confirm admin consent so the new scopes end up in the token.

#### What this section contains

Start with **Working with the Connector**. It explains the patterns that repeat across every component — how lists are returned, how monitors report, how triggers behave — so the component pages themselves stay short.

After that, the pages are grouped by area: users, groups, devices, licenses, directory roles, app registrations, authentication, and monitoring. **Workflow Examples** shows how these combine into complete processes, and **Required Permissions** lists the scopes each area needs.


---

# 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, and the optional `goal` query parameter:

```
GET https://hub.equipme.io/documentation/automation/connectors/microsoft-entra-id-connector.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.