Cloudek.Request a service session

Microsoft Entra

Microsoft 365 security exposure: five places the portal will not show in one view

Five Microsoft 365 exposures that sit in different admin centres: password spray, standing admin roles, Conditional Access gaps, legacy sign-in and guests.

Sources checked: 22 November 2026. Every Microsoft statement below comes from the Microsoft Learn pages listed at the end. This is a planning and review guide. It does not inspect your tenant, and licence requirements and portal labels can change, so confirm them against the linked pages.

Picture three things worth checking in any tenant. An administrator account with no MFA method registered. A guest account invited two years ago by someone who has since left. A legacy sign-in protocol that quietly sidesteps your MFA policy. Each one is visible somewhere in the Microsoft admin centres. None of them is visible next to the others, and each depends on a different licence.

That is the real Microsoft 365 security exposure problem: not a lack of settings, but no single view that answers "where are we exposed, and what could we not check?" Below are five places to look, with where to find each one, what hides it, and which licence the relevant feature needs.

Short answer

If you only have an hour, check these in order: legacy authentication (it is easy to find, and Microsoft documents a block policy for it), the number and type of admin role assignments, the exclusions in every Conditional Access policy, who can invite guests, and how far back your sign-in logs go. The table near the end puts the portal location and licence note for each in one place.

1. Sign-in anomalies and password spray

Why it hides. A password spray tries a few common passwords against many accounts, so no single account looks unusual. Microsoft Entra ID Protection does have a Password spray risk detection, but Microsoft's risk detection reference says it only triggers when an attacker successfully validates a user's password. Unsuccessful spray attempts against your users do not generate a detection. A quiet risk report therefore does not tell you nobody has been spraying.

Licence and retention limits. The same reference lists Password spray as a premium detection that needs Microsoft Entra ID P2. Tenants without P2 see detections titled "Additional risk detected" without the details. Microsoft's data retention page says sign-in logs are kept for seven days on Microsoft Entra ID Free and 30 days on P1 and P2, and that risky sign-ins are kept for 7, 30 and 90 days on Free, P1 and P2 respectively. Longer history needs the logs routed to Azure Monitor or a storage account.

What to do.

  • Find out which licence tier you have and what your sign-in log retention actually is, before an incident rather than during one.
  • Decide where sign-in logs are sent for longer retention, and who reads them.
  • Treat repeated failures spread across many accounts, or from one source, as worth a look. This is a practical heuristic, not a Microsoft-documented recipe.

2. Standing administrator roles

Why it hides. Role assignments are visible per role in the Microsoft Entra admin centre, but the full picture is spread across direct assignments, group-based assignments and eligible (just-in-time) assignments. Microsoft's best practices page recommends fewer than five Global Administrators and fewer than ten privileged role assignments overall, and says a card appears on the Overview page when there are five or more Global Administrator assignments. That card shows a count. It does not show whether those people also have MFA, whether they hold the role permanently, or whether the account is cloud-only.

What the guidance says.

  • Use Privileged Identity Management so people are eligible for a role and activate it for a limited time. Microsoft's licensing note on the same page says PIM needs Microsoft Entra ID P2 or Microsoft Entra ID Governance.
  • Turn on MFA for every administrator account.
  • Use cloud-native accounts for Microsoft Entra roles rather than accounts synced from on-premises.
  • Keep two cloud-only emergency access accounts that are permanently assigned Global Administrator, and exclude them from policies that could lock everyone out.
  • Review role assignments regularly with access reviews. Microsoft's access reviews page says that feature needs Microsoft Entra ID Governance or the Microsoft Entra Suite, with some capabilities working on P2.

For the full model of eligible versus active roles, see our PIM explainer.

3. Conditional Access gaps

Why it hides. Conditional Access is a set of independent policies. Reading one policy tells you little about what a user actually experiences, because several policies may apply, and each has its own exclusions. Microsoft recommends excluding emergency access accounts, and notes that calls made by service principals are not blocked by Conditional Access policies scoped to users. Sensible exclusions add up over time, and an excluded account is an account the policy does not protect.

What to check.

  • List every policy with its state (on, report-only or off), who it includes and who it excludes, in one table. Look for the same account excluded from many policies.
  • Remember that Microsoft says Conditional Access policies are enforced after first-factor authentication, so it is not meant to be a first line of defence for scenarios like denial of service.
  • Use report-only mode before enforcing a change. Microsoft's report-only page says results are logged in the Conditional Access and Report-only tabs of the sign-in log details, and that policies using the User Actions scope cannot be evaluated this way.
  • If you have Microsoft Entra ID P1 and a Log Analytics workspace receiving sign-in logs, the Conditional Access insights and reporting workbook shows the combined impact of policies, including a "Not applied" count for sign-ins that none of the selected policies covered.

For a checklist, see our Conditional Access review checklist.

4. Legacy authentication

Why it hides. Legacy protocols cannot do multifactor authentication, so an MFA policy that looks complete can leave a side door open. Microsoft's guidance says, based on its own analysis, that more than 97 percent of credential stuffing attacks and more than 99 percent of password spray attacks use legacy authentication, and that these attacks would stop with basic authentication disabled or blocked. Old printers, scanners, scripts and mail clients are common reasons it is still in use.

How to find it. Microsoft's page describes filtering the sign-in logs by the Client App field for the legacy protocols, on both the interactive tab and the User sign-ins (non-interactive) tab, and points to a Sign-ins using legacy authentication workbook for triage.

