10 Must-Have Teams Scripts for Microsoft 365 Administrators

Microsoft Teams administration becomes increasingly complex as environments grow. From governance and visibility to lifecycle management, administrators are expected to keep Teams sprawl under control while ensuring compliance and usability.

To simplify day-to-day administration, PowerShell scripts built on Microsoft Graph can save hours of manual effort. In this article, we’ve curated 10 must-have Microsoft Teams PowerShell scripts that every Microsoft 365 administrator should bookmark. These scripts focus on reporting, auditing, and proactive governance—and each one can automatically email reports to admins for easier monitoring.

Must-Have Microsoft Teams PowerShell Scripts

• Fetch and email Teams-enabled groups report (Teams vs Groups separation)
  This script identifies all Microsoft Teams in the tenant by filtering out Teams from standard Microsoft 365 groups. It provides administrators with a clear view of Teams-created workspaces without mixing them with non-Teams groups, making it easier to understand Teams usage across the tenant.

👉 Read more: Fetch and email Teams-enabled groups report

• Email private Microsoft Teams list to administrators
  Private Teams can pose governance challenges if left unchecked. This script generates a report of all private Teams and emails it to admins for regular review and compliance checks.

👉 Read more: Email private Teams list to M365 admin

• Email public Microsoft Teams list
  Public Teams are discoverable by all users and can grow rapidly. This script provides visibility into all public Teams, helping admins assess naming standards, descriptions, and usage.

👉 Read more: Email public Teams list to admin

• Email Teams without description report
  Missing descriptions often indicate poorly governed or hastily created Teams. This script helps enforce better documentation by listing Teams that lack descriptions and emailing the report to admins.

👉 Read more: Email Teams without description report

• Email archived Microsoft Teams report
  Archived Teams are easy to forget but still important for compliance and audits. This script retrieves all archived Teams and sends a clean report to administrators.

👉 Read more: Email archived Teams report

• Email recently deleted Teams report
  Tracking deleted Teams is critical for troubleshooting and recovery scenarios. This script lists recently deleted Teams and emails the details to administrators automatically.

👉 Read more: Email recently deleted Teams report

• Email recently created Microsoft Teams report
  New Teams are created frequently in active tenants. This script helps admins monitor recent Team creations, making it easier to enforce naming conventions and governance policies early.

👉 Read more: Email recently created Teams report

• Email Microsoft Teams owners list
  Knowing who owns which Team is essential for accountability. This script fetches all Teams along with their owners and emails the report to administrators.

👉 Read more: Email Microsoft Teams owners list

• Audit Teams with hidden membership for governance reviews
  As a complementary governance use case, this script can be reused during periodic audits to specifically focus on Teams with hidden membership, ensuring compliance with internal visibility policies.

👉 Read more: Hidden membership Teams audit script

• Fetch and email Microsoft Teams fun settings report
  Microsoft Teams includes “fun” features such as Giphy, memes, stickers, and custom emojis, which may not be suitable for all organizations. This script retrieves the fun settings configuration for Microsoft Teams and emails the report to administrators, helping them review and align Teams’ user experience with organizational policies

👉 Read more: Fetch and email Microsoft Teams fun settings report

If you’re tired of building custom Graph PowerShell scripts just to make sense of Microsoft 365 data, take a look at the M365 Reporting Tool – Community Edition. It provides ready-to-use reports without dealing with Graph API endpoints or scripting overhead.

👉 https://github.com/m365corner/m365corner-reporting-tool-community-edition.git