What it works with
Module: MicrosoftTeams
MicrosoftTeams lets PowerShell read or manage Microsoft Teams settings.
Context: PowerShell 7 · Microsoft Teams
Compatibility: PowerShell 7 is the supported target for this Microsoft 365 template.
POWERSHELL / MICROSOFTTEAMS
ProIntermediateRead-onlylow
Export Teams channel inventory
Export Microsoft Teams channel inventory to CSV with PowerShell, including each channel membership type.
Generated securely after server-side Pro license validation · Review before running · Opselith does not connect to your tenant
What this PowerShell script does
Exports channels for each Team.
Requirements
- CSV output path - Example: C:\Temp\report.csv
Environment
- Module: MicrosoftTeams
- Permissions: Teams Administrator
- Output: CSV report
- Context: PowerShell 7 · Microsoft Teams
- Risk: Low
Review before you run The script is generated securely after server-side Pro license validation. Test outside production first.
NEXT STEP
Ready to generate
Configure Export Teams channel inventory in the Builder, review the generated PowerShell and run it yourself in your own PowerShell session.
More about this script
Why use this template?
Use this PowerShell template when you need to export channels for each Team. It can be previewed in the Builder; Pro access is required to generate it for your own environment.
The template uses MicrosoftTeams and requires Teams Administrator. Output: CSV report. Level: Intermediate. Action: Read-only. Risk: Low.
Review before running
The script remains preview-only until Pro access is enabled. Review it before running it, and test it outside production first. “Read-only” describes the script itself; anything you add around it can still change data.
Preview the script
- Open the template in the PowerShell Builder.
- Review the purpose, requirements, permissions, output and risk.
- Activate Pro when you are ready to generate the full script, then test it outside production.
Pro templates remain previewable before purchase or activation. No tenant connection is required. When you generate a Pro script, only the configuration values needed for that template are sent to Opselith after license validation.Preview Export Teams channel inventory →
How to use this result
Use this report to inventory channels across Teams before governance, migration or channel-membership review.
When this helps
- Find standard, private and shared channels across the Teams inventory.
- Prepare a channel list before deeper membership, migration or ownership checks.
How to read the result
- Each row identifies the parent Team and channel together with channel ID, display name, description and MembershipType.
- MembershipType identifies the channel model; it does not contain the actual member list.
Things to check
- Channel inventory does not prove whether a channel is active or still required.
- Use the channel-membership report for private or shared channels when access detail is needed.
Related tasks
Official references
Before you runModule, permissions, inputs, compatibility and script checks
OPS / SCRIPT DETAILS
Script details
Exports channels returned for each enumerating Team, including hosted and incoming shared-channel contexts. Review these details before generating or running the script.
Generated here. Run by you.Opselith does not connect to your tenant or run PowerShell. After generating, review the script and run it in your own PowerShell session.
Permissions and changes
Permissions: Teams Administrator
Risk: Low
Read-only: designed to collect information without intentionally changing the target environment.
Changes: Read-only. The script reads data and does not intentionally change the target environment.
Inputs
- CSV output path - Example: C:\Temp\report.csv
What to expect
Output: CSV report
Expect a CSV file at the path you choose. Open it in Excel or another CSV viewer and review the rows.
Example: C:\Temp\report.csvThis template is in the Pro library. Generating the full script requires eligible Pro or tester access. Opselith receives only the values needed to build the script; it does not connect to your tenant, run PowerShell or store the generated script. You review and run the result in your own PowerShell session.
Example use
Exports channels returned for each enumerating Team, including hosted and incoming shared-channel contexts.
Enter the required values in the Builder, review the generated script and confirm the output before running it.
Before you run: Make sure your account has Teams Administrator. Check that the MicrosoftTeams PowerShell module is available and that you are using the supported PowerShell version. Review the generated script and output path, then test outside production first.
Script checksWhat has been verifiedQA reviewed
Static checksPassed
PSScriptAnalyzerPending
Real-world run testNot yet recorded
Last checkedNot yet recorded
Real-world run results are shown only after Opselith reviews and accepts a tester report.
Tester: report a result →TEST STATUSWhat Opselith has checked
Last reviewed: 10 Sept 2026
PSScriptAnalyzer: Awaiting a release PSScriptAnalyzer gate that includes this script. No analyzer pass is claimed yet.
Pending or Not yet recorded means there is no accepted result on file yet. A passed analyzer check does not mean the script has been run in a real tenant.
Was this useful?One click. No email.