Where are the risks in the tenant? Microsoft Secure Score as a starting point

Key takeaways
- The Microsoft Secure Score evaluates the security configuration of a Microsoft 365 tenant as a percentage and provides prioritized recommendations for action.
- It covers four areas: identity, devices, data, and applications, but it only evaluates measures within the Microsoft ecosystem.
- A high score does not automatically mean a company is secure, and a low score does not necessarily indicate acute danger.
- Typical, often overlooked risks include legacy authentication, guest access, over-privileged admin accounts, and a lack of monitoring for sign-in activities.
- A structured security check translates the score into concrete, prioritized measures for your specific tenant.
Many companies have been using Microsoft 365 for years without knowing exactly how securely their tenant—the company's own isolated Microsoft 365 environment, including all user accounts, devices, and settings—is actually configured. At the same time, cyberattacks are increasingly shifting to this very target: stolen credentials, missing multi-factor authentication, or overly broad permissions are often enough to gain access to sensitive company data. The Microsoft Secure Score is often the first point of contact for gaining a structured overview. However, it only answers part of the question regarding where the actual risks in the tenant lie. We show how to specifically assess your own tenant in our Webinar on the topic of Security Check.
What the Microsoft Secure Score really measures
The Secure Score is an assessment tool in the Microsoft Defender portal or the Microsoft 365 admin center. It represents an organization's security status as a percentage and derives prioritized recommendations from it. Simply put, it is an intelligent checklist with a point system that checks which of the security features recommended by Microsoft are already being actively used.
The assessment is divided into four categories:
Within a few minutes, this creates a structured overview of potential vulnerabilities and outstanding measures, prioritized by effort and impact. Separately, there is also the Identity Secure Score in the Microsoft Entra admin center, which focuses exclusively on identity and access topics and is often confused with the general Secure Score.
The Secure Score only shows a snapshot of reality
As helpful as this value is as a starting point, it is just as important to interpret it correctly. The Secure Score only evaluates the extent to which a company uses the security features proposed by Microsoft within its own ecosystem. Security measures from third-party providers or individual, company-specific policies are not included in the calculation. A company with a solid security architecture that relies heavily on third-party providers may therefore receive a comparatively low score, even though its actual security posture is not worse.
Furthermore, the basis for the calculation itself is constantly changing. Microsoft continuously expands the criteria being evaluated, as the official Secure Score documentation describes, among other things, additional recommendations for multi-cloud environments. In such cases, a sudden drop in the score does not mean that something has deteriorated in the tenant, but merely that the scope of assessment has expanded, as is also a technical article on managing the Secure Score explains. In practice, many companies realistically operate within a range of about 20 to 55 percent; a score of 100 percent is neither a realistic goal nor always sensible, as some recommendations require higher license tiers or conflict with the company's own business model (such as strictly limiting external sharing when working closely with partner companies).
The score therefore provides a good starting point, but it does not replace a holistic view of IT security within the company, such as that pursued within the framework of a Zero Trust approach .
Typical risks often overlooked in the tenant
In practice, certain vulnerabilities recur across almost all tenants, regardless of industry or company size:
- Missing or incomplete multi-factor authentication, especially for administrative accounts, which require extra protection.
- Outdated authentication protocols (legacy authentication), which can bypass conditional access policies.
- Over-privileged administrator accountsthat are permanently assigned elevated rights instead of only when needed.
- Uncontrolled guest accessthat was set up for projects but never revoked.
- Lack of monitoring for sign-in activities, which causes unusual login attempts to go unnoticed.
Many of these issues can be resolved with relatively little effort, but they are often overlooked in day-to-day operations because they are not visible in an isolated percentage figure. This is precisely where a structured Cybersecurity Consulting that goes beyond mere metrics.
From score to concrete action: How a security check works
A meaningful picture of tenant security only emerges when the Secure Score is evaluated in the context of an individual company's situation. In a structured security check, the current status is first recorded: configuration, license landscape, and existing security policies. Subsequently, the four evaluation areas of the Secure Score are examined in detail and compared with actual business processes—for example, determining whether a recommendation to restrict external sharing is compatible with collaboration with partner companies. This analysis results in a prioritized catalog of measures, sorted by urgency and implementation effort, rather than simply aiming for a higher percentage across the board.
At Baggenstos, we offer companies exactly this starting point as part of a webinar on the topic of security checks, in which we demonstrate how to realistically assess your own tenant in just a few steps.
The Secure Score as a continuous process, not a one-time project
Since Microsoft continuously adjusts the evaluation criteria and your own IT environment is constantly changing due to new employees, applications, or partnerships, a one-time snapshot is of limited value. It is more sensible to conduct regular reviews, for example on a quarterly basis, during which new recommendations are categorized and previously implemented measures are checked for their ongoing effectiveness. This ensures the Secure Score remains what it was intended to be: a management tool, not an end in itself.
Frequently Asked Questions
What is considered a good Microsoft Secure Score?
There is no universal target value, as the appropriate level depends heavily on licensing, industry, and business model. More important than an absolute figure is whether the key recommendations in the areas of identity and devices have been implemented.
Is a high Secure Score sufficient proof of adequate IT security?
No. The Secure Score only reflects measures within the Microsoft ecosystem and does not replace a holistic security strategy, which also includes processes, training, and, where applicable, third-party solutions.
How often should the Secure Score be reviewed?
Regular reviews, ideally on a quarterly basis, have proven effective in practice, as both Microsoft’s assessment criteria and your own IT environment are constantly evolving.
What is the difference between Secure Score and Identity Secure Score?
The Secure Score in the Microsoft Defender portal provides a holistic assessment of your security configuration across all four categories. The Identity Secure Score in the Microsoft Entra admin center is a separate metric that focuses exclusively on identity and access-related topics.














