Merge pull request #110562 from CarlRabeler/contextualtoc

links

Author: PRMerger6

articles/sql-database/sql-database-vnet-service-endpoint-rule-overview.md

@@ -58,6 +58,7 @@ You have the option of using [role-based access control (RBAC)][rbac-what-is-813
 
 > [!NOTE]
 > In some cases the Azure SQL Database and the VNet-subnet are in different subscriptions. In these cases you must ensure the following configurations:
+>
 > - Both subscriptions must be in the same Azure Active Directory tenant.
 > - The user has the required permissions to initiate operations, such as enabling service endpoints and adding a VNet-subnet to the given Server.
 > - Both subscriptions must have the Microsoft.Sql provider registered.
@@ -128,7 +129,7 @@ PolyBase is commonly used to load data into Azure SQL Data Warehouse from Azure
    > [!NOTE]
    > - If you have a general-purpose v1 or blob storage account, you must **first upgrade to v2** using this [guide](https://docs.microsoft.com/azure/storage/common/storage-account-upgrade).
    > - For known issues with Azure Data Lake Storage Gen2, please refer to this [guide](https://docs.microsoft.com/azure/storage/data-lake-storage/known-issues).
-    
+
 1. Under your storage account, navigate to **Access Control (IAM)**, and click **Add role assignment**. Assign **Storage Blob Data Contributor** RBAC role to your Azure SQL Server hosting your Azure SQL Data Warehouse which you've registered with Azure Active Directory (AAD) as in step#1.
 
    > [!NOTE]
@@ -258,6 +259,7 @@ You must already have a subnet that is tagged with the particular Virtual Networ
 
 > [!NOTE]
 > The following statuses or states apply to the rules:
+>
 > - **Ready:** Indicates that the operation that you initiated has Succeeded.
 > - **Failed:** Indicates that the operation that you initiated has Failed.
 > - **Deleted:** Only applies to the Delete operation, and indicates that the rule has been deleted and no longer applies.

articles/synapse-analytics/sql/overview-features.md

@@ -29,7 +29,7 @@ SQL pools and SQL on-demand capabilities enable you to use different database ob
 | Tables | [Yes](https://docs.microsoft.com/sql/t-sql/statements/create-table-azure-sql-data-warehouse) | No, SQL on-demand capability can query only external data placed on [Azure Storage](#storage-options) |
 | Views | [Yes](https://docs.microsoft.com/sql/t-sql/statements/create-view-transact-sql). Views can use [query language elements](#query-language) that are available in SQL pool. | [Yes](https://docs.microsoft.com/sql/t-sql/statements/create-view-transact-sql). Views can use [query language elements](#query-language) that are available in SQL on-demand. |
 | Schemas | [Yes](https://docs.microsoft.com/sql/t-sql/statements/create-schema-transact-sql) | [Yes](https://docs.microsoft.com/sql/t-sql/statements/create-schema-transact-sql) |
-| Temporary tables | [Yes](https://docs.microsoft.com/azure/sql-data-warehouse/sql-data-warehouse-tables-temporary) | No |
+| Temporary tables | [Yes](/sql-data-warehouse/sql-data-warehouse-tables-temporary.md) | No |
 | Procedures | [Yes](https://docs.microsoft.com/sql/t-sql/statements/create-procedure-transact-sql) | No |
 | Functions | [Yes](https://docs.microsoft.com/sql/t-sql/statements/create-function-sql-data-warehouse) | No |
 | Triggers | No | No |
@@ -73,7 +73,7 @@ SQL pools and SQL on-demand enable you to use built-in security features to secu
 | Storage AAD passthrough authentication | Yes, using `User Identity` credential | Yes, using `User Identity` credential |
 | Storage SAS token authentication | Yes, using [DATABASE SCOPED CREDENTIAL](https://docs.microsoft.com/sql/t-sql/statements/create-database-scoped-credential-transact-sql?view=sql-server-ver15) in [EXTERNAL DATA SOURCE](https://docs.microsoft.com/sql/t-sql/statements/create-external-data-source-transact-sql?view=azure-sqldw-latest) | Yes, using [DATABASE SCOPED CREDENTIAL](https://docs.microsoft.com/sql/t-sql/statements/create-database-scoped-credential-transact-sql?view=sql-server-ver15) in [EXTERNAL DATA SOURCE](https://docs.microsoft.com/sql/t-sql/statements/create-external-data-source-transact-sql?view=azure-sqldw-latest) or instance-level [CREDENTIAL](https://docs.microsoft.com/sql/t-sql/statements/create-credential-transact-sql?view=sql-server-ver15). |
 | Storage Access Key authentication | Yes, using [DATABASE SCOPED CREDENTIAL](https://docs.microsoft.com/sql/t-sql/statements/create-database-scoped-credential-transact-sql?view=sql-server-ver15) in [EXTERNAL DATA SOURCE](https://docs.microsoft.com/sql/t-sql/statements/create-external-data-source-transact-sql?view=azure-sqldw-latest) | No. |
-| Storage Managed Identity authentication | Yes, using [Managed Service Identity Credential](https://docs.microsoft.com/azure/sql-database/sql-database-vnet-service-endpoint-rule-overview?toc=/azure/sql-data-warehouse/toc.json#azure-sql-data-warehouse-polybase) | Yes, using `Managed Identity` credential. |
+| Storage Managed Identity authentication | Yes, using [Managed Service Identity Credential](../../sql-database/sql-database-vnet-service-endpoint-rule-overview.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json&view=azure-sqldw-latest) | Yes, using `Managed Identity` credential. |
 | Storage Application identity authentication | [Yes](https://docs.microsoft.com/sql/t-sql/statements/create-external-data-source-transact-sql?view=azure-sqldw-latest) | No |
 | Permissions - Object-level | Yes, including ability to GRANT, DENY, and REVOKE permissions to users | Yes, including ability to GRANT, DENY, and REVOKE permissions to users/logins on the system objects that are supported |
 | Permissions - Schema-level | Yes, including ability to GRANT, DENY, and REVOKE permissions to users/logins on the schema | Yes, including ability to GRANT, DENY, and REVOKE permissions to users/logins on the schema |