Skip to main content
Browse Documentation
Register Contensis with Azure AD (legacy apps)

Register Contensis with Azure AD (for legacy app registrations created before October 2021)

Created by j.moore, last modified by zengenti on 10 Mar 2022


Note: this article applies to app registrations created before October 2021 or that have the Contensis CMS domain (e.g. verified in the Azure portal (see this link for further details).

To be able to register Contensis CMS with Azure, you will first need to complete the following actions on Azure:

  1. Register a new application for each CMS instance
    Register new applications for each Contensis CMS instance that will be integrated with Azure. For example, if you have a live and development instance you will need to register two applications, one for the live CMS url and one for the development CMS url.

  2. Update the application manifest
    Allows group integration and adds the application id url.

  3. Update permissions
    Allows user integration.

  4. Obtain relevant federation data for the CMS
    Obtaining credentials and discovery document data that is required to allow the Zengenti identity provider to federate with your registered Azure application.

Registering a new application

Go to the Azure portal and click ‘Azure Active Directory’ from the options in the left panel.

Azure Active Directory option in the Azure portal

You will now be taken to the ‘Azure Active Directory Overview’ screen.

Click ‘App Registrations’ from the ‘Manage’ section.

'App registrations' option in the 'Manage' section

You now have the option to add a new registration.

Click ‘+ New registration’ in the toolbar.

Adding a new registration in 'App registrations'

You’ll be presented with a form allowing you to enter initial application registration information.

This is the display name for the registration in your Azure portal,  and can be anything of your choosing.

Supported Account Types
This defines the types of accounts the application grants permissions to.

Redirect URI
This is not optional and is a requirement for the Zengenti identity provider. It should be entered in the following format:

https://<your cms domain>/authenticate 


After completion, the form should look similar to the following:

Completed application registration form

Click ‘Register’. The application is now registered.

Update the application manifest

To allow the Zengenti identity provider to be able to identify itself, and process a user’s group membership, the application manifest must now be amended.

Click ‘Manifest’ from the application overview: 

'Manifest' option in the application

Update the ‘groupMembershipClaims’ value to ‘SecurityGroup’ , then add the application id url in the form of ‘https://<your domain>/authenticate’, as shown below.

Click ‘Save’.

Updating the groupMembershipClaim and the identifier Uri

A message will display confirming that the manifest has been updated successfully.

'API permissions' option

Click ‘API permissions’ and then click ‘+ Add a permission’.

'Add permissions' option in 'API permissions'

Click ‘Microsoft Graph’ from the top. 

'Microsoft Graph' option in 'Request API permissions'

Now add the following permissions: 

  1. Delegated permissions

    • Directory.Read.All

    • User.Read

  2. Application permissions

    • Directory.Read.All

To add these, click on the relevant permission type and copy/paste the permission as listed above into the search field, then check the permission as shown below:

'Delegated' and 'Application' permissions in 'Request API permissions'
'Directory.Read.All' setting in 'Request API permissions'
'User.Read' setting in 'Request API permissions'
'Directory.Read.All' setting in 'Application permissions'

When the three permission options have been selected, click ‘Add permissions’.

This will take you back to the API permissions page, where a warning relating to changed permissions will be visible.

To allow the permissions to be available for the Zengenti identity provider, you must grant admin access. Click ‘Grant admin consent’ at the bottom of the page. 

Granting admin consent for API permissions

A further warning will then display - click ‘Yes’.

Clicking 'Yes' to allow 'API permissions' to be set

A success message will display, together with details of the permissions granted.

'API permissions' with all permissions successfully granted.

Obtain relevant federation data for the CMS

The Zengenti identity provider requires the following information to federate with your Azure instance:

  • Metadata endpoint

  • Application id

  • Tenant id

  • Tenant name

  • Application key

Metadata endpoint

Go to “Azure Active Directory” > App Registrations

e.g. Home > Zengenti Ltd > App Registrations

Click ‘Endpoints’ in the top bar.

'Endpoints' option under 'App registrations'

You will see a list of available application endpoints.

Copy the link for ‘Federation metadata document

'Federation metadata document' option for the endpoint

Application id

Click ‘Overview’ in the application options pane and then copy the ‘Application (client) ID’ which will be required when configuring Contensis to use your Azure AD instance.

'Application id' in the application 'Overview' section

Tenant id

In the ‘Overview’ screen, copy the 'Directory (tenant) ID’ which will be required when configuring Contensis to use your Azure AD instance.

'Directory (tenant) ID' in the application 'Overview' section

Tenant name

Select ‘Azure Active Directory’ from the panel on the left, and then ‘Custom Domain Names’. You can then copy the ‘Name’ listed as the ‘Primary’ - this is your tenant name and will be required when configuring Contensis to use your Azure AD instance.

'Tenant name' in the 'Custom Domain names' section

Application key

In the application overview panel, click ‘Certificates & secrets’ and then click ‘+ New client secret’.

Adding a client secret in the 'Certificates & secrets' section

You will see a form for naming and choosing the lifespan of a key. Complete as appropriate for your requirements, then click ‘Add’.

Adding a key for a client secret

You will now need to copy the key as directed before navigating away from this screen. Click the ‘Copy to clipboard’ icon. 

Important: Once you leave this screen or carry out any other action, you will no longer be able to retrieve this key value. 

Copying the key for a client secret

You have now completed the registration of Contensis with Azure and are now ready to configure Contensis to use Azure AD