Merge pull request #229772 from charithcaldera/patch-4

Update known-issues.md

Author: ttorble

articles/synapse-analytics/known-issues.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Synapse Analytics
 description: Learn about the currently known issues with Azure Synapse Analytics, and their possible workarounds or resolutions.
 author: charithdilshan
 ms.author: ccaldera
-ms.date: 3/6/2023
+ms.date: 3/9/2023
 ms.service: synapse-analytics
 ms.subservice: overview
 ms.topic: conceptual
@@ -16,21 +16,20 @@ ms.reviewer: wiassaf
 This page lists the known issues in [Azure Synapse Analytics](overview-what-is.md), as well as their resolution date or possible workaround. 
 Before submitting a Support request, please review this list to see if the issue that you're experiencing is already known and being addressed.
 
-To learn more about Azure Synapse Analytics, see the [Overview](index.yml), and [What's new in Azure Synapse Analytics?](whats-new.md). 
+To learn more about Azure Synapse Analytics, see the [Azure Synapse Analytics Overview](index.yml), and [What's new in Azure Synapse Analytics?](whats-new.md). 
 
 ## Active Known issues
 
-|Issue |Status  |Synapse Component|
+|Azure Synapse Component|Status|Issue|
 |---------|---------|---------|
-|[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|
-|[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|
-|[Query failures while reading Cosmos Data using OPENROWSET](#query-failures-while-reading-cosmos-data-using-openrowset)|Has Workaround|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|Azure Synapse Serverless SQL Pool|
-|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|Azure Synapse Dedicated SQL Pool|
-|[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|
-|[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|
+|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|
+|Azure Synapse serverless SQL pool|[Query failures from serverless SQL pool to Azure Cosmos DB analytical store](#query-failures-from-serverless-sql-pool-to-azure-cosmos-db-analytical-store)|Has Workaround|
+|Azure Synapse serverless SQL pool|[Azure Cosmos DB analytical store view propagates wrong attributes in the column](#azure-cosmos-db-analytical-store-view-propagates-wrong-attributes-in-the-column)|Has Workaround|
+|Azure Synapse dedicated SQL pool|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|
+|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|
+|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|
 
-## Azure Synapse Analytics Serverless SQL Pool known issues summary
+## Azure Synapse Analytics serverless SQL pool active known issues summary
 
 ### Queries using Azure AD authentication fails after 1 hour
 
@@ -42,7 +41,7 @@ Following steps can be followed to work around the problem.
 1) It's recommended switching to Service Principal, Managed Identity or Shared Access Signature instead of using user identity for long running queries. 
 2) Restarting client (SSMS/ADS) acquires new token to establish the connection.
 
-### Query failures from Serverless SQL pool to Azure Cosmos DB analytical store
+### Query failures from serverless SQL pool to Azure Cosmos DB analytical store
 
 Queries from a serverless SQL pool to Azure Cosmos DB analytical store might fail with one of the following error messages:
 
@@ -59,24 +58,16 @@ The following conditions must be true to confirm this issue:
 1) Retry the failed query. It will automatically refresh the expired token.
 2) Disable the private endpoint. Before applying this change, confirm with your security team that it meets your company security policies.
 
-### Query failures while reading Cosmos Data using OPENROWSET
+### Azure Cosmos DB analytical store view propagates wrong attributes in the column
 
-Queries from serverless SQL pool to Cosmos DB Analytical Store using OPENROWSET fails with the following error message:
-
-`Resolving CosmosDB path has failed with error 'bad allocation'.`
-
-**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.
-
-### Cosmos DB analytical store view propagates wrong attributes in the column
-
-While using views in Synapse serverless pool over CosmosDB analytical store, If there is a change on files in the CosmosDB analytical store, the change does not get propagated correctly to the SELECT statements, the customer is using on the view. As a result of that, the attributes get incorrectly mapped to a different column in the results.
+While using views in Azure Synapse serverless pool over Cosmos DB analytical store, If there is a change on files in the Cosmos DB analytical store, the change does not get propagated correctly to the SELECT statements, the customer is using on the view. As a result of that, the attributes get incorrectly mapped to a different column in the results.
 
 **Workaround**: The engineering team is aware of this behavior and following actions can be taken as quick mitigation:
 
 1) Recreate the view by renaming the columns.
 2) Avoid using views if possible. 
 
-## Azure Synapse Analytics Dedicated SQL pool known issues summary
+## Azure Synapse Analytics Dedicated SQL pool active known issues summary
 
 ### Queries failing with Data Exfiltration Error
 
@@ -86,7 +77,7 @@ Synapse workspaces created from an existing dedicated SQL Pool report query fail
 
 **Workaround**: If you encountered a similar error, engage Microsoft Support Team for assistance.
 
-## Azure Synapse workspace known issues summary
+## Azure Synapse workspace active known issues summary
 
 The following are known issues with the Synapse workspace.
 
@@ -104,6 +95,23 @@ Deleting a Synapse workspace fails with the error message:
 
 **Workaround**: The problem can be mitigated by retrying the delete operation. The engineering team is aware of this behavior and working on a fix.
 
+## Recently Closed Known issues
+
+|Synapse Component|Issue|Status|Date Resolved
+|---------|---------|---------|---------|
+|Azure Synapse serverless SQL pool|[Query failures while reading Cosmos DB data using OPENROWSET](#query-failures-while-reading-azure-cosmos-db-data-using-openrowset)|Resolved|March 2023
+
+## Azure Synapse Analytics serverless SQL pool recently closed known issues summary
+
+### Query failures while reading Azure Cosmos DB data using OPENROWSET
+
+Queries from serverless SQL pool to Cosmos DB Analytical Store using OPENROWSET fails with the following error message:
+
+`Resolving CosmosDB path has failed with error 'bad allocation'.`
+
+**Status**: Resolved
+
+
 ## Next steps
 
 - [Synapse Studio troubleshooting](troubleshoot/troubleshoot-synapse-studio.md)