Deploy Intune Policies to Manage Windows LAPS - Microsoft Intune | Microsoft Learn
In brief
The article’s terminology, capitalization, phrasing, metadata date, and setup-step numbering were updated. Guidance on assigning LAPS policies and required permissions was also lightly revised.
What Intune admins need to know
Administrators following the article should use the updated wording and corrected sequence when creating LAPS policies. No administrator action is specified.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Deploy Intune policiesPolicies to manageManage Windows LAPS - Microsoft Intune | Microsoft Learn
When you're ready to manage the Windows Local Administrator Password Solution (LAPS) on Windows devices you manage with Microsoft Intune, the information in this article can help you use the Intune admin center to:
- Create and assign Intune LAPS policy to devices.
- View a device's local admin account details.
- Manually rotate the password for the managed account.
- Use reports on LAPS policy.
Before creatingyou create policies, be familiar with the information in Microsoft Intune support for Windows LAPS, which includes:
- An overview of Intune's Windows LAPS policy and capabilities.
- The prerequisites for using Intune policies for LAPS.
Intune policies manage LAPS by using the Windows LAPS configuration service provider (CSP). Windows LAPS CSP configurations take precedence over, and overwrite, any existing configurations from other LAPS sources, like GPOs or the Legacy Microsoft LAPS tool.
Windows LAPS allows for the management of a single local administrator account per device. Intune policy can specify which local admin account it applies to by use of the policy setting Administrator Account Name. If the account name specified in the policy isn't present on the device, no account is managed. However, whenWhen Administrator Account Name is left blank, the policy defaults to the devicesdevice's built-in local admin account that is identified by its well-known relative identifier (RID).
Note
Intune's LAPS policies don't create new accounts or passwords. Instead, they manage an account that's already on the device.
Configure and assign LAPS policies carefully. The Windows LAPS CSP supports a single configuration for each LAPS setting on a device. Devices that receive multiple Intune policies that include conflicting settings can fail to process a policy. Conflicts can also prevent the backup of the managed local admin account and password to your tenantstenant's Directory.
To help reduce potential conflicts, we recommend assigningassign a single LAPS policy to each device through device groups, and not through user groups. While LAPS policy supports user group assignments, they can result in a cycle of changing LAPS configurations each time a different user signs in to a device. Frequently changing policies can introduce conflicts, a lack of device compliance with requirements, and create confusion around which local admin account from a device is currently being managed.
Create a LAPS policy
Ensure that LAPS is enabled in Microsoft Entra, as covered in the Enabling Windows LAPS with Microsoft Entra ID documentation.
To create or manage a LAPS policy, your account must have applicable rights from the Security baseline category. By default, these permissions are included in the built-in role Endpoint Security Manager. includes these permissions. To use custom roles, ensure the custom role includes the rights from the Security baselines category. See Role based access controls for LAPS.
Before you create a policy, you can review details about the available settings in the Windows LAPS CSP documentation.
Sign in to the Microsoft Intune admin center and go to Endpoint security > Account protection, and then select Create Policy.
Set the Platform to Windows, Profile to Local admin password solution (Windows LAPS), and then select Create.
On Basics, enter the following properties:
- Name: Enter a descriptive name for the profile. Name profiles so you can easily identify them later.
- Description: Enter a description for the profile. This setting is optional but recommended.
On Configuration settings,
Configureconfigure a choice for Backup Directory to define the type ofDirectorydirectory to use to back up the local admin account. You can also choose not to back up an account and password. The type ofDirectorydirectory also determines which additional settings are available in this policy.Important
When
configuringyou configure a policy, keep in mind that the backup directory type in the policy must be supported by the join type of the device the policy is assigned to. For example, if you set the directory to Active Directory and the device isn't domain joined (but a member of Microsoft Entra), the device can apply the policy settings from Intune without error, but LAPS on the device won't be able to successfully use that configuration to back up the account.After
configuringyou configure Backup Directory, review and configure the available settings to meet your organization's requirements.On the Scope tags page, select any desired scope tags to apply, then select Next.
For Assignments, select the groups to receive this policy.
We recommend assigningAssign LAPS policy to device groups. Policies assigned to user groups follow a user from device to device. When the user of a device changes, a new policy might apply to the device and introduce inconsistent behavior, including which account the device backs up or when the managed
accountsaccount's password is next rotated.Note
As with all Intune policies, when a new policy applies to a device, Intune attempts to notify that device to check in and process the policy.
Until a device successfully checks in with Intune and successfully processes its LAPS policy, data about its managed local admin account
wonisn'tbeavailable to view or manage from within the admin center.For more
information on assigning profiles,information, see Assign user and device profiles.In Review + create, review your settings and then select Create. When you select Create, you save your changes
are saved,and assign theprofile is assigned.profile. The policyisalsoshownappears in the policy list.
View Devicedevice actions status
When your account has permissions equivalent to the Security baselines permissions that grant rights to all policy templates in the Endpoint security workload, you can use the Intune admin center to view the status of device actions that have beenyou requested for the device.
For more information, see Role based access controls for LAPS.
In the Microsoft Intune admin center, go to Devices > All devices, and select a device that has a LAPS policy that backs up a local admin account. Intune displays that
devicesdevice's Overview pane.On the device Overview pane, you can view Device actions status. Previously requested actions and pending actions display, including the time of the request, and if the action failed or was successful. In the following example screenshot, a device
hashad its Local Admin account Password successfully rotated.Selecting an action from the list opens the Device action status pane, which can display
additionalmore details about that action.
View account and password details
Use the following methods to grant accounts these permissions:
Assign the following built-in Microsoft Entra role:
- Cloud Device Administrator
Create and assign a custom role in Microsoft Entra ID that grants these permissions. See Create and assign a custom role in Microsoft Entra ID in the Microsoft Entra documentation..
For more information, see Role based access controls for LAPS.
In the Microsoft Intune admin center, go to Devices > All devices
>, and then select a Windows device to open its Overview pane.From the overview pane, you can view the
devicesdevice's Device actions status. The status displays current and past actions, such as password rotation.On the devices Overview pane,
belowunder Monitor select Local admin password. If your account has sufficient permissions, the Local admin password pane for the device opens, which is the same view that's available from within the Azure portal.TheYou can view the following informationcan be viewedfrom within the admin center.However,You can only view the Local admin passwordcan only be viewedwhen the accountwasis backed up to Microsoft Entra.ItYou can'tbe viewedview it for an account that's backed up to an on-premises Active Directory (Windows Server Active Directory):- Account name
–. The name of the local admin account thatwasis backed up from the device. - Security ID
–. The well-known SID for the account that is backed up from the device. - Local admin password
–. Obscured by default. If your account has permission, you can select Show to reveal the password. You can then use the Copy option to copy the password to your clipboard. This information isn't available for devices that back up to an on-premises Active Directory. - Last password rotation
–. In UTC, the date, and time that the password was last changed or rotated by policy. - Next password rotation
–. In UTC, the next date, and time when the passwordwill beis rotated per policy.
- Account name
The following are considerations apply for viewing a devicesdevice's account and password information:
Retrieving (viewing) the password for a local admin account triggers an audit event.
You can't view password details for the following devices:
- Devices that have their local admin account backed up to an on-premises Active Directory
- Devices that are set to use Active Directory to back up the account
password.password
Manually rotate passwords
LAPS policy includes a schedule for automatically rotating account passwords. In addition to a scheduled rotation, you can use the Intune device action of Rotate local admin password to manually rotate a devicesdevice's password independent of the rotation schedule set by the devicesdevice's LAPS Policy.
To use this device action, your account must have the following three Intune permissions:
To rotate a password
In the Microsoft Intune admin center, go to Devices > All devices, and select the Windows device with the account you want to rotate.
While viewing the device details,
expandselect the ellipsis (…) on the right side of the menu bar to reveal the available options, and then select Rotate Local adminpassword.password.When you select Rotate Local admin password, Intune displays a warning that requires confirmation before the password is rotated.
After you confirm the intent to rotate the password, Intune initiates the process, which can take a few minutes to complete. During this time, the device details pane displays a banner and a Device actions status that indicate the action is Pending.
After a successful rotation, the confirmation will beis visible in the Device actions status as Complete.
The following are considerations for manual password rotation:
The Rotate local admin password device action is available for all Windows devices, but any device that
hasndoesn't successfullybackedback up its account and password data fails to complete a rotate request.Each manual rotation attempt results in an audit event. Scheduled password rotations also log an audit event.
When a password is manually rotated, the time to the next scheduled password rotation is reset. The time to the next scheduled rotation is managed through the PasswordAgeDays setting in the LAPS policy.
Here's how this works: AFor example, a device receives a policy on March 1, which sets PasswordAgeDays to 10 days. The result is that the devicewillautomaticallyrotaterotates its password after 10 days, on March 11. On March 5, an admin manually rotates that device's password, and action that resets the start date for PasswordAgeDays to March 5. As a result, the devicewillnow automaticallyrotaterotates its password 10 days later, on March 15.For Microsoft Entra joined devices, the device must be online at the time the manual rotation is requested. If the device isn't online at the time of the request, it results in a failure.
Password rotation isn't supported as Bulk Action. You can only rotate a single device at a time.
Settings aren't sent to the device, and both policies are reported as having conflicts.
While a conflict remains, settings from the policies don't apply to the device.
\ No newline at end of file
To resolve conflicts, you must either remove policy assignments from the device, or reconfigure settings in applicable policies until no more conflicts remain.
\ No newline at end of file
\ No newline at end of file
@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Deploy Intune policies to manage Windows LAPS - Microsoft Intune | Microsoft Learn+title: Deploy Intune Policies to Manage Windows LAPS - Microsoft Intune | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/intune/device-security/laps/deploy-policy author: iceorbital ms.author: acabello@@ -13,7 +13,7 @@ ms.collection: - sub-secure-endpoints ms.subservice: protect description: Create policies to manage the Windows Local Administrator Policy Solution (LAPS) on Windows devices that enrolled with Microsoft Intune.-ms.date: 2025-07-22T00:00:00.0000000Z+ms.date: 2026-11-11T00:00:00.0000000Z ms.topic: how-to ms.reviewer: laarrizz locale: en-us@@ -42,16 +42,16 @@ spProducts: platformId: 086a27d1-4b8e-ab4d-677c-8f53b86eddc6 --- -# Deploy Intune policies to manage Windows LAPS - Microsoft Intune | Microsoft Learn+# Deploy Intune Policies to Manage Windows LAPS - Microsoft Intune | Microsoft Learn -When you're ready to manage the *Windows Local Administrator Password Solution* ([Windows LAPS](/en-us/windows-server/identity/laps/laps-overview)) on Windows devices you manage with Microsoft Intune, the information in this article can help you use the Intune admin center to:
+When you're ready to manage the *Windows Local Administrator Password Solution* ([LAPS](/en-us/windows-server/identity/laps/laps-overview)) on Windows devices you manage with Microsoft Intune, the information in this article can help you use the Intune admin center to:
- Create and assign Intune LAPS policy to devices.
- View a device's local admin account details.
- Manually rotate the password for the managed account.
- Use reports on LAPS policy.
-Before creating policies, be familiar with the information in [Microsoft Intune support for Windows LAPS](overview), which includes:
+Before you create policies, be familiar with the information in [Microsoft Intune support for Windows LAPS](overview), which includes:
- An overview of Intune's Windows LAPS policy and capabilities.
- The prerequisites for using Intune policies for LAPS.
@@ -72,7 +72,7 @@ Intune supports configuration of Windows LAPS on devices through the **Local adm
Intune policies manage LAPS by using the Windows LAPS configuration service provider (CSP). Windows LAPS CSP configurations [take precedence](/en-us/windows-server/identity/laps/laps-management-policy-settings#supported-policy-roots) over, and overwrite, any existing configurations from other LAPS sources, like GPOs or the [Legacy Microsoft LAPS](https://www.microsoft.com/en-us/download/details.aspx?id=46899) tool.
-Windows LAPS allows for the management of a single local administrator account per device. Intune policy can specify which local admin account it applies to by use of the policy setting **Administrator Account Name**. If the account name specified in the policy isn't present on the device, no account is managed. However, when **Administrator Account Name** is left blank, the policy defaults to the devices built-in local admin account that is identified by its well-known relative identifier (RID).
+Windows LAPS allows for the management of a single local administrator account per device. Intune policy can specify which local admin account it applies to by use of the policy setting **Administrator Account Name**. If the account name specified in the policy isn't present on the device, no account is managed. When **Administrator Account Name** is left blank, the policy defaults to the device's built-in local admin account that is identified by its well-known relative identifier (RID).
Note
@@ -80,9 +80,9 @@ Ensure the [prerequisites](overview#prerequisites) for Intune to support Windows
Intune's LAPS policies don't create new accounts or passwords. Instead, they manage an account that's already on the device.
-Configure and assign LAPS policies carefully. The Windows LAPS CSP supports a single configuration for each LAPS setting on a device. Devices that receive multiple Intune policies that include conflicting settings can fail to process policy. Conflicts can also prevent the backup of the managed local admin account and password to your tenants Directory.
+Configure and assign LAPS policies carefully. The Windows LAPS CSP supports a single configuration for each LAPS setting on a device. Devices that receive multiple Intune policies that include conflicting settings can fail to process a policy. Conflicts can also prevent the backup of the managed local admin account and password to your tenant's Directory.
-To help reduce potential conflicts, we recommend assigning a single LAPS policy to each device through device groups, and not through user groups. While LAPS policy supports user group assignments, they can result in a cycle of changing LAPS configurations each time a different user signs in to a device. Frequently changing policies can introduce conflicts, a lack of device compliance with requirements, and create confusion around which local admin account from a device is currently being managed.
+To help reduce potential conflicts, assign a single LAPS policy to each device through device groups, and not through user groups. While LAPS policy supports user group assignments, they can result in a cycle of changing LAPS configurations each time a different user signs in to a device. Frequently changing policies can introduce conflicts, a lack of device compliance with requirements, and create confusion around which local admin account from a device is currently being managed.
### Create a LAPS policy
@@ -90,51 +90,52 @@ Important
Ensure that LAPS is enabled in Microsoft Entra, as covered in the [Enabling Windows LAPS with Microsoft Entra ID](/en-us/azure/active-directory/devices/howto-manage-local-admin-passwords#enabling-windows-laps-with-microsoft-entra-id) documentation.
-To create or manage LAPS policy, your account must have applicable rights from the **Security baseline** category. By default, these permissions are included in the built-in role *Endpoint Security Manager*. To use custom roles, ensure the custom role includes the rights from the *Security baselines* category. See [Role based access controls for LAPS](overview#role-based-access-controls-for-laps).
+To create or manage a LAPS policy, your account must have applicable rights from the **Security baseline** category. By default, the built-in role *Endpoint Security Manager* includes these permissions. To use custom roles, ensure the custom role includes the rights from the *Security baselines* category. See [Role based access controls for LAPS](overview#role-based-access-controls-for-laps).
-Before you create a policy, you can review details about the available settings in the [Windows LAPS CSP](/en-us/windows-server/identity/laps/laps-management-policy-settings#windows-laps-csp) documentation.
+Before you create a policy, review details about the available settings in the [Windows LAPS CSP](/en-us/windows-server/identity/laps/laps-management-policy-settings#windows-laps-csp) documentation.
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and go to **Endpoint security** > **Account protection**, and then select **Create Policy**.
[](media/deploy-policy/create-laps-policy.png#lightbox)
-
- Set the *Platform* to **Windows**, *Profile* to **Local admin password solution (Windows LAPS)**, and then select **Create**.
-2. On **Basics**, enter the following properties:
+2. Set the *Platform* to **Windows**, *Profile* to **Local admin password solution (Windows LAPS)**, and then select **Create**.
+3. On **Basics**, enter the following properties:
- **Name**: Enter a descriptive name for the profile. Name profiles so you can easily identify them later.
- **Description**: Enter a description for the profile. This setting is optional but recommended.
-3. On **Configuration settings**, Configure a choice for **Backup Directory** to define the type of Directory to use to back up the local admin account. You can also choose not to back up an account and password. The type of Directory also determines which additional settings are available in this policy.
+4. On **Configuration settings**, configure a choice for **Backup Directory** to define the type of directory to use to back up the local admin account. You can also choose not to back up an account and password. The type of directory also determines which additional settings are available in this policy.
[](media/deploy-policy/specify-the-backup-directory.png#lightbox)
Important
- When configuring a policy, keep in mind that the backup directory type in the policy must be supported by the join type of the device the policy is assigned to. For example, if you set the directory to Active Directory and the device isn't domain joined (but a member of Microsoft Entra), the device can apply the policy settings from Intune without error, but LAPS on the device won't be able to successfully use that configuration to back up the account.
+ When you configure a policy, keep in mind that the backup directory type in the policy must be supported by the join type of the device the policy is assigned to. For example, if you set the directory to Active Directory and the device isn't domain joined (but a member of Microsoft Entra), the device can apply the policy settings from Intune without error, but LAPS on the device won't be able to successfully use that configuration to back up the account.
+
+ After you configure *Backup Directory*, review and configure the available settings to meet your organization's requirements.
+5. On the **Scope tags** page, select any desired scope tags to apply, then select **Next**.
+6. For **Assignments**, select the groups to receive this policy.
- After configuring *Backup Directory*, review and configure the available settings to meet your organization's requirements.
-4. On the **Scope tags** page, select any desired scope tags to apply, then select **Next**.
-5. For **Assignments**, select the groups to receive this policy. We recommend assigning LAPS policy to device groups. Policies assigned to user groups follow a user from device to device. When the user of a device changes, a new policy might apply to the device and introduce inconsistent behavior, including which account the device backs up or when the managed accounts password is next rotated.
+ Assign LAPS policy to device groups. Policies assigned to user groups follow a user from device to device. When the user of a device changes, a new policy might apply to the device and introduce inconsistent behavior, including which account the device backs up or when the managed account's password is next rotated.
Note
As with all Intune policies, when a new policy applies to a device, Intune attempts to notify that device to check in and process the policy.
- Until a device successfully checks in with Intune and successfully processes its LAPS policy, data about its managed local admin account won't be available to view or manage from within the admin center.
+ Until a device successfully checks in with Intune and successfully processes its LAPS policy, data about its managed local admin account isn't available to view or manage from within the admin center.
- For more information on assigning profiles, see [Assign user and device profiles](../../device-configuration/assign-device-profile).
-6. In **Review + create**, review your settings and then select **Create**. When you select *Create*, your changes are saved, and the profile is assigned. The policy is also shown in the policy list.
+ For more information, see [Assign user and device profiles](../../device-configuration/assign-device-profile).
+7. In **Review + create**, review your settings and then select **Create**. When you select *Create*, you save your changes and assign the profile. The policy also appears in the policy list.
-## View Device actions status
+## View device actions status
-When your account has permissions equivalent to the *Security baselines* permissions that grant rights to all policy templates in the Endpoint security workload, you can use the Intune admin center to view the status of device actions that have been requested for the device.
+When your account has permissions equivalent to the *Security baselines* permissions that grant rights to all policy templates in the Endpoint security workload, you can use the Intune admin center to view the status of device actions that you requested for the device.
For more information, see [Role based access controls for LAPS](overview#role-based-access-controls-for-laps).
-1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **All devices** , and select a device that has a LAPS policy that backs up a local admin account. Intune displays that devices Overview pane.
-2. On the device Overview pane, you can view *Device actions status*. Previously requested actions and pending actions display, including the time of the request, and if the action failed or was successful. In the following example screenshot, a device has had its Local Admin account Password successfully rotated.
+1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **All devices**, and select a device that has a LAPS policy that backs up a local admin account. Intune displays that device's **Overview** pane.
+2. On the device **Overview** pane, you can view *Device actions status*. Previously requested actions and pending actions display, including the time of the request, and if the action failed or was successful. In the following example screenshot, a device had its Local Admin account Password successfully rotated.
[](media/deploy-policy/view-device-actions-status.png#lightbox)
-3. Selecting an action from the list opens the *Device action status* pane, which can display additional details about that action.
+3. Selecting an action from the list opens the **Device action status** pane, which can display more details about that action.
## View account and password details
@@ -146,38 +147,39 @@ To view account and password details, an account must have one of the following Use the following methods to grant accounts these permissions:
- Assign the following [built-in Microsoft Entra role](/en-us/entra/identity/role-based-access-control/permissions-reference):
- - *Cloud Device Administrator*
-Create and assign a custom role in Microsoft Entra ID that grants these permissions. See [Create and assign a custom role in Microsoft Entra ID](/en-us/azure/active-directory/roles/custom-create) in the Microsoft Entra documentation.
+ - Cloud Device Administrator
+
+Create and assign a custom role in Microsoft Entra ID that grants these permissions. See [Create and assign a custom role in Microsoft Entra ID](/en-us/azure/active-directory/roles/custom-create).
For more information, see [Role based access controls for LAPS](overview#role-based-access-controls-for-laps).
-1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **All devices** > select a Windows device to open its Overview pane.
+1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **All devices**, and then select a Windows device to open its **Overview** pane.
- From the overview pane, you can view the devices *Device actions status*. The status displays current and past actions, such as password rotation.
-2. On the devices Overview pane, below *Monitor* select **Local admin password**. If your account has sufficient permissions, the Local admin password pane for the device opens, which is the same view that's available from within the Azure portal.
+ From the overview pane, you can view the device's **Device actions status**. The status displays current and past actions, such as password rotation.
+2. On the devices Overview pane, under **Monitor** select **Local admin password**. If your account has sufficient permissions, the Local admin password pane for the device opens, which is the same view that's available from within the Azure portal.
[](media/deploy-policy/view-password.png#lightbox)
- The following information can be viewed from within the admin center. However, the *Local admin password* can only be viewed when the account was backed up to Microsoft Entra. It can't be viewed for an account that's backed up to an on-premises Active Directory (Windows Server Active Directory):
+ You can view the following information from within the admin center. You can only view the *Local admin password* when the account is backed up to Microsoft Entra. You can't view it for an account that's backed up to an on-premises Active Directory (Windows Server Active Directory):
- - **Account name** – The name of the local admin account that was backed up from the device.
- - **Security ID** – The well-known SID for the account that is backed up from the device.
- - **Local admin password** – Obscured by default. If your account has permission, you can select **Show** to reveal the password. You can then use the *Copy* option to copy the password to your clipboard. This information isn't available for devices that back up to an on-premises Active Directory.
- - **Last password rotation** – In UTC, the date, and time that the password was last changed or rotated by policy.
- - **Next password rotation** – In UTC, the next date, and time when the password will be rotated per policy.
+ - **Account name**. The name of the local admin account that is backed up from the device.
+ - **Security ID**. The well-known SID for the account that is backed up from the device.
+ - **Local admin password**. Obscured by default. If your account has permission, you can select **Show** to reveal the password. You can then use the *Copy* option to copy the password to your clipboard. This information isn't available for devices that back up to an on-premises Active Directory.
+ - **Last password rotation**. In UTC, the date, and time that the password was last changed or rotated by policy.
+ - **Next password rotation**. In UTC, the next date, and time when the password is rotated per policy.
-The following are considerations for viewing a devices account and password information:
+The following considerations apply for viewing a device's account and password information:
- Retrieving (viewing) the password for a local admin account triggers an [audit event](monitor#events-and-audit-logs).
- You can't view password details for the following devices:
- Devices that have their local admin account backed up to an on-premises Active Directory
- - Devices that are set to use Active Directory to back up the account password.
+ - Devices that are set to use Active Directory to back up the account password
## Manually rotate passwords
-LAPS policy includes a schedule for automatically rotating account passwords. In addition to a scheduled rotation, you can use the Intune [device action](../../device-management/actions/) of **Rotate local admin password** to manually rotate a devices password independent of the rotation schedule set by the devices LAPS Policy.
+LAPS policy includes a schedule for automatically rotating account passwords. In addition to a scheduled rotation, you can use the Intune [device action](../../device-management/actions/) of **Rotate local admin password** to manually rotate a device's password independent of the rotation schedule set by the device's LAPS Policy.
To use this device action, your account must have the following three Intune permissions:
@@ -190,22 +192,22 @@ See [Role based access controls for LAPS](overview#role-based-access-controls-fo ### To rotate a password
1. In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **All devices**, and select the Windows device with the account you want to rotate.
-2. While viewing the device details, expand the ellipsis (…) on the right side of the menu bar to reveal the available options, and then select Rotate Local admin password.
+2. While viewing the device details, select the ellipsis (…) on the right side of the menu bar to reveal the available options, and then select **Rotate Local admin password**.
[](media/deploy-policy/manually-rotate-password.png#lightbox)
3. When you select **Rotate Local admin password**, Intune displays a warning that requires confirmation before the password is rotated.
- After you confirm the intent to rotate the password, Intune initiates the process, which can take a few minutes to complete. During this time, the device details pane displays a banner and a *Device actions status* that indicate the action is *Pending*.
+ After you confirm the intent to rotate the password, Intune initiates the process, which can take a few minutes to complete. During this time, the device details pane displays a banner and a **Device actions status** that indicate the action is *Pending*.
-After a successful rotation, the confirmation will be visible in the Device actions status as *Complete*.
+After a successful rotation, the confirmation is visible in the Device actions status as *Complete*.
The following are considerations for manual password rotation:
-- The **Rotate local admin password** device action is available for all Windows devices, but any device that hasn't successfully backed up its account and password data fails to complete a rotate request.
+- The **Rotate local admin password** device action is available for all Windows devices, but any device that doesn't successfully back up its account and password data fails to complete a rotate request.
- Each manual rotation attempt results in an [audit event](monitor#events-and-audit-logs). Scheduled password rotations also log an audit event.
- When a password is manually rotated, the time to the next scheduled password rotation is reset. The time to the next scheduled rotation is managed through the *PasswordAgeDays* setting in the LAPS policy.
- Here's how this works: A device receives a policy on March 1, which sets *PasswordAgeDays* to 10 days. The result is that the device will automatically rotate its password after 10 days, on March 11. On March 5, an admin manually rotates that device's password, and action that resets the start date for *PasswordAgeDays* to March 5. As a result, the device will now automatically rotate its password 10 days later, on March 15.
+ For example, a device receives a policy on March 1, which sets *PasswordAgeDays* to 10 days. The result is that the device automatically rotates its password after 10 days, on March 11. On March 5, an admin manually rotates that device's password, and action that resets the start date for *PasswordAgeDays* to March 5. As a result, the device now automatically rotates its password 10 days later, on March 15.
- For Microsoft Entra joined devices, the device must be online at the time the manual rotation is requested. If the device isn't online at the time of the request, it results in a failure.
- Password rotation isn't supported as *Bulk Action*. You can only rotate a single device at a time.
@@ -223,4 +225,4 @@ When a device that doesn't have a LAPS policy then receives two conflicting poli - Settings aren't sent to the device, and both policies are reported as having conflicts.
- While a conflict remains, settings from the policies don't apply to the device.
-To resolve conflicts, you must either remove policy assignments from the device, or reconfigure settings in applicable policies until no more conflicts remain.\ No newline at end of file+To resolve conflicts, either remove policy assignments from the device, or reconfigure settings in applicable policies until no more conflicts remain.\ No newline at end of file 



