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 · Accepted solution]

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? 

[David Martínez López]

@tzuhwii 

Thank you very much for your comment, but according to this article, I believe the product is discontinued.

[JSDCLOUD-10502] Azure Integration for JSM Assets: cree y realice un seguimiento de las solicitudes de características de los productos de Atlassian.

[JSDCLOUD-15146] Cambio de adaptador de usuarios de ID de Entra: capacidad para admitir Administrador, Departamento y otros campos importantes: cree y realice un seguimiento de solicitudes de funciones para productos de Atlassian.

[tzuhwii]

@David Martínez López We are still using this but this was implemented before Atlassian Data Manager was in the picture.
But it should still work the same if you use the API adapter for Entra Data Manager - Entra ID User Adapter | Assets | Atlassian Support although not all fields  are retrieved compared to the app. 

[tzuhwii]

@Mohammed Abdul we push the import button in the asset schema to retrieve new information from Entra. Typically once a day but you can run it as frequent as you like.

[dmartinez_ext]

@tzuhwii Thank you very much for the response. How do you handle this part? "To avoid this, we create a custom field that is assigned to the user object in the resource schema. This allows us to display the full details of the Entra ID user directly in the ticket."

Thanks!

[Ankita Mehta]

Hi @David Martínez López

You’re asking if Jira Cloud can natively pull in Azure Entra ID (formerly Azure AD) user attributes like department, location, or manager — and use them in issues, automations, or workflows. The short answer is: Not natively (yet). Jira Cloud doesn’t expose those Entra metadata fields by default. Please consider the following before you begin:

• Jira only shows basic user info (like name/email), not custom Entra attributes.
• Jira Automation and workflows can’t access Entra fields out-of-the-box.
• SCIM sync handles user provisioning, but not metadata enrichment.
• You’d need a workaround — either a connector, an app, or custom API setup.

 If you're looking for a deep and seamless integration without the headache of plugins, you may want to explore OpsHub Integration Manager (OIM) (an Atlassian partner) that supports syncing user metadata from systems like Azure Entra ID directly into Jira. It automates the flow of attributes like department, manager, and location — no manual entry, no scripting. Just connect your systems, and it runs.

If you have questions or want to see a demo, drop us a line.

Good Luck!

[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