Skip to content

Commit 873fb19

Browse files
authored
Merge pull request #8403 from MicrosoftDocs/editing-task-21132-edits-cnr
AB#4442: Edited
2 parents 802a2b5 + 3fe37cd commit 873fb19

4 files changed

Lines changed: 19 additions & 13 deletions

File tree

support/power-platform/dataverse/auditing/media/auditlog-troubleshoot-1.png renamed to support/power-platform/dataverse/auditing/media/api-permissions-type-status.png

File renamed without changes.

support/power-platform/dataverse/auditing/media/auditlog-troubleshoot-2.png renamed to support/power-platform/dataverse/auditing/media/azure-key-vault-roles.png

File renamed without changes.
Lines changed: 18 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,41 @@
11
---
2-
title: Troubleshooting sync problems in audit logs
3-
description: Provides common causes for sync issues to help troubleshooting.
2+
title: Troubleshoot synchronization issues in audit logs
3+
description: Provides solutions for resolving synchronization issues in audit logs by validating API permissions and secret environment variables.
44
author: pete-msft
55
ms.component: pa-admin
6-
ms.date: 02/20/2025
6+
ms.date: 03/17/2025
77
ms.author: petrip
8-
ms.reviewer: paulliew, sericks
8+
ms.reviewer: paulliew, sericks, v-christread
99
ms.custom: sap:Microsoft Dataverse\Auditing
1010
search.audienceType:
1111
- admin
1212
contributors:
1313
- Grant-Archibald-MS
1414
---
15-
# Troubleshooting sync problems in audit logs
15+
# Troubleshoot synchronization issues in audit logs
16+
17+
This article provides guidance for resolving synchronization issues in audit logs. It focuses on validating API permissions and secret environment variables to ensure proper configuration for your app registration.
1618

1719
## API permissions
1820

19-
Go to your app registration and validate that you have the correct API permissions. Your app registration requires application permissions not delegated. Validate that the status is _Granted_.
21+
To ensure that you have the correct API permissions, follow these steps:
22+
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**.
2026

21-
:::image type="content" source="media/auditlog-troubleshoot-1.png" alt-text="Screenshot that highlights the Application type and Granted for status of a configured permission." lightbox="media/auditlog-troubleshoot-1.png":::
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":::
2228

2329
## Secret environment variable - Azure secret
2430

25-
If you're using Azure Key value to store the app registration secret, validate that the Azure Key Vault permissions are correct.
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.
2632

27-
A user needs to be in the _Key Vault Secret User_ role to read and in the _Key Vault Contributor_ role to update.
33+
A user must have 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).
2834

29-
:::image type="content" source="media/auditlog-troubleshoot-2.png" alt-text="Screenshot that shows the Key Vault Contributor and Key Vault Secrets User roles." lightbox="media/auditlog-troubleshoot-2.png":::
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":::
3036

31-
If you have other issues with Azure Key Vault regarding a firewall, static IPs for the Dataverse environment, or other such feature issues, contact product support to resolve them.
37+
If you have other issues with Azure Key Vault related to a firewall, static IP addresses for the Dataverse environment, or other feature issues, contact Microsoft Support through the **Help + Support** experience in the [Power Platform admin center](https://admin.powerplatform.microsoft.com/support).
3238

3339
## Secret environment variable - plain text
3440

35-
If you're using plain text to store the app registration secret, validate that you entered the secret value itself, and not the secret ID. The secret value is a longer string with a larger character set than a GUID. For example, the string might have tilde characters.
41+
If you're using plain text to store the app registration secret, validate that you entered the secret value itself, not the secret ID. The secret value is a longer string that has a larger character set compared to a globally unique identifier (GUID). For example, the string for the secret value might include tilde (~) characters.

support/power-platform/dataverse/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
href: welcome-dataverse.yml
33
- name: Auditing
44
items:
5-
- name: Troubleshooting sync problems in audit logs
5+
- name: Troubleshoot synchronization issues in audit logs
66
href: auditing/setup-auditlog-troubleshooting.md
77
- name: Bulk deleting data
88
items:

0 commit comments

Comments
 (0)