Edit

Share via

Cross-tenant management experiences

As a service provider, use Azure Lighthouse to manage your customers' Azure resources from within your own Microsoft Entra tenant. You can perform many common tasks and services across these managed tenants.

Tip

You can also use Azure Lighthouse within an enterprise that has multiple Microsoft Entra tenants to simplify cross-tenant administration.

Understanding tenants and delegation

A Microsoft Entra tenant represents an organization. It's a dedicated instance of Microsoft Entra ID that an organization receives when it creates a relationship with Microsoft by signing up for Azure, Microsoft 365, or other services. Each Microsoft Entra tenant is distinct and separate from other Microsoft Entra tenants, and has its own tenant ID (a GUID). For more information, see What is Microsoft Entra?

Typically, service providers must sign in to the Azure portal by using an account associated with the customer's tenant when they manage Azure resources for a customer. In this scenario, an administrator in the customer's tenant must create and manage user accounts for the service provider.

By using Azure Lighthouse, the onboarding process specifies users in the service provider's tenant who are assigned roles to delegated subscriptions and resource groups in the customer's tenant. These users can then sign in to the Azure portal by using their own credentials and work on resources belonging to all of the customers to which they have access. Users in the managing tenant can see all of these customers by visiting the My customers page in the Azure portal. They can also work on resources directly within the context of that customer's subscription, either in the Azure portal or via APIs.

Azure Lighthouse provides flexibility to manage resources for multiple customers without having to sign in to different accounts in different tenants. For example, a service provider might have two customers with different responsibilities and access levels. By using Azure Lighthouse, authorized users sign in to the service provider's tenant and access all of the delegated resources across these customers, according to the roles they've been assigned for each delegation.

Diagram showing resources for two customers managed through one service provider tenant.

APIs and management tool support

You can perform management tasks on delegated resources in the Azure portal, or you can use APIs and management tools such as Azure CLI and Azure PowerShell. You can use any existing APIs on delegated resources, as long as the functionality supports cross-tenant management and you have the appropriate permissions.

The Azure PowerShell Get-AzSubscription cmdlet shows the TenantId for the managing tenant by default. The HomeTenantId and ManagedByTenantIds attributes for each subscription help you identify whether a returned subscription belongs to a managed tenant or to your managing tenant.

Similarly, Azure CLI commands such as az account list show the homeTenantId and managedByTenants attributes. If you don't see these values when using Azure CLI, try clearing your cache by running az account clear followed by az login --identity.

In the Azure REST API, the Subscriptions - Get and Subscriptions - List commands include ManagedByTenant.

Note

In addition to tenant information related to Azure Lighthouse, these APIs might also show partner tenants for Azure Databricks or Azure managed applications.

You can use APIs to perform specific tasks related to Azure Lighthouse onboarding and management. For more info, see the Reference section.

Enhanced services and scenarios

Most Azure tasks and services work with delegated resources across managed tenants, as long as the onboarding process granted the right roles. The following scenarios show some key scenarios where cross-tenant management can be especially effective.

Azure Arc:

Azure Automation:

  • Use Automation accounts to access and work with delegated resources

Azure Backup:

  • Back up and restore customer data by using Azure Backup. Currently, the following Azure workloads are supported: Azure Virtual Machines (Azure VM), Azure Files, SQL Server on Azure VMs, SAP HANA on Azure VMs. Workloads that use Backup vaults (such as Azure Database for PostgreSQL, Azure Blob, Azure Managed Disk, and Azure Kubernetes Services) currently aren't fully supported.
  • View data for all delegated customer resources in Backup center
  • Use Backup Explorer to help view operational information of backup items (including Azure resources not yet configured for backup) and monitoring information for delegated subscriptions. Backup Explorer is currently available only for Azure VM data.
  • Use Backup reports across delegated subscriptions to track historical trends, analyze backup storage consumption, and audit backups and restores.

Azure Cost Management + Billing:

  • From the managing tenant, CSP partners can view, manage, and analyze pre-tax consumption costs (not inclusive of purchases) for customers who are under the Azure plan. The cost is based on retail rates and the Azure role-based access control (Azure RBAC) access that the partner has for the customer's subscription. Currently, you can view consumption costs at retail rates for each individual customer subscription based on Azure RBAC access.

Azure Key Vault:

  • Create Key Vaults in customer tenants
  • Use a managed identity to create Key Vaults in customer tenants

Azure Kubernetes Service (AKS):

  • Manage hosted Kubernetes environments and deploy and manage containerized applications within customer tenants
  • Deploy and manage clusters in customer tenants
  • Monitor cluster performance across customer tenants

Azure Migrate:

  • Create migration projects in the customer tenant and migrate VMs

