Skip to content

Commit 613e676

Browse files
authored
Update synapse-link-frequently-asked-questions.yml
1 parent 0213a4d commit 613e676

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/synapse-link-frequently-asked-questions.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -218,7 +218,7 @@ sections:
218218
Yes, You can control network access to the data in the transactional and analytical stores independently. Network isolation is done using separate managed private endpoints for each store, within managed virtual networks in Azure Synapse workspaces. To learn more, see how to [Configure private endpoints for analytical store](analytical-store-private-endpoints.md) article.
219219
220220
- question: |
221-
I'm getting error 403 (Could not retrieve Analytical Store status for one or more containers Response status code does not indicate success: 403 (Forbidden)) after Azure Private Link was enable for my database account. What's happening?
221+
I'm getting error 403 (Could not retrieve Analytical Store status for one or more containers Response status code does not indicate success: 403 (Forbidden)) after Azure Private Link was enabled for my database account. What's happening?
222222
answer: |
223223
Usually, 403's are due to network/firewall settings that prevent users from accessing specific data, even from the portal. The most common cause for this problem is that step 1 of the enable Network isolation process using private endpoints has not been performed. You need to use Azure CLI or PowerShell for this. More details [here](analytical-store-private-endpoints.md).
224224

0 commit comments

Comments
 (0)