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

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

🔎 Quick overview

Question	Answer for User Profiles for Confluence (Microsoft Attributes Sync)
Migration effort and automation level	Medium – Usually one migration run with verification steps for user attributes. Partially automated – Core user profiles and synced attributes migrate automatically; some mappings, space permissions, or macros may need manual adjustment.
Main risks/limitations	Certain Data Center–specific user attributes or macros may not exist in Cloud. Space permissions or page restrictions may require manual reconfiguration. Authentication and directory sync methods differ between Data Center and Cloud.
Key prerequisites	Active Microsoft 365/Azure AD environment for attribute sync Confluence Cloud site provisioned and accessible Backup of Confluence Data Center spaces recommended Test migration in a staging environment suggested
Best practice	User impact during migration: Short downtime recommended; read-only mode for affected spaces advised. Typical duration: From several minutes up to a few hours, depending on the number of users and spaces. Recommendation: Perform migration outside business hours or on weekends.
Available Cloud types	User Profiles for Confluence (Microsoft Attributes Sync) is available on Commercial Cloud.

What User Profiles for Confluence (Microsoft Attributes Sync) does

User Profiles for Confluence (Microsoft Attributes Sync) enables administrators to synchronize user attributes from Microsoft 365 (Entra ID) with Confluence Cloud.

Profile details such as pictures, email addresses, phone numbers, positions, departments, and locations are automatically kept up to date. This information can be displayed directly on Confluence pages using the Contact Person and Contact List macros.

By embedding synchronized profile data into pages and spaces, teams can quickly identify responsible colleagues, check availability via Microsoft Teams status, and get in touch without leaving Confluence.

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 Confluence (Microsoft Attributes Sync)
- Documentation for Data Center version
- Documentation for Cloud version
Marketplace listing
- Link to app on Atlassian Marketplace
Cloud Security Standards
- Link to Communardo Cloud Security Standards page
Feature parity & known limitations
- Link to parity/limitations page
Need help with planning or running your migration?
- Link to Communardo support

❓ FAQ for User Profiles for Confluence (Migration Attributes Sync) migration

Can users work while the migration is running?
Read-only mode for affected spaces is recommended to avoid inconsistencies.

What is not migrated automatically?

Certain global space settings
Page restrictions that depend on Data Center user groups
Custom macro settings (if not supported in Cloud)

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?