> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/integrations/sso/sp-azure-ad-saml-configuration-for-aqua-sso.md).

# SP: Azure AD SAML configuration for aqua SSO

Azure AD SAML configuration for aqua SSO

1\. Create an application in Azure AD as Non-Gallery and assign it a custom name. This name will later be required as the Entity ID, which we will add in aqua. [See Microsoft documentation for instructions.](https://learn.microsoft.com/en-us/entra/identity/saas-apps/saml-toolkit-tutorial)

2\. Configure the URLs:

![Edit Basic SAML Configuration](https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FSM3wg1zNgUwqnrbGajkf%2F0.png?alt=media)

• Login URL: https\://\<aqua-server>/aquaWebNG/Account/saml2-acs

• Logout URL: https\://\<aqua-server>/aquaWebNG/Account/saml2-logout

3\. aqua allows login only via username. If the username should be defined as the beginning of the email address (everything before '@'), a new claim with \`extractmailprefix\` from \`user.principalname\` must be added and a transformation applied. [See documentation for additional claims.](https://learn.microsoft.com/en-us/entra/identity-platform/saml-claims-customization)

Then you need to provide us with the **full claim name**. It usually starts with *<http://schemas.xmlsoap.org>...*

4\. The XML metadata file and certificates (at the moment aqua only supports the metadata having one certificate inside, the one that is used for signing the saml response) must also be provided if they are not globally trusted.

![](https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2F1aXEjn9g8sK7k97poxfG%2F1.png?alt=media)


---

# 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.aqua-cloud.io/documentation/integrations/sso/sp-azure-ad-saml-configuration-for-aqua-sso.md?ask=<question>&goal=<user_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.