> 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/a-possible-risky-login-to-azure.md).
# A possible risky login to Azure
### 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 Analytics |
| ATT\&CK Tactic | Initial Access (TA0001), Resource Development (TA0042) |
| ATT\&CK Technique | Compromise Accounts (T1586), Valid Accounts (T1078) |
| Severity | Informational |
### Description
A risky sign-in attempt was observed in Azure.
### Attacker's Goals
An attacker is attempting to compromise an Azure account by exploiting weak or guessed passwords for initial access.
### Investigative actions
* Monitor the user account for indications of compromise, such as irregular login patterns or atypical activities.
* Reach out to the user to confirm the legitimacy of the recent password reset activity.
* Continue monitoring the account for any subsequent actions that may indicate suspicious behavior.
### Variations
Azure Risky Login with Suspicious Characteristics
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------ |
| ATT\&CK Tactic | Initial Access (TA0001), Resource Development (TA0042) |
| ATT\&CK Technique | Compromise Accounts (T1586), Valid Accounts (T1078) |
| Severity | Low |
**Description**
A risky sign-in attempt was observed in Azure.
**Attacker's Goals**
An attacker is attempting to compromise an Azure account by exploiting weak or guessed passwords for initial access.
**Investigative actions**
* Monitor the user account for indications of compromise, such as irregular login patterns or atypical activities.
* Reach out to the user to confirm the legitimacy of the recent password reset activity.
* Continue monitoring the account for any subsequent actions that may indicate suspicious behavior.
Azure-Defined High-Risk Login Attempt
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------ |
| ATT\&CK Tactic | Initial Access (TA0001), Resource Development (TA0042) |
| ATT\&CK Technique | Compromise Accounts (T1586), Valid Accounts (T1078) |
| Severity | Low |
**Description**
A risky sign-in attempt was observed in Azure.
**Attacker's Goals**
An attacker is attempting to compromise an Azure account by exploiting weak or guessed passwords for initial access.
**Investigative actions**
* Monitor the user account for indications of compromise, such as irregular login patterns or atypical activities.
* Reach out to the user to confirm the legitimacy of the recent password reset activity.
* Continue monitoring the account for any subsequent actions that may indicate suspicious behavior.
---
# 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/a-possible-risky-login-to-azure.md?ask=&goal=
```
`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.