Skip to content

Commit d986ab8

Browse files
authored
Merge pull request #153018 from MGoedtel/task1708417b
updated overview of Change Tracking about Lighthouse
2 parents 6800fe5 + 0c950aa commit d986ab8

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/automation/change-tracking/overview.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,8 @@ Machines connected to the Log Analytics workspace use the [Log Analytics agent](
3636
> [!NOTE]
3737
> Change Tracking and Inventory requires linking a Log Analytics workspace to your Automation account. For a definitive list of supported regions, see [Azure Workspace mappings](../how-to/region-mappings.md). The region mappings don't affect the ability to manage VMs in a separate region from your Automation account.
3838
39+
As a service provider, you may have onboarded multiple customer tenants to [Azure Lighthouse](../../lighthouse/overview.md). Azure Lighthouse allows you to perform operations at scale across several Azure Active Directory (Azure AD) tenants at once, making management tasks like Change Tracking and Inventory more efficient across those tenants you're responsible for. Change Tracking and Inventory can manage machines in multiple subscriptions in the same tenant, or across tenants using [Azure delegated resource management](../../lighthouse/concepts/azure-delegated-resource-management.md).
40+
3941
## Current limitations
4042

4143
Change Tracking and Inventory doesn't support or has the following limitations:

0 commit comments

Comments
 (0)