> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-references/org/general/check-aad-sync-status_scheduled.md).

# Check Aad Sync Status Scheduled

Check the last Entra Connect sync and alert when it is off

{% hint style="info" %}
This is a scheduled runbook. It is designed to run on a recurring schedule rather than being triggered for a single object. See [Scheduling](/automation/runbooks/scheduling.md) for details on how to configure runbook schedules.
{% endhint %}

### Description

Checks whether directory synchronization from on-premises Active Directory is enabled in the tenant. If it is not, an alert email is sent.

### Location

Organization → General → Check Aad Sync Status (Scheduled)

**Full Runbook name**

rjgit-org\_general\_check-aad-sync-status\_scheduled

### Details

| Property         | Value                               |
| ---------------- | ----------------------------------- |
| Version          | 1.0.1                               |
| Required modules | RealmJoin.RunbookHelper (>= 0.8.10) |
| Schedulable      | yes                                 |

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * Directory.Read.All
    * *Reads /organization to evaluate onPremisesSyncEnabled and the last sync timestamp*
  * Mail.Send
    * *Sends the alert email via /users/{sendAlertFrom}/sendMail when the Entra Connect sync is stale*

### Parameters

#### sendAlertTo

Gets the alert email when directory synchronization is found disabled.

| Property            | Value                     |
| ------------------- | ------------------------- |
| Required            | false                     |
| Default Value       | <support@glueckkanja.com> |
| Type                | String                    |
| Portal display name | Alert recipient           |

#### sendAlertFrom

User in the tenant the alert is sent as; needs a mailbox.

| Property            | Value                      |
| ------------------- | -------------------------- |
| Required            | false                      |
| Default Value       | <runbooks@glueckkanja.com> |
| Type                | String                     |
| Portal display name | Alert sender               |

[Back to Runbook Reference overview](/automation/runbooks/runbook-references.md)


---

# 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.realmjoin.com/automation/runbooks/runbook-references/org/general/check-aad-sync-status_scheduled.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.