> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeperpam/privileged-access-manager/references/active-directory-least-privilege.md).
# Active Directory Least Privilege
Granting a service account the minimum permissions to rotate
### Overview
When creating a PAM Directory Resource, it is recommended that you use a service account with the least required privileges to perform rotation.
The following steps show you how to enable a service account to rotate credentials using Active Directory's Delegation of Control feature.
{% hint style="info" %}
Before starting, create a service account for password rotation whose credentials you will store in the Keeper resource record.
{% endhint %}
### Procedure
1. Launch Active Directory Users and Computers
2. In the directory tree, select a node for which password rotation should be allowed.
3. Right-click on the node, then click Delegate Control.
4. In the Delegation of Control Wizard, click 'Add'.
5. Locate your chosen service account, then click 'OK'.
Selecting a service account to perform rotation
6. Click 'Next' to advance to permission selection.
7. In 'Delegate the following common tasks', check the option for 'Reset user passwords and force password change at next logon', then click 'Next'.
Delegating permission to reset user passwords
8. Add the service account's login and password to the Resource Record for the AD instance.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.keeper.io/keeperpam/privileged-access-manager/references/active-directory-least-privilege.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
