Anavem
Languagefr
How to Disable RDP Password Saving on All Endpoints Using Microsoft Intune

How to Disable RDP Password Saving on All Endpoints Using Microsoft Intune

Configure and deploy an Intune policy that prevents users from saving RDP passwords on Windows devices, enhancing security by forcing credential entry for every Remote Desktop connection.

April 25, 2026 12 min
mediumintune 10 steps 12 min

Why Disable RDP Password Saving in Enterprise Environments?

Remote Desktop Protocol (RDP) password saving represents a significant security vulnerability in enterprise environments. When users save their credentials in the RDP client, these passwords are stored locally on their devices, creating multiple attack vectors for malicious actors. If a device is compromised, stolen, or accessed by unauthorized personnel, saved RDP credentials provide direct pathways to critical servers and infrastructure.

What Security Risks Does RDP Password Saving Create?

Saved RDP passwords bypass several security controls that organizations implement to protect their infrastructure. These credentials persist across sessions, meaning a single device compromise can lead to prolonged unauthorized access. Additionally, saved passwords often become stale when users change their credentials, leading to account lockouts and support tickets. From a compliance perspective, many security frameworks including CIS benchmarks explicitly recommend disabling password saving to maintain proper credential hygiene.

How Does Microsoft Intune Address RDP Security Concerns?

Microsoft Intune provides centralized policy management that can enforce security configurations across all managed Windows devices simultaneously. By deploying a configuration policy through Intune, administrators can ensure that RDP password saving is disabled organization-wide, regardless of individual user preferences or local device settings. This approach scales effectively from small businesses to large enterprises and provides consistent security posture across diverse device populations. The Settings Catalog method introduced in recent Intune updates offers a more intuitive interface compared to legacy Custom profiles, making policy management more accessible to administrators while maintaining the same security effectiveness.

Implementation Guide

Full Procedure

01

Access the Microsoft Intune Admin Center

Start by signing into the Microsoft Intune admin center where you'll create the configuration policy. This is your central hub for managing all device policies across your organization.

Open your web browser and navigate to https://endpoint.microsoft.com. Sign in using your administrator credentials that have permissions to create and manage device configuration policies.

Once logged in, you'll see the main dashboard. The interface should display your tenant information and various management options. Take a moment to verify you're in the correct tenant if your organization uses multiple tenants.

Pro tip: Bookmark the Intune admin center URL and consider using a dedicated browser profile for administrative tasks to avoid session conflicts with personal accounts.

Verification: Confirm you can see the main navigation menu on the left side with options like "Devices," "Apps," and "Users." If you don't see these options, check your administrative permissions with your IT administrator.

02

Navigate to Device Configuration Policies

Now you'll access the device configuration section where all Windows policies are managed. This is where you'll create the new policy to disable RDP password saving.

In the left navigation pane, click on Devices. This expands the devices menu with several sub-options. Next, click on Configuration under the "Manage devices" section.

You'll see the Configuration page displaying any existing policies. At the top of the page, click the Create button, then select New policy from the dropdown menu.

A "Create a profile" wizard will open. This is where you'll define the platform and profile type for your new policy.

Warning: Make sure you're in the Configuration section, not Compliance policies or Security baselines. These are different policy types that won't achieve the same result.

Verification: You should see a dialog titled "Create a profile" with dropdown menus for Platform and Profile type. If you see a different interface, navigate back to Devices > Configuration and try again.

03

Configure the Policy Platform and Type

Select the correct platform and profile type to ensure your policy targets Windows devices and uses the modern Settings Catalog approach. The Settings Catalog is Microsoft's recommended method for configuring Windows policies in 2026.

In the "Create a profile" dialog:

  • Set Platform to Windows 10 and later
  • Set Profile type to Settings catalog

Click Create to proceed to the policy configuration wizard.

The Settings Catalog provides a more intuitive interface compared to the legacy Custom profile method and includes built-in validation for policy settings.

Pro tip: Settings Catalog is preferred over Custom profiles because it provides better error checking, clearer setting descriptions, and automatic updates when Microsoft adds new policies.