Azure Monitor:

  • View alerts for delegated subscriptions, with the ability to view and refresh alerts across all subscriptions
  • View activity log details for delegated subscriptions
  • Log analytics: Query data from remote workspaces in multiple tenants (note that automation accounts used to access data from workspaces in customer tenants must be created in the same tenant)
  • Create, view, and manage alerts in customer tenants
  • Create alerts in customer tenants that trigger automation, such as Azure Automation runbooks or Azure Functions, in the managing tenant through webhooks
  • Create diagnostic settings in workspaces created in customer tenants, to send resource logs to workspaces in the managing tenant
  • For Microsoft Entra External ID, route sign-in and auditing logs to different monitoring solutions
  • For SAP workloads, monitor SAP Solutions metrics with an aggregated view across customer tenants

Azure Networking:

Azure Policy:

  • Create and edit policy definitions within delegated subscriptions
  • Deploy policy definitions and policy assignments across multiple tenants
  • Assign customer-defined policy definitions within delegated subscriptions
  • Customers see policies authored by the service provider alongside any policies they author themselves
  • Can remediate deployIfNotExists or modify assignments within the managed tenant
  • Note that viewing compliance details for noncompliant resources in customer tenants is not currently supported

Azure Resource Graph:

  • See the tenant ID in returned query results, allowing you to identify whether a subscription belongs to a managed tenant

Azure Service Health:

  • Monitor the health of customer resources with Azure Resource Health
  • Track the health of the Azure services used by your customers

Azure Site Recovery:

  • Manage disaster recovery options for Azure virtual machines in customer tenants (note that you can't use RunAs accounts to copy VM extensions)

Azure Virtual Machines:

  • Use virtual machine extensions to provide post-deployment configuration and automation tasks on Azure VMs
  • Use boot diagnostics to troubleshoot Azure VMs
  • Access VMs with serial console
  • Integrate VMs with Azure Key Vault for passwords, secrets, or cryptographic keys for disk encryption by using managed identity through policy, ensuring that secrets are stored in a Key Vault in the managed tenant
  • Note that you can't use Microsoft Entra ID for remote authentication to VMs

Microsoft Defender for Cloud:

  • Cross-tenant visibility
    • Monitor compliance with security policies and ensure security coverage across all tenants' resources
    • Continuous regulatory compliance monitoring across multiple tenants in a single view
    • Monitor, triage, and prioritize actionable security recommendations with secure score calculation
  • Cross-tenant security posture management
    • Manage security policies
    • Take action on resources that are out of compliance with actionable security recommendations
    • Collect and store security-related data
  • Cross-tenant threat detection and protection
    • Detect threats across tenants' resources
    • Apply advanced threat protection controls such as just-in-time (JIT) VM access
    • Harden network security group configuration with Adaptive Network Hardening
    • Ensure servers are running only the applications and processes they should be with adaptive application controls
    • Monitor changes to important files and registry entries with File Integrity Monitoring (FIM)
  • Note that the entire subscription must be delegated to the managing tenant; Microsoft Defender for Cloud scenarios aren't supported with delegated resource groups

Microsoft Sentinel:

Support requests:

Current limitations

With all scenarios, be aware of the following current limitations:

  • Azure Lighthouse supports requests handled by Azure Resource Manager. The operation URIs for these requests start with https://management.azure.com. However, Azure Lighthouse doesn't support requests that are handled by an instance of a resource type, such as Key Vault secrets access or storage data access. The operation URIs for these requests typically start with an address that's unique to your instance, such as https://myaccount.blob.core.windows.net or https://mykeyvault.vault.azure.net/. These requests are typically data operations rather than management operations.
  • Role assignments must use Azure built-in roles. Azure Lighthouse currently supports all built-in roles except for Owner or any built-in roles with DataActions permission. The User Access Administrator role is supported only for limited use in assigning roles to managed identities. Custom roles and classic subscription administrator roles aren't supported. For more information, see Role support for Azure Lighthouse.
  • For users in the managed tenant, Access Control (IAM) and CLI tools such as az role assignment list don't show role assignments made through Azure Lighthouse. These assignments are only visible in the Azure portal in the Delegations section of Azure Lighthouse, or through the Azure Lighthouse API.
  • While you can onboard subscriptions that use Azure Databricks, users in the managing tenant can't launch Azure Databricks workspaces on a delegated subscription.
  • While you can onboard subscriptions and resource groups that have resource locks, those locks don't prevent actions from being performed by users in the managing tenant. Deny assignments that protect system-managed resources (system-assigned deny assignments), such as those created by Azure managed applications, do prevent users in the managing tenant from acting on those resources. However, users in the customer tenant can't create their own deny assignments.
  • Delegation of subscriptions across a national cloud and the Azure public cloud, or across two separate national clouds, isn't supported.

Next steps

  • Last updated on