
Microsoft · Security · Product design
Password generator
Enhancing digital safety through strong passwords
- Type
- Interaction design
- Duration
- Sep ’21 – Nov ’21
- Tools
- Figma
- Client
- Microsoft
- Status
- Shipped
Background
We store an ever-increasing amount of personal and sensitive data online. As our reliance on digital accounts grows, so does the concern for cyber safety and data security. Today, many security breaches can be traced back to the use of weak passwords.
Scroll across to see all five years.
- Credentials
- Phishing
- Vulnerability exploitation
View approximate values
| Year | Credentials | Phishing | Vulnerability exploitation |
|---|---|---|---|
| 2020 | 49% | 26% | 5% |
| 2021 | 64% | 35% | 3% |
| 2022 | 48% | 17% | 6% |
| 2023 | 50% | 13% | 5% |
| 2024 | 38% | 15% | 14% |
Credential-based attacks remain the most common of these three breach entry points, despite the decline from 2021. Source: Verizon 2024 Data Breach Investigations Report (PDF)
Why strong passwords are hard to use.
What makes a password weak? Simply put, a password is weak if it can be guessed or interpreted by anyone other than the account owner. Reusing the same password across multiple accounts also makes it weak.
The recommendation is to use passwords that are:
- Pattern free – no predictable sequences or decipherable logic
- Hard to guess – not based on personal or related information
- Unique – different for every account
- Complex – a mix of uppercase and lowercase letters, numbers, and special characters
In technical terms, strong passwords have high entropy—meaning they’re highly unpredictable.
Creating a strong, unique password for every account is hard, and remembering them all is harder. Yet they significantly reduce the chance of an account being compromised.
| Number of characters | Numbers only012345 | Lowercase lettersabcdef | Upper & lowercaseAbCdEf | Numbers & lettersAb3dE6 | With symbols, tooAb3dE! |
|---|---|---|---|---|---|
| 4 | Instantly | Instantly | Instantly | Instantly | Instantly |
| 5 | Instantly | Instantly | Instantly | Instantly | Instantly |
| 6 | Instantly | Instantly | Instantly | Instantly | Instantly |
| 7 | Instantly | Instantly | 1 sec | 2 secs | 4 secs |
| 8 | Instantly | Instantly | 28 secs | 2 mins | 5 mins |
| 9 | Instantly | 3 secs | 24 mins | 2 hours | 6 hours |
| 10 | Instantly | 1 min | 21 hours | 5 days | 2 weeks |
| 11 | Instantly | 32 mins | 1 month | 10 months | 3 years |
| 12 | 1 sec | 14 hours | 6 years | 53 years | 226 years |
| 13 | 5 secs | 2 weeks | 332 years | 3 thousand years | 15 thousand years |
| 14 | 52 secs | 1 year | 17 thousand years | 202 thousand years | 1 million years |
| 15 | 9 mins | 27 years | 898 thousand years | 12 million years | 77 million years |
| 16 | 1 hour | 713 years | 46 million years | 779 million years | 5 billion years |
| 17 | 14 hours | 18 thousand years | 2 billion years | 48 billion years | 380 billion years |
| 18 | 6 days | 481 thousand years | 126 billion years | 2 trillion years | 26 trillion years |
Source: How Long Does It Take for a Hacker to Crack a Password? 🤔 (tech.co)
Brief
Design a password generator for Microsoft Authenticator & Microsoft Autofill Chrome extension that fits into the flow of creating an account or updating a password, without requiring people to open the tool. Once someone uses a suggested password, it should be saved automatically, so they don't need to remember it.
My role
I took over the project after the in-app experience had been designed. I refined the in-app experience, designed the flow for generating passwords without leaving the sign-up page, and solved for offline password use. I was also responsible for meeting Microsoft's accessibility standards and privacy and legal requirements.
Findings
Initial research raised two important considerations:
- People wanted to use the generator beyond online accounts, for example for PDF or Excel files, Wi-Fi networks and hard drives.
- Strong passwords can look intimidating, and so can the customization options. We learned this when we tested the first prototype with users.
Approach
Keep the choice. Reduce the intimidation.
Initially, we displayed all customization options alongside the generated passwords. However, the interface felt so complex that many research participants chose to skip the suggestion entirely and type their own passwords, which defeated the purpose. Since removing customization wasn’t an option, I redesigned the flow to hide these options by default in the in-context view. They remained visible in the in-app view, where the purpose and user expectations were different.
We expected people to confuse characters such as 1 and I, or 0 and O, so we colour-coded passwords to distinguish letters, numbers and special characters.
Further details are confidential.
Final design
The final version, demonstrated in the animations I created for the Microsoft blog post announcing the feature: Generate strong passwords with Microsoft Authenticator - Microsoft Community Hub
Impact
Like many Microsoft products, this feature attracted significant attention in tech blogs and online communities. While I can’t share the exact numbers, these articles offer a glimpse into how the community at large received it.
Learnings & conclusion
This project was an important milestone in my journey at Microsoft. I worked with many teams and stakeholders to bring it to reality. When dealing with credentials, accessibility and privacy are essential, and I made sure the experience never came at the cost of compliance.