Skip to content

Commit b168cf2

Browse files
Merge pull request #278106 from rcdun/patch-2
Fix typo managed-identity.md
2 parents 249ec10 + 1f496ce commit b168cf2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/operator-insights/managed-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Azure Operator Insights use a user-assigned managed identity for:
3131

3232
- Encryption with customer-managed keys, also called CMK-based encryption.
3333
- Integration with Microsoft Purview. The managed identity allows the Data Product to manage the collection and the data catalog within the collection.
34-
- Authentication to Azure for an [Azure Operator Insights ingestion agent](ingestion-agent-overview.md) on an Azure VM. The managed identity allows the ingestion agent to access a Data Product's Key Vault. See [use a managed identity for authentication](set-up-ingestion-agent.md#use-a-managed-identity-for-authentication).
34+
- Authentication to Azure for an [Azure Operator Insights ingestion agent](ingestion-agent-overview.md) on an Azure VM. The managed identity allows the ingestion agent to access a Data Product's Key Vault. See [Use a managed identity for authentication](set-up-ingestion-agent.md#use-a-managed-identity-for-authentication).
3535

3636
When you [create a Data Product](data-product-create.md), you set up the managed identity and associate it with the Data Product. To use the managed identity with Microsoft Purview, you must also [grant the managed identity the appropriate permissions in Microsoft Purview](purview-setup.md#access-and-set-up-your-microsoft-purview-account).
3737

0 commit comments

Comments
 (0)