Manage Azure Sentinel workspaces at scale

As a service provider, you may have onboarded multiple customer tenants to Azure Lighthouse. Azure Lighthouse allows service providers to perform operations at scale across several Azure Active Directory (Azure AD) tenants at once, making management tasks more efficient.

Azure Sentinel delivers security analytics and threat intelligence, providing a single solution for alert detection, threat visibility, proactive hunting, and threat response. With Azure Lighthouse, you can manage multiple Azure Sentinel workspaces across tenants at scale. This enables scenarios such as running queries across multiple workspaces, or creating workbooks to visualize and monitor data from your connected data sources to gain insights. IP such as queries and playbooks remain in your managing tenant, but can be used to perform security management in the customer tenants.

This topic provides an overview of how to use Azure Sentinel in a scalable way for cross-tenant visibility and managed security services.


Though we refer to service providers and customers in this topic, this guidance also applies to enterprises using Azure Lighthouse to manage multiple tenants.

Architectural considerations

For a managed security service provider (MSSP) who wants to build a Security-as-a-service offering using Azure Sentinel, a single security operations center (SOC) may be needed to centrally monitor, manage, and configure multiple Azure Sentinel workspaces deployed within individual customer tenants. Similarly, enterprises with multiple Azure AD tenants may want to centrally manage multiple Azure Sentinel workspaces deployed across their tenants.

This centralized model of deployment has the following advantages:

  • Ownership of data remains with each managed tenant.
  • Supports requirements to store data within geographical boundaries.
  • Ensures data isolation, since data for multiple customers isn't stored in the same workspace.
  • Prevents data exfiltration from the managed tenants, helping to ensure data compliance.
  • Related costs are charged to each managed tenant, rather than to the managing tenant.
  • Data from all data sources and data connectors that are integrated with Azure Sentinel (such as Azure AD Activity Logs, Office 365 logs, or Microsoft Threat Protection alerts) will remain within each customer tenant.
  • Reduces network latency.
  • Easy to add or remove new subsidiaries or customers.


You can manage delegated resources that are located in different regions. However, delegation of subscriptions across a national cloud and the Azure public cloud, or across two separate national clouds, isn't supported.

Granular Azure role-based access control (Azure RBAC)

Each customer subscription that an MSSP will manage must be onboarded to Azure Lighthouse. This allows designated users in the managing tenant to access and perform management operations on Azure Sentinel workspaces deployed in customer tenants.

When creating your authorizations, you can assign the Azure Sentinel built-in roles to users, groups, or service principals in your managing tenant:

You may also want to assign additional built-in roles to perform additional functions. For information about specific roles that can be used with Azure Sentinel, see Permissions in Azure Sentinel.

Once you've onboarded your customers, designated users can log into your managing tenant and directly access the customer's Azure Sentinel workspace with the roles that were assigned.

View and manage incidents across workspaces

If you are managing Azure Sentinel resources for multiple customers, you can view and manage incidents in multiple workspaces across multiple tenants at once. For more information, see Work with incidents in many workspaces at once and Extend Azure Sentinel across workspaces and tenants.


Be sure that the users in your managing tenant have been assigned read and write permissions on all the workspaces that are managed. If a user only has read permissions on some workspaces, warning messages may be shown when selecting incidents in those workspaces, and the user won't be able to modify those incidents or any others you've selected with those (even if you do have permissions for the others).

Configure playbooks for mitigation

Playbooks can be used for automatic mitigation when an alert is triggered. These playbooks can be run manually, or they can run automatically when specific alerts are triggered. The playbooks can be deployed either in the managing tenant or the customer tenant, with the response procedures configured based on which tenant's users will need to take action in response to a security threat.

Create cross-tenant workbooks

Azure Monitor Workbooks in Azure Sentinel help you visualize and monitor data from your connected data sources to gain insights. You can use the built-in workbook templates in Azure Sentinel, or create custom workbooks for your scenarios.

You can deploy workbooks in your managing tenant and create at-scale dashboards to monitor and query data across customer tenants. For more information, see Cross-workspace monitoring.

You can also deploy workbooks directly in an individual tenant that you manage for scenarios specific to that customer.

Run Log Analytics and hunting queries across Azure Sentinel workspaces

Create and save Log Analytics queries for threat detection centrally in the managing tenant, including hunting queries. These queries can then be run across all of your customers' Azure Sentinel workspaces by using the Union operator and the workspace () expression. For more information, see Cross-workspace querying.

Use automation for cross-workspace management

You can use automation to manage multiple Azure Sentinel workspaces and configure hunting queries, playbooks, and workbooks. For more information, see Cross-workspace management using automation.

Manage security of Office 365 environments

Use Azure Lighthouse in conjunction with Azure Sentinel to manage the security of Office 365 environments across tenants. First, out-of-the box Office 365 data connectors must be enabled in the managed tenant so that information about user and admin activities in Exchange and SharePoint (including OneDrive) can be ingested to an Azure Sentinel workspace within the managed tenant. This includes details about actions such as file downloads, access requests sent, changes to group events, and mailbox operations, along with information about the users who performed the actions. Office 365 DLP alerts are also supported as part of the built-in Office 365 connector.

You can enable the Microsoft Cloud App Security (MCAS) connector to stream alerts and Cloud Discovery logs into Azure Sentinel. This lets you gain visibility into cloud apps, get sophisticated analytics to identify and combat cyberthreats, and control how data travels. Activity logs for MCAS can be consumed using the Common Event Format (CEF).

After setting up Office 365 data connectors, you can use cross-tenant Azure Sentinel capabilities such as viewing and analyzing the data in workbooks, using queries to create custom alerts, and configuring playbooks to respond to threats.

Next steps