> For the complete documentation index, see [llms.txt](https://docs.ludi.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ludi.co/management/azure.md). # Azure Integration ## Prerequisites In order to configure Azure SSO integration with Ludi you will need: * Admin access to your Ludi account. * Admin access to your Azure portal (with permission to add Enterprise Applications). * One or more authorized domains adding to your Ludi account (see end of article). * A note of your organizations Ludi Account ID. ### How to find your Ludi Account ID Before you begin, you will need your organization's 12 character Ludi Account ID. You can find this in the under the management menu within Ludi: ![Ludi Account ID](/files/-Mi6AcRovUTo_ct6dQ-k) ## Integration Setup From within the Azure portal, search for and select *Enterprise Applications* from the resources palette, click *New Application* and then *Create your own application*.\ \ Set the name as Ludi and select *Integrate any other application you don't find in the gallery* if not already selected. Click Create. Select *Single sign-on* from the left menu (or getting started quick link) and select *SAML* as the sign-in method. Under Basic SAML configuration, enter your Ludi Account ID number as the Identifier (Entity ID) and set the Reply URL to . Leave all other fields in this section blank. ![SAML Settings](/files/-MkkzjyHmpRgWltMpg0v) Leave the default User Attributes & Claims settings, as per the screenshot above. If the defaults are different or you have changed them, please set them as above. Next, download the Base64 encoded Certificate file from Section 3. Make a note of the Login URL and Azure AD Identifier from Section 4. We will need all these values to configure the Ludi side of the integration. ![The data we need from Azure](/files/-Mkl-cD69x4B5tiTyc2k) Go to your Ludi account administration screen and navigate to Single Sign-On. Map the values from Azure to Ludi like so: * Entry Point = Login URL * Issuer = Azure AD Identifier * Certificate = Text content of the Base64 certificate file ![Example configuration within Ludi](/files/-Mkl0R4c7lSAdgXUJUEd) Once added, click Save Configuration. We recommend leaving the "Restrict login" setting off until you are sure all your team members are able to login via SSO otherwise it may block their access. If you have not already had your authorized domains configured by a Ludi team member, please contact us on Intercom or at to set these up. The domains should include all domains that your team will login from. Authorized domains allow us to redirect users from Ludi to your SSO Identity Provider if they login directly via our login interface rather than going via your service portal. They are not required, but recommended. --- # 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://docs.ludi.co/management/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.