Allow Long Passwords
the current max password is 16 chars, please make it larger
Longer is (Usually) Stronger section
source of current max length: https://docs.microsoft.com/en-us/azure/active-directory/active-directory-passwords-policy
We now support up to 256 character passwords, including spaces. Please see Alex’s blog post for some more details:
Rob Wilderman commented
Some major operating systems are now suggesting strong passwords that go beyond the 16 character length. Apple's Safari password vault suggests 25 character passwords for example. It is confusing and disheartening to our users who are trying to put in to practice what we have been preaching about password security to them, to have an error pop up when they try to use a more secure password. Yes we can change the password on Premise, and then synchronize it at the next ADSyncCycle, but a user should not have to wait to start using their e-mail again for a pre-determined period of time after changing their password. This is unacceptable. I cannot imagine why this seemingly arbitrary limit was put in place to start with in the Cloud. Microsoft's cloud products should have remained compatible with On-Premise products at all times.
Daniel Rollins commented
I'm with everyone else on this, how in the world do we have a 16 char max and no spaces? Regular AD has allowed both for years because it is more secure. Did they just copy the Azure password system from some really old code? Get with the program MSFT, how long can it possibly take to increase the max to something reasonable, like maybe 64, and allow spaces? I still can't believe this actually went public in its current state.
Roger Seekell commented
Yes, Pass-through Auth is fine for most, but we have cloud-only accounts that need to have more-secure passwords/passphrases.
We are 10 months now from "the team is aware of this feedback and is in considering/planning stage."
I know you guys work hard and have tons of deliverables, so there is clearly enough developers to fix this issue and fix in a reasonabel time frame. I see the new feature announcements every couple weeks.
Management needs to prioritize these very serious, very basic security concerns and stop just paying lip service to them with "we are aware" feedback. It is completely ridiculous that enterprise customers have to wait YEARS to have issues addressed. This isn't the only one. These feedback forums are stuffed to the gills with issues that Microsoft is "aware of" but are too busy chasing the latest shiny new feature rather than finishing their existing features.
The cloud promised so much, but all it ever seems to deliver at the end of the day is high costs, delays, and downtime.
Guido Vilariño commented
I can't believe it's 2019 and we still have to ask for this
I am surprised and disappointed by Microsoft in this. Come on, folks. It's 2019, a sixteen character maximum is totally nuts. All good security practice allows for phrases for passwords, and by limiting them in this way, you make security worse!
This restriction interferes with Safari's "Strong Password" feature. It is also worrying that such a limit even exists this day and age, especially given what kind of resources these passwords potentially protect.
Alexander Martin commented
The fact that this restriction exists, and that it has gone unchanged for so long after numerous requests to remove it, casts serious doubt on the architecture of password storage for cloud-native Azure AD users. Such a restriction likely indicates that passwords are either being stored in an insecure manner, such as plain-text or two-way encryption, that is length sensitive, or that password hashes are computed in a highly incorrect manner that limits input length. I am forced to question if cloud-native accounts' passwords are even stored in a secure manner.
No other modern directory or authentication service of which I am aware imposes such a strict and disconcerting restriction on passwords. The fact that passwords synced from AD DS are subject only to AD DS's password policies causes even further confusion, as it would seem to indicate that it is possible to handle longer passwords in Azure AD's backend, yet this capability is not available to cloud-native accounts. Again, this casts serious doubts on the Azure AD's password storage architecture.
Have just discovered that in addition to the length restriction "feature", that /spaces/ will not be accepted as passwords. I'm lost for words.
Moreover, this is no actual indication of this when setting a password. I continue to be astounded as to how absolutely p**s-poor this insane password policy is. This should have been laughed out of the meeting room at the first possible opportunity.
This should not be a feature request. It's not a feature, it certainly should not have to be requested. I'm frankly speechless. There is no good reason on this earth why this limit should exist in this day and age. I'm inclined to believe the 5-eyes crackability theory, in absence of any other credible reason.
Currently resetting passwords following a decidedly tiresome migration from G-Suite, and I'm currently regretting performing that migration.
This is supposed to be a grown-up business tool, not jazzed up copy of Hotmail sold to business users.
Fix it, Microsoft. Fix it yesterday. This would currently cause our business to fail NCSC requirements. If this isn't resolved /very/ quickly (unlikely given the "Yeah, we're looking at it" post way back in March) then I'll be strongly recommending a migration back to G-Suite - for all it's warts and prying, they at least appear to understand elementary security principles.
The disruption is moot since that's precisely what this "feature" is about to cause for the entire userbase I'm migrating.
Allow longer passwords
This needs to happen ASAP. It's such an annoying and stupid restriction anyway - the passwords are salted and encrypted - the length doesn't matter - they're all the same length in the database anyway!
T. K. commented
If you are storing hashed passwords, the length of the password itself doesn't matter. It's just a web input field. How can this be in considering/planning phase for eight months?
Unless you are storing passwords in plain text and the password column is actually 16 characters. In which case, holy **** all the cloud naysayers were right.
Peter Janeczko commented
Allow longer passwords
Is it possible to configure the minimum password length to ... more than 8?
Why do we actually need to vote for this? This should be a OOB feature.
For some reason this also limits our on-premise AD which does password hash synchronization using Azure AD Connect. Users in on-premise windows AD cannot set password with more than 16 characters...I don't really understand why that is.
MS support is useless.
NIST and Microsoft (since early 2000's) have suggested passphrases. The issue is that Microsoft has failed to make the cloud as secure as on-premises. Many of the controls for passwords, even the newest password controls such as "deny lists" are far from where things need to be. Granted, "deny lists" don't exist on-premises from Microsoft (ok, via a proxy), but other organizations have provided robust password controls for on-premises AD for years.
The key is to know the limitations and work within the confines.
A 16 char maximum password is not secure... no matter "who" says it is. We all can come up with a list saying that 16 is weak compared to 20+
Steve Catlin commented
Wow.... This is just pathetic. It honestly never occurred to me that this would be in issue in 2018. Every MS rep on Earth is pushing everyone to AzureAD as hard as they can and it doesn't even support a reasonable PW policy.
I'm surprised this is still an issue on AzureAD. Microsoft should be embarrassed since they actually do so well protecting credentials in other areas. Active Directory on-premises (ADDS) has allowed 127 character passwords since the year 2000!
Jared Thirsk commented
How are we supposed to take Azure AD and Microsoft seriously if there is a low and seemingly arbitrary cap on how secure passwords can be?