m365-admin
PassAudited by ClawScan on May 10, 2026.
Overview
This is a coherent Microsoft 365 admin guidance skill, but users should treat it as capable of planning high-impact tenant changes.
This skill appears safe as an instruction-only Microsoft 365 admin helper. Before using it for real tenant changes, make sure every generated script is reviewed, scoped to the intended users or resources, run first in audit or dry-run mode when possible, and executed only with the minimum Microsoft 365 permissions needed.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mis-scoped automation could change mailbox, Teams, SharePoint, or licensing settings for many users.
Bulk Microsoft 365 administrative changes are purpose-aligned for this skill, but they can affect many accounts or resources if executed without tight scoping and review.
“Bulk update mailbox settings across departments”
Use read-only audits first, define the exact target set, require user approval before changes, and keep a rollback plan for bulk operations.
If granted excessive admin rights, commands produced under this skill could alter tenant permissions, app access, or identity configuration.
The skill covers privileged Microsoft 365 identity and application administration. This matches its purpose, and no credential collection or hidden token handling is shown.
“Use Microsoft Graph PowerShell for identity and workload automation” and “Manage service principals, apps, roles”
Use least-privilege Microsoft 365 roles, avoid broad tenant-wide consent unless necessary, and review all Graph or Exchange commands before running them.