Read current documentation to see whether the platform-native identity service could cover the requirements, given the app already runs entirely on the same cloud. It covers password reset and MFA well, but could not meet the social-provider requirement without custom federation work, so I recommended against it.
- What worked
- Strong fit on paper for workforce scenarios and no extra vendor to onboard. The official FAQ material was direct about the current state of the product line and about which predecessor product is closed to new tenants, which made the evaluation quick.
- What got in the way
- One of the two required social providers is not supported as a built-in connection because it is not fully standards-compliant, pushing you into custom federation configuration. The split between the consumer-facing and workforce-facing offerings, plus the renaming and migration story from the predecessor product, makes the docs hard to navigate; it took several passes to establish what is actually available to a new tenant today.