Resources · Make integration

Microsoft Entra ID Make integrationAutomate Microsoft Entra ID with Make.

Tired of creating accounts and group memberships by hand? The Microsoft Entra ID Make integration gives you 12 modules: 9 actions and 3 searches on users and groups. This guide is for IT and ops teams, and it walks you from the connection to a working onboarding scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Microsoft Entra ID Make integration?

The Microsoft Entra ID Make integration links your directory to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when another app calls Make. Each module is one brick, here an action or a search on your users and groups.

Onboarding without tickets. A new row lands in your HR tool, Create a User opens the account and Add Members to a Group gives access to the right teams. If your hiring data lives in a base, the Airtable Make integration is a natural starting point.

Clean offboarding. When someone leaves, Get a User's Memberships shows every group they belong to, Remove Member from Group takes them out one group at a time, and Delete a User closes the account once the checks are done.

Directory reports. Search Users and Search Groups pull lists you can send to a spreadsheet for an access review, with Update a User to correct what the review finds.

Know the limits before you start: the app has no trigger, so Entra ID never starts a scenario by itself. You start it from another app or on a schedule. For endpoints the 12 modules skip, Make an API Call reuses the same connection. The same directory also has an n8n node, covered in the Microsoft Entra ID n8n integration guide, and the n8n vs Make comparison helps you pick a tool.

Connect

How do you connect Microsoft Entra ID to Make?

  1. 01

    Add a Microsoft Entra ID module

    In your scenario, click the +, search for Microsoft Entra ID and pick any of its modules, such as Get Current User. Then click Create a connection. A connection is your account linked to Make once, then reused by every module of the app.

  2. 02

    Name the connection

    Giving it a name is optional, but it pays off later. A label such as "Entra ID, admin account" tells you at a glance which account a module runs under when your team shares scenarios.

  3. 03

    Authorize Make and save

    Follow the window that opens: either you authorize Make on the app's page, or you paste the key the app gives you. Click Save, and Make can now read and change your directory through that account.

First scenario

Build your first scenario: onboard a new hire

GoalWhen a new hire is added in another app, Make creates the user in Microsoft Entra ID and adds them to a group.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module comes from the app that holds your hiring data, such as a sheet or an HR tool.

  2. 02

    Add Create a User

    Click the + on the right, search Microsoft Entra ID and pick Create a User. Map the name and details from the first module, so each bundle (one new hire) becomes one account.

  3. 03

    Add the group

    Add Add Members to a Group next. Once the connection exists, Make can list what it reads from your directory, and you map the user created by the previous module.

  4. 04

    Test with Run once

    Click Run once with a test row. Open the bubble on each module to read the bundles it received, and check in Entra ID that the test account and its group look right.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and turn the scenario on. Each run costs operations: one operation is one module handling one bundle.

Modules

What can Microsoft Entra ID do in Make?

Microsoft Entra ID gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Microsoft Entra ID1

Add Members to a Group

Action

In MakeAllows you to add multiple members to a group.

Puts several people into one group in a single step, so a whole team gets the same access at once instead of a module per person.

When to use it
right after Create a User in an onboarding flow, or when a project kicks off and a list of colleagues needs the project group.
Watch out
it adds to a group but does not remove anyone, so pair it with Remove Member from Group for moves between teams.
Microsoft Entra ID2

Create a User

Action

In MakeCreates a new user.

Opens a new account in your directory from data that arrives in the scenario, which turns a signed offer or a new HR record into a working login.

When to use it
as the core of an onboarding scenario, fed by the app where hiring happens.
Watch out
run it on a test person with Run once before switching the scenario on, because every bundle that reaches this module becomes a real account.
Microsoft Entra ID3

Delete a User

Action

In MakeDeletes a specific user.

Removes a specific account from the directory, the last step of an offboarding flow once access and data have been handed over.

When to use it
at the end of a departure scenario, after Get a User's Memberships and Remove Member from Group have done their part.
Watch out
place a filter or a check before it so only the intended account reaches the module, and test it on a dummy user first.
Microsoft Entra ID4

Get a Group

Action

In MakeRetrieves information about a specific group.

Fetches the details of one group you already know, so later modules can use its information in a message or a report.

When to use it
when a scenario receives a group reference from another app and needs the readable details before notifying a manager.
Watch out
it works on one known group; if you only have part of a name, start with Search Groups instead.
Microsoft Entra ID5

Get a User

Action

In MakeRetrieves a specific user.

Reads one specific account, which lets you check who a person is in the directory before the scenario changes anything about them.

