Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into bfdnote

duongau · duongau · commit ee4218e829c4 · 2022-03-15T11:11:29.000-07:00
diff --git a/articles/azure-sql/database/active-directory-interactive-connect-azure-sql-db.md b/articles/azure-sql/database/active-directory-interactive-connect-azure-sql-db.md
@@ -120,7 +120,6 @@ For the C# program to successfully run, you need to assign proper values to stat
 | Initial_DatabaseName | "myDatabase" | **SQL servers** > **SQL databases** |
 | ClientApplicationID | "a94f9c62-97fe-4d19-b06d-111111111111" | **Azure Active Directory** > **App registrations** > **Search by name** > **Application ID** |
 | RedirectUri | new Uri("https://mywebserver.com/") | **Azure Active Directory** > **App registrations** > **Search by name** > *[Your-App-registration]* > **Settings** > **RedirectURIs**<br /><br />For this article, any valid value is fine for RedirectUri, because it isn't used here. |
-| &nbsp; | &nbsp; | &nbsp; |
 
 ## Verify with SQL Server Management Studio
 
diff --git a/articles/azure-sql/database/manage-data-after-migrating-to-database.md b/articles/azure-sql/database/manage-data-after-migrating-to-database.md
@@ -111,7 +111,7 @@ Azure AD supports [Azure AD Multi-Factor Authentication](authentication-mfa-ssms
 |Are logged in to Windows using your Azure AD credentials from a federated domain|Use [Azure AD integrated authentication](authentication-aad-configure.md).|
 |Are logged in to Windows using credentials from a domain not federated with Azure|Use [Azure AD integrated authentication](authentication-aad-configure.md).|
 |Have middle-tier services which need to connect to SQL Database or Azure Synapse Analytics|Use [Azure AD integrated authentication](authentication-aad-configure.md).|
-|||
+
 
 ### How do I limit or control connectivity access to my database
 
diff --git a/articles/azure-sql/database/migrate-dtu-to-vcore.md b/articles/azure-sql/database/migrate-dtu-to-vcore.md
@@ -178,7 +178,7 @@ The following table provides guidance for specific migration scenarios:
 |General purpose|Premium|Upgrade|Must migrate secondary first|
 |Business critical|General purpose|Downgrade|Must migrate primary first|
 |General purpose|Business critical|Upgrade|Must migrate secondary first|
-||||
+
 
 ## Migrate failover groups
 
diff --git a/articles/azure-sql/database/powershell-script-content-guide.md b/articles/azure-sql/database/powershell-script-content-guide.md
@@ -51,7 +51,7 @@ The following table includes links to sample Azure PowerShell scripts for Azure
 | [Sync data between databases](scripts/sql-data-sync-sync-data-between-sql-databases.md?toc=%2fpowershell%2fmodule%2ftoc.json) | This PowerShell script configures Data Sync to sync between multiple databases in Azure SQL Database. |
 | [Sync data between SQL Database and SQL Server on-premises](scripts/sql-data-sync-sync-data-between-azure-onprem.md?toc=%2fpowershell%2fmodule%2ftoc.json) | This PowerShell script configures Data Sync to sync between a database in Azure SQL Database and a SQL Server on-premises database. |
 | [Update the SQL Data Sync sync schema](scripts/update-sync-schema-in-sync-group.md?toc=%2fpowershell%2fmodule%2ftoc.json) | This PowerShell script adds or removes items from the Data Sync sync schema. |
-|||
+
 
 Learn more about the [Single-database Azure PowerShell API](single-database-manage.md#powershell). 
 
@@ -69,7 +69,7 @@ The following table includes links to sample Azure PowerShell scripts for Azure
 | [Manage transparent data encryption in a managed instance using your own key from Azure Key Vault](../managed-instance/scripts/transparent-data-encryption-byok-powershell.md?toc=%2fpowershell%2fmodule%2ftoc.json)| This PowerShell script configures transparent data encryption in a Bring Your Own Key scenario for Azure SQL Managed Instance, using a key from Azure Key Vault.|
 |**Configure a failover group**||
 | [Configure a failover group for a managed instance](../managed-instance/scripts/add-to-failover-group-powershell.md?toc=%2fpowershell%2fmodule%2ftoc.json) | This PowerShell script creates two managed instances, adds them to a failover group, and then tests failover from the primary managed instance to the secondary managed instance. |
-|||
+
 
 Learn more about [PowerShell cmdlets for Azure SQL Managed Instance](../managed-instance/api-references-create-manage-instance.md#powershell-create-and-configure-managed-instances).
 
diff --git a/articles/azure-sql/database/purchasing-models.md b/articles/azure-sql/database/purchasing-models.md
@@ -34,7 +34,7 @@ The following table and chart compares and contrasts the vCore-based and the DTU
 |---|---|---|
 |DTU-based|This model is based on a bundled measure of compute, storage, and I/O resources. Compute sizes are expressed in DTUs for single databases and in elastic database transaction units (eDTUs) for elastic pools. For more information about DTUs and eDTUs, see [What are DTUs and eDTUs?](purchasing-models.md#dtu-purchasing-model).|Customers who want simple, preconfigured resource options|
 |vCore-based|This model allows you to independently choose compute and storage resources. The vCore-based purchasing model also allows you to use [Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/) for SQL Server to save costs.|Customers who value flexibility, control, and transparency|
-||||  
+
 
 :::image type="content" source="./media/purchasing-models/pricing-model.png" alt-text="Pricing model comparison" lightbox="./media/purchasing-models/pricing-model.png":::
 
diff --git a/articles/azure-sql/database/replication-to-sql-database.md b/articles/azure-sql/database/replication-to-sql-database.md
@@ -54,7 +54,6 @@ There are different [types of replication](/sql/relational-databases/replication
 | [**Peer-to-peer**](/sql/relational-databases/replication/transactional/peer-to-peer-transactional-replication) | No | No|
 | [**Bidirectional**](/sql/relational-databases/replication/transactional/bidirectional-transactional-replication) | No | Yes|
 | [**Updatable subscriptions**](/sql/relational-databases/replication/transactional/updatable-subscriptions-for-transactional-replication) | No | No|
-| &nbsp; | &nbsp; | &nbsp; |
 
   
 ## Remarks
diff --git a/articles/azure-sql/database/resource-limits-dtu-elastic-pools.md b/articles/azure-sql/database/resource-limits-dtu-elastic-pools.md
@@ -58,7 +58,7 @@ For the same number of DTUs, resources provided to an elastic pool may exceed th
 | Min DTU per database choices | 0, 5 | 0, 5 | 0, 5 | 0, 5 | 0, 5 | 0, 5 | 0, 5 | 0, 5 |
 | Max DTU per database choices | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
 | Max storage per database (GB) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
-||||||||
+
 
 <sup>1</sup> See [Resource management in dense elastic pools](elastic-pool-resource-management.md) for additional considerations.
 
@@ -77,7 +77,7 @@ For the same number of DTUs, resources provided to an elastic pool may exceed th
 | Min DTU per database choices | 0, 10, 20, 50 | 0, 10, 20, 50, 100 | 0, 10, 20, 50, 100, 200 | 0, 10, 20, 50, 100, 200, 300 | 0, 10, 20, 50, 100, 200, 300, 400 | 0, 10, 20, 50, 100, 200, 300, 400, 800 |
 | Max DTU per database choices | 10, 20, 50 | 10, 20, 50, 100 | 10, 20, 50, 100, 200 | 10, 20, 50, 100, 200, 300 | 10, 20, 50, 100, 200, 300, 400 | 10, 20, 50, 100, 200, 300, 400, 800 |
 | Max storage per database (GB) | 1024 | 1024 | 1024 | 1024 | 1024 | 1024 |
-||||||||
+
 
 <sup>1</sup> See [SQL Database pricing options](https://azure.microsoft.com/pricing/details/sql-database/elastic/) for details on additional cost incurred due to any extra storage provisioned.
 
@@ -98,7 +98,7 @@ For the same number of DTUs, resources provided to an elastic pool may exceed th
 | Min DTU per database choices | 0, 10, 20, 50, 100, 200, 300, 400, 800, 1200 | 0, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600 | 0, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000 | 0, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500 | 0, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500, 3000 |
 | Max DTU per database choices | 10, 20, 50, 100, 200, 300, 400, 800, 1200 | 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600 | 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000 | 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500 | 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500, 3000 |
 | Max storage per database (GB) | 1024 | 1536 | 1792 | 2304 | 2816 |
-|||||||
+
 
 <sup>1</sup> See [SQL Database pricing options](https://azure.microsoft.com/pricing/details/sql-database/elastic/) for details on additional cost incurred due to any extra storage provisioned.
 
@@ -119,7 +119,7 @@ For the same number of DTUs, resources provided to an elastic pool may exceed th
 | Min eDTUs per database | 0, 25, 50, 75, 125 | 0, 25, 50, 75, 125, 250 | 0, 25, 50, 75, 125, 250, 500 | 0, 25, 50, 75, 125, 250, 500, 1000 | 0, 25, 50, 75, 125, 250, 500, 1000|
 | Max eDTUs per database | 25, 50, 75, 125 | 25, 50, 75, 125, 250 | 25, 50, 75, 125, 250, 500 | 25, 50, 75, 125, 250, 500, 1000 | 25, 50, 75, 125, 250, 500, 1000|
 | Max storage per database (GB) | 1024 | 1024 | 1024 | 1024 | 1536 |
-|||||||
+
 
 <sup>1</sup> See [SQL Database pricing options](https://azure.microsoft.com/pricing/details/sql-database/elastic/) for details on additional cost incurred due to any extra storage provisioned.
 
@@ -140,7 +140,7 @@ For the same number of DTUs, resources provided to an elastic pool may exceed th
 | Min DTU per database choices | 0, 25, 50, 75, 125, 250, 500, 1000, 1750 | 0, 25, 50, 75, 125, 250, 500, 1000, 1750 | 0, 25, 50, 75, 125, 250, 500, 1000, 1750 | 0, 25, 50, 75, 125, 250, 500, 1000, 1750 | 0, 25, 50, 75, 125, 250, 500, 1000, 1750, 4000 |
 | Max DTU per database choices | 25, 50, 75, 125, 250, 500, 1000, 1750 | 25, 50, 75, 125, 250, 500, 1000, 1750 | 25, 50, 75, 125, 250, 500, 1000, 1750 | 25, 50, 75, 125, 250, 500, 1000, 1750 | 25, 50, 75, 125, 250, 500, 1000, 1750, 4000 |
 | Max storage per database (GB) | 2048 | 2560 | 3072 | 3584 | 4096 |
-|||||||
+
 
 <sup>1</sup> See [SQL Database pricing options](https://azure.microsoft.com/pricing/details/sql-database/elastic/) for details on additional cost incurred due to any extra storage provisioned.
 
@@ -169,7 +169,7 @@ The following table describes per database properties for pooled databases.
 | Max DTUs per database |The maximum number of DTUs that any database in the pool may use, if available based on utilization by other databases in the pool. Max DTUs per database is not a resource guarantee for a database. If the workload in each database does not need all available pool resources to perform adequately, consider setting max DTUs per database to prevent a single database from monopolizing pool resources. Some degree of over-committing is expected since the pool generally assumes hot and cold usage patterns for databases, where all databases are not simultaneously peaking. |
 | Min DTUs per database |The minimum number of DTUs reserved for any database in the pool. Consider setting a min DTUs per database when you want to guarantee resource availability for each database regardless of resource consumption by other databases in the pool. The min DTUs per database may be set to 0, and is also the default value. This property is set to anywhere between 0 and the average DTUs utilization per database.|
 | Max storage per database |The maximum database size set by the user for a database in a pool. Pooled databases share allocated pool storage, so the size a database can reach is limited to the smaller of remaining pool storage and maximum database size. Maximum database size refers to the maximum size of the data files and does not include the space used by the log file. |
-|||
+
 
 > [!IMPORTANT]
 > Because resources in an elastic pool are finite, setting min DTUs per database to a value greater than 0 implicitly limits resource utilization by each database. If, at a point in time, most databases in a pool are idle, resources reserved to satisfy the min DTUs guarantee are not available to databases active at that point in time.
@@ -197,7 +197,7 @@ The following table lists tempdb sizes for single databases in Azure SQL Databas
 |Standard Elastic Pools (1200 eDTU)|32|10|320|
 |Standard Elastic Pools (1600-3000 eDTU)|32|12|384|
 |Premium Elastic Pools (all DTU configurations)|13.9|12|166.7|
-||||
+
 
 ## Next steps
 
diff --git a/articles/azure-sql/database/resource-limits-vcore-elastic-pools.md b/articles/azure-sql/database/resource-limits-vcore-elastic-pools.md
@@ -564,7 +564,7 @@ The following table describes per database properties for pooled databases.
 | Max vCores per database |The maximum number of vCores that any database in the pool may use, if available based on utilization by other databases in the pool. Max vCores per database is not a resource guarantee for a database. If the workload in each database does not need all available pool resources to perform adequately, consider setting max vCores per database to prevent a single database from monopolizing pool resources. Some degree of over-committing is expected since the pool generally assumes hot and cold usage patterns for databases, where all databases are not simultaneously peaking. |
 | Min vCores per database |The minimum number of vCores reserved for any database in the pool. Consider setting a min vCores per database when you want to guarantee resource availability for each database regardless of resource consumption by other databases in the pool. The min vCores per database may be set to 0, and is also the default value. This property is set to anywhere between 0 and the average vCores utilization per database.|
 | Max storage per database |The maximum database size set by the user for a database in a pool. Pooled databases share allocated pool storage, so the size a database can reach is limited to the smaller of remaining pool storage and maximum database size. Maximum database size refers to the maximum size of the data files and does not include the space used by the log file. |
-|||
+
 
 > [!IMPORTANT]
 > Because resources in an elastic pool are finite, setting min vCores per database to a value greater than 0 implicitly limits resource utilization by each database. If, at a point in time, most databases in a pool are idle, resources reserved to satisfy the min vCores guarantee are not available to databases active at that point in time.
diff --git a/articles/azure-sql/database/saas-dbpertenant-get-started-deploy.md b/articles/azure-sql/database/saas-dbpertenant-get-started-deploy.md
@@ -128,7 +128,7 @@ The Wingtip application uses [*Azure Traffic Manager*](../../traffic-manager/tr
     | .*&lt;user&gt;* | *af1* in the example. |
     | .trafficmanager.net/ | Traffic Manager, base URL. |
     | fabrikamjazzclub | Identifies the tenant named Fabrikam Jazz Club. |
-    | &nbsp; | &nbsp; |
+
 
 - The tenant name is parsed from the URL by the events app.
 - The tenant name is used to create a key.
diff --git a/articles/azure-sql/database/saas-tenancy-app-design-patterns.md b/articles/azure-sql/database/saas-tenancy-app-design-patterns.md
@@ -185,7 +185,7 @@ The following table summarizes the differences between the main tenancy models.
 | Performance monitoring and management | Per-tenant only | Aggregate + per-tenant | Aggregate; although is per-tenant only for singles. |
 | Development complexity | Low | Low | Medium; due to sharding. |
 | Operational complexity | Low-High. Individually simple, complex at scale. | Low-Medium. Patterns address complexity at scale. | Low-High. Individual tenant management is complex. |
-| &nbsp; ||||
+
 
 ## Next steps
 
diff --git a/articles/azure-sql/database/sql-vulnerability-assessment.md b/articles/azure-sql/database/sql-vulnerability-assessment.md
@@ -190,7 +190,7 @@ You can use Azure PowerShell cmdlets to programmatically manage your vulnerabili
 | [Update-AzSqlDatabaseVulnerabilityAssessmentSetting](/powershell/module/az.sql/Update-azSqlDatabaseVulnerabilityAssessmentSetting) | Updates the vulnerability assessment settings of a database. |
 | [Update-AzSqlInstanceDatabaseVulnerabilityAssessmentSetting](/powershell/module/az.sql/Update-AzSqlInstanceDatabaseVulnerabilityAssessmentSetting) | Updates the vulnerability assessment settings of a managed database. |
 | [Update-AzSqlInstanceVulnerabilityAssessmentSetting](/powershell/module/az.sql/Update-AzSqlInstanceVulnerabilityAssessmentSetting) | Updates the vulnerability assessment settings of a managed instance. |
-| &nbsp; | &nbsp; |
+
 
 For a script example, see [Azure SQL vulnerability assessment PowerShell support](/archive/blogs/sqlsecurity/azure-sql-vulnerability-assessment-now-with-powershell-support).
 
@@ -212,7 +212,6 @@ You can use Azure CLI commands to programmatically manage your vulnerability ass
 | [az security va sql results show](/cli/azure/security/va/sql/results#az_security_va_sql_results_show) | View Sql Vulnerability Assessment scan results. |
 | [az security va sql scans list](/cli/azure/security/va/sql/scans#az_security_va_sql_scans_list) | List all Sql Vulnerability Assessment scan summaries. |
 | [az security va sql scans show](/cli/azure/security/va/sql/scans#az_security_va_sql_scans_show) | View Sql Vulnerability Assessment scan summaries. |
-| &nbsp; | &nbsp; |
 
 ---
 
diff --git a/articles/azure-sql/managed-instance/auto-failover-group-configure-sql-mi.md b/articles/azure-sql/managed-instance/auto-failover-group-configure-sql-mi.md
@@ -72,7 +72,7 @@ Create the primary virtual network gateway using the Azure portal.
     | **Virtual network**| Select the virtual network for your secondary managed instance. |
     | **Public IP address**| Select **Create new**. |
     | **Public IP address name**| Enter a name for your IP address. |
-    | &nbsp; | &nbsp; |
+
 
 1. Leave the other values as default, and then select **Review + create** to review the settings for your virtual network gateway.
 
@@ -134,7 +134,7 @@ The following table shows the values necessary for the gateway for the secondary
    | **Virtual network**| Select the virtual network that was created in section 2, such as `vnet-sql-mi-secondary`. |
    | **Public IP address**| Select **Create new**. |
    | **Public IP address name**| Enter a name for your IP address, such as `secondary-gateway-IP`. |
-   | &nbsp; | &nbsp; |
+
 
    ![Secondary gateway settings](./media/auto-failover-group-configure-sql-mi/settings-for-secondary-gateway.png)
 
diff --git a/articles/azure-sql/managed-instance/failover-group-add-instance-tutorial.md b/articles/azure-sql/managed-instance/failover-group-add-instance-tutorial.md
@@ -444,7 +444,7 @@ To create a virtual network, follow these steps:
     | **Region** | The location where you will deploy your secondary managed instance. |
     | **Subnet** | The name for your subnet. `default` is provided for you by default. |
     | **Address range**| The address range for your subnet. This must be different than the subnet address range used by the virtual network of your primary managed instance, such as `10.128.0.0/24`.  |
-    | &nbsp; | &nbsp; |
+
 
     ![Secondary virtual network values](./media/failover-group-add-instance-tutorial/secondary-virtual-network.png)
 
@@ -483,7 +483,7 @@ Create the secondary managed instance using the Azure portal.
     | **Region**| The location for your secondary managed instance.  |
     | **SQL Managed Instance admin login** | The login you want to use for your new secondary managed instance, such as `azureuser`. |
     | **Password** | A complex password that will be used by the admin login for the new secondary managed instance.  |
-    | &nbsp; | &nbsp; |
+
 
 1. Under the **Networking** tab, for the **Virtual Network**, select the virtual network you created for the secondary managed instance from the drop-down.
 
@@ -778,7 +778,7 @@ Create the gateway for the virtual network of your primary managed instance usin
     | **Virtual network**| Select the virtual network that was created in section 2, such as `vnet-sql-mi-primary`. |
     | **Public IP address**| Select **Create new**. |
     | **Public IP address name**| Enter a name for your IP address, such as `primary-gateway-IP`. |
-    | &nbsp; | &nbsp; |
+
 
 1. Leave the other values as default, and then select **Review + create** to review the settings for your virtual network gateway.
 
@@ -859,7 +859,7 @@ Using the Azure portal, repeat the steps in the previous section to create the v
    | **Virtual network**| Select the virtual network for the secondary managed instance, such as `vnet-sql-mi-secondary`. |
    | **Public IP address**| Select **Create new**. |
    | **Public IP address name**| Enter a name for your IP address, such as `secondary-gateway-IP`. |
-   | &nbsp; | &nbsp; |
+
 
    ![Secondary gateway settings](./media/failover-group-add-instance-tutorial/settings-for-secondary-gateway.png)
 
diff --git a/articles/azure-sql/managed-instance/replication-transactional-overview.md b/articles/azure-sql/managed-instance/replication-transactional-overview.md
diff --git a/articles/azure-sql/virtual-machines/windows/availability-group-clusterless-workgroup-configure.md b/articles/azure-sql/virtual-machines/windows/availability-group-clusterless-workgroup-configure.md
diff --git a/articles/azure-sql/virtual-machines/windows/availability-group-quickstart-template-configure.md b/articles/azure-sql/virtual-machines/windows/availability-group-quickstart-template-configure.md
diff --git a/articles/azure-sql/virtual-machines/windows/doc-changes-updates-release-notes-whats-new.md b/articles/azure-sql/virtual-machines/windows/doc-changes-updates-release-notes-whats-new.md
diff --git a/articles/azure-sql/virtual-machines/windows/sql-agent-extension-manually-register-vms-bulk.md b/articles/azure-sql/virtual-machines/windows/sql-agent-extension-manually-register-vms-bulk.md
