nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Last pass "MFA conflict" when trying to enforce MFA after a grace period.

Marko Makuc

Hey everyone! I recently started as an IT manager for small company of cca 60 employees. I recently reminded everyone to enable and use MFA of their choice. We are using Last pass Teams subscription. When I try to enforce or make any changes to MFA policies, the system returns MFA conflict error, and no changes can be made. I had a problem with applying changes to MFA enabled for all, but I clicked one to many times, and the changes were accepted.

I still can't enable "Require MFA after grace period"

Has anyone encountered a similar problem?

Find more posts tagged with

Accepted answers

rachael.orovets

Enablinga policy only sets a requirement, it does not directly effect a user's MFA in any way other than prompting them to set up MFA in line with the selected policy if they do not currently have it set up so you should be able to disable the "Multifactor Authentication" option then enabled the "Require MFA after grace period" option which will affect new users.

All comments

rachael.orovets

Hello,

This may be a conflict between two policies,Require Multi-Factor Authentication andRequire MFA after grace period. Could you try disabling one of these policies and see if you can then save the changes?

TheRequire Multi-Factor Authentication policy requires MFA enrollment immediately, and the Require MFA after grace period allows a grace period before MFA enrollment.

Marko Makuc

Thank you for your answer. I don't see an option for "Require MFA". I can only enable or disable MFA for users. Currently MFA is enabled for all users, one hasn't set it up yet because of abscence. I tried to configure to require MFA after grace period excluding the user that hasn't se it up yet, but got the same error. If I disable MFA, everyone will have to set it up again and I want to avoid that

We are using Team subscriptions, we currently don't need to upgrade to advanced. Could it be a bug in the system? I should mention again, when I tried to enable MFA for all, I had the same error popped up, but after some clicks, the system accepted the change.

Attaching a screen of my options:

rachael.orovets

From your screenshot, you would need to disable the "Multifactor Authentication" option and instead enable the "Require any MFA option after grace period" option.

If you'd prefer to have over-the-phone support for this issue you can also reach out to our Teams support team. You can access the Teams support number through the Admin Console > Support to contact the team any time who can help with this as well.

Marko Makuc

Would disabling "Multifactor Authentication" require the users to set up multifactor again?

If I enable Multifactor Authentication for users that already have multifactor set up, can I require "Require.." option for new users?

Best regards, Marko

rachael.orovets

Enablinga policy only sets a requirement, it does not directly effect a user's MFA in any way other than prompting them to set up MFA in line with the selected policy if they do not currently have it set up so you should be able to disable the "Multifactor Authentication" option then enabled the "Require MFA after grace period" option which will affect new users.