> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/first-time-directory-sync-of-an-on-premises-domain-user-to-an-existing-cloud-account.md).

# First-time directory sync of an on-premises domain user to an existing cloud account

### Synopsis

| Field                | Value                  |
| -------------------- | ---------------------- |
| Activation Period    | 14 Days                |
| Training Period      | 30 Days                |
| Test Period          | N/A (single event)     |
| Deduplication Period | 1 Day                  |
| Required Data        | AzureAD Audit Log      |
| Detection Modules    | Identity Threat Module |
| ATT\&CK Tactic       | Persistence (TA0003)   |
| ATT\&CK Technique    | Valid Accounts (T1078) |
| Severity             | Informational          |

### Description

First-time synchronization of an on-premises domain user with an existing cloud account.

### Attacker's Goals

* Attackers may leverage DirectorySync to move laterally from a compromised on-premise environment into the cloud tenant, allowing them to bypass the cloud's security boundaries and take over high-value cloud identities.

### Investigative actions

* Check if the cloud account was an administrator (Global Admin, etc.) before this sync.
* Determine if the on-premise user was recently created or if its 'proxyAddress' attribute was recently modified.
* Confirm if the organization intended to transition this account from Cloud-Only to Hybrid.
* Verify the consistency between the on-premises 'ObjectGUID' and the newly assigned 'ImmutableID' in Azure AD.


---

# 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://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/first-time-directory-sync-of-an-on-premises-domain-user-to-an-existing-cloud-account.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.