You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-insights/set-up-ingestion-agent.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -217,7 +217,7 @@ The configuration you need is specific to the type of source and your Data Produ
217
217
1. For the secret provider with type `key_vault` and name `data_product_keyvault`, set the following fields.
218
218
- `vault_name` must be the name of the Key Vault for your Data Product. You identified this name in [Grant permissions for the Data Product Key Vault](#grant-permissions-for-the-data-product-key-vault).
219
219
- Depending on the type of authentication you chose in [Set up authentication to Azure](#set-up-authentication-to-azure), set either `managed_identity` or `service_principal`.
220
-
- For a managed identity: set `object_id` to the Object ID of the managed identity that you created in [Create a managed identity](#create-a-managed-identity).
220
+
- For a managed identity: set `object_id` to the Object ID of the managed identity that you created in [Use a managed identity for authentication](#use-a-managed-identity-for-authentication).
221
221
- For a service principal: set `tenant_id` to your Microsoft Entra ID tenant, `client_id` to the Application (client) ID of the service principal that you created in [Create a service principal](#create-a-service-principal), and `cert_path` to the file path of the base64-encoded P12 certificate on the VM.
222
222
1. For the secret provider with type `file_system` and name `local_file_system`, set the following fields.
223
223
- `secrets_directory` to the absolute path to the secrets directory on the agent VM, which was created in the [Prepare the VMs](#prepare-the-vms) step.
@@ -231,7 +231,7 @@ The configuration you need is specific to the type of source and your Data Produ
231
231
1. For the secret provider with type `key_vault` and name `data_product_keyvault`, set the following fields.
232
232
- `vault_name` must be the name of the Key Vault for your Data Product. You identified this name in [Grant permissions for the Data Product Key Vault](#grant-permissions-for-the-data-product-key-vault).
233
233
- Depending on the type of authentication you chose in [Set up authentication to Azure](#set-up-authentication-to-azure), set either `managed_identity` or `service_principal`.
234
-
- For a managed identity: set `object_id` to the Object ID of the managed identity that you created in [Create a managed identity](#create-a-managed-identity).
234
+
- For a managed identity: set `object_id` to the Object ID of the managed identity that you created in [Use a managed identity for authentication](#use-a-managed-identity-for-authentication).
235
235
- For a service principal: set `tenant_id` to your Microsoft Entra ID tenant, `client_id` to the Application (client) ID of the service principal that you created in [Create a service principal](#create-a-service-principal), and `cert_path` to the file path of the base64-encoded P12 certificate on the VM.
236
236
237
237
You can add more secret providers (for example, if you want to upload to multiple data products) or change the names of the default secret provider.
0 commit comments