> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/subworkflows/rewst-task-run-ad-sync-entra-cloud-sync.md).

# \[REWST - TASK] Run AD Sync/Entra Cloud Sync

This workflow functions as a critical automation building block that triggers both Active Directory and Microsoft Entra ID (formerly Azure AD) synchronization processes, ensuring consistent identity data across on-premises and cloud environments. The workflow orchestrates two key operations: initiating an Entra Cloud Sync task and executing AD synchronization via PowerShell commands through the client's RMM tool. MSPs will find this particularly valuable when building user onboarding/offboarding automations, troubleshooting identity inconsistencies, implementing scheduled maintenance routines, or within any workflow that modifies directory objects and requires synchronized updates to cloud services. This synchronization workflow eliminates the need for manual intervention during identity-related changes, reducing human error and ensuring reliable, consistent directory services for clients.

This workflow contains 5 tasks.

### Inputs

* **ad\_sync\_result**
  * Input identified from code reference
* **cloud\_sync\_result**
  * Input identified from code reference
* **output**
  * Input identified from code reference

### Outputs

* **automation\_log**: Standardized Rewst automation log
* **success**: Boolean; States if workflow was successful.

### Key tasks

* **attempt\_entra\_cloud\_sync**: Workflows integration: \[REWST - TASK] M365: Start Entra Cloud Sync
* **run\_ad\_sync**: Execution
* **failure\_catch**: Core integration: noop

### Jinja examples

#### Example 1

```jinja
{{ CTX.cloud_sync_result.success|d(false) }}
```

Used in transition condition


---

# 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.rewst.help/documentation/automations/subworkflows/rewst-task-run-ad-sync-entra-cloud-sync.md?ask=<question>&goal=<user_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.