> For the complete documentation index, see [llms.txt](https://msdocs.aohwv.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://msdocs.aohwv.com/readme.md).

# Welcome

**Microsoft Identity Security** is RedLegg & AOHWV's guide to securing your Microsoft cloud environment and getting the right security data to your SOC. It covers Microsoft best practices for hardening your tenant, measuring your progress, and sending only the most relevant and important identity, endpoint and cloud logs to your SIEMs that your business deems necessary.

{% hint style="info" %}
**New here?** Start with [**Why This Matters**](/readme/why-cloud-logs-matter.md), or jump straight to the [**Quick Start**](/quick-start/getting-started.md).
{% endhint %}

### What you'll find here

#### Secure & Measure

* **Top 10 Hardening Steps:** the highest-impact settings to secure your Microsoft cloud tenant
* **Get More From Your Microsoft Licenses:** what E3, E5 and E7 include, and the Entra ID and Defender features to turn on
* **Microsoft Dashboards:** your security scores, dashboards and Security Copilot, and what they leave out
* **Check Your Setup:** a checklist, and soon a script, to see how well your logging is set up

#### Quick Start

Step-by-step setup to send every Microsoft cloud source to your SIEM, in about 2–3 hours.

#### Get Expert Help

RedLegg Managed SOC, Penetration Testing, Advisory, EDR & Automation, and AOHWV Identity.

## Related

* [Why This Matters](/readme/why-cloud-logs-matter.md) — How attackers use Microsoft accounts, and what your SOC needs to see
* [Top 10 Hardening Steps](/secure-and-measure/top-10-hardening-steps.md) — The highest-impact settings to fix first
* [Quick Start](/quick-start/getting-started.md) — Connect your Microsoft environment in about 2–3 hours
* [AOH Sync documentation](https://docs.aohwv.dev/) — Identity visibility across HR systems, Entra ID and Active Directory


---

# 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://msdocs.aohwv.com/readme.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.