Security
Built for the people who review security postures for a living. Here's exactly how M365 Toolbox works under the hood.
Read-only by design
The application is hardcoded to only perform read operations. Write commands cannot execute — this isn't a permission setting you can toggle, it's baked into the code. An explicit allowlist determines which API calls the platform can make. If a command isn't on the list, it doesn't run.
Can't read user content
The platform cannot access email messages, documents, chat conversations, or any user-generated content. It only reads configuration and policy settings — the stuff that defines how your tenant is set up, not what people are doing inside it.
How access works
IT Departments
Standard Microsoft Entra ID admin consent. A Global Administrator approves a set of read-only permissions once. Setup takes about two minutes. No agents to install, no firewall rules to configure.
MSPs
Access works through GDAP (Granular Delegated Admin Privileges) via Microsoft's partner framework. It uses your existing partner relationships — no separate credentials or service accounts required.
Data handling
Tenant configuration is processed in memory during assessments. Security baselines are encrypted at rest. No personally identifiable information is written to application logs. Each subscriber's data is logically isolated at the database level.
Infrastructure
Hosted entirely on Microsoft Azure. All data is encrypted in transit (TLS) and at rest. Authentication is handled through Microsoft Entra ID — there are no separate passwords to manage or password databases to protect.
Compliance
SOC 2 Type 2 journey is in progress. We're not going to claim a certification we haven't earned yet — but the controls, processes, and architecture are being built to that standard from day one.