Password non compliant issues on 5.0.4892.0 Intune Company Portal Beta for Android

%3CLINGO-SUB%20id%3D%22lingo-sub-1629027%22%20slang%3D%22en-US%22%3EPassword%20non%20compliant%20issues%20on%205.0.4892.0%20Intune%20Company%20Portal%20Beta%20for%20Android%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1629027%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22p1%22%3EI%20am%20getting%20password%20non%20compliant%20issues%20since%20upgrading%20today%20to%205.0.4892.0%20Intune%20Company%20Portal%20beta%20on%20Android%20on%20Samsung%20Galaxy%20Note%2010%20phone%20running%20Android%2010.%20I've%20changed%20my%20passcode%20multiple%20times%20and%20it%20keeps%20saying%20not%20compliant.%20Is%20this%20a%20bug%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1629027%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAndroid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1629872%22%20slang%3D%22en-US%22%3ERe%3A%20Password%20non%20compliant%20issues%20on%205.0.4892.0%20Intune%20Company%20Portal%20Beta%20for%20Android%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1629872%22%20slang%3D%22en-US%22%3EI%20had%20to%20downgrade%20to%205.0.4882.0%20(leaving%20the%20beta%20and%20having%20to%20wipe%20and%20load%20my%20work%20profile).%20Please%20get%20this%20bug%20fixed%2C%20I%20have%20another%20Android%20device%20(Samsung%20Galaxy%20Tab%20A)%20which%20just%20encountered%20the%20same%20issue%20immediately%20on%20upgrade%20to%205.0.4892.0.%20I'll%20wait%20to%20see%20if%20you%20can%20push%20out%20a%20fix%20for%20that.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I am getting password non compliant issues since upgrading today to 5.0.4892.0 Intune Company Portal beta on Android on Samsung Galaxy Note 10 phone running Android 10. I've changed my passcode multiple times and it keeps saying not compliant. Is this a bug?

1 Reply
Highlighted
I had to downgrade to 5.0.4882.0 (leaving the beta and having to wipe and load my work profile). Please get this bug fixed, I have another Android device (Samsung Galaxy Tab A) which just encountered the same issue immediately on upgrade to 5.0.4892.0. I'll wait to see if you can push out a fix for that.