Before
An administrator would likely retrieve the tenant's users, open or query each user's details, and manually check account activation and MFA status. They would then need to update users who lacked MFA or send activation emails individually.
How it works
- Retrieve the tenant's users after the email-triggered workflow begins.
- Review each user for account activation and MFA status, applying the relevant conditional path.
- Enable MFA for activated users who do not have it enabled, or send an activation email to users who are not activated.
Workflow details
- Trigger and user retrieval: An incoming email event starts the workflow, which retrieves the tenant's user list for review.
- User-by-user validation: The workflow processes each user individually, retrieves the user's details, checks whether the account is activated, and then evaluates the user's MFA status when applicable.
- Conditional remediation: Activated users whose MFA status is not enabled are updated so MFA is enabled, while users who are not activated receive an activation email.
- Operational result: The tenant's users are assessed consistently and the appropriate account or MFA action is performed automatically for each user without requiring a separate manual review and follow-up.
What changed
User activation and MFA checks now run automatically across the tenant after the trigger occurs. The workflow performs the appropriate status update or activation-email handoff for each user, replacing separate manual lookups and follow-up actions.
Work removed
Retrieving the user list, reviewing each user's activation and MFA status, identifying users requiring action, enabling MFA, and sending activation emails one user at a time.
Expected outcome
For every user processed, the workflow removes at least one manual status review and, when needed, one manual remediation or email action, providing consistent MFA coverage checks across the tenant.
