Anavem
Languagefr
How to Enable Alphanumeric Device Password Requirements Using Microsoft Intune

How to Enable Alphanumeric Device Password Requirements Using Microsoft Intune

Configure and deploy alphanumeric password policies for Windows devices through Microsoft Intune, enforcing complex passwords with letters and numbers to strengthen security beyond simple numeric PINs.

May 13, 2026 15 min
Start procedure
Mediumintune8 steps 15 min

Why Enforce Alphanumeric Device Password Requirements?

Simple numeric PINs and basic passwords create significant security vulnerabilities in modern enterprise environments. While convenient, four or six-digit PINs can be easily compromised through shoulder surfing, brute force attacks, or social engineering. Alphanumeric password requirements force users to create more complex credentials that combine letters and numbers, dramatically increasing the difficulty for attackers to guess or crack passwords.

What Makes Microsoft Intune the Right Tool for Password Policy Management?

Microsoft Intune provides centralized, cloud-based device management that can enforce consistent password policies across your entire Windows device fleet. Unlike traditional Group Policy, which requires domain membership and on-premises infrastructure, Intune works with Azure AD-joined, hybrid-joined, and even workgroup devices. The DeviceLock Configuration Service Provider (CSP) gives you granular control over password complexity requirements, allowing you to specify exactly which character types must be included in user passwords.

How Does the DeviceLock CSP Differ from Basic Compliance Policies?

While Intune's standard compliance policies offer basic password requirements, the DeviceLock CSP provides advanced control through the MinDevicePasswordComplexCharacters setting. This CSP can enforce specific combinations of digits, lowercase letters, uppercase letters, and special characters. The key advantage is precision – you can require exactly the character types your security policy demands, rather than relying on generic "alphanumeric" settings that may not meet your specific compliance requirements.

This tutorial walks you through both approaches: the standard compliance policy method for straightforward deployments, and the advanced DeviceLock CSP method for organizations requiring precise password complexity control. You'll learn to troubleshoot common issues like error code 2016281112, handle Windows Hello PIN conflicts, and ensure successful policy deployment across your managed device environment.

Implementation Guide

Full Procedure

01

Access Microsoft Endpoint Manager and Create Device Compliance Policy

Start by navigating to the Microsoft Endpoint Manager admin center where you'll create a new device compliance policy specifically for alphanumeric password requirements.

Open your browser and navigate to https://endpoint.microsoft.com. Sign in with your administrator credentials.

Once logged in, follow this navigation path:

  1. Click Devices in the left navigation pane
  2. Select Compliance policies
  3. Click + Create Policy
  4. Choose Windows 10 and later as the platform
  5. Select Device Compliance as the profile type
  6. Click Create

In the Basics tab, configure these settings:

Name: Alphanumeric Password Required Policy
Description: Enforces alphanumeric password complexity on Windows devices
Platform: Windows 10 and later

Verification: Confirm you see the policy creation wizard with the correct platform selected. The policy should appear in your compliance policies list once created.

Pro tip: Use descriptive naming conventions that include the security requirement and target platform. This makes policy management easier as your environment grows.
02

Configure Basic Password Compliance Settings

Now configure the fundamental password requirements that will work alongside the alphanumeric complexity requirement. Click on the Compliance settings tab in your policy creation wizard.

Navigate to the Password section and configure these essential settings:

Require a password to unlock mobile devices: Yes
Minimum password length: 8 characters
Maximum minutes of inactivity before password is required: 15 minutes
Number of previous passwords to prevent reuse: 5
Password complexity: Alphanumeric
Number of failed sign-in attempts before wiping device: 10
Minutes of inactivity before password reset: 1

Pay special attention to the Password complexity setting. You'll see these options:

  • Device default - Uses whatever the device currently requires
  • Numeric - Numbers only (like a PIN)
  • Alphanumeric - Letters and numbers required

Select Alphanumeric to enforce the requirement for both letters and numbers in passwords.

Also enable Block simple passwords to prevent common patterns like "123456" or "password".

Verification: Review your settings before proceeding. The alphanumeric option should be clearly selected, and minimum length should be at least 8 characters for security best practices.

03

Create Advanced DeviceLock CSP Configuration Profile

For more precise control over password complexity, create a custom configuration profile using the DeviceLock Configuration Service Provider (CSP). This method provides granular control over exactly which character types are required.

Navigate to Devices > Configuration profiles > + Create profile.

Configure the profile basics:

Platform: Windows 10 and later
Profile type: Templates > Custom
Name: DeviceLock Alphanumeric Password CSP

In the Configuration settings, add a new OMA-URI setting:

