> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/sso-configuration.md). # SSO Configuration ## Azure SSO Configuration IZ Suite can be configured to integrate with Azure Single Sign-On (SSO) using Microsoft Entra ID (formerly Azure Active Directory) to provide secure and centralized authentication. By registering IZ Suite as an enterprise application in Azure and configuring SAML or OpenID Connect, organizations can enable users to log in with their corporate Azure credentials. ### Registering App in Azure Entra ID Follow the below steps to register an App in Entra ID - 1. Navigate to **`Microsoft Entra ID`** -> **`App Registrations`** -> **`New Registration`** 2. Enter the basic details - 1. **`Name`** - Name of the new App 2. **`Supported account types`** - Single Tenant Only 3. **`Redirect URI`** - Should be Web, **`https:///azure_auth`** 3. Click on Save 4. Once the app is created, click on **`Add a certificate or secret`** under Client credentials 5. Click on **`Client secrets`** -> **`New Client Secret`** 6. Enter name, expiry and click on Add 7. Copy the generated Client Value which will be displayed only once 8. Click on **`API Permissions`** and make sure **`User.Read`** is assigned. ### Configuring the App in IZ Suite 1. Navigate to main menu **`Global Settings`** -> **`Settings`** and search for **`Azure Auth`** 2. Click on edit action item 3. Enter the following details - 1. **`Is Enabled`** - Set the value to true 2. **`Tenant Id`** - The tenant id from the Azure’s App 3. **`Client Id`** - The client id from the Azure’s App 4. **`Client Secret`** - The secret copied while generating the Client secret 4. Click on save.
### See Also * [Configure Code Scan Schedules](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/code-scan-schedule-configuration.md) * [Logic Apps](/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/applications/logic-applications.md) * [API Management](/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/applications/apim-applications.md) * [Function Apps](/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/applications/function-applications.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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/sso-configuration.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.