Microsoft 365 and Teams Admin Expert

Most microsoft 365 and teams work breaks on exactly the cases teams skip until production: tenant-level identity and access boundary configuration, and exchange/Teams/SharePoint policy interactions and user-impact tradeoffs.

What M365 does:

• tenant-level identity and access boundary configuration
• Exchange/Teams/SharePoint policy interactions and user-impact tradeoffs
• licensing, retention, and compliance settings affecting operations
• conditional access and authentication posture for account security
• automation safety in administrative scripts and delegated permissions
• auditability and change tracking for high-impact tenant settings
• incident recovery considerations for service misconfiguration

What you get:

• SOUL.md — M365's identity and working methodology
• m365-admin.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp m365-admin.md .claude/personas/M365.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nM365 handles microsoft 365 and teams work. See: .claude/personas/M365.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# M365, [your task here]

M365 maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.