When to use it
ahead of Update a User or Delete a User, to confirm the target and pass its details to the next module.
Watch out
it expects one precise user; to find people by criteria, Search Users is the better fit and may return several bundles.
Microsoft Entra ID6

Get Current User

Action

In MakeRetrieves user information for the signed-in user.

Returns the profile of the signed-in user, the account your Make connection runs under. Handy for a quick sanity check.

When to use it
right after creating the connection, or when a shared scenario behaves oddly and you want to see which account it uses.
Watch out
it only describes that account, never the colleague you are working on; use Get a User for anyone else.
Microsoft Entra ID7

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Calls any endpoint of the app's API with the same connection, which covers what the 11 other modules leave out without a separate login.

When to use it
when your process needs an operation on users or groups that no listed module offers.
Watch out
you write the request yourself, so keep the API reference open and try it with Run once on harmless data first.
Microsoft Entra ID8

Remove Member from Group

Action

In MakeRemoves a single member from a specific group.

Takes a single person out of one specific group, which closes an access without touching the account itself.

When to use it
when someone changes team, or during offboarding for each group returned by Get a User's Memberships.
Watch out
it handles one member of one group per run, so a person in several groups needs one bundle per group, fed by the search before it.
Microsoft Entra ID9

Update a User

Action

In MakeUpdates a user information.

Changes the information of an existing account, so a promotion or a move recorded in your HR tool also shows up in the directory.

When to use it
when a role change is recorded in another app and the directory should reflect it too.
Watch out
fetch the user first with Get a User or Search Users so the change lands on the right person.
Microsoft Entra ID10

Get a User's Memberships

Search

In MakeRetrieves the list of groups memberships for a specific user.

Lists every group a given person belongs to, so you see their current access in one place.

When to use it
at the start of offboarding or of an access review, before removing or reporting anything.
Watch out
as a search, it can return zero, one or many bundles, and each following module runs once per group it finds.
Microsoft Entra ID11

Search Groups

Search

In MakeRetrieves a list of groups.

Returns a list of groups from your directory, useful to build an inventory or to find the group a scenario should target.

When to use it
for an access review sheet, or when a request names a team and you need the matching group.
Watch out
a large result means many bundles, and every module after it consumes operations for each one.
Microsoft Entra ID12

Search Users

Search

In MakeRetrieves a list of users.

Pulls a list of accounts, which gives you a directory export you can filter, compare or send to a spreadsheet.

When to use it
to spot accounts that no longer match your HR records, or to feed Update a User in bulk.
Watch out
it may return nothing; add a filter after it so the next modules only run when a user was actually found.
Need help

Need help automating Microsoft Entra ID with Make?

A person reads every message.

FAQ

Microsoft Entra ID and Make: frequently asked questions

01Is the Microsoft Entra ID Make integration free?
Yes, Microsoft Entra ID is a standard app in Make, so its 12 modules work from the Free plan. The Free plan limits you to 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle, and Make pricing covers the plans in detail.
02What do you need to connect Microsoft Entra ID to Make?
You need a Make account and access to the Microsoft account you want Make to act with. Add any Microsoft Entra ID module, click Create a connection, give it a name if you like, then authorize Make on the app's page or paste the key the app provides, and click Save. The documentation lists no other prerequisite. Keep in mind that every module of the scenario runs with the rights of that account, so check it with Get Current User before you let a scenario create, update or delete users.
03Can Microsoft Entra ID start a Make scenario on its own?
No. The app has no trigger module, neither scheduled nor instant, so a change in your directory never launches a scenario by itself. You have two ways around it. Start the scenario from another app, such as the HR tool or the form where new hires are recorded, and let the Entra ID modules act after it. Or set a schedule on the first module, every 15 minutes by default, and open with Search Users or Search Groups to read the directory again on every run.
04What if a Microsoft Entra ID module is missing in Make?
Use Make an API Call. It lets the scenario call any endpoint of the app's API with the connection you already set up, so you are not limited to the 12 listed modules. You write the request yourself, which asks for a look at the API reference, and Run once is the safe way to try it. The documentation gives no numeric limit for this app. If a scenario fails after that, the Make troubleshooting guide walks through reading errors and bundles.
05Should you use Make or n8n for Microsoft Entra ID?
It depends on the tool your team already works in. Microsoft Entra ID has modules in Make and a node in n8n, so both can handle users and groups for you. In Make you get 12 ready modules, 9 actions and 3 searches, plus Make an API Call for the rest. The best way to decide is to read both guides for this app side by side, check which one covers your process, and see the n8n vs Make comparison linked above for the general criteria.