m365-audit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_tenant_privacy_configA | Return the tenant's M365 privacy / compliance configuration with verification status. Mirrors the structure of the m365-privacy-config checklist (data residency, Copilot no-training, Azure OpenAI retention, BAA scope) so the output can be pasted straight into a sign-off document for the compliance owner. Returns a dict with the tenant metadata, a summary count of verified vs
outstanding items, and per-item evidence (or |
| find_orphaned_documentsA | Find documents in the tenant that look orphaned. A document is flagged if EITHER:
Each flagged document includes a recommendation (archive, reassign, or review). Useful for monthly governance review or before enabling Copilot on a site (orphaned docs leak into Copilot grounding by default). |
| audit_conditional_access_policiesA | Audit Conditional Access policies for risks. Lists every CA policy and flags any that aren't in |
| list_dlp_policiesA | List Data Loss Prevention (DLP) policies. Optional |
| summarize_copilot_usageA | Summarize Microsoft 365 Copilot usage. With no arguments, returns a tenant-wide summary plus per-team breakdown
sorted by adoption percentage (lowest first - the rollout-gap teams).
With Adoption is |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct aspect of M365 auditing: conditional access policies, tenant privacy config, orphaned documents, DLP policies, and Copilot usage. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (audit_, check_, find_, list_, summarize_) using snake_case, making them predictable and easy to distinguish.
With 5 tools covering different audit domains, the count is well-scoped for an audit-focused MCP server. Each tool serves a clear purpose without redundancy.
The tools cover key audit areas (conditional access, privacy, orphaned docs, DLP, Copilot) but lack common audit tasks like user activity logs, sharing policy audits, or admin role reviews. Several important audit dimensions are missing.