Cloud Migration Hub: User Profiles for Jira (Microsoft Attributes Sync)

Atlassian is ending support for Jira Data Center by March 2029.
This page explains how User Profiles for Jira (Microsoft Attributes Sync) will be migrated from Data Center to Jira Cloud, what you need to prepare, and what you can expect.

🔎 Quick overview

Question	Answer for User Profiles for Jira (Microsoft Attributes Sync)
Migration effort and automation level	Medium – Usually one migration run with verification steps for user attributes. Manual Configuration required – Core user profiles and synced attributes migrate automatically; Custom Fields and permissions need manual adjustment.
Main risks/limitations	Certain Data Center–specific user information may not exist in Cloud. Custom field mappings require manual reconfiguration. Authentication and directory sync methods differ between Data Center and Cloud.
Key prerequisites	Microsoft Entra ID for attribute sync Jira Cloud site provisioned and accessible Test environment recommended for attribute sync validation
Best practice	User impact during migration: Short downtime recommended. Typical duration: From several minutes up to a few hours, depending on the number of custom fields to be configured. Recommendation: Perform migration outside business hours or on weekends.
Available Cloud types	User Profiles for Jira (Microsoft Attributes Sync) is available on Commercial Cloud.

What User Profiles for Jira (Microsoft Attributes Sync) does

User Profiles for Jira (Microsoft Attributes Sync) synchronizes user attributes from Microsoft Entra ID (Azure AD) with Jira Cloud.

Additional profile details, such as job title, department, location, phone number, and manager, can be displayed directly on Jira issues for assignees, reporters, or user-picker fields. These attributes can also be used in JQL, queues, and automation rules.

By making Entra ID user data available in Jira, teams can reduce resolution time, automate approval workflows (e.g., using the manager attribute), and support structured processes across IT, HR, Finance, and Marketing.

This section explains how your app data and configuration move from Data Center to Cloud.

🔄 How to migrate

Find detailed information on migrating the app in our comprehensive migration guide. This guide provides step-by-step instructions to help you transition smoothly and efficiently.

🤝 Support & resources

Documentation for User Profiles for Jira (Microsoft Attributes Sync)
- Documentation for Data Center version
- Documentation for Cloud version
Marketplace listing
- User Profiles for Jira on Atlassian Marketplace
Cloud Security Standards
- Link to Communardo Cloud Security Standards page
Feature parity & known limitations
- Differences between User Profiles for Jira Data Center and Jira Cloud
Need help with planning or running your migration?
- Contact our support

❓ FAQ for User Profiles for Jira (Microsoft Attributes Sync) migration

What are the biggest changes compared to Data Center?

Microsoft Entra ID required
No extended user profiles - user data sourced directly from Microsoft Entra ID
There are certain differences between our DC and Cloud versions.

Are you a solution partner and have questions about licensing during migration?