|
| 1 | +--- |
| 2 | +title: Troubleshoot Azure Synapse Link profile creation issues |
| 3 | +description: Resolves networking, permissions, regional mismatches, or profile limits in Microsoft Dataverse. |
| 4 | +author: Greggbarker-ms |
| 5 | +ms.author: grbarker |
| 6 | +ms.reviewer: saukuma |
| 7 | +ai-usage: ai-assisted |
| 8 | +ms.date: 04/03/2025 |
| 9 | +ms.custom: sap:Importing and exporting data\Configuring Export to Azure Data Lake and Azure Synapse Link integration |
| 10 | +--- |
| 11 | +# Troubleshoot Azure Synapse Link profile creation issues |
| 12 | + |
| 13 | +This article provides detailed guidance for troubleshooting common issues encountered during the [creation of Azure Synapse Link profiles](/power-apps/maker/data-platform/azure-synapse-link-synapse). The steps outlined address causes like networking misconfigurations, insufficient permissions, regional mismatches, and other factors that might impact the setup process. |
| 14 | + |
| 15 | +## Networking misconfiguration |
| 16 | + |
| 17 | +**Cause:** Public network access is disabled or IP access rules are improperly configured for the storage account. |
| 18 | + |
| 19 | +**Solution:** |
| 20 | + |
| 21 | +1. Ensure **Public network access** is enabled for the linked storage account. |
| 22 | +2. Set the IP addresses access rule to "allowAll" if linking to a Synapse Workspace. If restricting public access, enable the [managed identities feature](/power-apps/maker/data-platform/azure-synapse-link-msi) for the linked storage account and workspace. |
| 23 | + |
| 24 | +:::image type="content" source="media/troubleshoot-synapse-link-profile-creation-issues/synapse-networking-configuration.png" alt-text="Screenshot of the Networking setup page in synapse."::: |
| 25 | + |
| 26 | +## Insufficient permissions |
| 27 | + |
| 28 | +**Cause:** Missing required roles and permissions for Synapse Workspace, storage account, or Dataverse environment. |
| 29 | + |
| 30 | +**Solution:** |
| 31 | + |
| 32 | +1. Ensure you have the following roles: |
| 33 | + |
| 34 | + - **Dataverse System Administrator** security role. |
| 35 | + - **Synapse Administrator** role for Synapse Workspace. |
| 36 | + - **Reader** role for the resource group containing the storage account and Synapse Workspace. |
| 37 | + - **Owner** and **Storage Blob Data Contributor** roles for the Azure Data Lake Storage Gen2 account. |
| 38 | + |
| 39 | + For more information, review the prerequisites based on your profile type: |
| 40 | + |
| 41 | + - [Prerequisites for Azure Synapse Link profile with Azure Data Lake](/power-apps/maker/data-platform/azure-synapse-link-data-lake#prerequisites) |
| 42 | + - [Prerequisites for Azure Synapse Link profile with your Azure Synapse Workspace](/power-apps/maker/data-platform/azure-synapse-link-synapse#prerequisites) |
| 43 | + |
| 44 | +2. Select the **Enable storage account key access** checkbox during initial setup. |
| 45 | + |
| 46 | + :::image type="content" source="media/troubleshoot-synapse-link-profile-creation-issues/permissions-setup-create-storage-account.png" alt-text="Screenshot of the Advanced setup page in Create a storage account page."::: |
| 47 | + |
| 48 | +## Azure region mismatch |
| 49 | + |
| 50 | +**Cause:** Synapse Workspace, storage account, and Power Apps environment aren't in the same Azure region. |
| 51 | + |
| 52 | +**Solution:** |
| 53 | + |
| 54 | +1. Verify that all resources are in the same region. |
| 55 | +2. If necessary, move the storage account to the appropriate region using [Relocate Azure Storage Account to another region](/azure/storage/common/storage-account-move). |
| 56 | + |
| 57 | +## The Track changes property isn't enabled |
| 58 | + |
| 59 | +**Cause:** The tables intended for export don't have the **Track changes** property enabled. |
| 60 | + |
| 61 | +**Solution:** |
| 62 | + |
| 63 | +To solve this issue, enable the **Track changes** property for the desired tables by following the steps described in [Enable change tracking to control data synchronization](/power-platform/admin/enable-change-tracking-control-data-synchronization). |
| 64 | + |
| 65 | +## Maximum number of Azure Synapse Link profiles is reached |
| 66 | + |
| 67 | +**Cause:** The Dataverse environment has reached its limit for Azure Synapse Link profiles. |
| 68 | + |
| 69 | +**Solution:** |
| 70 | + |
| 71 | +1. Review the current Azure Synapse Link profiles in your environment. |
| 72 | +2. If the maximum limit is reached, consider removing unused profiles to create new ones. |
| 73 | + |
| 74 | +## Mitigation for UI stuck on the "Fetching App..." status |
| 75 | + |
| 76 | +**Cause:** The "Common Data Service - Azure Data Lake Storage" app (ID: 546068c3-99b1-4890-8e93-c8aeadcfe56a) is missing in your Microsoft Entra ID. |
| 77 | + |
| 78 | +**Validation:** |
| 79 | + |
| 80 | +1. Use [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer) or the following [Azure PowerShell](/powershell/module/az.resources/get-azadserviceprincipal) command to check if the app exists: |
| 81 | + |
| 82 | + ```powershell |
| 83 | + Get-AzADServicePrincipal -ApplicationId 546068c3-99b1-4890-8e93-c8aeadcfe56a |
| 84 | + ``` |
| 85 | + |
| 86 | +2. If a 404 error is returned in Graph Explorer, the app is missing. |
| 87 | + |
| 88 | + ```jsonc |
| 89 | + { |
| 90 | + "error": { |
| 91 | + "code": "Request_ResourceNotFound", |
| 92 | + "message": "Resource '' does not exist or one of its queried reference-property objects are not present.", |
| 93 | + "innerError": |
| 94 | + } |
| 95 | + ``` |
| 96 | +
|
| 97 | + :::image type="content" source="media/troubleshoot-synapse-link-profile-creation-issues/graph-explorer-404-error.png" alt-text="Screenshot of the 404 error that occurs in Graph Explorer."::: |
| 98 | +
|
| 99 | +**Solution:** |
| 100 | +
|
| 101 | +1. Ensure you have the necessary privileges (Application Administrator or Global Administrator). |
| 102 | +
|
| 103 | +2. Open PowerShell and run: |
| 104 | +
|
| 105 | + ```powershell |
| 106 | + Connect-AzAccount |
| 107 | + ``` |
| 108 | +
|
| 109 | +3. Add the missing service principal using: |
| 110 | +
|
| 111 | + ```powershell |
| 112 | + New-AzADServicePrincipal -ApplicationId '546068c3-99b1-4890-8e93-c8aeadcfe56a' |
| 113 | + ``` |
| 114 | +
|
| 115 | +4. After adding the principal, retry creating the Azure Synapse Link profile. |
0 commit comments