This is to confirm the contents of "Communication Record Commented" COMM1643484.

[幸司福島]

This is to confirm the contents of "Communication Record Commented" COMM1643484.

I am using version "Washington DC" and have not yet used multi-factor authentication notifications.
Even after "Yokohama" is released in March, will I need to change the settings in advance to continue disabling multi-factor authentication in "Washington DC"?
Or, if I do not upgrade to "Yokohama" or later, will I not need to disable multi-factor authentication?
P.S. I am planning to upgrade to "Xanadu".

[Ravi Chandra_K · Accepted solution]

Hello @幸司福島 

Please refer below article:

https://www.servicenow.com/community/platform-privacy-security-blog/enforced-multifactor-authenticat...

For existing customers upgrading to the Now Platform Yokohama release, if your ServiceNow instance doesn’t already have an active MFA policy, a default MFA policy will be automatically enabled.

That means that for the first 90 days following the upgrade to the Yokohama release, all internal users (users without snc_external role) logging in with local or LDAP (network-based—e.g., Active Directory credentials) authentication will need to set up MFA within 30 days of their first successful login.

During this period, users can log in normally but will see a message prompting them to enroll in MFA. After 30 days, MFA will be required by default and users will not be able to log in without completing the MFA setup.

Since the Now Platform Xanadu release, we’ve made it even easier to set up MFA by enabling passkeys to be registered and used directly, without requiring users to download an authenticator app.

For new customers, MFA will be active by default from day 1 for all internal users logging in with local or LDAP authentication. This helps ensure accounts are protected from the moment customers start using the ServiceNow platform.

Please mark the answer as helpful and correct if helped. 

Kind Regards,

Ravi Chandra