> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/reference/how-to-guides/configure-sso-for-microsoft-entra.md). # Configure SSO for Microsoft Entra Flow Connect supports Single Sign-On (SSO) with Microsoft Entra. To ensure a smooth experience, configure your Entra ID by adding the Novacura Flow Connect application before inviting your users. By following these steps, you can ensure that users will be able to sign in to Flow using their Microsoft accounts. ## Add Novacura Flow as an Enterprise Application Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) with at least a Cloud Application Administrator role. Navigate to **Identity > Applications > Enterprise applications > All applications**. Click on **New application**.

In the search box, enter “Novacura Flow” and select it from the results.

Select "Sign up for Novacura Flow Connect" and you will be redirected to the Flow Connect login screen.

Select "Continue with Microsoft".

Don’t worry if you see the following error message after accepting the permissions for Flow Connect. This occurs because users need to be invited before they can sign in. SSO is now enabled for Flow Connect and ready for use.

Novacura Flow Connect is now listed in the Enterprise Applications section.

--- # 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://docs.novacura.com/flow-connect/reference/how-to-guides/configure-sso-for-microsoft-entra.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.