Cross-tenant management experiences
As a service provider, you can use Azure delegated resource management to manage Azure resources for multiple customers from within your own tenant in the Azure portal. Most tasks and services can be performed on delegated Azure resources across managed tenants. This article describes some of the enhanced scenarios where Azure delegated resource management can be effective.
Azure delegated resource management can also be used within an enterprise which has multiple Azure AD tenants of its own to simplify cross-tenant administration.
Understanding customer tenants
An Azure Active Directory (Azure AD) tenant is a representation of an organization. It's a dedicated instance of Azure AD that an organization receives when they create a relationship with Microsoft by signing up for Azure, Microsoft 365, or other services. Each Azure AD tenant is distinct and separate from other Azure AD tenants, and has its own tenant ID (a GUID). For more info, see What is Azure Active Directory?
Typically, in order to manage Azure resources for a customer, service providers would have to sign in to the Azure portal using an account associated with that customer's tenant, requiring an administrator in the customer's tenant to create and manage user accounts for the service provider.
With Azure delegated resource management, the onboarding process specifies users within the service provider's tenant who will be able to access and manage subscriptions, resource groups, and resources in the customer's tenant. These users can then sign in to the Azure portal using their own credentials. Within the Azure portal, they can manage resources belonging to all customers to which they have access. This can be done by visiting the My customers page in the Azure portal, or by working directly within the context of that customer's subscription, either in the Azure portal or via APIs.
Azure delegated resource management allows greater flexibility to manage resources for multiple customers without having to sign in to different accounts in different tenants. For example, a service provider may have three customers, with different responsibilities and access levels, as shown here:
Using Azure delegated resource management, authorized users can sign in to the service provider’s tenant to access these resources, as shown here:
APIs and management tool support
You can perform management tasks on delegated resources either directly in the portal or by using APIs and management tools (such as Azure CLI and Azure PowerShell). All existing APIs can be used when working with delegated resources, as long as the functionality is supported for cross-tenant management and the user has the appropriate permissions.
We also provide APIs to perform Azure delegated resource management tasks. For more info, see the Reference section.
Enhanced services and scenarios
Most tasks and services can be performed on delegated resources across managed tenants. Below are some of the key scenarios where cross-tenant management can be effective.
- Connect Windows Server or Linux machines outside Azure to delegated subscriptions and/or resource groups in Azure
- Manage connected machines using Azure constructs, such as Azure Policy and tagging
- Use automation accounts to access and work with delegated customer resources
- Back up and restore customer data in customer tenants
- Manage hosted Kubernetes environments and deploy and manage containerized applications within customer tenants
- View alerts for delegated subscriptions, with the ability to view alerts across all subscriptions
- View activity log details for delegated subscriptions
- Log analytics: Query data from remote customer workspaces in multiple tenants
- Create alerts in customer tenants that trigger automation, such as Azure Automation runbooks or Azure Functions, in the service provider tenant through webhooks
- Compliance snapshots show details for assigned policies within delegated subscriptions
- Create and edit policy definitions within a delegated subscription
- Assign customer-defined policy definitions within the delegated subscription
- Customers see policies authored by the service provider alongside any policies they've authored themselves
- Can remediate deployIfNotExists or modify assignments within the customer tenant
- Now includes the tenant ID in returned query results, allowing you to identify whether a subscription belongs to the customer tenant or service provider tenant
- Cross-tenant visibility
- Monitor compliance to security policies and ensure security coverage across all tenants’ resources
- Continuous regulatory compliance monitoring across multiple customers 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)
- Manage Azure Sentinel resources in customer tenants
- Track attacks and view security alerts across multiple customer tenants
- Monitor the health of customer resources with Azure Resource Health
- Track the health of the Azure services used by your customers
- Manage disaster recovery options for Azure virtual machines in customer tenants (note that you can't use RunAs accounts to copy VM extensions)
- Use virtual machine extensions to provide post-deployment configuration and automation tasks on Azure VMs in customer tenants
- Use boot diagnostics to troubleshoot Azure VMs in customer tenants
- Access VMs with serial console in customer tenants
- Note that you can't use Azure Active Directory for remote login to a VM, and you can't integrate a VM with a Key Vault for passwords, secrets or cryptographic keys for disk encryption
- Deploy and manage virtual networks and virtual network interface cards (vNICs) within customer tenants
- Open support requests for delegated resources from the Help + support blade in the Azure portal (selecting the support plan available to the delegated scope)
With all scenarios, please be aware of the following current limitations:
- Requests handled by Azure Resource Manager can be performed using Azure delegated resource management. The operation URIs for these requests start with
https://management.azure.com. However, requests that are handled by an instance of a resource type (such as KeyVault secrets access or storage data access) aren’t supported with Azure delegated resource management. The operation URIs for these requests typically start with an address that is unique to your instance, such as
https://mykeyvault.vault.azure.net/. The latter also are typically data operations rather than management operations.
- Role assignments must use role-based access control (RBAC) built-in roles. All built-in roles are currently supported with Azure delegated resource management 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 are not supported.
- Currently, you can’t onboard a subscription (or resource group within a subscription) for Azure delegated resource management if the subscription uses Azure Databricks. Similarly, if a subscription has been registered for onboarding with the Microsoft.ManagedServices resource provider, you won’t be able to create a Databricks workspace for that subscription at this time.
- While you can onboard subscriptions and resource groups for Azure delegated resource management which have resource locks, those locks will not prevent actions from being performed by users in the managing tenant. Deny assignments that protect system-managed resources, such as those created by Azure managed applications or Azure Blueprints (system-assigned deny assignments), do prevent users in the managing tenant from acting on those resources; however, at this time users in the customer tenant can’t create their own deny assignments (user-assigned deny assignments).
- Onboard your customers to Azure delegated resource management, either by using Azure Resource Manager templates or by publishing a private or public managed services offer to Azure Marketplace.
- View and manage customers by going to My customers in the Azure portal.