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
FreeIntermediateRead-onlylow
Export Teams for a user
Export the Microsoft Teams a specified user belongs to with PowerShell for access or migration review.
Generated locally in your browser · Review before running · Opselith does not connect to your tenant
What this PowerShell script does
Exports Teams a specified user belongs to.
Requirements
- User UPN - e.g. admin@contoso.com
- 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 locally. Test outside production first.
NEXT STEP
Ready to generate
Configure Export Teams for a user 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 Teams a specified user belongs to. 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: Intermediate. 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
- Open the template in the PowerShell Builder.
- Enter the requested values and review the module, permissions, output and risk.
- 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 for a user →How to use this result
Use this report to list the Team memberships returned for one user instead of reviewing every Team manually.
When this helps
- Review a user's Team footprint before offboarding, role change or migration.
- Create a focused list of Teams that may need owner or membership follow-up for one account.
How to read the result
- Each row describes a Team returned by Get-Team -User for the supplied user identity.
- Archived and visibility values describe the Team, not the user's activity level or role inside it.
Things to check
- This report does not show the user's Team role or private/shared-channel memberships.
- Membership returned by the cmdlet is a current-state view and does not provide historical join or removal dates.
Related tasks
Official references
Before you runModule, permissions, inputs, compatibility and script checks
OPS / SCRIPT DETAILS
Script details
Exports the Team objects returned for one specified user. 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
- User UPN - e.g. admin@contoso.com
- 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 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 Team objects returned for one specified user.
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.