Name: Minimum Password Complexity Characters
Description: Requires digits, lowercase, and uppercase letters
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DeviceLock/MinDevicePasswordComplexCharacters
Data type: Integer
Value: 3

The complexity values work as follows:

ValueRequirementsAccount Support
1Digits + lowercase OR uppercaseAll account types
2Digits + lowercase + uppercaseLocal and Microsoft accounts
3Digits + lowercase + uppercase + special charactersLocal accounts only
4All character types + additional complexityLocal accounts only

Verification: After saving, check that the OMA-URI path is exactly correct. Any typos will prevent the policy from applying properly.

Warning: Value 3 and above only work with local accounts. Microsoft accounts are limited to complexity values 1 and 2 due to platform restrictions.
04

Assign Policies to Target Device Groups

Both your compliance policy and configuration profile need to be assigned to the appropriate device groups. Start with your compliance policy.

In your compliance policy, click on the Assignments tab. Configure the assignments:

Include groups: All Devices (or specific Entra ID groups)
Exclude groups: Pilot Test Group (recommended for initial testing)

For the DeviceLock CSP configuration profile, follow the same assignment process:

  1. Open your DeviceLock configuration profile
  2. Click Assignments
  3. Select the same groups as your compliance policy
  4. Ensure both policies target the same devices

Consider creating a phased rollout approach:

Phase 1: IT Test Group (10-20 devices)
Phase 2: Department Pilots (100-200 devices)
Phase 3: All Corporate Devices

Click Save on both policy assignments.

Verification: Navigate to Devices > All devices and select a test device. Check the Device compliance and Device configuration tabs to confirm both policies are listed as assigned.

Pro tip: Always test with a small pilot group first. Password policy changes can lock users out of their devices if local account configurations aren't properly prepared.
05

Prepare Local User Accounts for Compliance

The most common reason for alphanumeric password policy failures is improper local account configuration. You need to ensure all local accounts can change passwords and have password expiration enabled.

On each target device, open an elevated Command Prompt or PowerShell and run these commands to identify problematic accounts:

# List all local user accounts
net user

# Check specific account properties (replace 'LocalAdmin' with actual username)
net user LocalAdmin

# Look for these problematic flags:
# - Password never expires: Yes
# - User may not change password: Yes

Fix any accounts with problematic settings:

# Enable password expiration for specific user
wmic useraccount where name='LocalAdmin' set PasswordExpires=TRUE

# Allow user to change password
net user LocalAdmin /passwordreq:yes

# Verify the changes
net user LocalAdmin

For multiple accounts, use this PowerShell script:

# Fix all local accounts at once
Get-LocalUser | Where-Object {$_.Enabled -eq $true} | ForEach-Object {
    Set-LocalUser -Name $_.Name -PasswordNeverExpires $false
    Write-Host "Fixed account: $($_.Name)"
}

Verification: Run net user [username] for each account and confirm that "Password never expires" shows "No" and "User may not change password" shows "No".

Warning: The error code 2016281112 almost always indicates local account configuration issues. Fix these before deploying the policy to avoid mass compliance failures.
06

Force Policy Sync and Monitor Initial Compliance

After assigning policies, force a sync on test devices to immediately apply the new password requirements rather than waiting for the automatic sync cycle.

On target devices, open the Company Portal app and force a sync:

  1. Open Company Portal app
  2. Go to Devices
  3. Select the current device
  4. Click Check status
  5. Click Sync

Alternatively, use PowerShell to trigger sync remotely:

# Force Intune policy sync
$session = New-CimSession
Invoke-CimMethod -CimSession $session -Namespace root/cimv2/mdm/dmmap -ClassName MDM_EnterpriseModernAppManagement_AppManagement01 -MethodName UpdateScanMethod

Monitor compliance status in the admin center:

  1. Navigate to Devices > Monitor > Compliance status
  2. Look for devices showing "Not compliant" status
  3. Click on individual devices to see specific compliance issues

Check the Event Viewer on devices for detailed policy application logs:

Path: Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider
Look for Event IDs: 1906, 1907 (success) or 1908, 1909 (failure)

Verification: Successful policy application should show compliance status changing from "Not evaluated" to either "Compliant" or "Not compliant" with specific password requirement details.

07

Test Password Changes and Handle Windows Hello PIN Conflicts

Once policies are applied, test the actual password change process to ensure users can successfully set alphanumeric passwords that meet the new requirements.

On a test device, attempt to change the password:

  1. Press Ctrl + Alt + Del
  2. Click Change a password
  3. Try setting a numeric-only password (should fail)
  4. Set a proper alphanumeric password (should succeed)

