To integrate with Azure AD, add a SAML application in your Azure AD account and in the Command Center. Metadata from the Azure application (IdP) and the Command Center application (SP) are shared during this process.
Azure Active Directory is a third-party identity provider (IdP) that can act as the IdP when your users log on to Commvault. Commvault is the service provider (SP).
Microsoft supports up to 150 user groups for each SAML token. If a user belongs to more than 150 user groups when Azure AD issues the SAML token, they may experience unpredictable results. For more information about configuring group membership in tokens to prevent this issue, see Configure group claims for applications with Azure Active Directory on the Microsoft documentation website.
Before You Begin
You must have the Azure Active Directory Premium P1 or Premium P2 edition. For information, go to the Microsoft Azure Active Directory documentation.
If you need to create a SAML app for a specific company, in the upper-right corner of the page, from the Select a company list, select the company that you want to create the SAML app for.
Verify that groups in Azure AD have the exact name as the Commvault user groups you want to map them to. If an Azure AD group does not have the exact name as the group you want to map it to in Commvault, complete one of the following:
Create a new user group in Commvault that has the exact name as the group in Azure AD.
Rename the Azure AD group to match the user group in Commvault.
Create an Application in the Azure Portal
Go to the Microsoft Azure portal.
From the navigation pane, go to Azure Active Directory > Enterprise applications, and then click New application ().
Under Browse Azure AD Gallery, click Create your own application.
Enter a name for the application, select Integrate any other application you don't find in the gallery (Non-gallery), and then click Create.
Review the overview, and under the Getting Started section, complete the following steps required by Microsoft: Assign users and groups and Add user/group.
Note: Only the users and groups that are assigned in the steps can access the application.
From the navigation pane, go to Single sign-on, and then click the SAML tile.
The SAML-based Sign-on page appears.
In the upper-right corner of the Basic SAML Configuration section, click Edit.
In the Identifier (Entity ID) box and the Reply URL (Assertion Consumer Service URL) box, enter the Web Console URL, and then click Save.
Enter the URL in the following format: https://hostname:443/webconsole. For example, if you use Metallic, enter https://mnnn.metallic.io:443/webconsole where nnn is your ring number.
In the upper-right corner of the User Attributes & Claims section, click Edit.
In the Unique User Identifier box, specify user.userprincipalname.
In the SAML Signing Certificate section, beside Federation Metadata XML, click Download.
The federated metadata file that you download is the IdP metadata file that you will upload to Commvault.
Remain on the SAML-based Sign-on page.
You must upload the SP metadata file created in Commvault to your Azure application from the SAML-based Sign-on page.
Add a SAML Application in Commvault
From the navigation pane, go to Manage > Security.
The Security page appears.
Click the Identity servers tile.
The Identity servers page appears.
In the upper-right corner of the page, click Add > SAML.
The Add SAML app page appears.
On the General tab, in the Name box, enter the domain name that you want to associate users with.
The SAML application is created using the domain name.
For SAML user groups mapping to function correctly, the name that you enter here must be the same as your Metallic Tenant Name.
On the Identity provider metadata tab, in the Upload IDP metadata box, browse to the XML file that contains the IdP metadata, and then click Open.
The Entity ID and the Redirect URL from the file are displayed.
On the Service provider metadata tab, review the value in the Service provider endpoint box.
This value is automatically generated and is used in the SP metadata file. The format of the value is https://mycompany:443/webconsole.
To digitally sign the SAML message, move the Auto generate key for digital signing of SAML messages toggle key to the right.
On the Associations tab, identify the users who can log on using SAML:
To identify users by their email addresses, in the Email suffixes box enter an email suffix, and then click Add.
Note: You must use an email suffix as specified in the SAML integration settings to avoid integration issues.
If you face SAML integration issues, use a break glass account. The break glass account must be on different domain than that of the current domain.
To identify users by the companies they are associated with, from the Companies list, select a company, and then click Add.
To identify users by the domains they are associated with, from the Domains list, select a domain, and then click Add.
To identify users by the user groups they are in, from the User groups list, select a user group, and then click Add.
If you migrate from an Exchange On-premises server to an Exchange Online server, you must add the appropriate domain and user group.
You can add any combination of associations, and you can add multiple associations in each category.
The SP metadata file is generated, the IdP metadata is saved, and the SAML app properties page appears.
In the upper-right corner of the page, click Download SP metadata.
The name of the file that is downloaded begins with SPMetadata.
On the General tab, in the General section, next to NameID attribute, click the Edit button .
From the NameID attribute list, based on what is in the IdP response, select either Email or User Principal Name.
The SP metadata file must be uploaded to the Azure application.
Upload the Metadata to the Azure Portal
In the Microsoft Azure portal, on the Single sign-on page, click Upload metadata file.
Upload the SP metadata file.
The Identifier (Entity ID), Reply URL (Assertion Consumer Service URL), and Logout URL values are pre-filled using the SP metadata file.