Verification: You should now see the policy creation wizard with tabs for "Basics," "Configuration settings," "Assignments," and "Review + create" at the top of the page.

04

Define Policy Basics and Metadata

Provide clear identification and documentation for your policy. This helps with management and troubleshooting, especially in large organizations with multiple administrators.

On the Basics tab, fill in the following information:

  • Name: Disable RDP Password Saving - Security Policy
  • Description: Prevents users from saving Remote Desktop credentials by disabling the 'Allow me to save credentials' checkbox in RDP client. Enhances security by requiring credential entry for each RDP session.

The name should be descriptive enough that other administrators can understand the policy's purpose without opening it. Include keywords like "RDP," "Security," and "Password" to make it searchable.

Click Next to proceed to the configuration settings.

Pro tip: Use a consistent naming convention across all your Intune policies. Consider prefixes like "SEC-" for security policies or "CORP-" for corporate standards to improve organization.

Verification: The Next button should be enabled, and you should see the "Configuration settings" tab become active. If the Next button is grayed out, ensure both Name and Description fields contain text.

05

Add the RDP Password Saving Setting

Now you'll locate and configure the specific Windows policy setting that controls RDP password saving. The Settings Catalog organizes thousands of Windows policies in a searchable interface.

On the Configuration settings tab, click + Add settings. This opens the settings picker where you can search for or browse to specific policies.

In the search box, type: Do not allow password saving

Alternatively, you can browse to the setting by expanding: Administrative Templates > System > Group Policy > Continue experiences on this device

Select the checkbox next to "Do not allow password saving" and click Add.

Warning: Make sure you select the exact setting "Do not allow password saving" under the correct path. There are similar-sounding settings that control different features and won't achieve the desired result.

Verification: The setting should appear in your Configuration settings list with a toggle switch. The OMA-URI should show as ./Device/Vendor/MSFT/Policy/Config/System/RemoteDesktopServices/DoNotAllowPasswordSaving.

06

Enable the RDP Password Restriction

Configure the policy setting to actively prevent password saving in the Remote Desktop client. This is the core security configuration that will be enforced on all targeted devices.

In the Configuration settings list, you'll see the "Do not allow password saving" setting with a toggle switch. Click the toggle to set it to Enabled.

When enabled, this setting modifies the Windows registry to prevent the RDP client from displaying the "Allow me to save credentials" checkbox. Users will be required to enter their credentials for every RDP session.

The setting corresponds to the registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\DisablePasswordSaving with a DWORD value of 1.

Click Next to proceed to the assignment configuration.

Pro tip: Document this change in your security procedures. When users report that they can't save RDP passwords, you can quickly reference this policy as the intended security measure.

Verification: The toggle should show "Enabled" and the Next button should be available. You should see a brief description of what this setting does when enabled.

07

Assign the Policy to Target Groups

Define which devices or users will receive this security policy. Proper assignment ensures the policy reaches the intended endpoints without affecting systems that shouldn't be restricted.

On the Assignments tab, click + Add groups to select your target audience.

You have several assignment options:

  • All devices: Applies to every Windows device enrolled in Intune
  • Specific device groups: Target particular departments or device types
  • All users: Applies based on user login rather than device
  • Specific user groups: Target particular user populations

For maximum security coverage, select All devices or choose specific Azure AD groups that contain your target devices. Click Select to confirm your choice.

Warning: If you assign to "All users," the policy only applies when those users are logged in. Device-based assignment is more reliable for security policies that should always be enforced.

Click Next to proceed to the final review.

Verification: Your selected groups should appear in the "Included groups" section. The assignment scope should clearly indicate how many devices or users will be affected.

08

Review and Deploy the Policy

Perform a final review of all policy settings before deployment. Once created, the policy will begin deploying to assigned devices during their next Intune check-in cycle.

On the Review + create tab, carefully verify:

  • Policy name and description are correct
  • Platform: Windows 10 and later
  • Profile type: Settings catalog
  • Setting: "Do not allow password saving" is Enabled
  • Assignments: Correct groups are targeted

If everything looks correct, click Create to deploy the policy.

