> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/platform-overview/connections-and-integrations/identity-sources/microsoft-entra-id.md). # Microsoft Entra ID Connect Microsoft Entra ID to Cakewalk as an identity source: a Global Administrator signs in and approves the connection. Microsoft Entra ID connects to Cakewalk when a Global Administrator signs in and approves the connection. The shared flow in [Connecting an HRIS](/docs/platform-overview/connections-and-integrations/connecting-an-hris.md) covers what syncs and what happens after you save; this page covers the Microsoft side. ### ✅ Before You Start * You need a user who is a Global Administrator in your organization's Microsoft Entra ID account to complete the setup. * To check: navigate to `portal.azure.com`, search for "roles and administrators" and click **Azure AD roles and administrators**. Confirm that **Global Administrator** is listed under **Your Role**. * Microsoft renamed Azure AD to Microsoft Entra ID. Only the name changed; the console labels in this check still read Azure AD. ### 🛠 Connect 1. In Cakewalk, go to **Settings → Data Sources → Users** and select Microsoft Entra ID. 2. Have the Global Administrator complete the connection flow: they sign in with their Entra ID account and follow the instructions on the screen. The first sync starts immediately. Sync details and cadence: [Connecting an HRIS](/docs/platform-overview/connections-and-integrations/connecting-an-hris.md). ### 📚 Related * [HRIS and IdP](/docs/platform-overview/connections-and-integrations/hris-and-idp.md) * [Connecting an HRIS](/docs/platform-overview/connections-and-integrations/connecting-an-hris.md) --- # 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://www.cakewalk.security/docs/platform-overview/connections-and-integrations/identity-sources/microsoft-entra-id.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.