- Home
- Resources
- Integrations
- Microsoft Entra ID
Microsoft Entra ID Zapier integrationAutomate Microsoft Entra ID with Zapier.
The Microsoft Entra ID Zapier integration gives you 2 triggers, 10 actions and 1 search. Here is what each one does to your users and groups, why it needs a paid plan, how to connect your directory and what can go wrong.
Premium app Zapier reserves this app to its paid plans.
Verified Trustpilot reviews · AI, automation & growth agency
What the Microsoft Entra ID Zapier integration does
Microsoft Entra ID is the directory that decides who can sign in to Microsoft 365, Azure and the other apps your company plugs into it. Connecting it to Zapier lets your onboarding and offboarding steps run on their own: a user appears or changes, and Zapier creates, updates, groups, disables or deletes accounts for you.
Three results worth building. Onboarding without tickets: New User spots the account the moment Zapier checks, and Add User to Group puts it in the right team. Accounts created from HR data: a hire recorded elsewhere becomes a directory account with Create User. Offboarding that does not wait: Disable User cuts access the day someone leaves, and Remove User from Group cleans up memberships.
Before you build, three limits. Microsoft Entra ID is a premium app: it only runs on paid plans and the free trial. Both triggers are polling triggers, so nothing here reacts instantly. And there are only two of them, about users: no trigger watches groups or memberships. For anything the ten actions do not cover, API Request (Beta) talks to the directory directly, which is advanced work.
The same directory has its own pages on other platforms: the Microsoft Entra ID n8n integration and the Microsoft Entra ID Make integration.
Zapier vocabulary in one minute
Seven words come back all along this page. Here they are, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it to happen.
- Action
- What the Zap does once it has started: the step that creates, changes or removes something for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer, keeping only what it has not seen yet. Both Entra ID triggers work this way.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something already in an app, here a user, so the next steps can reuse what it found.
What Microsoft Entra ID on Zapier really costs
The first cost is the plan itself: Microsoft Entra ID is a premium app, reserved to paid plans and the free trial.
- Premium appyes, paid plans and free trial
- Triggernever counted
- Successful action1 task each
- Free plannot available for this app
After that, Zapier bills successful actions only. The trigger never costs a task, and checking the directory for new users costs nothing however often it runs. Each action that succeeds counts once; one that fails is not counted. A Zap that creates a user and then adds it to two groups uses three tasks per run. Any Zap with a filter, a search such as Find User, or more than one action is a multi-step Zap, which the paid plan you need anyway already allows. Both triggers poll, so the interval below sets how fast you react.
Connect Microsoft Entra ID to Zapier in 3 steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. In the dialog, search for Microsoft Entra ID and pick it from the results. A connection is your directory account linked to Zapier once, then reused.
- 02
Sign in with the right account
Click Add connection. A Microsoft tab opens: sign in with an account that has the rights to manage the users and groups your Zaps will touch, not just your personal one.
- 03
Grant access
Accept the access Zapier asks for on the directory. The connection is then saved once, and every Microsoft Entra ID step of every Zap reuses it. No sign in again.
Your first Zap: new partner accounts join the Partners group
GoalWhen a partner account is created in the directory, Microsoft Entra ID adds it to the Partners group; employee accounts are left alone.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose Microsoft Entra ID and the event New User. It is a polling trigger: Zapier checks the directory at the interval of your plan.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent users of the directory. Pick a real one so the next steps are mapped on actual data.
- 03
Add the filter
Add a Filter step and set its three boxes: a field the trigger brought back that tells partner accounts apart, the rule, and the value to compare with. Employees stop here and only partner accounts go on.
- 04
Add Add User to Group
Add Microsoft Entra ID with Add User to Group. Pick the Partners group, then map the user from the trigger: both fields are required.
- 05
Test, then publish
Run the action test once and check the group membership in the directory. Then click Publish to switch the Zap on. Partner accounts now land in their group on their own.
Microsoft Entra ID triggers on Zapier
2 events start a Zap when something happens in Microsoft Entra ID. Zapier checks for them at the interval your plan allows.
New User
Polling triggerIn Zapier“Triggers when a new user is created.”
Starts your Zap when an account is created in the directory. It is the front door of any automated onboarding.
Updated User
Polling triggerIn Zapier“Triggers when an existing user's details are updated.”
Reacts when the details of an existing user change. It is the hook for anything that should follow a move, a new role or a correction in the directory.
Microsoft Entra ID actions on Zapier
Microsoft Entra ID gives you 10 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add User to Group
ActionIn Zapier“Adds the selected user to a group you choose.”
Puts a user in a group you choose, so membership no longer depends on someone remembering it.
Create Group
ActionIn Zapier“Creates a new group.”
Builds a group in the directory, ready to receive members and access rights.
Create User
ActionIn Zapier“Creates a new user.”
Opens a new account in the directory from data that arrived elsewhere, typically your HR tool.
Delete Group
ActionIn Zapier“Deletes a group.”
Deletes a group from the directory, the clean-up step once a team or project is over.
Delete User
ActionIn Zapier“Deletes an existing user.”
Removes an account from the directory, a step further than disabling it.
Disable User
ActionIn Zapier“Disables an existing user.”
Switches an account off without deleting it, so the person can no longer sign in.
Remove User from Group
ActionIn Zapier“Removes user from a group.”
Takes a user out of a group, the mirror of Add User to Group.
Update Group
ActionIn Zapier“Updates a group in Azure Active Directory.”
Edits a group that already exists, such as its display name.
Update User
ActionIn Zapier“Updates an existing user.”
Changes the details of an existing account instead of creating a new one.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
An advanced action that sends your own request to Microsoft Entra ID through the connection you already set up, for what the other nine do not cover.
Microsoft Entra ID search on Zapier
1 search step looks for data that already exists in Microsoft Entra ID, so a later step can use it.
A search step finds a user who already exists and hands their details to the next steps. In the editor it sits at the bottom of the Action event list, under SEARCH. This app has no find or create variant.
Find User
SearchIn Zapier“Finds a user by id or user principal name.”
Looks up one user by ID or by User Principal Name and brings back their account so later steps can act on it.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds no user stops the Zap and skips what depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?On apps that offer it, this box turns a search into a find or create. Microsoft Entra ID offers no such variant, so Find User never creates anyone.
- If multiple search results are found?Three ways out when several match: keep the first one (the default), stop the Zap, or pass them all on.
When a Microsoft Entra ID Zap breaks
Zapier attaches no help article to Microsoft Entra ID, so the failures worth knowing are the ones every Zap shares, which hurt more on a directory.
On user accounts, a mistake means someone locked out or let in. Read these before publishing, and the Zapier troubleshooting page covers the rest.
Existing users are never picked up
A Zap only reacts to what happens after it is switched on. The people already in the directory stay out of it; bringing them into a new group is a separate job.Update User feeding Updated User
A Zap on Updated User that runs Update User on the same account writes where its own trigger watches. It sets itself off again and burns through your tasks.Mass imports held back
After a bulk import or a migration, New User can return a huge batch at once. Zapier's flood protection may hold it back rather than run every account.No account handled twice
On both polling triggers, Zapier remembers the users it has already seen, so the same account does not start the Zap twice.
Need help automating Microsoft Entra ID with Zapier?
A person reads every message.



