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: support/power-platform/dataverse/auditing/setup-auditlog-troubleshooting.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Troubleshoot sync issues in audit logs
2
+
title: Troubleshoot synchronization issues in audit logs
3
3
description: Provides solutions for resolving synchronization issues in audit logs by validating API permissions and secret environment variables.
4
4
author: pete-msft
5
5
ms.component: pa-admin
@@ -18,19 +18,19 @@ This article provides guidance for resolving synchronization issues in audit log
18
18
19
19
## API permissions
20
20
21
-
To ensure you have the correct API permissions,
21
+
To ensure that you have the correct API permissions, follow these steps.
22
22
23
-
1.Navigate to your [app registration](/entra/identity-platform/quickstart-configure-app-access-web-apis#application-permission-to-microsoft-graph).
24
-
1. Ensure that the API permissions are set to **Application** type rather than **Delegated**.
25
-
1.Check the permission status and verify that it's**Granted**.
23
+
1.Go to your [app registration](/entra/identity-platform/quickstart-configure-app-access-web-apis#application-permission-to-microsoft-graph).
24
+
1. Ensure that the API permissions are set to the **Application** type instead of the **Delegated** type.
25
+
1.Verify that the permission status is**Granted**.
26
26
27
27
:::image type="content" source="media/api-permissions-type-status.png" alt-text="Screenshot that highlights the Application type and Granted status of a configured permission." lightbox="media/api-permissions-type-status.png":::
28
28
29
29
## Secret environment variable - Azure secret
30
30
31
31
If you're using [Azure Key Vault](/azure/key-vault/general/basic-concepts) to store the app registration secret, validate that the Azure Key Vault permissions are correct.
32
32
33
-
A user must be in the _Key Vault Secrets User_ role to read and the _Key Vault Contributor_ role to update. For detailed role definitions, see[Azure built-in roles for Key Vault data plane operations](/azure/key-vault/general/rbac-guide?tabs=azure-cli#azure-built-in-roles-for-key-vault-data-plane-operations).
33
+
A user must be in the _Key Vault Secrets User_ role to read and the _Key Vault Contributor_ role to update. You can find detailed role definitions in[Azure built-in roles for Key Vault data plane operations](/azure/key-vault/general/rbac-guide?tabs=azure-cli#azure-built-in-roles-for-key-vault-data-plane-operations).
34
34
35
35
:::image type="content" source="media/azure-key-vault-roles.png" alt-text="Screenshot that shows the Key Vault Contributor and Key Vault Secrets User roles." lightbox="media/azure-key-vault-roles.png":::
0 commit comments