More markups

Author: Kishan Odedra

articles/operator-insights/managed-identity.md

@@ -27,10 +27,11 @@ For more general information about managed identities, see [What are managed ide
 
 ## User-assigned managed identities in Azure Operator Insights
 
-Azure Operator Insights Data Products use a user-assigned managed identity for:
+Azure Operator Insights use a user-assigned managed identity for:
 
 - Encryption with customer-managed keys, also called CMK-based encryption.
 - Integration with Microsoft Purview. The managed identity allows the Data Product to manage the collection and the data catalog within the collection.
+- Authentication to Azure with an [ingestion agent](ingestion-agent-overview.md). See [use a managed identity for authentication](set-up-ingestion-agent.md#use-a-managed-identity-for-authentication).
 
 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).
 
@@ -40,6 +41,8 @@ You use Microsoft Entra ID to manage user-assigned managed identities. For more
 
 Azure Operator Insights Data Products don't support system-assigned managed identities.
 
+Azure Operator Insights ingestion agents on Azure VMs support system-assigned managed identites, see [Use a managed identity for authentication](set-up-ingestion-agent.md#use-a-managed-identity-for-authentication).
+
 ## Related content
 
 See [Store credential in Azure Key Vault](../data-factory/store-credentials-in-key-vault.md) for information about when and how to use managed identity.

articles/operator-insights/set-up-ingestion-agent.md

@@ -59,7 +59,7 @@ The ingestion agent must be able to authenticate with the Azure Key Vault create
 If the ingestion agent is running in Azure, we recommend managed identities. For more detailed information, see the [overview of managed identities](managed-identity.md#overview-of-managed-identities).
 
 > [!NOTE]
-> The ingestion agent runs on a standard Azure VM and supports both system-assigned and user-assigned managed identity. For multiple agents, a user-assigned managed identity is simpler as you can authorise the identity to the Data Product Key Vault for all VMs running the agent.
+> Ingestion agents on Azure VMs support both system-assigned and user-assigned managed identities. For multiple agents, a user-assigned managed identity is simpler because you can authorise the identity to the Data Product Key Vault for all VMs running the agent.
 
 1. Create or obtain a user-assigned managed identity, follow the instructions in [Manage user-assigned managed identities](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities). If you plan to use a system-assigned managed identity, do not create a user-assigned managed identity.
 1. Follow the instructions in [Configure managed identities for Azure resources on a VM using the Azure portal](/entra/identity/managed-identities-azure-resources/qs-configure-portal-windows-vm) according to the type of managed identity being used.