Sign In
Choose your region
Sign in to your workspace
Sign In
Choose your region
Sign in to your workspace
Email is still where the compromise starts. Verify mailbox auditing, external auto-forwarding, legacy mail protocols and mailbox delegation across every client tenant, and deploy an Exchange baseline where a tenant has nothing.
Exchange configuration across every client tenant in one view
An Exchange baseline where a tenant has nothing
Drift alerts when a control moves off the standard
Exportable evidence mapped to recognized standards
A forwarding rule quietly copying mail out, a legacy protocol accepting a password that skips MFA. These are configuration states, not alerts, and nothing is watching them across a whole client base.
Exchange is the workload clients and third-party vendors touch most often. A setting relaxed for one migration or one integration stays relaxed, and no one is told.
The Exchange admin center is single-tenant. Across every client an MSP manages, answering one mail question means a login per client, or a script somebody now owns and maintains.
Mail leaving the organization through a forwarding rule is the quietest form of data loss there is. Augmentt shows which tenants still allow external forwarding, so the risk is visible before an incident occurs.
SMTP AUTH still accepts a password on tenants where MFA is otherwise enforced. Augmentt shows which tenants have it enabled, so you find the gap between an MFA report and what mail actually accepts.
An investigation is only as good as the audit trail that was already running. Mailbox audit configuration sits in one view across the whole client base, so a team knows which clients have an evidence trail and which do not, ahead of the incident that depends on it.
Exchange configuration is scored against a security baseline alongside the rest of the tenant, so mail sits in the same compliance view as identity and endpoint. When a control moves off the standard, drift is flagged and the platform’s alerting, auto-remediation and snoozing apply.
Every Exchange control a team manages maps back to a recognized standard. Export the evidence in a click when an auditor or a cyber insurer asks for it, instead of rebuilding it by hand. And when a control needs premium Microsoft licensing, the view says so, turning a compliance gap into a licensing conversation.
The same five jobs, done per tenant or done once.
Magic Link onboarding and GDAP automation bring client tenants in on the permission model an MSP already uses for Conditional Access and Intune.
Compare auto-forwarding, SMTP AUTH, mailbox auditing and delegation across every client in one view, and see where licensing limits what a client can enforce.
Push a baseline where a tenant has nothing, then let drift alerts tell the team when a forwarding rule or a legacy protocol comes back.
The same coverage pays off differently depending on which seat you sit in.
Common questions from MSPs evaluating multi-tenant Exchange Online management.
It is checking and setting Exchange Online security configuration across many client tenants from one console instead of opening the Exchange admin center per client. Augmentt shows mail configuration across all client tenants in one view, flags where a control is off, and deploys a baseline Exchange configuration where a tenant has nothing.
Yes. The external auto-forwarding setting is shown across every managed tenant in one view, so the tenants where mail is still allowed to leave the organization are visible on one screen rather than found after an incident.
Yes. SMTP AUTH status is shown across the whole client base in one view, so the clients still accepting authentication that bypasses MFA are identifiable at a glance rather than one login at a time.
Yes. Mailbox audit configuration is shown across every managed tenant in one view, so a team knows before an incident which clients have the audit trail an investigation depends on and which do not.
Yes, a custom or standardized Exchange baseline can be pushed across tenants.
Drift on a managed control is flagged against the same benchmark used for reporting, and the platform’s alerting, auto-remediation and snoozing apply, so a re-enabled forwarding rule or a re-opened legacy protocol surfaces as an alert rather than as an audit finding later.
Every check maps to a recognized standard including CIS, HIPAA, CMMC, NIST CSF and Essential Eight, and posture is exportable. Augmentt evidences control state, so the report a client sees and the evidence an auditor sees come from the same source.
Augmentt scores each tenant’s Exchange configuration against a named benchmark and exports the result as evidence. Lighthouse deploys baseline tasks and reports whether they landed; it doesn’t produce a benchmark score or an auditor-ready record.
Yes. Microsoft Exchange sits alongside Conditional Access, Microsoft Intune, Defender, SharePoint and OneDrive sharing, Microsoft Teams policy and Microsoft Purview in the same multi-tenant console, with one compliance view across all of them.
Run Microsoft 365 security reports across your customers and see which tenants still allow external forwarding, which still accept legacy protocols, and where mailbox auditing was never switched on.
HIPAA
NIST / CIS
Safety standards
MAPPED
CMMC