ms365-tenant-manager_skill

This skill helps Global Administrators streamline Microsoft 365 tenant setup, security, and governance with actionable guidance and automation.
  • Python

1.4k

GitHub Stars

7

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill alirezarezvani/claude-skills --skill ms365-tenant-manager

  • expected_output.json2.0 KB
  • HOW_TO_USE.md7.1 KB
  • powershell_generator.py13.9 KB
  • sample_input.json471 B
  • SKILL.md9.3 KB
  • tenant_setup.py16.6 KB
  • user_management.py16.0 KB

Overview

This skill provides comprehensive Microsoft 365 tenant administration guidance and automation for Global Administrators. It covers tenant setup, user and group lifecycle, security and compliance policies, Teams/SharePoint/Exchange administration, license optimization, and reporting. The skill delivers step-by-step instructions, ready-to-run PowerShell with safety checks, validation checklists, and rollback procedures.

How this skill works

Provide an action type (setup, create, modify, delete, report, audit), resource details, organizational context, current state, and desired outcome. The skill validates inputs, recommends Microsoft-recommended configurations, and generates actionable outputs: manual steps, PowerShell scripts with dry-run and logging, configuration checklists, and compliance reports. Outputs include safety checks, rollback guidance, and module dependency notes for execution.

When to use it

  • Initial Microsoft 365 tenant setup for a new organization
  • Bulk user or license provisioning and lifecycle automation
  • Implementing or validating Conditional Access, MFA, DLP, or retention policies
  • Provisioning and governing SharePoint sites, Teams, and external sharing
  • Generating audit reports, usage analytics, or license cost optimization
  • Creating repeatable PowerShell automation with dry-run and logging

Best practices

  • Enable and enforce MFA before adding standard users and secure admin accounts with PIM
  • Use group-based licensing and consistent naming conventions for scalability
  • Start Conditional Access in report-only mode, then enforce gradually after validation
  • Prefer Microsoft Graph API and modern PowerShell modules; include try/catch and logging
  • Test scripts in a non-production tenant with -WhatIf/dry-run; store credentials in Azure Key Vault

Example use cases

  • Set up a 50-person tenant with domains, DNS records, baseline security, and onboarding checklist
  • Generate a PowerShell script to provision 100 users from CSV with licenses and group assignments
  • Configure a Conditional Access policy requiring MFA for all privileged accounts and provide rollback steps
  • Audit inactive users for 90 days and produce a remediation plan and bulk disable script
  • Standardize Teams templates, external sharing rules, and guest lifecycle policies for a regulated org

FAQ

Global Administrator or equivalent role-based permissions are typically required; some tasks may need specific admin roles like Exchange or SharePoint Admin.

How do I safely test automation before production?

Run scripts in a non-production tenant, use -WhatIf/dry-run modes, validate outputs with report-only Conditional Access, and enable verbose logging for audits.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
ms365-tenant-manager skill by alirezarezvani/claude-skills | VeilStrat