How to Use Azure Entra ID User Attributes Natively in Jira Cloud?

[David Martínez López]

Hi Community,

I'm looking for a **native way in Jira Cloud** to access and use **metadata from users synchronized via Azure Entra ID (formerly Azure AD)**.

What I'm trying to achieve is to **automatically extract specific custom attributes** from the user directory (such as **office location, department, country, region, manager**, etc.) and use them within Jira Cloud as:

- Custom fields in issues.
- Reference data for automations (e.g., with Jira Automation).
- Conditions or validations within workflows.

The goal is that when a user is involved in a ticket (e.g., as "Reporter" or "Assignee"), these metadata attributes are already available and linked without requiring manual input or complex external integrations.

**Is there any native functionality in Jira Cloud that supports this type of integration with Azure Entra ID and the use of its user attributes?**
If not natively supported, what alternatives does the community recommend (e.g., Marketplace apps, APIs, or other integration options) to automate and enrich Jira tickets with this directory data?

Thanks in advance for any guidance!

[tzuhwii]

Hi there,

Are you using Jira Assets? If so, we’re currently using the app “JSM Assets – Microsoft Entra ID (Azure AD) Beta Integration”, and it does exactly what you're looking for. 

While we can’t modify the imported data in Entra ID directly, we manage and manipulate the data within the asset schema itself. We’re leveraging these attributes heavily for automations.

For example, as you may know, the native Reporter or Assignee fields in Jira/JSM only pull limited user info from the Atlassian directory — typically missing details like phone numbers or employee IDs. To get around this, we created a custom field that maps to the user object in the asset schema. This allows us to display full Entra ID user details directly in the ticket.

Hope that helps!

[Mohammed Abdul]

@tzuhwii 

does the information that pulls from Entra via jsm Asset update information for example attribute like department, if user changes department would the integration update information? how did you link for example attribute like department to be linked to a custom field and have it displayed for agents within the context field so we us agents build customised context field of employees details hope this makes sense? 

[Eduardo Anflor - MindPro]

Hi, @David Martínez López 

If you have Atlassian Guard, you should be able to sync the basic information from your identity provider, but I believe you cannot import it into custom fields natively. If you do not have Atlassian Guard or want to bring more than just basic attributes, you may need to look for a marketplace app. If you are open to that, I recommend Mindpro Sync. I work at Mindpro and believe the app fits your use case. 

The app lets you sync all the main attributes from different identity providers (Entra ID/Azure AD, MS 365, Okta, OneLogin, and Google Workspace) and map them to Jira read-only custom fields. This means you can use these fields not only in automation but also in JQL within Jira:

The app also allows you to display these attributes inside issue screens. It provides a way to display the hierarchy, groups, and set approvers using the manager information (there are also post-functions for additional workflow approvals):

If you want to share this information with internal or external customers, you can also choose to display these attributes or the hierarchy in the Customer Portal:

I hope that helps.

Regards,

Eduardo