Test these password scenarios to verify enforcement:

❌ Fails: 12345678 (numbers only)
❌ Fails: password (letters only)
❌ Fails: Password (no numbers)
✅ Passes: Password123 (letters + numbers)
✅ Passes: MyPass2024 (mixed case + numbers)

Address Windows Hello PIN conflicts that commonly occur:

  1. Go to Settings > Accounts > Sign-in options
  2. Under PIN (Windows Hello), click Remove
  3. Restart the device
  4. Set up a new PIN that meets alphanumeric requirements

For devices experiencing PIN issues, use this PowerShell command:

# Reset Windows Hello PIN container
certlm.msc
# Navigate to Personal > Certificates
# Delete any "MS-Organization-Access" certificates
# Restart and recreate PIN

Verification: Users should be able to sign in with their new alphanumeric passwords, and the device should show as "Compliant" in the Intune admin center within 24 hours.

Pro tip: Create a user communication template explaining the new password requirements before rolling out to all users. Include examples of compliant passwords to reduce help desk calls.
08

Troubleshoot Common Issues and Verify Full Deployment

Monitor your deployment for common issues and implement fixes for the most frequent problems encountered during alphanumeric password policy rollouts.

Check for the most common error codes and their solutions:

Error CodeDescriptionSolution
2016281112Password complexity not metFix local account password flags
2016281113Password length insufficientIncrease minimum length in policy
2016281114Password reuse detectedClear password history or wait

Use this PowerShell script to check DeviceLock CSP application on devices:

# Check applied CSP values
dsregcmd /status

# Verify DeviceLock registry entries
Get-Item -Path "HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\DeviceLock" -ErrorAction SilentlyContinue

# Check specific complexity setting
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\DeviceLock" -Name "MinDevicePasswordComplexCharacters" -ErrorAction SilentlyContinue

For domain-joined devices showing policy conflicts:

Warning: DeviceLock CSP is not supported on domain-joined devices. Use Group Policy instead: Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies > Password Policy.

Generate a compliance report to verify successful deployment:

  1. Go to Reports > Device compliance
  2. Select Device compliance report
  3. Filter by your alphanumeric password policy
  4. Export results for documentation

Create an ongoing monitoring process:

Daily: Check compliance dashboard for new non-compliant devices
Weekly: Review error codes and trends
Monthly: Audit local account configurations on sample devices

Verification: A successful deployment should show 95%+ compliance rate within one week, with remaining non-compliant devices having documented exceptions or remediation plans.

Frequently Asked Questions

What is error code 2016281112 in Microsoft Intune password policies?+
Error code 2016281112 indicates that a device cannot meet the password complexity requirements, typically because local user accounts have 'Password never expires' or 'Users cannot change password' flags enabled. To fix this, run 'wmic useraccount where name='username' set PasswordExpires=TRUE' and 'net user username /passwordreq:yes' for each affected local account. This error is the most common cause of alphanumeric password policy failures.
Can Microsoft accounts use DeviceLock CSP complexity value 3 or higher?+
No, Microsoft accounts are limited to DeviceLock CSP complexity values 1 and 2 only. Values 3 and 4, which require special characters and additional complexity, only work with local accounts. If you need maximum password complexity, ensure your devices use local administrator accounts rather than Microsoft accounts for the primary user login.
How do I resolve Windows Hello PIN conflicts with alphanumeric password policies?+
Windows Hello PIN conflicts occur when existing PINs don't meet new complexity requirements. To resolve: go to Settings > Accounts > Sign-in options, remove the existing PIN, restart the device, then create a new PIN that meets the alphanumeric requirements. You may also need to delete MS-Organization-Access certificates from the certificate store (certlm.msc) before recreating the PIN.
Why doesn't DeviceLock CSP work on domain-joined Windows devices?+
DeviceLock CSP is not supported on traditional domain-joined devices because domain controllers manage password policies through Group Policy, which takes precedence over MDM policies. For domain-joined devices, configure password complexity through Group Policy at Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies > Password Policy instead of using Intune's DeviceLock CSP.
What's the difference between Intune compliance policies and DeviceLock CSP for password requirements?+
Intune compliance policies provide basic password requirements like minimum length and general 'alphanumeric' complexity, but DeviceLock CSP offers precise control through the MinDevicePasswordComplexCharacters setting. CSP values 1-4 specify exact character type combinations (digits, lowercase, uppercase, special characters), while compliance policies use broader categories. Use DeviceLock CSP when you need specific character requirements that meet detailed security standards or compliance frameworks.

Discussion

Share your thoughts and insights

Sign in to join the discussion