> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/library-packs/l1-support/workflow-proactive-password-reset/usage-guide-proactive-password-reset.md).

# Usage guide: Proactive password reset

## Overview <a href="#overview" id="overview"></a>

This workflow helps automate password expiration reminders to users through multi-level checks and reminders across multiple communication channels. With support for both on-premises Active Directory domains and Entra ID environments, the workflow provides a universal way to help reduce disruptions caused by expiring user passwords and IT support workload on the topic.

Ensure your workflow is properly configured by following the steps highlighted in its configuration guide:

[Configuration guide: Proactive password reset](/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/library-packs/l1-support/workflow-proactive-password-reset/configuration-guide-proactive-password-reset.md)

## Workflow Structure <a href="#workflow-structure" id="workflow-structure"></a>

The first block of conditions, one on top of the other, is necessary to ensure coverage of both on-premises and hybrid environments (on-premises AD and Entra ID hybrid). It determines whether the device is joined to the local Active Directory or is a member of Entra ID. These conditions evaluate the Membership Type property and the presence of a device distinguished name. If the membership type is domain and the distinguished name is present, the device is considered a local AD member, otherwise, it is considered an Entra ID member.

<figure><img src="/files/UOeyHbBhUXkGL8JOwMkL" alt="" width="563"><figcaption></figcaption></figure>

After these two conditions, the workflow execution path is split into two: the left one is executed if the device is a member of the local AD, and the right one is executed if the device is a member of Entra ID.

<figure><img src="/files/HdI795k9d6lvA2RxCKOs" alt="" width="563"><figcaption></figcaption></figure>

The logic of the two execution paths is almost the same, but these use different remote actions and campaigns. Below are examples of such campaigns:

<figure><img src="/files/72oKeRI9yHSU1JA71Q8J" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/LFddKYgTkHqwoUw2vgMy" alt=""><figcaption></figcaption></figure>

Because the workflow supports both on-premises on-premises AD and Entra ID hybrid environments, its logic is split into two branches:

* On-premises AD: Get the last password change date using a remote action, then evaluate the result against a defined expiration policy and reminder threshold. If the number of days, until a password expires, reaches the threshold, notify the user using an Engage campaign. If the user has the Password never expires flag set, the workflow exits with the appropriate exit code. If the password expiration threshold is reached, the workflow will send another email notification.
* Entra ID: The logic here is very similar except that it uses a GraphAPI call (LastPasswordChangeDateTime) to get the last password change date and uses an external campaign.

<figure><img src="/files/QYk8Wg88G1rHRduNkyFs" alt=""><figcaption></figcaption></figure>

If the password has not been changed and it is still about to expire, the workflow will obtain that user's manager email address and send that user an email from the manager's email address notifying them that they need to change the password. Below is an example of such an email reminder:

<figure><img src="/files/EkcbCHEjbUHlnlTfUf5x" alt=""><figcaption></figcaption></figure>

***

RELATED TOPICS&#x20;

* [Manage Workflows](https://docs.nexthink.com/platform/latest/manage-workflows)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexthink.com/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/library-packs/l1-support/workflow-proactive-password-reset/usage-guide-proactive-password-reset.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.