Analysis updated 2026-06-24
Audit every Microsoft Teams policy in a tenant and produce a stakeholder-ready Excel workbook.
Compare current Teams settings to recommended values and see how many users each setting affects.
Fill in a DECISION column in the workbook and feed it back to apply or generate a review script.
Run a headless export from a CI runner using DeviceCode authentication.
| disintegr8te/teams-policy-export | zy-zmc/tianming-skill | andyvandaric/kiroku | |
|---|---|---|---|
| Stars | 114 | 27 | 25 |
| Language | PowerShell | PowerShell | PowerShell |
| Setup difficulty | moderate | hard | moderate |
| Complexity | 3/5 | 3/5 | 2/5 |
| Audience | ops devops | writer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires PowerShell 5.1 or 7.2+, the MicrosoftTeams and ImportExcel modules, and Teams Admin or Global Admin rights.
This tool is a PowerShell script that connects to a Microsoft 365 tenant, reads every Microsoft Teams policy setting it can find, and writes the results out as structured files plus a formatted Excel workbook. The workbook is laid out for stakeholder meetings: it shows what is currently configured, what the recommended settings are, where the two differ, and how many users are affected, and provides columns where attendees can record decisions. To run it, the user needs PowerShell 5.1 or 7.2 and above, the MicrosoftTeams and ImportExcel modules from the PowerShell Gallery, and either Teams Administrator or Global Administrator rights. The basic usage is to open PowerShell in the tool folder and run Export-TeamsPolicies.ps1. A browser window asks for sign-in, the script connects to Teams, discovers around 70 to 80 policy cmdlets, dumps each one to JSON and CSV, and produces TeamsPolicies.xlsx in a timestamped output folder. For headless or SSH sessions there is a DeviceCode authentication mode that prints a code to enter at microsoft.com/devicelogin. The README documents several parameters. IncludeAssignments queries every user in the tenant to attach policy assignments, with BatchSize and UserResultSize knobs for memory and scale. DefaultsOnly limits output to global default rows. SkipExcel skips workbook generation, ExcelOnly rebuilds the workbook from a previous export without reconnecting to Teams. A second workflow lets the user fill in a DECISION column in the Excel after the meeting and feed it back with -ApplyDecisions. That mode can generate a reviewable PowerShell script, do a dry run with no changes, or apply directly to global policies after confirmation. Output is organized into raw-json, flat-csv, the workbook, a manifest, and a README.
PowerShell script that connects to a Microsoft 365 tenant, dumps every Teams policy to JSON and CSV, and builds an Excel workbook for stakeholder review and apply.
Mainly PowerShell. The stack also includes PowerShell, MicrosoftTeams, ImportExcel.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.