The policy will appear in your Configuration policies list with a status of "Pending" initially, then change to "Succeeded" as devices receive and apply the configuration.

Pro tip: After creating the policy, bookmark or note its name for future reference. You'll need this information for monitoring compliance and troubleshooting user reports.

Verification: You should see a confirmation message that the policy was created successfully, and it should appear in your Devices > Configuration list with the name you specified.

09

Monitor Policy Deployment and Compliance

Track the policy deployment status to ensure it's reaching target devices and being applied successfully. Monitoring helps identify any deployment issues early.

Navigate back to Devices > Configuration and locate your "Disable RDP Password Saving" policy in the list. Click on the policy name to open its details.

In the policy overview, you'll see deployment statistics including:

  • Succeeded: Devices that successfully applied the policy
  • Error: Devices that encountered issues
  • Conflict: Devices with conflicting policies
  • Not applicable: Devices that don't meet the policy criteria

Click on Device status to see individual device results. This view shows which specific devices have applied the policy and any error details.

Warning: Devices typically check in with Intune every 8 hours. Don't expect immediate deployment unless you force a manual sync on test devices.

Verification: Within 24 hours, you should see most assigned devices showing "Succeeded" status. Any devices showing "Error" or "Conflict" require investigation.

10

Test and Verify RDP Password Saving is Disabled

Confirm the policy is working correctly by testing the RDP client behavior on a target device. This verification ensures users can no longer save credentials as intended.

On a device that has received the policy (check Device status to confirm), open the Remote Desktop Connection client by running:

mstsc.exe

In the Remote Desktop Connection window, enter any server name or IP address in the "Computer" field. Before clicking Connect, look for the "Allow me to save credentials" checkbox.

The checkbox should be grayed out and unchecked, preventing users from saving their credentials. This confirms the policy is active.

You can also verify the registry setting directly by opening Registry Editor and navigating to:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services

Look for the DisablePasswordSaving DWORD value, which should be set to 1.

Pro tip: Test this on a few different devices and with different user accounts to ensure consistent behavior across your environment. Document the expected behavior for your help desk team.

Verification: The "Allow me to save credentials" checkbox should be grayed out in mstsc.exe, and the registry value should show DisablePasswordSaving = 1.

Frequently Asked Questions

How long does it take for the RDP password saving policy to apply to devices?+
The policy typically applies within 8 hours, which is the default Intune check-in interval for Windows devices. However, you can force immediate synchronization by going to Settings > Accounts > Access work or school > Info > Sync on the target device. In large environments, allow up to 24 hours for complete deployment across all devices.
Can users bypass the RDP password saving restriction using third-party RDP clients?+
The Intune policy specifically targets the built-in Windows Remote Desktop Connection client (mstsc.exe). Third-party RDP clients like RDP Manager or mRemoteNG may not be affected by this policy. To ensure comprehensive security, consider implementing application control policies to restrict unauthorized RDP clients or deploy enterprise RDP solutions with centralized credential management.
What happens to existing saved RDP credentials when this policy is deployed?+
Existing saved credentials remain in the Windows Credential Manager until manually removed or expired. The policy prevents new credentials from being saved but doesn't automatically clear existing ones. To remove existing credentials, users can access Credential Manager (Windows + S > Credential Manager > Windows Credentials) and delete stored RDP entries, or administrators can deploy additional policies to clear credential stores.
How can I troubleshoot devices that show 'Error' status for this policy?+
Check the Intune Management Extension logs in Event Viewer under Applications and Services > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider. Common issues include conflicting Group Policy settings, devices not meeting Windows version requirements, or enrollment problems. Run 'gpresult /h report.html' to identify conflicting local policies, and ensure devices are running Windows 10 version 1903 or later.
Does this policy affect other credential saving features in Windows?+
No, this policy specifically targets RDP credential saving and doesn't affect other Windows credential storage mechanisms like saved passwords in browsers, Windows Hello, or other application credential managers. The policy modifies only the Terminal Services registry settings related to RDP password saving. Other credential saving features continue to function normally unless targeted by separate policies.

Discussion

Share your thoughts and insights

Sign in to join the discussion