Skip to content

Commit 081b518

Browse files
authored
Apply suggestions from PR review
1 parent 305e01a commit 081b518

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/synapse-analytics/known-issues.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Known issues
33
titleSuffix: Azure Synapse Analytics
44
description: Learn about the currently known issues with Azure Synapse Analytics and their possible workarounds or resolutions.
5-
author: charithdilshan
5+
author: charithcaldera
66
ms.author: ccaldera
77
ms.reviewer: wiassaf, joanpo
88
ms.date: 04/08/2024
@@ -133,9 +133,10 @@ The Azure Policy Alias can be used for managing this property with a Deny Azure
133133
Since the Microsoft.Synapse/workspaces/trustedServiceByPassConfiguration child resource has no GET operation available, Azure Policy cannot manage these requests, and Azure Policy cannot generate an Azure Policy Alias for it.
134134

135135
**Parent Resource:** Microsoft.Synapse/workspaces
136+
136137
**Child Resource:** Microsoft.Synapse/workspaces/trustedServiceByPassConfiguration
137138

138-
The Azure Portal makes the PUT request directly to the PUT API for the child resource and therefore the Azure Portal, along with any other API requests made outside of the parent Microsoft.Synapse/workspaces APIs, cannot be managed by Azure Policy through a Deny or other actionable Azure Policy Effect.
139+
The Azure portal makes the PUT request directly to the PUT API for the child resource and therefore the Azure portal, along with any other API requests made outside of the parent Microsoft.Synapse/workspaces APIs, cannot be managed by Azure Policy through a Deny or other actionable Azure Policy Effect.
139140

140141
## Azure Synapse Analytics serverless SQL pool active known issues summary
141142

0 commit comments

Comments
 (0)