23% of Part II — the final and most policy-heavy use case.
5 tasks · this deck covers task 1 of 5
↑ Security Enforcement OverviewThis exact concept already has a full deck — built for Part I's Security section. Here it's the same facts, just framed as something to actually click through.
That deck covers the 3 factor categories, the 5 method properties, the 15+ authenticator options, and Okta Verify's specific setup requirements (enrollment policy, OIE-only desktop support, Windows Autopilot incompatibility).
Setting one up, in practice: Security > Authenticators, add the authenticator tile, then set its enrollment policy to Optional or Required. That single setting is what actually determines whether users are forced to enroll or simply offered the option.
Watch for this in your own sandbox run:
→ Adding an authenticator but leaving it effectively unused because the enrollment policy wasn't set to Required where it needed to be.
Sources: help.okta.com — about-authenticators.htm (full deck: Security Module 1, Sub 1)
Next: Task 2 →