Create an Org Chart from Microsoft Entra ID in Microsoft 365

A useful org chart starts with accurate identity data. In 2026, Microsoft Entra ID, formerly Azure AD, remains the foundation for organization views across Microsoft 365, including Teams, Outlook, SharePoint, profile cards, Power Apps, Visio, Power BI, and Microsoft Graph-based solutions.

Why org charts still matter

Org charts help employees understand reporting lines, find the right colleague, and clarify responsibilities across departments, locations, and business units. They are especially valuable during onboarding, reorganizations, mergers, and hybrid work. In Microsoft 365, the most reliable org chart experiences are powered by directory attributes such as display name, job title, department, office location, phone number, and, most importantly, the manager relationship stored in Microsoft Entra ID.

Microsoft Entra ID is the source for organization relationships

Microsoft Entra ID is the identity platform behind Microsoft 365. When each user has a manager assigned and core profile fields are kept current, Microsoft 365 can show organization context in profile cards, Teams, Outlook, SharePoint, Microsoft Search, and other people experiences. For hybrid environments, this data may be synchronized from on-premises Active Directory using Microsoft Entra Connect Sync or Cloud Sync. For larger organizations, HR-driven provisioning from systems such as Workday or SAP SuccessFactors can help keep joiner, mover, and leaver data consistent.

Where users can see org chart data in Microsoft 365

Modern Microsoft 365 experiences use profile and relationship data in several places. Outlook and Microsoft 365 profile cards show contact details, reporting lines, and related people information. Microsoft Teams includes people search, profile cards, and the Organization view where available. SharePoint can display people information through people-focused web parts and organization chart experiences on modern pages. Microsoft Search can help users discover people by name, role, department, or related profile information. Microsoft 365 Copilot experiences may also use Microsoft Graph data according to licensing, permissions, and tenant configuration.

How to prepare your directory data

Before building an org chart, decide which system owns employee data: HR, on-premises Active Directory, Microsoft Entra ID, or another authoritative source. Then standardize profile fields such as jobTitle, department, companyName, officeLocation, businessPhones, mobilePhone, and employee attributes where appropriate. Assign each employee a manager and validate that executive, shared-service, contractor, and matrix-reporting scenarios are handled consistently. Microsoft 365 org charts are usually based on a primary manager relationship, so dotted-line reporting may require a custom Power Apps, Power BI, Viva, or Microsoft Graph solution.

Basic admin workflow: assign managers and validate the result

A practical implementation path is: 1. Review current user profile completeness in Microsoft Entra ID. 2. Assign or synchronize each user’s manager attribute from the authoritative source. 3. Confirm that inactive accounts, shared mailboxes, service accounts, and external guest accounts are not incorrectly included in employee reporting lines. 4. Wait for Microsoft 365 services to refresh directory data. 5. Validate the result in Teams, Outlook profile cards, Microsoft 365 profile experiences, and SharePoint. Administrators can manage individual users in the Microsoft Entra admin center, automate updates with Microsoft Graph or Microsoft Graph PowerShell, or use HR-driven provisioning for repeatable lifecycle management.

Options for creating org charts in 2026

For many companies, built-in Microsoft 365 profile cards and Teams organization views are enough. If you need a page-based experience, use SharePoint people and organization chart capabilities. If you need a presentation-ready diagram, Microsoft Visio can create data-linked organization charts from supported data sources, but Visio licensing is separate from many Microsoft 365 plans. If you need a mobile or role-specific experience, Power Apps can use the Office 365 Users connector and other data sources to build an employee directory or org chart. If you need analytics, Power BI can visualize reporting structures and workforce attributes when data is modeled carefully. If you need a tailored application, Microsoft Graph can retrieve user, manager, and directReports data with appropriate permissions.

Power Apps and licensing considerations

Power Apps is the current name for the low-code application platform. Some Microsoft 365 subscriptions include limited Power Apps use rights for standard connectors such as Office 365 Users, but licensing depends on the app design, connectors, data sources, environments, and user access. Premium connectors, Dataverse, custom connectors, advanced automation, or direct Microsoft Graph integration may require additional Power Platform licensing. If licenses are purchased through CSP, they are typically transacted under Microsoft’s New Commerce Experience (NCE), so term length, cancellation windows, add-ons, and seat changes should be reviewed before rollout.

Security, privacy, and governance

Org charts contain sensitive business information. Apply least-privilege administration, limit who can update identity data, and review application permissions before granting Microsoft Graph access. Be careful with external sharing, guest access, and screenshots or exports that expose reporting lines, phone numbers, locations, or executive structures. Use role-based access control in Microsoft Entra ID, monitor changes to user attributes, and align profile visibility with internal privacy policies and regional compliance requirements.

What changed from older Azure AD-based guidance

The retired Azure AD name has been replaced by Microsoft Entra ID. Skype for Business Online and older Delve-centric guidance should no longer be treated as the primary path for org chart discovery. The recommended approach is to maintain accurate manager and profile attributes in Microsoft Entra ID, then use current Microsoft 365 people experiences such as Teams, Outlook profile cards, SharePoint, Microsoft Search, Power Apps, Visio, Power BI, or Microsoft Graph depending on the level of customization required.

Key takeaways

• Microsoft Entra ID manager relationships are the foundation for most Microsoft 365 org chart experiences.
• Teams, Outlook profile cards, SharePoint, and Microsoft Search can surface org information without building a custom app.
• Power Apps, Power BI, Visio, and Microsoft Graph are better choices when you need custom layouts, analytics, automation, or integration with HR data.
• Accurate org charts require ongoing data governance, HR or directory synchronization, lifecycle processes, and privacy controls.
• Licensing varies by Microsoft 365, Teams, Visio, Power Platform, Copilot, and CSP/NCE subscription terms, so confirm requirements before deployment.

Need help cleaning up Microsoft Entra ID profile data or building a Microsoft 365 org chart experience? IT Partner can assess your directory, licensing, Teams configuration, and Power Platform options, then recommend the simplest secure approach for your organization.