> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/soc-analyst-guide/quickstart/practice-alert-triage/office-365-impossible-travel.md).
# Office 365 Impossible Travel
**Alert Overview:** This alert triggers when a user account is successfully accessed from geographically distant locations within an impossible time frame, indicating potential account compromise.
**Step 1: Initial Dashboard Review**
1. **Navigate** to the default "Security Detections" dashboard in your ThreatDefence Analyst Console.
2. **Locate** the "Impossible Travel" alert in the table to the left and click on the filter to select it:
The dashboard will refresh, only showing you the selected alert. Review impacted users, indicators, techniques for quick awareness. Select(filter) one user if you wish to investigate one user only.
3. **Do an initial review:**
1. review the td.alert.message which contains a summary of the detection:
1. expand the alert using the > in the left side and inspect the available fields in the detection feed: logon locations, user agent, username, ISP to determine the event outcome.
---
# 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.threatdefence.com/soc-analyst-guide/quickstart/practice-alert-triage/office-365-impossible-travel.md?ask=&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.
