Unable to log in a Samsung smartphone in Intune - device not compliant

%3CLINGO-SUB%20id%3D%22lingo-sub-3013516%22%20slang%3D%22en-US%22%3EUnable%20to%20log%20in%20a%20Samsung%20smartphone%20in%20Intune%20-%20device%20not%20compliant%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3013516%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%2C%3C%2FP%3E%3CP%3EI%20have%20set%20up%20a%20Samsung%20smartphone%20for%20a%20user%20and%20wanted%20to%20register%20this%20on%20the%20company%20portal%2C%20but%20it%20does%20not%20work%20in%20any%20case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20error%20message%3A%20Device%20is%20not%20compliant.%3C%2FP%3E%3CP%3EThe%20password%20is%20too%20weak.%20However%2C%20even%20with%20a%20strong%20password%20it%20does%20not%20work.%3C%2FP%3E%3CP%3EI%20have%20already%20deleted%20the%20app%2C%20disenfranchised%20the%20device%20in%20Intune%2C%20disconnected%20and%20re-registered%2C%20but%20no%20success.%20Reboots%20...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20found%20this%20blog%20post%3A%20%3CA%20href%3D%22https%3A%2F%2Fbr.atsit.in%2Fde%2F%3Fp%3D120846%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fbr.atsit.in%2Fde%2F%3Fp%3D120846%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20how%20I%20can%20create%20the%20device%20as%20a%20conform%3F%20I%20think%20it%20is%20a%20bug!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3013516%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3014075%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20log%20in%20a%20Samsung%20smartphone%20in%20Intune%20-%20device%20not%20compliant%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3014075%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1232219%22%20target%3D%22_blank%22%3E%40TheuerJa%3C%2FA%3E%26nbsp%3Bdid%20u%20try%20to%20see%20if%20secure%20startup%20is%20enabled.%20Is%20a%20known%20feature%20that%20make%20fail%20the%20Intune%20compliancy%20check.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello all,

I have set up a Samsung smartphone for a user and wanted to register this on the company portal, but it does not work in any case.

 

The error message: Device is not compliant.

The password is too weak. However, even with a strong password it does not work.

I have already deleted the app, disenfranchised the device in Intune, disconnected and re-registered, but no success. Reboots ...

 

I found this blog post: https://br.atsit.in/de/?p=120846

 

Does anyone know how I can create the device as a conform? I think it is a bug!

 

Thank you in advance!

7 Replies

@TheuerJa did u try to see if secure startup is enabled. Is a known feature that make fail the Intune compliancy check.

@Amidah1 

Hello,

I have now checked this. There is no password stored on this test device in particular.

Is there another option?

Thank you very much for your help!

Normally to enroll U need to have both a compliance password and secure startup enable. If it fail with both try put a pin and a biometric and see if they accept the device as compliant. In my case it worked with secure startup. But some devices doesn't have that option but is enabled with dual security like pin and biometric o pin and password.
I have now tested a PIN, password and face recognition. Each time I got the message that the device is not compliant.
If still gives problems u should revise the device policy restrictions. Because even if the message says is the password some time get different triggers. In your case is encryption. From my knowledge Samsung encryption works fine if the OS is not cooked, is a original image. Even then some mobile operator cook the image for their devices and make mistakes on default configuration. So if u have secure startup enabled fixed a password and a biometric and still gives u the error then could be de device itself recognized as rooted or something that trigger non compliancy.
The smartphone is purchased, so it is not from any mobile provider. The phone was set up from scratch and nothing changed "jailbreaked".

Do you have any other ideas?

As I said, in the article: https://br.atsit.in/de/?p=120846 from November, is exactly the problem described. It says that it is a bug from Samsung and Microsoft.
The smartphone is purchased, so it is not from any mobile carrier. The phone was set up from scratch and nothing changed "jailbreaked".

Do you have any other ideas?

As I said, in the article: https://br.atsit.in/de/?p=120846 from November, is exactly the problem described. It says that it is a bug from Samsung and Microsoft.
@TheuerJa

It seems is a known issue that Samsung made with the last security update that triggered the issue so the Intune can't check the compliance of the password.
Here is the link of discussion: https://techcommunity.microsoft.com/t5/intune-customer-success/known-issue-samsung-devices-are-nonco...