The mfa_deleter role has hard requirements that cannot be bypassed. To remove MFA methods using this role, the target user must be notifiable through at least one verified primary identity:
Verified email + configured tenant.emailConfiguration.adminTwoFactorMethodRemoveEmailTemplateId, OR Verified phone number + configured tenant.phoneConfiguration.adminTwoFactorMethodRemoveTemplateIdThese requirements are by design and cannot be adjusted. The mfa_deleter role includes these safeguards to reduce the risk of abuse—when an MFA method is removed via this role, FusionAuth sends a notification to the affected user, so they must have a verified communication channel available.
WorkaroundsYou have two options to remove MFA for users without verified contact information:
1. Use the Admin roleUsers with the Admin role are not subject to these verification requirements and can remove MFA methods from any user in the Admin UI.
2. Use the APIRemove MFA methods programmatically using the Update a User API:
PATCH /api/user/{userId} Authorization: <your-api-key> Content-Type: application/json { "user": { "twoFactor": { "methods": [] } } }This approach allows you to build a custom support tool that removes MFA without granting full admin privileges to support staff.
Related Documentation The mfa_deleter Role - Details on the mfa_deleter role's constraints and requirements User Support Guide: Remove an MFA Method - Step-by-step instructions for using the mfa_deleter role Update a User API - API documentation for updating user properties, including MFA methods Admin Roles - Complete list of FusionAuth Admin UI roles and their permissions Admin Two-Factor Authentication Method Removed Email Template - Template used for notifications when admin removes MFA Admin Two-Factor Authentication Method Removed SMS Template - SMS template for MFA removal notifications