> 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/user-signed-in-to-an-application-via-power-automate-for-the-first-time.md).

# User signed in to an application via Power Automate for the first time

### Synopsis

| Field                | Value                                                  |
| -------------------- | ------------------------------------------------------ |
| Activation Period    | 14 Days                                                |
| Training Period      | 30 Days                                                |
| Test Period          | N/A (single event)                                     |
| Deduplication Period | 1 Day                                                  |
| Required Data        | AzureAD                                                |
| Detection Modules    | Identity Threat Module                                 |
| ATT\&CK Tactic       | Initial Access (TA0001), Exfiltration (TA0010)         |
| ATT\&CK Technique    | Valid Accounts (T1078), Automated Exfiltration (T1020) |
| Severity             | Informational                                          |

### Description

A user signed in to an application via Power Automate for the first time. This may be indicative of a compromised account.

### Attacker's Goals

Use automation flows to automate data exfiltration, C2 communication, lateral movement and evade DLP solutions.

### Investigative actions

* Check if this was a desired behavior as part of the automation flow.\* Analyze the actions taken by the user during the session and verify that this is a legitimate session.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Look for signs of different data exfiltration via email, shared links or uploads to online storage.

### Variations

<details>

<summary>User signed in to an uncommon application via Power Automate for the first time</summary>

**Synopsis**

| Field             | Value                                                  |
| ----------------- | ------------------------------------------------------ |
| ATT\&CK Tactic    | Initial Access (TA0001), Exfiltration (TA0010)         |
| ATT\&CK Technique | Valid Accounts (T1078), Automated Exfiltration (T1020) |
| Severity          | Low                                                    |

**Description**

A user signed in to an uncommon application via Power Automate for the first time. This may be indicative of a compromised account.

**Attacker's Goals**

Use automation flows to automate data exfiltration, C2 communication, lateral movement and evade DLP solutions.

**Investigative actions**

* Check if this was a desired behavior as part of the automation flow.\* Analyze the actions taken by the user during the session and verify that this is a legitimate session.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Look for signs of different data exfiltration via email, shared links or uploads to online storage.

</details>


---

# 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/user-signed-in-to-an-application-via-power-automate-for-the-first-time.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.