- Home
- Resources
- Integrations
- Microsoft Entra ID
Microsoft Entra ID n8n integrationAutomate Microsoft Entra ID with n8n.
Your directory changes every week, and most of it still happens by hand. The Microsoft Entra ID n8n integration puts 12 operations and 2 resources, User and Group, inside a workflow: open an account, update it, move it between groups, or pull the full list.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Microsoft Entra ID n8n integration actually cover?
The Microsoft Entra ID node connects n8n to your Microsoft identity directory. It ships with n8n, so there is nothing to install and nothing extra to pay on the n8n side: pick the credential, pick a resource, pick an operation. Two resources are exposed, User and Group, with 12 operations between them, covering creation, reading, updating, deletion, and group membership in both directions.
The first thing teams build with it is onboarding. A row lands in a Google Sheets tab when HR validates a hire, the workflow runs user.create with the account details, then user.addGroup for each team the person belongs to. The account exists before the laptop is unboxed, and nobody retypes a display name.
The second one is the reverse, and it matters more. On the day someone leaves, an update on the user with Account Enabled switched off blocks the sign-in immediately, a removal from each group cuts the shared access, and a delete closes the file once the retention window has passed. A message posted to Slack at the end of the run tells the IT channel what was touched, which is what an auditor asks for later.
The third is plain reporting. Get Many on users and on groups, with Return All enabled, gives you the whole directory in one execution, and the Filter field narrows it when you only want part of it. Push the result into Postgres and you have a snapshot you can compare from one month to the next, without asking anyone to run an export by hand.
When an operation is not in the node's catalogue, the HTTP Request node calls any endpoint of the tool's API and reuses the same credential through its predefined authentication. That is the standard way out: you stay in the same workflow and you keep one place where the connection is configured.
One behavior is worth knowing before you chain nodes. Allow External Senders and Auto Subscribe New Members cannot be updated right after a group is created, so a workflow that creates a group and then sets those options needs a Wait node between the two, configured to pause for at least two seconds so the group finishes initializing. If you would rather see these patterns built live on your own tenant, the n8n training covers them.
How do you connect n8n to Microsoft Entra ID ?
- 01
Register the application on the Microsoft side
Open the Microsoft Application Registration Portal and select Register an application. Give it a Name, then under Supported account types choose accounts in any organizational directory and personal Microsoft accounts. Copy the OAuth Callback URL shown in the n8n credential and paste it into Redirect URI (optional), with Select a platform set to Web. Select Register to finish.
- 02
Generate the client secret and connect the account
Copy the Application (client) ID from the app page into n8n as the Client ID. Then go to Certificates & secrets, select + New client secret, write a Description such as
n8n credential, and select Add. Copy the secret from the Value column into n8n as the Client Secret, select Connect my account, sign in to Microsoft and allow the app to access your info. - 03
Check the tenant prerequisites before the first run
You need a Microsoft Azure account and at least one user account with access to the service. If that account is managed by a corporate Microsoft Entra directory, an administrator has to enable the option that lets users consent to apps accessing company data on their behalf. Running on a government cloud tenant, US Government, US Government DOD or China? Select the matching Microsoft Graph API Base URL in the credential configuration.
The 12 operations the Microsoft Entra ID node exposes
The Microsoft Entra ID node exposes 12 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
| Resource | Create | Get | Get Many | Update | Delete | Add to Group | Remove from Group |
|---|---|---|---|---|---|---|---|
| Group | ✓ | ✓ | ✓ | ✓ | ✓ | ||
| User | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Operations index
Group
5 operationsCreate group
group.createWhat you see in n8n
Notes & use cases
Creates a group in the directory, ready to receive members in the same workflow.
Key parameters
- Group Name: the name shown in the address book for the group.
- Group Email Address: the mail alias, local part only, without the domain (
alias). - Mail Enabled: whether the group is mail-enabled.
- Group Type: Unified for a Microsoft 365 group, or Security.
- Membership Type: Assigned to add specific users, or Dynamic to let a Membership Rule such as
user.department -eq "Marketing"add and remove them for you.
Delete group
group.deleteWhat you see in n8n
Notes & use cases
Removes an existing group from the directory.
Key parameters
- Group to Delete: a resource locator, so you can pick the group from the list n8n loads from your tenant, or feed it from an earlier node with an expression like
{{ $json.field }}.
Get group
group.getWhat you see in n8n
Notes & use cases
Retrieves the data of one specific group, on its own or with its member list attached.
Key parameters
- Group to Get: the group you want, picked from the list or passed in from a previous step.
- Include Members: an option that brings the members back with the group, instead of a second call.
- Output: Simplified for a readable set, Raw for everything, or Selected Fields when you name what you need.
Get many groups
group.getAllWhat you see in n8n
Notes & use cases
Lists the groups of the tenant, all of them or a narrowed selection.
Key parameters
- Return All: enabled, n8n walks the pages of the API until every group is back; disabled, Limit caps how many come through.
- Filter: a query parameter such as
startswith(displayName, 'a'). Left empty, all the groups are returned.
Update group
group.updateWhat you see in n8n
Notes & use cases
Edits an existing group without recreating it. The 11 entries of Update Fields are all optional, so you send only what changes.
Key parameters
- Group to Update: the target group.
- Visibility: Private or Public.
- Description: the description carried by the group.
- Allow External Senders and Auto Subscribe New Members: wait a few seconds before editing these two on a group that was just created.
User
7 operationsAdd user to group
user.addGroupWhat you see in n8n
Notes & use cases
Puts an existing user into an existing group. Both objects have to exist already, so this operation usually sits after a creation step.
Key parameters
- Group: the destination group, chosen from the list or resolved from the incoming item.
- User to Add: the account that joins it.
Create user
user.createWhat you see in n8n
Notes & use cases
Opens a new account in the directory. Five fields are required, the rest of the profile sits in the 36 entries of Additional Fields.
Key parameters
- Display Name: the name shown in the address book.
- User Principal Name: the UPN, for instance
NathanSmith@contoso.com. - Mail Nickname: the mail alias for the user.
- Password and Account Enabled: the initial password, and whether the account is active on creation.
- Force Change Password: Next Sign In, or Next Sign In with MFA.
Delete user
user.deleteWhat you see in n8n
Notes & use cases
Deletes an existing user account.
Key parameters
- User to Delete: a resource locator, so the account is picked from the tenant list or resolved from the item coming out of the previous node.
Get user
user.getWhat you see in n8n
Notes & use cases
Reads one account and returns its profile data.
Key parameters
- User to Get: the account to read.
- Output: Simplified, Raw, or Selected Fields when the workflow only needs part of the profile.
- Fields: the exact fields added to the output when Selected Fields is on.
Get many users
user.getAllWhat you see in n8n
Notes & use cases
Pulls a list of accounts, from a handful to the whole directory.
Key parameters
- Return All: on, the node chains the API pages to bring back every user; off, Limit stops it earlier.
- Filter: a query parameter, for example
startswith(displayName, 'a'). - Output and Fields: trim the payload to the columns your destination actually stores.
Remove user from group
user.removeGroupWhat you see in n8n
Notes & use cases
Takes a user out of a group. The account stays in the directory, only the membership goes away.
Key parameters
- Group: the group the person leaves.
- User to Remove: the account losing that membership.
Update user
user.updateWhat you see in n8n
Notes & use cases
Changes an account that already exists. Update Fields holds 41 optional entries and only the ones you fill in are sent.
Key parameters
- User to Update: the account to edit.
- Account Enabled: the switch that turns a sign-in on or off.
- Job Title: the title carried by the user.
- Password: it has to satisfy the minimum requirements set by the password policies.
Need help automating Microsoft Entra ID with n8n?
A person reads every message.
Questions that come up next
01Is the Microsoft Entra ID n8n integration free?
02What credentials do you need for the Microsoft Entra ID node?
03What are the limits of the Microsoft Entra ID node in n8n?
04Is there a Microsoft Entra ID trigger in n8n?
05n8n or Make for Microsoft Entra ID?
Get our weekly integration tips.
No spam. Unsubscribe anytime.



