Security 101

How Do You Monitor Security Across Multiple Microsoft 365 Tenants?

How to connect Sentinel, Defender and your configuration baselines across several Microsoft 365 tenants so your team sees them as one environment.

To monitor security across several Microsoft 365 tenants, connect each tenant’s Microsoft Sentinel workspace to one managing tenant through Azure Lighthouse or Microsoft Defender multitenant management, then hold every tenant to the same configuration baseline. Each tenant keeps its own data, and your team works from one view.

The Accelerynt Security Platform is built for that view. If you manage tenants for a family of companies, they all show up in one console, each with its own evidence, and Accelerynt MDR works inside each tenant’s Sentinel through Azure Lighthouse.

Before you connect tenants

  • Each tenant keeps its data. Azure Lighthouse gives your team access without moving logs out of the tenant.
  • Two ways to see across tenants. Azure Lighthouse works through each Sentinel workspace, and Defender multitenant management works through the Defender portal.
  • The same connectors everywhere. A cross-tenant detection only works when every tenant sends the data it needs.
  • One baseline, checked per tenant. Each tenant drifts on its own, so each needs its own comparison with the approved baseline.

Why do multiple tenants create monitoring gaps?

Organizations end up with several tenants for sound reasons, such as an acquisition, a regional data boundary or a business unit with its own compliance obligations. Each tenant brings its own identities and its own security settings.

Microsoft provides the pieces for watching tenants together, and nothing connects them by default. Until your team builds that connection, each tenant gets checked on its own, and a change in one of them can sit unnoticed.

Azure Lighthouse or Defender multitenant management?

QuestionAzure LighthouseDefender multitenant management
Where your team worksIn each tenant’s Sentinel workspace, from the managing tenantIn the Defender portal, with incidents and hunting across tenants in one view
How cross-tenant queries workKQL with the workspace() expression, combined with unionAdvanced hunting across selected tenants, up to 50,000 records in total
Secondary workspaces in other tenantsSupported through delegated accessStill needs Azure Lighthouse and the workspace() operator
Best fitTeams that build custom analytics rules and playbooks in SentinelTeams that work mainly from Defender XDR and Sentinel incidents
Sources: Microsoft Learn on extending Sentinel across workspaces and tenants, Defender multitenant management and multitenant advanced hunting.

Many teams use both. Microsoft also plans to move Sentinel fully into the Defender portal and recommends planning that move now.

Mar 31, 2027

After this date, Microsoft says Sentinel will no longer be supported in the Azure portal and will be available only in the Defender portal. Source: Microsoft Learn, Sentinel for service providers.

How do you set up multi-tenant monitoring?

  1. Map your tenants. List every tenant, where its data has to stay and which data sources it has, before you decide where queries and rules will run.
  2. Delegate access. In your managing tenant, create a group for each Sentinel role, then delegate those roles from each tenant through Azure Lighthouse.
  3. Match the data connectors. Give every tenant the same minimum set, such as Entra ID sign-in and audit logs, Defender XDR incidents, identity protection alerts and Office 365 activity.
  4. Publish detections from one place. Use workspace manager, currently in preview, to publish analytics rules, automation rules, hunting queries and workbooks from a central workspace to member workspaces.
  5. Hunt and correlate across tenants. Write hunting queries with the workspace() expression, and agree in advance how an incident that spans two tenants gets investigated.

Source: Microsoft Learn, workspace manager. If your workspaces are already onboarded to the Defender portal, Microsoft points you to Defender multitenant management instead.

How do you catch configuration drift in every tenant?

Each tenant drifts from your approved baseline on its own. A Conditional Access exclusion added in one tenant does not show up in the others, and it may not raise a Sentinel alert at all.

  • Conditional Access. New exclusions and changes to policy state.
  • Privileged roles. New or standing admin role assignments.
  • Mail flow. Transport and forwarding rules that send mail outside the tenant.
  • Sharing. External sharing defaults in SharePoint and OneDrive.

Microsoft’s Tenant Configuration Management APIs can compare settings with a baseline across Defender, Entra, Exchange Online, Intune, Purview and Teams. The Accelerynt Security Platform compares each tenant with your approved baseline on a schedule your team sets and on demand, and records each change with before and after values and the account responsible.

For what to do once a change is found, read how to respond to configuration drift, and for why checks between audits matter, read what continuous control validation means for Microsoft security.

Where does multi-tenant monitoring break down?

Uneven connectors

A rule that joins Defender for Endpoint alerts with Entra ID sign-ins returns nothing in a tenant that only sends sign-in logs. The rule does not fail. It simply never fires.

Tuning that stays local

An analyst tunes a rule in one tenant to cut noise, and the other tenants keep the old version. Decide which local changes should become global.

Baselines nobody reviews

Microsoft changes defaults and retires settings on its own schedule. An old baseline starts flagging legitimate changes and missing real ones.

Access nobody tracks

Delegated access is scoped and time-limited by design. Someone has to keep track of who holds which role in each tenant.

How Accelerynt monitors multiple tenants

The Accelerynt Security Platform shows posture across your tenants in one view, with scores across Identity, Email, SharePoint, Teams, Defender XDR, Power Platform, Azure DevOps, GitHub, AWS and GCP. Each tenant keeps its own evidence, and the platform works with read-only permissions.

Accelerynt MDR connects to each tenant’s Sentinel through Azure Lighthouse, so detection rules and playbooks are built inside your workspaces and your data stays in each tenant. For how one provider and your team share a workspace, read what co-managed Microsoft Sentinel means, and for the baseline cycle behind it, see our post on Zero Trust discovery and the baseline audit cycle.

Each connected tenant can carry the same hidden gaps. Read why vulnerability scanners miss Microsoft 365 misconfigurations for the settings worth watching in every tenant.

Frequently asked questions

How do you monitor security across multiple Microsoft 365 tenants?

Connect each tenant’s Sentinel workspace to a managing tenant through Azure Lighthouse or Defender multitenant management, give every tenant the same data connectors, and compare each tenant with one approved baseline. The Accelerynt Security Platform shows every tenant in one console, each with its own evidence.

Is there one dashboard for all our Microsoft 365 security settings?

The Accelerynt Security Platform shows posture across your tenants in one view, sorted worst first, and you can click any score to see the findings behind it. For incidents, Microsoft’s Defender multitenant management brings several tenants into one portal.

Does Azure Lighthouse move data out of the customer tenant?

No. Azure Lighthouse delegates role-based access, so each tenant’s Sentinel workspace and its data stay where they are while analysts in the managing tenant work on them.

Can you run one query across several Sentinel workspaces?

Yes. The workspace() expression refers to a table in another workspace, and union combines several. Microsoft allows up to 20 workspaces in a scheduled analytics rule and recommends no more than 5 for performance.

Talk to a Microsoft security engineer

We work inside your Microsoft environment, with your team, and show you where to focus first.