Forum Discussion
Set 'Account lockout threshold' to 1-10 invalid login attempts
Received the following from MS support.
(I have reported them as inaccurate recommendations)We can confirm that the configuration options at the moment are not available to set from Intune. This looks like an invalid recommendation originating from Microsoft Defender for Endpoint.
Right now in Intune, the ones below are the settings most similar to the account lockout threshold policy (screenshots with descriptions):
Device configuration profiles (Win 10) > Templates > Administrative templates > Computer Configuration > System > Trusted Platform Module Services
- Standard User Individual Lockout Threshold
- Standard User Total Lockout Threshold
JimmyWork this is interesting. The only thin I can find about the GPO you are referring to (Computer Configuration\Policies\Windows Settings\Security Settings\Account Policies\Account Lockout Policy\Account lockout threshold) and it's azure counterpart is Azure Smart Lockout. Have a look at this doc and in particular "verify on-premises account lockout policy" This is where they refer to your GPO Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies > Account Lockout Policy.. A little below that "Manage Azure AD smart lockout values"
So...If I had to guess, it looks like that the security recommendation is not about your baseline or device configuration profile, but about Azure smart lockout. Can you have a look at that?
- That setting is also already set, and the policy is not available in Intune, I can do a remediation script where I just set the net accounts /lockoutthreshold:10.
But this seems more related to On-prem devices and this is a fully cloud device so not sure why security recommendations are bringing this up as there is currently no way to set this in IntuneJimmyWork I agree. It does look like this does not exist with MEM yet. I think your best bet is to reach out to Intune support at this stage (frustrating....) I'm not sure what they can do... besides point you in the direction of a remediation script (which you already know), but who knows... I do hope that custom ADMX/ADML import (in development) will become available with the next Intune release because I think that can solve your problem.
Please keep us informed about your findings. Sorry couldn't help you out yet, but if I do have news to share, I'll give an update here.
- Thank you, I will create a Microsoft Case just to get more information. Have a great weekend