Skip to main content

Setting Up Azure Entra ID SSO

Configure SAML single sign-on with Azure Entra ID.

This article explains how to configure single sign-on (SSO) for Cye Cloud Posture Solution with Microsoft Azure Entra ID as your SAML 2.0 identity provider.


Overview

Cye Cloud Posture Solution supports a wide variety of SAML 2.0 Identity Providers (IdPs), so your team can sign in to the console with the credentials it already uses. For SAML 2.0, the console uses AWS Cognito, which does not support IdP-initiated flows: users always start from the SSO login page at console.solvo.cloud/loginsso, not from the Microsoft My Apps portal.

  • Create & Configure the Enterprise App: Add a non-gallery enterprise application in Azure Entra ID, set SAML as the single sign-on method, and enter the console's entity ID, reply URL, and sign-on URL.

  • Map Claims & Assign Users: Keep the default user attributes and claims so user details populate automatically, then assign the users or groups who may sign in.

  • Connect & Test: Paste the App Federation Metadata Url into the console's SSO settings, then sign in from the SSO login page to confirm the redirect to Azure Entra ID and back.


1. Create a custom enterprise application

The enterprise application represents the console inside your Azure Entra ID tenant.

  1. In the Azure Entra ID admin center, go to Enterprise applications > New application.

  2. Select Create your own application.

  3. Choose Integrate any other application you don't find in the gallery (Non-gallery).

  4. Give the application a descriptive name and click Create.


2. Configure SAML single sign-on

  1. In your new enterprise application, go to Single sign-on.

  2. Select SAML as the SSO method. The SAML-based Sign-on configuration page opens.


3. Configure basic SAML settings

These values tell Azure Entra ID where to send SAML responses.

  1. In the Basic SAML Configuration section, click Edit.

  2. Enter the following values:

    • Identifier (Entity ID): urn:amazon:cognito:sp:us-east-1_U0FR6cmpe

    • Reply URL (Assertion Consumer Service URL): https://signin.solvo.cloud/saml2/idpresponse

    • Sign on URL: https://console.solvo.cloud/loginsso


4. Review user attributes and claims

The default claims populate user attributes in Cye Cloud Posture Solution automatically during SSO, so no changes are usually needed.

  1. Go to the User Attributes & Claims section.

  2. Confirm the claims match the defaults:

    • Required claim: Unique User Identifier (Name ID), typically user.userprincipalname.

    • Additional claims:

Claim name

Source attribute

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress

user.mail

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname

user.givenname

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

user.userprincipalname

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname

user.surname


5. Copy the metadata URL

The console reads all SAML configuration details from this URL.

  1. In the SAML Signing Certificate section, locate the App Federation Metadata Url.

  2. Copy the URL. You paste it into the console in step 7.


6. Assign users or groups

Only assigned users can sign in through the enterprise application.

  1. In your enterprise application, go to Users and groups.

  2. Click Add user/group.

  3. Select the users or security groups who need access.


7. Set up the SSO integration in the console

  1. Log in to the console, open the settings page, and click Add SSO integration.

  1. In the SSO settings dialog, paste the URL you copied in step 5 and click Done.


8. Test the configuration

  1. Log out of the console.

  2. Enter your email address and click Login.

  3. You are redirected to Azure Entra ID to authenticate.

  4. After successful authentication, you are redirected back to the console and logged in automatically.


External users

A user who signs in through an SSO integration is an external user. The users management page shows these users with the external label.


Wrap-up / Next Steps

  • Sign in with SSO: Start from the SSO login page. Signing in from the Microsoft My Apps portal (IdP-initiated flow) is not supported.

  • Review SSO users: Open the users management page to see which users signed in through Azure Entra ID.

  • Use a different IdP: For Okta, see Setting Up Okta SSO.

Did this answer your question?