You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn about the currently known issues with Azure Synapse Analytics, and their possible workarounds or resolutions.
5
5
author: charithdilshan
6
6
ms.author: ccaldera
7
-
ms.date: 3/8/2023
7
+
ms.date: 3/9/2023
8
8
ms.service: synapse-analytics
9
9
ms.subservice: overview
10
10
ms.topic: conceptual
@@ -20,14 +20,14 @@ To learn more about Azure Synapse Analytics, see the [Overview](index.yml), and
20
20
21
21
## Active Known issues
22
22
23
-
|Issue |Status|Synapse Component|
23
+
|Synapse Component|Status|Issue|
24
24
|---------|---------|---------|
25
-
|[Queries using Azure AD authentication fails after 1 hour](#queries-using-azure-ad-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
-
|[Cosmos DB analytical store view propagates wrong attributes in the column](#cosmos-db-analytical-store-view-propagates-wrong-attributes-in-the-column)|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|
25
+
|Azure Synapse Serverless SQL Pool|[Queries using Azure AD authentication fails after 1 hour](#queries-using-azure-ad-authentication-fails-after-1-hour)|Has Workaround|
26
+
|Azure Synapse Serverless SQL pool|[Query failures from Serverless SQL to Cosmos DB analytical store](#query-failures-from-serverless-sql-pool-to-azure-cosmos-db-analytical-store)|Has Workaround|
27
+
|Azure Synapse Serverless SQL Pool|[Cosmos DB analytical store view propagates wrong attributes in the column](#cosmos-db-analytical-store-view-propagates-wrong-attributes-in-the-column)|Has Workaround|
28
+
|Azure Synapse Dedicated SQL Pool|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|
29
+
|Azure Synapse Workspace|[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|
30
+
|Azure Synapse Workspace|[Failed to delete Synapse workspace & Unable to delete virtual network](#failed-to-delete-synapse-workspace--unable-to-delete-virtual-network)|Has Workaround|
31
31
32
32
## Azure Synapse Analytics Serverless SQL Pool active known issues summary
33
33
@@ -97,9 +97,9 @@ Deleting a Synapse workspace fails with the error message:
97
97
98
98
## Recently Closed Known issues
99
99
100
-
|Issue |Status|Synapse Component|
101
-
|---------|---------|---------|
102
-
|[Query failures while reading Cosmos Data using OPENROWSET](#query-failures-while-reading-cosmos-data-using-openrowset)|Resolved|Azure Synapse Serverless SQL Pool|
100
+
|Synapse Component|Issue|Status|Date Resolved
101
+
|---------|---------|---------|---------|
102
+
|Azure Synapse Serverless SQL Pool|[Query failures while reading Cosmos Data using OPENROWSET](#query-failures-while-reading-cosmos-data-using-openrowset)|Resolved|March 2023
103
103
104
104
## Azure Synapse Analytics Serverless SQL Pool recently closed known issues summary
105
105
@@ -109,7 +109,7 @@ Queries from serverless SQL pool to Cosmos DB Analytical Store using OPENROWSET
109
109
110
110
`Resolving CosmosDB path has failed with error 'bad allocation'.`
111
111
112
-
**Workaround**: The engineering team is aware of this behavior and working on a fix. If you encounter this error engage Microsoft Support Team for assistance.
0 commit comments