Forum Discussion
Intune Company portal on androids continue to give me an error
I have removed the user and reset him up in the company portal. I continue to get a message "your company needs you to adjust these settings to comply with organizational policies. Set a longer device password, A device password must be at least 4 characters long. I have changed it and have done a resolve and it still does not work. It is an Android Samsung Galaxy S10e version 11 with the Knox version 3.7. Could you please help!
35 Replies
- MC294075 has been updated - this makes it sound like it is less likely to be resolved as pointed at Android not with the company portal app.
As described in MD293553 or MG293714, due to a change in Android 11 (move to API 30), you must enable the Require an alphanumeric password access requirement setting whenever the Minimum password length access requirement setting is enabled. In Basic Mobility and Security, these settings are configured in the Access Requirements section of your Device Security Policies. Without Require an alphanumeric password, Android 11 devices will remain noncompliant regardless of how long the password is made if the Minimum password length access requirement setting is enabled. In Basic Mobility and Security, settings like password policy are not specific to a platform; when the policy is set, access requirements are applied to all mobile device types. When you enable the Require an alphanumeric password for Android 11, it will also affect iOS and Windows devices of the assigned users.
How this will affect your organization:
Our telemetry indicates you are currently using Device Security Policies from Basic Mobility and Security. If these policies are mis-configured, your users may be impacted.
User impact: Users' Android 11 devices will be marked as non-compliant and prevented from accessing corporate resources. If you manage multiple platforms with Basic Mobility and Security, once you move to set an alphanumeric password, it will apply the same policy on other managed platforms.
What you need to do to prepare:
Login to https://protection.office.com/devicev2 with your admin credentials.
Review your device security policies to identify any that require the minimum password length access requirement and is assigned to users who may use Android 11 devices.
For each identified policy, enable the require an alphanumeric password access requirement. NOTE: once you move to set an alphanumeric password, it will apply the same policy on other managed platforms.- Just to advise, I have also got a ticket open with MS, and the engineer is saying the issue is due to Google Password Policy, which does not make sense if a downgrade does work.
He is following up internally but also suggested creating the policy in the intune portal rather than the MDM portal.
I have resolved the issue via the MDM portal, I did have to untick minimum password length and tick require alphanumeric password, if minimum length was ticked, it would remain uncompliant no matter what other options were set.- Sorry for my ignorance. What is the MDM portal?
- Hi all,
I has resolved this issue, that occurred when I downloaded release Intune version on Google Play.
So, I try to download that version:
https://company-portal.en.uptodown.com/android/download/3941239
And, everything is good.
Wish all have this issue will resolve it success.
Cuong Tran.- I had this issue with a Galaxy Note 10 +and downgrading it to the older version of Intune worked for me too.
- Info: I joined the beta version of the Company Portal app, and this weekend a new version was released which solves the problem: 5.0.5326.0. After that, all the sudden the device became compliant again by itself. So either join the beta to get the fix sooner, or wait a bit more until it is promoted to a prod release.
Thank you. This worked. I had this issue with Samsung Galaxy S10+. I thought it was due to Samsung Knox.
- Hi, just wondering if there is a fix for this yet? Lots of reviews on play store for the company portal app, do we need to wait for that to be updated? Is there any update on the ticket logged with MS?
Thanks
Andy - Hi, have you any policy conditional access ?
vinicarmo As far as I can see, Policy Conditional Access options are not available in the Office 365 MDM portal. The policy is tied to a Active Directory security group. Users of that security group have this policy enforced on their mobile devices when they attempt to connect.
There is an option for "If a device doesn't meet the requirements above, then ..." which mine is set to Block access. I guess I could change this to Allow access, but that really isn't a great fix for this.
I hope that answers your question.
- Andys100 I have gotten word back, this did not seem to help me but it may help you. If you are using the free MDM version that comes with E3 this will not work.
Go to Endpoint Manager and login with your administrator credentials. Go to Device > Compliance Policies and check your policies of type “Personally-owned work profiles” or “Android Compliance Policy” and edit to include one of five configurations as needed:
At least numeric (default): Enter the minimum password length a user must enter, between 4 and 16 characters.
Numeric complex: Enter the minimum password length a user must enter, between 4 and 16 characters.
At least alphabetic: Enter the minimum password length a user must enter, between 4 and 16 characters.
At least alphanumeric: Enter the minimum password length a user must enter, between 4 and 16 characters.
At least alphanumeric with symbols: Enter the minimum password length a user must enter, between 4 and 16 characters.
Once you save the updated policy, the next time a device checks in or a user initiates a check compliance on their device, users will receive the updated policy. At that time, the user may be asked to set their password and then will regain access to corporate resources.
- Hi,
We have started seeing this issue with users too. I can only assume the latest version has introduced a bug. If you view the app reviews in the Google Play Store plenty of people are all having the same issue in the last week. We are using a variety of Samsung Galaxy models also with Knox.
I don't see where to find out if this is being addressed by Microsoft, never mind a time-line. - I am facing with your issue bro, can you share me your solutions if you have fixed it success.
Thank you.
