End user verification with Microsoft Entra ID
Mizo connects to your clients' Entra ID tenants through GDAP. Before anyone resets a password or changes access, the End User Verification Agent proves who is behind the ticket with a Microsoft Authenticator push or a sign-in link, and writes the evidence to the ticket.
- Status
- Live
- Connection
- GDAP delegated access, scoped per client tenant
- Works in
- ConnectWise PSA · Autotask · HaloPSA
- Agents
- End User Verification Security & Identity
About Entra ID: Microsoft Entra ID (formerly Azure AD) is the identity platform behind Microsoft 365: user accounts, sign-in and MFA.
What Mizo does with Entra ID
Identity comes first: before any change to an account, Mizo proves the request is real.
Authenticator MFA push
Mizo sends a Microsoft Authenticator push to the device already registered for the requester's account, never to a number or address supplied in the ticket.
Sign-in link verification
When a push isn't practical, the requester gets a link and proves who they are by signing in with their own account.
Evidence written to the ticket
The verification method, result and time are recorded on the ticket in your PSA, so you can show a client or an auditor exactly how a request was verified.
Requester matched to the right account
Mizo resolves the requester to their Entra ID account before anything else happens, so the right person is verified and the right account is changed.
Verification before every change
Actions in Microsoft 365 run only after the requester is verified through Entra ID and, if you choose, after a technician approves the plan.
How the Entra ID connection works
Mizo runs in recommendation mode first, writing its reasoning to each ticket, and moves to autonomous handling only where you allow it.
Connect through GDAP
Mizo reaches each client tenant through Granular Delegated Admin Privileges with scoped roles. No global admin accounts, no shared credentials.
Choose which requests need verification
Per client, decide which requests require verification, such as password resets, MFA changes or access requests.
Start in recommendation mode
Mizo writes its verification result and reasoning to the ticket. Technicians stay in control until you decide to let it run on its own.
Mizo and Entra ID: common questions
How does Microsoft Authenticator verification work?
Mizo triggers an MFA push to the Authenticator app already registered on the requester's account. The user approves it on their own device and the result is logged on the ticket. Contact details supplied in the ticket itself are never used as the verification channel.
What if the user doesn't have Microsoft Authenticator set up?
Mizo can send a sign-in link instead, where the user authenticates with their own account. For clients standardized on Duo, Mizo can use a Duo Push.
Does Mizo need global admin in my clients' tenants?
No. Mizo connects through GDAP with scoped roles, client by client. You decide which client tenants are enabled.
Agents and pages that work with Entra ID
End User Verification Agent
Proves who is behind a ticket before any account change.
Mizo for Microsoft 365
User, license and mailbox changes in your clients' tenants.
Mizo for Duo
Duo Push verification before sensitive changes.
Agentic L1 for MSPs
Automating password resets, access requests and L1 work.