Skip to content

Commit 497df6a

Browse files
Update known-issues.md
Adding Serverless AAD behavior after having an internal check. [email protected] (PM) and [email protected] (EEE) aware of this.
1 parent 9727ba2 commit 497df6a

File tree

1 file changed

+18
-7
lines changed

1 file changed

+18
-7
lines changed

articles/synapse-analytics/known-issues.md

Lines changed: 18 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -20,16 +20,27 @@ To learn more about Azure Synapse Analytics, see the [Overview](index.yml), and
2020

2121
## Active Known issues
2222

23-
|Issue |Date discovered |Status |Synapse Component|
24-
|---------|---------|---------|---------|
25-
|[Query failures from Serverless SQL to Cosmos DB analytical store](#query-failures-from-serverless-sql-pool-to-azure-cosmos-db-analytical-store)|June 2022|Has Workaround|Azure Synapse Serverless SQL pool|
26-
|[Query failures while reading Cosmos Data using OPENROWSET](#query-failures-while-reading-cosmos-data-using-openrowset)|September 2022|Has Workaround|Azure Synapse Serverless SQL Pool|
27-
|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|October 2022|Has Workaround|Azure Synapse Dedicated SQL Pool|
28-
|[Blob storage linked service with User Assigned Managed Identity (UAMI) is not getting listed](#blob-storage-linked-service-with-user-assigned-managed-identity-uami-is-not-getting-listed)|October 2022|Has Workaround|Azure Synapse Workspace|
29-
|[Failed to delete Synapse workspace & Unable to delete virtual network](#failed-to-delete-synapse-workspace--unable-to-delete-virtual-network)|November 2022|Has Workaround|Azure Synapse Workspace|
23+
|Issue |Status |Synapse Component|
24+
|---------|---------|---------|
25+
|[Queries using AAD authentication fails after 1 hour](#queries-using-aad-authentication-fails-after-1-hour)|Has Workaround|Azure Synapse Serverless SQL Pool|
26+
|[Query failures from Serverless SQL to Cosmos DB analytical store](#query-failures-from-serverless-sql-pool-to-azure-cosmos-db-analytical-store)|Has Workaround|Azure Synapse Serverless SQL pool|
27+
|[Query failures while reading Cosmos Data using OPENROWSET](#query-failures-while-reading-cosmos-data-using-openrowset)|Has Workaround|Azure Synapse Serverless SQL Pool|
28+
|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|Azure Synapse Dedicated SQL Pool|
29+
|[Blob storage linked service with User Assigned Managed Identity (UAMI) is not getting listed](#blob-storage-linked-service-with-user-assigned-managed-identity-uami-is-not-getting-listed)|Has Workaround|Azure Synapse Workspace|
30+
|[Failed to delete Synapse workspace & Unable to delete virtual network](#failed-to-delete-synapse-workspace--unable-to-delete-virtual-network)|Has Workaround|Azure Synapse Workspace|
3031

3132
## Azure Synapse Analytics Serverless SQL Pool known issues summary
3233

34+
### Queries using AAD authentication fails after 1 hour
35+
36+
SQL connections using Azure AD authentication that remain active for more than 1 hour will start to fail. This includes querying storage using Azure AD pass-through authentication and statements that interact with Azure AD, like CREATE EXTERNAL PROVIDER. This affects every tool that keeps connections active, like query editor in SSMS and ADS. Tools that open new connection to execute queries are not affected, like Synapse Studio.
37+
38+
**Workaround**: The engineering team is currently aware of this behavior and working on a fix. <br>
39+
Following steps can be followed to workaround the problem.
40+
41+
1) It is recommended switching to Service Principal, Managed Identity or Shared Access Signature instead of using user identity for long running queries.
42+
2) Restarting client (SSMS/ADS) acquires new token to establish the connection.
43+
3344
### Query failures from Serverless SQL pool to Azure Cosmos DB analytical store
3445

3546
Queries from a serverless SQL pool to Azure Cosmos DB analytical store might fail with one of the following error messages:

0 commit comments

Comments
 (0)