Microsoft Entra ID on Make Enterprise
Microsoft Entra ID is an identity and access system. Users, groups and sign-in. Automation here changes who can get into what. Here is what Make lists for it, what we build around it, and what to settle before you automate it.
What does Make list for Microsoft Entra ID?
Make's page lists 9 actions, 3 searches by name.
Actions
- Add Members to a Group
- Create a User
- Delete a User
- Get a Group
- Get a User
- Get Current User
- Make an API Call
- Remove Member from Group
- Update a User
Searches
- Get a User's Memberships
- Search Groups
- Search Users
Module lists change as Make updates the app. Treat this as a snapshot and confirm on Make's page before you scope work.
What do we build around Microsoft Entra ID?
These are the kinds of scenarios we build for identity and access. They describe our work, not features of Microsoft Entra ID.
- Joiner, mover and leaver flows driven by the HR system
- Group and role membership changes with an approval step
- Reports of accounts that no longer match HR
- Alerts on changes outside the expected pattern
Example flows
- An HR termination removes the user from groups and opens a review task
- A role change updates group membership after manager approval
- A weekly report lists accounts with no matching employee record
What should you settle before automating Microsoft Entra ID?
Settle these before the first production scenario so builders can start without waiting on a later security review.
- Which changes run automatically and which need a person to approve
- A dedicated service account with only the permissions the scenarios need
- How a failed removal is escalated, since a missed removal is a risk
- Who reviews the automation's own access on a schedule
Platform-level controls such as SSO, roles, encryption and log retention are Make's own published terms; see make.com/security and our Make Enterprise page for how we scope against them. Make describes the Enterprise plan itself at make.com/enterprise.
Frequently asked questions
Can Make connect to Microsoft Entra ID?
Yes. Make has a Microsoft Entra ID app, and its page states that it is supported and maintained by Make. It is listed in Make's Enterprise integrations category. The modules and names on this page are what Make shows on its own Microsoft Entra ID page as of November 5, 2026, so check Make's page for the current list.
What do you build around Microsoft Entra ID?
We build the scenarios around it: joiner, mover and leaver flows driven by the HR system; group and role membership changes with an approval step; reports of accounts that no longer match HR. Scope is set on a call, and each scenario is documented in plain language before hand-over.
What should we decide before automating Microsoft Entra ID?
Start with the guardrails: which changes run automatically and which need a person to approve; a dedicated service account with only the permissions the scenarios need; how a failed removal is escalated, since a missed removal is a risk. Settling these first lets builders start without waiting on a security review later.
Does the connection need Microsoft Entra ID admin access?
That depends on what the scenarios do and on Microsoft Entra ID's own permission model. We aim for a dedicated service account with the narrowest role that works, and we record which scenarios write and which only read. Your Microsoft Entra ID administrator decides what that account may reach.
Consultants in a Box is a Make partner. This page is written by us and is not published by Make or by Microsoft Entra ID's vendor. Microsoft Entra ID, Make and related names are trademarks of their owners. Statements about Make's platform are the ones Make publishes.
Planning to automate Microsoft Entra ID?
Book a call. We map your systems to the pages here, agree the guardrails and give you a written scope and price afterwards.