How to block it. Microsoft documents a Conditional Access policy that selects Exchange ActiveSync clients and Other clients under Client apps, set to Block access, starting in report-only mode and excluding at least one account to avoid lockout. Customers without a licence that includes Conditional Access can use security defaults, which Microsoft says block legacy authentication.

5. Guest and external access

Why it hides. Guest accounts are created by people, apps and group owners across the year, and nobody sees them all at once. Microsoft's B2B overview says B2B collaboration is enabled by default, and that by default all users in your organisation, including B2B guest users, can invite external users. It also describes letting application and group owners add guests themselves.

What to check.

  • The two sets of controls are different. Cross-tenant access settings decide whether users can authenticate with external Microsoft Entra organisations. External collaboration settings decide who in your organisation can invite guests. Review both.
  • Which guests still exist, who invited them, and whether they have signed in recently.
  • Whether guests are covered by your Conditional Access policies. Microsoft says Conditional Access policies such as MFA can be enforced for specific guest users.
  • Whether group owners are asked to confirm guests still need access. Microsoft's access reviews page describes this use, with the licence requirement noted above.

The five places in one table

Where to look and what each feature needs, from Microsoft Learn pages read on 22 November 2026.
ExposureWhere to look firstLicence note from Microsoft
Sign-in anomalies and password spraySign-in logs, ID Protection risk detectionsPassword spray detection needs Entra ID P2; sign-in log retention is 7 days on Free and 30 on P1 and P2
Standing administrator rolesRoles and administrators, PIMPIM needs Entra ID P2 or Entra ID Governance
Conditional Access gapsConditional Access policies, sign-in log Report-only tabConditional Access needs Entra ID P1; the insights workbook also needs Log Analytics
Legacy authenticationSign-in logs filtered by Client AppSecurity defaults can block it if you have no Conditional Access licence
Guest and external accessExternal collaboration and cross-tenant access settings, access reviewsAccess reviews need Entra ID Governance or the Entra Suite, with some capabilities on P2

A theme runs through the table: several answers depend on a licence, and an empty report can mean either "nothing found" or "this cannot be seen with your licence". Keep a note of which of your answers are checked and which are not checked.

See it in 30 seconds, without signing up

OpsPilot is Cloudek's read-only Microsoft 365 review workspace, and you can try it before talking to anyone. The interactive demo opens in your browser: nothing to install, no tenant connected, sample data only. The animated tour on the sign-in page walks through a fix-first list, an A to F graded report, read-only checks and a report you can download, all drawn from a fictional sample organisation.

Behind it are sixteen Live read-only reviews. Four of them map straight onto the exposures above:

Status labels as shown on the OpsPilot reports library on 22 November 2026.
StatusOpsPilot reviewWhat it answers
LiveLegacy authentication reviewWhich old sign-in protocols bypass MFA, and whether anything blocks them
LiveConditional Access reviewWhich policies are on, report-only or off, who they cover and who is excluded
LivePrivileged access reviewWho holds powerful admin roles, standing versus eligible
LiveGuest and external access reviewWhich guest accounts exist and what they can reach

Each finding comes in plain English with the evidence behind it, and reviews are graded A to F with a prioritised list of what to fix first. When a check needs a licence you do not have, the result says "Not checked: needs" that licence rather than showing a pass.

The design is read-only. OpsPilot reads and reports, never changes your tenant, shows what it will read before you approve a run, and never reads email, files or chat content. Results describe what Microsoft returned on the day they ran. They are not an audit or a certification, and any change is made by a named person in Microsoft's own tools.

Customer access is an invitation-only free trial: 30 days, one organisation of up to 250 users, read-only. To ask for an invitation, email info@cloudekhosting.com. You do not need to send any tenant data to start the conversation. Start with the live demo, or read the OpsPilot overview.

Frequently asked questions

Does a quiet Identity Protection report mean nobody sprayed our passwords?

No. Microsoft's reference says the Password spray detection only fires when an attacker successfully validates a password, so unsuccessful attempts do not generate it. It also needs Entra ID P2 for full details.

How many Global Administrators should we have?

Microsoft recommends fewer than five, plus two cloud-only emergency access accounts, and fewer than ten privileged role assignments overall.

Is report-only mode safe to use for everything?

It is the documented way to test most Conditional Access policies without enforcing them. Microsoft says policies in the User Actions scope cannot be evaluated this way, and that report-only policies requiring a compliant device can prompt users on macOS, iOS and Android to select a device certificate.

Can we block legacy authentication without a Conditional Access licence?

Microsoft says customers without licences that include Conditional Access can use security defaults to block it.

Does OpsPilot change anything in our tenant?

No. The reviews are read-only. OpsPilot reads and reports, and a named person makes any change in Microsoft's tools.

Sources

OPSPILOT • READ-ONLY MICROSOFT 365 REVIEWS

See what OpsPilot reviews in your tenant

  • WHAT IT DOES: Runs fixed, read-only checks of a Microsoft 365 tenant (identity, licences, email authentication, admin changes and more) and grades the results. It changes nothing in the tenant. Some capabilities are still in development; each page says which.
  • DATA HANDLING: You sign in with Microsoft and approve read-only access. Read the product pages to see exactly what is and is not read.

Was this helpful?