Update journey-step-3.md

[hedbergtech]

Proposing to use New-Guid instead, it will generate a "complex" password easier than having to rely on a custom PSFunction.

Why

• Closes #[Issue Number]

Changes

[hedbergtech]

@microsoft-github-policy-service agree [company="Truesec"]

[learn-build-service-prod]

Learn Build status updates of commit f16bc77:

✅ Validation status: passed

File	Status	Preview URL	Details
windows/security/identity-protection/passwordless-strategy/journey-step-3.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[hedbergtech]

@microsoft-github-policy-service agree

[paolomatarazzo]

Hello @hedbergtech, new-guid doesn't generate a complex enough string to satisfy most of the password policies out there. the generated string doesn't include any special characters and only lowercase letters.

[paolomatarazzo]

I don't think this would be a good idea. The generated GUID is not "complex", other than length.

[hedbergtech]

On the contrary, a guid always contains a hyphen, which is in fact a "special" character, satisfying the complexity requirement. Changing the character to upper could also ve enforced.

[hedbergtech]

Making it 3/4 ;). Just a suggestion, totally fine with not having the doc state it

[paolomatarazzo]

fair, - is a special character. Still, most scenarios require upper and lower case too. Since the script has been approved by identity PMs I'm inclined to leave it as-is. Any specific concerns about the function itself? This is a sample script that can be used as a reference...