Microsoft Entra ID (Azure AD) SSO
Use this guide to connect Cloudaware to Microsoft Entra ID with SAML single sign-on. It walks through the Entra enterprise application setup, required SAML values, user attribute claims, optional group claims, and the Cloudaware settings needed to enable Entra ID as an authentication service.
info
- Audience: Cloudaware administrators, IAM teams
- Outcome: Microsoft Entra ID is enabled as a Cloudaware authentication service, and users can sign in with Entra-managed identities and optional group-based RBAC mapping
Prerequisites
Before you begin, make sure you have:
- Access to a Cloudaware account.
- Your Cloudaware domain, e.g.,
your_cloudaware_domain.my.salesforce.com - A Cloudaware Administrator user (access to the Salesforce Setup)
- Entra role that can create/configure enterprise applications (for example,
Global Administrator,Cloud Application Administrator,Application Administrator, or a custom role with app permissions) - Agreed identity attributes:
- Unique user identifier (email/username)
- Username format for Salesforce (must be globally unique)
- Group claim source (Entra groups/roles), if you plan to map groups → permission sets
High-Level Setup Flow
- Set up the SAML enterprise app in Entra ID.
- Configure Basic SAML Configuration and claims (+ optional JIT provisioning claims).
- Assign users/groups and download the Federation Metadata XML.
- Create the SSO setting in Cloudaware (in the Setup menu).
- Enable the SSO method under My Domain authentication configuration.
Setup In Microsoft Entra ID
Create The Enterprise Application
- Sign in to the Azure portal.
- Navigate to Enterprise applications → + New application.
- Search the Microsoft Entra gallery for Salesforce.
- Enter a name for the app (for example, Cloudaware), then select Create.
Enable SAML SSO
- In the app’s Overview, select Set up single sign-on and click Get started.
- Choose SAML as the single sign-on method.
Configure Basic SAML Configuration
In Basic SAML Configuration, set the following values (replace <your_cloudaware_domain>):
- Identifier (Entity ID):
https://<your_cloudaware_domain>.my.salesforce.com - Reply URL (Assertion Consumer Service URL):
https://<your_cloudaware_domain>.my.salesforce.com - Sign-on URL (recommended):
https://<your_cloudaware_domain>.lightning.force.com/CA10UI/lca.app(lands users on the CMDB main page)
Click Save.
Configure Attributes & Claims
- Unique User Identifier (Name ID)
- By default, Name ID is often set to
user.userprincipalname. - Adjust if needed to match your Cloudaware/Salesforce user identifier (commonly email).
- By default, Name ID is often set to
Add Claims For Just-In-Time (JIT) Provisioning
If you want Just-In-Time (JIT) user provisioning, create Additional claims for the Salesforce JIT fields.
Recommended mappings:
User.Username- Salesforce usernames must be globally unique.
- Use a transformation to ensure uniqueness. Example: prefix + email (for example,
cloudaware-<email>).
User.FirstName:user.givennameUser.LastName:user.surnameUser.Email:user.emailUser.ProfileId- Use a value that matches your Cloudaware profile strategy.
- If you need different profiles for different groups, use claim conditions based on group membership.
User.IsActive(optional):true- If you have automation that deactivates users after inactivity, this helps ensure deactivated users can be reactivated on login.
Add Group Claims (For RBAC Mapping)
If you map Entra groups to Cloudaware permission sets/profiles, configure a groups claim so group membership is available at login time.
- Include only Cloudaware-relevant groups where possible (to avoid overage/size limits).
Assign Users/Groups And Download Metadata XML
- Assign users or groups to the app.
- When assigning an individual user, you may be prompted to select a role; the selection does not affect Cloudaware access.
- In the app’s Single sign-on section, download the Federation Metadata XML and save it.
Setup In Cloudaware (Salesforce Setup)
Enable SAML
- Log in to Cloudaware and open Setup.
- In Quick Find, type
Single. - Under Identity, open Single Sign-On Settings.
- Ensure SAML Enabled is checked.
- If not, click Edit, enable it, and Save.
- (Optional) Federation ID case-sensitivity:
- By default, Federation IDs are case-sensitive.
- If required, enable Make Federation ID case-insensitive.
Create The SSO Setting From Metadata XML
- In Single Sign-On Settings, click New from Metadata File.
- Upload the Federation Metadata XML file downloaded from Entra ID.
- Click Create.
Configure SAML Single Sign-On Settings
On the newly created SSO setting, configure:
Name: a descriptive name (for example,entra)SAML Identity Type:- If JIT is required, select
Assertion contains the Federation ID from the User object
- If JIT is required, select
Just-in-time User Provisioning:- If JIT is required, check
User Provisioning Enabled - Set
User Provisioning TypetoStandard
- If JIT is required, check
Click Save.
Enable Entra As An Authentication Service (My Domain)
- In Quick Find, type
My Domain. - Open My Domain.
- In Authentication Configuration, click Edit.
- Enable the checkbox next to the new SSO configuration (for example,
entra). - Click Save.