Skip to content

Commit 0c138a1

Browse files
committed
clarify resource provider tip
1 parent ace16b8 commit 0c138a1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/lighthouse/how-to/monitor-at-scale.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Monitor delegated resources at scale
33
description: Learn how to effectively use Azure Monitor Logs in a scalable way across the customer tenants you're managing.
4-
ms.date: 02/11/2021
4+
ms.date: 05/10/2021
55
ms.topic: how-to
66
---
77

@@ -26,7 +26,7 @@ We recommend creating these workspaces directly in the customer tenants. This wa
2626
You can create a Log Analytics workspace by using the [Azure portal](../../azure-monitor/logs/quick-create-workspace.md), by using [Azure CLI](../../azure-monitor/logs/quick-create-workspace-cli.md), or by using [Azure PowerShell](../../azure-monitor/logs/powershell-workspace-configuration.md).
2727

2828
> [!IMPORTANT]
29-
> Even if all of the workspaces are created in the customer tenant, the Microsoft.Insights resource provider must also be registered on a subscription in the managing tenant.
29+
> Even if all of the workspaces are created in the customer tenant, the Microsoft.Insights resource provider must also be registered on a subscription in the managing tenant. If your managing tenant doesn't have a subscription, you'll need to create one, then [register the resource provider](../../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider).
3030
3131
## Deploy policies that log data
3232

0 commit comments

Comments
 (0)