How to extract an organization chart from Microsoft Teams

Microsoft Teams shows reporting lines in profile cards and the Organization tab, but it does not provide a direct Excel or CSV export. The hierarchy comes from manager relationships in Microsoft Entra ID. Export those relationships with Microsoft Graph or Entra PowerShell; if you do not have directory access, extract the visible names and reporting lines from overlapping Teams screenshots.

Option 1: export reporting lines with Microsoft Graph

Microsoft Graph exposes the hierarchy as relationships. GET /users/{id}/manager returns the person one level above a user, while GET /users/{id}/directReports returns the people immediately below them. The directReports endpoint does not return the entire tree recursively, so a full export must page through users and resolve a manager for each one.

• GET /users/{id}/manager — who this person reports to
• GET /users/{id}/directReports — who reports to this person
• GET /users — start from the top and walk down, or page through everyone

For an organization-wide export, register an app in Entra ID, request the least directory permission that covers your tenant, and obtain administrator consent. Store both a stable identifier and a readable value for the manager. Names are not unique; manager_id or manager_email is a safer key than manager_name.

Option 2: export with Entra PowerShell

For a one-off administrator export, Entra PowerShell is easier to audit than a recursive script. Connect with User.Read.All, list active member users, resolve each manager with Get-EntraUserManager, and write a flat employee-manager row. Microsoft's current Entra PowerShell documentation also provides Get-EntraUserDirectReport for walking downward from a known leader.

$users = Get-EntraUser -All -Property Id,DisplayName,UserPrincipalName,JobTitle,Department,AccountEnabled $rows = foreach ($user in $users | Where-Object AccountEnabled) { $manager = Get-EntraUserManager -UserId $user.Id -ErrorAction SilentlyContinue [PSCustomObject]@{ employee_id = $user.Id employee = $user.DisplayName email = $user.UserPrincipalName title = $user.JobTitle department = $user.Department manager_id = $manager.Id manager = $manager.DisplayName } } $rows | Export-Csv org-chart.csv -NoTypeInformation -Encoding UTF8

Test the command on a small group before running it tenant-wide. Directory permissions can expose personal and organizational data, so keep the export in an approved location and remove columns you do not need. For a visualization, the essential columns are employee_id, employee, manager_id, and manager.

Option 3: extract the chart from Teams screenshots

Microsoft Support confirms that the Teams Organization tab shows who a person reports to and who reports to them. It is not available in every tenant because an administrator must enable it. When the tab is available but you cannot query Entra ID, screenshots are the practical fallback for a small team.

1. Start with the most senior person visible in your part of the organization and open their Organization tab.
2. Capture the manager, selected employee, and every visible direct report in the same screenshot.
3. Open each direct report and take the next screenshot with one or two people overlapping the previous image. The overlap is how you verify the branch connection.
4. Extract each image into the same columns: employee, title, department, manager, and source_screenshot.
5. Append the rows, normalize names, and deduplicate on employee plus manager. Review people who appear with two different managers before importing the result.

Use a stable table shape

Keep the export flat even if the final result is a tree. One employee per row makes missing managers, loops, duplicates, and disconnected branches easy to find. It also imports cleanly into Power BI, Visio, Lucidchart, OrgPlus, and most HR systems.

Validate the hierarchy before visualizing

• Every employee except the root should have exactly one manager.
• No employee_id should also appear as its own manager_id.
• Disabled accounts, contractors, shared mailboxes, and unfilled positions should be marked explicitly instead of silently dropped.
• Duplicate display names should be resolved with email or Entra object ID.
• A manager referenced by a row should either have their own row or be deliberately marked as outside the exported scope.

Once the checks pass, a flat employee-manager table is enough to render the org chart. Keep the CSV as the source of truth and regenerate the diagram when Entra relationships change instead of editing boxes manually.