An Agile Refresh Of The Passwordless Strategy
Background
The Microsoft passwordless strategy guidance has existed since 2018, and since then it’s continued to be a solid document. You can view the full doc here, Password-less strategy – Windows security | Microsoft Docs, but where the focus usually lands is on the four-step graph at the top of that page:

The Microsoft passwordless strategy
When discussing the strategy with organizations, the focus is usually on Step 1 – develop (deploy) password replacement offerings, and the technology involved, such as Windows Hello for Business, FIDO2 security keys, and MS Authenticator App passwordless sign-in. After all, the strategy is provided as a stepped approach, so you start with the first step, and then move on.
There are three primary issues with the approach:
- Organizations look at this as a reinforcement that passwordless must be deployed in a waterfall approach.
- Application authentication modernization is not emphasized strongly enough, and subsequently organizations do not right-size the efforts required.
- Organizations do not emphasize the pluralization on offerings, and potentially focus on the requirement of one-size-must-fit-all.
While issue three is not specific to this approach as designed, many organizations will take the waterfall approach with a single solution, and then box themselves into only deploying one solution, slowing down progress.