20221206 edit pass, linkage, toc

Author: WilliamDAssafMSFT

articles/synapse-analytics/known-issues.md

@@ -4,100 +4,87 @@ 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: 11/09/2022
+ms.date: 12/06/2022
 ms.service: synapse-analytics
 ms.subservice: overview
 ms.topic: conceptual
 ---
 
-# Azure Synapse Analytics Known Issues
+# Azure Synapse Analytics known issues
 
-This page lists the  known issues in [Azure Synapse Analytics](https://learn.microsoft.com/azure/synapse-analytics/overview-what-is), as well as their resolution date or possible workaround. 
+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 are experiencing is already known and being addressed.
 
-To learn more about Azure Synapse Analytics, see the [overview](https://learn.microsoft.com/azure/synapse-analytics/), and [what's new](https://learn.microsoft.com/azure/synapse-analytics/whats-new). 
+To learn more about Azure Synapse Analytics, see the [Overview](index.yml), and [What's new in Azure Synapse Analytics?](whats-new.md). 
 
 ## Active Known issues
 
 |Issue  |Date discovered  |Status  |Synapse Component|
 |---------|---------|---------|---------|
-|[Queries using AAD authentication fails after 1 hour](#queries-using-aad-authentication-fails-after-1-hour)|January 2021|Has Workaround|Azure Synapse Serverless SQL Pool|
-|[Query failures from Serverless SQL to Cosmos DB Analytical Store](#query-failures-from-serverless-sql-pool-to-cosmos-db-analytical-store)|June 2022|Has Workaround|Azure Synapse Serverless SQL Pool|
+|[Query failures from Serverless SQL to Cosmos DB analytical store](#query-failures-from-serverless-sql-pool-to-cosmos-db-analytical-store)|June 2022|Has Workaround|Azure Synapse Serverless SQL pool|
 |[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|
 |[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|October 2022|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)|October 2022|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)|November 2022|Has Workaround|Azure Synapse Workspace|
 
+## Azure Synapse Analytics Serverless SQL Pool known issues summary
 
-## Azure Synapse Analytics Serverless SQL Pool Known Issues Summary
+### Query failures from Serverless SQL pool to Azure Cosmos DB analytical store
 
-### Queries using AAD authentication fails after 1 hour
+Queries from a serverless SQL pool to Azure Cosmos DB analytical store might fail with one of the following error messages:
 
-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.
-
-**Workaround**: There are 2 mitigation steps can be taken.
-
-1) It is 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 Cosmos DB Analytical Store
-
-Queries from serverless SQL to Cosmos DB Analytical store might fail with one of the following error messages:
-
-_"Resolving CosmosDB path has failed with error 'This request is not authorized to perform this operation'"_
-_"Resolving CosmosDB path has failed with error 'Key not found'"_
+- `Resolving CosmosDB path has failed with error 'This request is not authorized to perform this operation'`
+- `Resolving CosmosDB path has failed with error 'Key not found'`
 
 The following conditions must be true to confirm this issue:
 
-1) The connection to Cosmos DB Analytical store uses a private endpoint. 
+1) The connection to Azure Cosmos DB analytical store uses a private endpoint. 
 2) Retrying the query succeeds.
 
-**Workaround**: The engineering team is aware of this behavior and following actions can be taken as quick mitigations.
+**Workaround**: The engineering team is aware of this behavior and following actions can be taken as quick mitigation:
 
-1) Retry the failed query. It will automatically refresh the expired token. 
+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
 
 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'."_
-
+`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.
 
-## Azure Synapse Analytics Dedicated SQL Pool Known Issues Summary
+## Azure Synapse Analytics Dedicated SQL pool known issues summary
 
 ### Queries failing with Data Exfiltration Error
 
-Synapse workspaces created from an existing dedicated SQL Pool report query failures related to [Data Exfiltration Protection](https://learn.microsoft.com/azure/synapse-analytics/security/workspace-data-exfiltration-protection) with generic error message while Data Exfiltration Protection is turned off in Synapse Analytics: 
+Synapse workspaces created from an existing dedicated SQL Pool report query failures related to [Data Exfiltration Protection](security/workspace-data-exfiltration-protection.md) with generic error message while Data Exfiltration Protection is turned off in Synapse Analytics: 
 
-_"Data exfiltration to '{****}' is blocked. Add destination to allowed list for data exfiltration and try again."_
+`Data exfiltration to '{****}' is blocked. Add destination to allowed list for data exfiltration and try again.`
 
 **Workaround**: If you encountered a similar error, engage Microsoft Support Team for assistance.
 
-## Azure Synapse Analytics Workspace Known Issues Summary
+## Azure Synapse workspace known issues summary
+
+The following are known issues with the Synapse workspace.
 
 ### Blob storage linked service with User Assigned Managed Identity (UAMI) is not getting listed
 
-The linked service may not be visible under the "Data Hub - Linked - Azure Blob Storage Tab" after configuring the Blob storage linked service to use "User Assigned Managed Identity" authentication in Azure Synapse Analytics.
+The linked service may not be visible under the **Data Hub** -> **Linked** -> **Azure Blob Storage** after configuring the blob storage linked service to use "User Assigned Managed Identity" authentication in Azure Synapse Analytics.
 
 **Workaround**: The engineering team is currently aware of this behavior and working on a fix. As an alternative, use "System Assigned Managed Identity" authentication method instead of "User Assigned Managed Identity".
 
-
 ### Failed to delete Synapse workspace & Unable to delete virtual network
 
 Deleting a Synapse workspace fails with the error message:
 
-_Failed to delete Synapse workspace '[Workspace Name]'._ <br>
-_Unable to delete virtual network. The correlationId is ********-****-****-****-************;_
+`Failed to delete Synapse workspace '[Workspace Name]'. Unable to delete virtual network. The correlationId is ********-****-****-****-************;`
 
 **Workaround**: The problem can be mitigated by retrying the delete operation. The engineering team is aware of this behavior and working on a fix.
 
-
 ## Next steps
 
-- [Synapse Studio troubleshooting](https://learn.microsoft.com/azure/synapse-analytics/troubleshoot/troubleshoot-synapse-studio)
-- [Troubleshoot serverless SQL pool in Azure Synapse Analytics](https://learn.microsoft.com/azure/synapse-analytics/sql/resources-self-help-sql-on-demand?tabs=x80070002)
-- [Best practices for serverless SQL pool in Azure Synapse Analytics](https://learn.microsoft.com/azure/synapse-analytics/sql/best-practices-serverless-sql-pool)
-- [Troubleshoot a slow query on a dedicated SQL Pool](https://learn.microsoft.com/troubleshoot/azure/synapse-analytics/dedicated-sql/troubleshoot-dsql-perf-slow-query)
+- [Synapse Studio troubleshooting](troubleshoot/troubleshoot-synapse-studio.md)
+- [Troubleshoot serverless SQL pool in Azure Synapse Analytics](sql/resources-self-help-sql-on-demand.md)
+- [Best practices for serverless SQL pool in Azure Synapse Analytics](sql/best-practices-serverless-sql-pool.md)
+- [Troubleshoot a slow query on a dedicated SQL Pool](/troubleshoot/azure/synapse-analytics/dedicated-sql/troubleshoot-dsql-perf-slow-query)

articles/synapse-analytics/sql/create-use-views.md

@@ -76,7 +76,7 @@ from openrowset(
            ) as rows
 ```
 
-Review the known issues on [Synapse serverless SQL pool self-help page](resources-self-help-sql-on-demand.md#delta-lake).
+For more information, review [Synapse serverless SQL pool self-help page](resources-self-help-sql-on-demand.md#delta-lake) and [Azure Synapse Analytics known issues](../known-issues.md).
 
 ## Partitioned views
 
@@ -117,7 +117,7 @@ The folder name in the `OPENROWSET` function (`yellow` in this example) that is
 > [!div class="mx-imgBorder"]
 >![Yellow Taxi Delta Lake folder](./media/shared/yellow-taxi-delta-lake.png)
 
-Review the known issues on [Synapse serverless SQL pool self-help page](resources-self-help-sql-on-demand.md#delta-lake).
+For more information, review [Synapse serverless SQL pool self-help page](resources-self-help-sql-on-demand.md#delta-lake) and [Azure Synapse Analytics known issues](../known-issues.md).
 
 ## JSON views
 
@@ -189,3 +189,9 @@ ORDER BY
 ## Next steps
 
 For information on how to query different file types, refer to the [Query single CSV file](query-single-csv-file.md), [Query Parquet files](query-parquet-files.md), and [Query JSON files](query-json-files.md) articles.
+
+- [What's new in Azure Synapse Analytics?](../whats-new.md). 
+- [Best practices for serverless SQL pool in Azure Synapse Analytics](best-practices-serverless-sql-pool.md)
+- [Troubleshoot serverless SQL pool in Azure Synapse Analytics](resources-self-help-sql-on-demand.md)
+- [Troubleshoot a slow query on a dedicated SQL Pool](/troubleshoot/azure/synapse-analytics/dedicated-sql/troubleshoot-dsql-perf-slow-query)
+- [Synapse Studio troubleshooting](../troubleshoot/troubleshoot-synapse-studio.md)