This seems to be a common issue when migrating to the new Microsoft Authentication Policy. It looks like you're caught between two conflicting requirements:
- The migration requires you to disable all methods in the legacy MFAand SSPR policies.
- The system doesn't allow you to disable all auth methods to prevent potential lockouts.
Here's a step-by-step approach to resolve the issue:
- Disable Most, But Not All, Methods:
- Go to the legacy MFA and SSPR settings.
- Disable all methods except for one (e.g., leave SMS or phone call enabled). This will prevent the system from throwing the "cannot disable all auth methods" error.
- Go to the legacy MFA and SSPR settings.
- Migrate to the New Policy:
- Now, try saving the new migration state. With only one method enabled, the system should treat it as compliant with the migration requirements.
- Finalize the New Policy:
- Once migrated, adjust the settings in the new Microsoft Authentication Policy as needed. This is where you can fine-tune which methods you want to have enabled or disabled.