Opselith
POWERSHELL / MICROSOFTTEAMS
FreeBeginnerRead-onlylow

Export Teams inventory

Export Microsoft Teams inventory to CSV with PowerShell, including team identity, visibility and archive state.

Open in PowerShell Builder →Browse all scripts

Generated locally in your browser · Review before running · Opselith does not connect to your tenant

What this PowerShell script does

Exports visible Teams.

Requirements

  • CSV output path - Example: C:\Temp\report.csv

Environment

  • Module: MicrosoftTeams
  • Permissions: Teams Administrator
  • Output: CSV report
  • Context: Microsoft Teams PowerShell
  • Risk: Low
Review before you run The script is generated locally. Test outside production first.
NEXT STEP

Ready to generate

Configure Export Teams inventory in the Builder, review the generated PowerShell and run it yourself in your own PowerShell session.

Configure this script →Open Builder
More about this script

Why use this template?

Use this free PowerShell script when you need a configuration inventory of Teams visible to the signed-in account. It is generated locally and can be reviewed before you run it yourself in your own PowerShell session.

The template uses MicrosoftTeams and requires Teams Administrator. Output: CSV report. Level: Beginner. Action: Read-only. Risk: Low.

Review before running

The script is generated in your browser. Read it before you run it, and test it outside production first. “Read-only” describes the script itself; anything you add around it can still change data.

Generate the script

  1. Open the template in the PowerShell Builder.
  2. Enter the requested values and review the module, permissions, output and risk.
  3. Generate the script, read it carefully, and test it outside production before use.

The script is generated locally in your browser. Nothing needs to be uploaded to Opselith.

Generate Export Teams inventory →

How to use this result

Use this report as a tenant-wide Teams inventory before ownership, lifecycle, migration or governance review.

When this helps

  • Create a CSV inventory of Teams before a governance or migration project.
  • Filter the tenant by visibility or archived state before opening more focused ownership and membership reports.

How to read the result

  • Each row represents a Team returned by Get-Team and includes GroupId, display name, description, visibility, archived state and mail nickname.
  • Visibility and Archived describe the Team configuration snapshot; they do not say whether the Team is active or still required.

Things to check

  • The result is limited to Teams the signed-in account and role can enumerate.
  • A Team inventory does not include channel-specific membership, owners or guest details unless you run the related reports.

What to do next: Use the owner, member and channel reports for Teams that need deeper governance review.

Related tasks

Official references

Before you runModule, permissions, inputs, compatibility and script checks
OPS / SCRIPT DETAILS

Script details

Exports the Teams returned to the signed-in administrator with stable Team identity and configuration fields. Review these details before generating or running the script.

teamsexportreporting
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.

What it works with

Module: MicrosoftTeams

MicrosoftTeams lets PowerShell read or manage Microsoft Teams settings.

Context: Microsoft Teams PowerShell

Compatibility: PowerShell 7 is the supported target for this cloud template.

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 (Required)

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.csv

This template is in the Free library and is generated locally in your browser. Opselith does not run it; you review and run the script in your own PowerShell session.

Example use

Exports the Teams returned to the signed-in administrator with stable Team identity and configuration fields.

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.

NEXT IN THE LIBRARY

Scripts for similar admin tasks and Microsoft services.

Browse Microsoft Teams PowerShell scripts →
POWERSHELLExport archived Teamsteams · export · archivePOWERSHELLExport members of one Teamteams · export · permissionsPOWERSHELLExport private Teamsteams · export · permissions