Microsoft 365 connection
Read-only delegated Microsoft Graph consent linking the customer tenant for posture assessment.
Solution
A customer workspace is one managed client’s security world: their Microsoft 365 tenant, their external assets, their findings, their reports, and the team members allowed to touch them. Your MSP operates across all of them from a single organization account, without a login per client.
Read-only delegated Microsoft Graph consent linking the customer tenant for posture assessment.
Domains, websites, and discovered subdomains registered and monitored for the customer.
Severity-ranked issues with remediation guidance, plus baseline and prior-run history for the tenant.
Scan schedules, notification policies, and alert groups set independently per customer.
Customer-ready reports generated from that workspace’s data.
Which organization members can see and act on this customer.
Findings, assets, scans, and reports stay inside the customer workspace. A technician working one client does not see another client’s data unless their role grants it.
Organization roles decide who can onboard customers, run scans, change settings, and produce reports. Workspace count is governed by the organization quota for your deployment.
The organization view aggregates posture, open findings, and monitoring health across every workspace, so leadership has a portfolio picture without opening each client in turn.
Organization events are recorded for auditability whenever members manage customers, run scans, or change settings.
How workspaces fit the wider MSP model.
Monitoring configured per workspace.
The portfolio posture view across workspaces.
Findings scoped to each customer workspace.
Working across workspaces in the daily loop.
Request a demo.
Walk through tenant connection, assets, findings, and reports per customer.