IMPORTANT Azure AD may require specific access previously configured in order to allow mapped fields to appear in Jira. Click here to see how to configure them.
After you click on the "Get Started" option or access the "Configuration" link, the following screen is displayed.
Select "Azure" as the Identity Provider to connect and fill the fields accordingly:
Application (Client) ID: Inform the Azure AD Application ID. The Azure active directory allows to create applications and service principal that can be used with the role-based access control. When you have applications, hosted services, or automated tools that needs to access or modify resources, you can create an identity for the app. Learn more here.
Directory (Tenant) ID:A tenant represents an organization. It's a dedicated instance of Azure AD that an organization or app developer receives at the beginning of a relationship with Microsoft. That relationship could start with signing up for Azure, or Microsoft 365, for example. Click here to learn how to set up a tenant in Azure AD. If you already have a tenant, click here to learn how to find it in Azure AD.
Client Secret: This is the password of the service principle. If you don't have a client secret yet, click here to see how to create one.
After informing all data, click on "Save".
When clicking on "Save" the system validates the connection with Azure AD and informs in case any issue occurs.
After saving the connection data, the "Client Secret" field appears empty when you return to the Authentication screen. This is for security purposes. The connection is still alive, we just hide this content to avoid exposing sensitive data.
As soon as the connection is established, the system will show a pop-up to move to the next step: