> 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/data-security-documentation/onboard-and-configure/csp-onboarding/microsoft-azure-cloud-onboarding.md). # Microsoft Azure cloud onboarding Cortex Data Security onboarding is the process of connecting your Microsoft Azure cloud environment to Cortex Data Security so it can continuously monitor, scan, and protect your cloud resources. This process establishes secure, least-privilege access for comprehensive security monitoring and threat detection. You gain visibility into your cloud infrastructure and can choose to enable security capabilities such as vulnerability scanning, data protection, and compliance monitoring. The onboarding process provisions the infrastructure in your Microsoft Azure environment required to monitor, secure, and analyze your cloud resources. The sections below describe the available capabilities, the resources created, the security model, and the step-by-step onboarding process. --- # 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://cortex-docs.paloaltonetworks.com/data-security-documentation/onboard-and-configure/csp-onboarding/microsoft-azure-cloud-onboarding.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.