Is SecurityScore.me designed specifically for MSPs?

Yes. The whole model is an organization workspace with separate, isolated customer workspaces underneath it: multi-tenant Microsoft 365 assessment, one findings queue, monitoring, alert routing, and per-customer reports. It is not a single-tenant tool with an MSP mode bolted on.

Does the platform write changes to customer tenants?

No. Microsoft Graph access is delegated and read-only, used for posture assessment and monitoring. The platform never modifies customer tenant configuration; remediation stays in your hands.

How many customer tenants can one organization manage?

The model is built for portfolios in the tens to low hundreds of tenants. Each customer is its own workspace, and the organization view ranks and compares them; there is no per-tenant portal to visit.

What does onboarding a customer involve?

Granting delegated read-only Microsoft Graph consent for the tenant, registering the customer’s domains and websites as monitored assets, and running the first assessment to establish a baseline. Subsequent assessments run on a schedule.

What Microsoft 365 data does an assessment cover?

Secure Score, Conditional Access, Defender for Endpoint, and identity signals such as risky sign-ins, users, groups, and licenses — the posture data available through Microsoft Graph — plus the external asset checks registered in the workspace.

Can several team members work in the same organization?

Yes. Organization members, roles, and permissions control who can manage customers, run scans, change settings, and produce reports.

MSP Security Platform for Microsoft 365

The Microsoft admin center was built for one tenant

Every Microsoft security surface — Secure Score, Conditional Access, Defender, Entra identity — assumes you are signed into one tenant, looking at one organization. An MSP is signed into thirty.

Portal work does not scale linearly

A ten-minute posture check per tenant is a full day across a portfolio of fifty, every time you want a current picture. Because that is unsustainable, the check quietly becomes quarterly, then only when something breaks.

Partner portals such as Lighthouse help, but they aggregate a subset of signals and still send you into each tenant to act. The gap between "I can see it" and "I have done something about it" stays wide.

There is no portfolio view of risk

The question an MSP owner actually needs answered — "which three customers are most exposed right now, and why" — has no screen in the Microsoft consoles. It has to be assembled by hand from separate tenants.

Without a single ranked list, remediation effort follows whoever shouts loudest rather than whichever tenant carries the most risk.

Remediation is not a workflow

Microsoft shows recommendations. It does not assign them to a technician, track whether they were done, alert you when they regress, or record that you told the customer.

MSPs end up rebuilding that workflow in a ticketing system or a spreadsheet, disconnected from the data that generated it.

Reporting is rebuilt every quarter

A customer QBR needs posture, Secure Score, open issues, and what changed since last time, in language a non-technical stakeholder can follow. Producing that from raw admin-center screens is hours of copy-paste per customer.

What one organization workspace consolidates

SecurityScore.me connects each customer tenant once with read-only delegated Microsoft Graph access, then keeps the whole portfolio in view from a single MSP account.

Customer workspaces

Every managed customer gets a dedicated workspace holding their Microsoft 365 context, monitored assets, findings, and reports. Data stays isolated per customer while your team works from one organization login.

Organization members, roles, and permissions decide who can onboard customers, run scans, and change settings.

Microsoft 365 posture assessment

Scheduled read-only assessments pull Secure Score, Conditional Access, Defender for Endpoint, and identity signals such as risky sign-ins, then express the result as severity-ranked findings rather than a raw settings dump.

Nothing is written back to the tenant. The platform reads posture data; it does not change customer configuration.

External attack surface

Customer-facing infrastructure outside the tenant — domains, subdomains, exposed services, TLS certificates — is registered as monitored assets so it lands in the same queue as tenant findings.

Certificate Transparency and DNS discovery surface hosts the customer never told you about.

Findings and triage

Findings from every source carry the same severity language, remediation guidance, and customer context, so a technician works one ranked list instead of switching between tools and mental models.

Monitoring and alert routing

Scheduled re-assessment and asset scans detect change between reviews. Notification policies and alert groups route the events that matter to the right person, per customer and per team.

Customer reporting

Customer-ready reports assemble Microsoft 365 posture, Secure Score, open findings, and recommended actions into a document built for a QBR, generated per workspace rather than rebuilt by hand.

Priority customers

A week on the platform

Onboard a customer: Delegated read-only Graph consent, register domains and websites as assets, run the first assessment to set a baseline.
Portfolio review: Open the organization view, read the ranked list of customers needing attention, and see what moved since last week.
Triage the queue: Work critical and high findings across customers first, with remediation guidance and the customer context attached.
Route what matters: Send new critical findings and monitoring events to the assigned technician or the customer contact via notification policies.
Quarterly report: Generate the customer report from the workspace: posture, Secure Score, open issues, and the delta since the last review.

Security Posture Report

Who it is for

Managed service providers

MSPs running recurring Microsoft 365 posture management and security operations across a portfolio of customer tenants.

IT service providers and MSSPs

Providers delivering security reviews, monitoring, and reporting as a recurring service line for business customers.

Multi-tenant administrators

Internal teams supporting several Microsoft 365 tenants — holding companies, franchises, acquisitions — that need one place to see and report on all of them.

Customer workspaces
Dedicated, isolated security workspace per managed customer.
Microsoft 365 security posture
The posture program the platform runs across every tenant.
Security findings
One severity-ranked queue across tenant and external sources.
Microsoft 365 monitoring
Scheduled re-assessment and change detection between reviews.
CVE alerts for MSPs
NVD, CISA KEV, and EPSS correlation against customer assets.
External attack surface monitoring (guide)
Subdomains, exposed services, and certificate expiry outside the tenant.

Frequently asked questions

The MSP security platform for Microsoft 365 operations