Merge branch 'main' of https://github.com/MicrosoftDocs/sql-docs-pr into WI-45775-Update-ASC-branding-to-MDC

Author: AlizaBernstein

.openpublishing.redirection.json

@@ -58910,6 +58910,11 @@
       "redirect_url": "/sql/ssms/menu-help/sql-server-management-studio-menu-help",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/ssms/output-window.md",
+      "redirect_url": "/sql/ssms/menu-help/options-output-window-page",
+      "redirect_document_id": true
+    },
     {
       "source_path": "docs/ssms/object/index.md",
       "redirect_url": "/sql/ssms/object/object-explorer",

azure-sql/database/active-geo-replication-configure-portal.md

@@ -39,7 +39,7 @@ To configure active geo-replication, you need a database in Azure SQL Database.
 
 Prepare your environment for the Azure CLI.
 
-[!INCLUDE [azure-cli-prepare-your-environment-no-header](../includes/azure-cli-prepare-your-environment-no-header.md)]
+[!INCLUDE [azure-cli-prepare-your-environment-no-header](~/../azure-sql/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
 ---
 

azure-sql/database/automated-backups-change-settings.md

@@ -61,7 +61,7 @@ To change the PITR backup retention period or the differential backup frequency
 
 Prepare your environment for the Azure CLI:
 
-[!INCLUDE[azure-cli-prepare-your-environment-no-header](../includes/azure-cli-prepare-your-environment-no-header.md)]
+[!INCLUDE[azure-cli-prepare-your-environment-no-header](~/../azure-sql/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
 Change the PITR backup retention and differential backup frequency for active databases by using the following example:
 

azure-sql/database/az-cli-script-samples-content-guide.md

@@ -33,7 +33,7 @@ You can configure Azure SQL Database and SQL Managed Instance by using the <a hr
 
 [!INCLUDE [quickstarts-free-trial-note](../includes/quickstarts-free-trial-note.md)]
 
-[!INCLUDE [azure-cli-prepare-your-environment.md](../includes/azure-cli-prepare-your-environment.md)]
+[!INCLUDE [azure-cli-prepare-your-environment.md](~/../azure-sql/reusable-content/azure-cli/azure-cli-prepare-your-environment.md)]
 
 ## Samples
 

azure-sql/database/azure-defender-for-sql.md

@@ -98,6 +98,6 @@ To view and manage Microsoft Defender for SQL settings:
 
 ## Next steps
 
-- Learn more about [Vulnerability Assessment](sql-vulnerability-assessment.md)
+- Learn more about [Vulnerability Assessment](/azure/defender-for-cloud/sql-azure-vulnerability-assessment-overview)
 - Learn more about [Advanced Threat Protection](threat-detection-configure.md)
-- Learn more about [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
+- Learn more about [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)

azure-sql/database/connect-query-nodejs.md

@@ -32,7 +32,7 @@ To complete this quickstart, you need:
   | Action | SQL Database | SQL Managed Instance | SQL Server on Azure VM |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
-  || [CLI](scripts/create-and-configure-database-cli.md) | [Bicep](/azure/azure-sql/managed-instance/create-bicep-quickstart) |
+  || [CLI](scripts/create-and-configure-database-cli.md) | [Bicep](../managed-instance/create-bicep-quickstart.md) |
   || [PowerShell](scripts/create-and-configure-database-powershell.md) | [PowerShell](../managed-instance/scripts/create-configure-managed-instance-powershell.md) | [PowerShell](../virtual-machines/windows/sql-vm-create-powershell-quickstart.md)
   | Configure | [Server-level IP firewall rule](firewall-create-server-level-portal-quickstart.md)| [Connectivity from a VM](../managed-instance/connect-vm-instance-configure.md)|
   |||[Connectivity from on-premises](../managed-instance/point-to-site-p2s-configure.md) | [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)

azure-sql/database/elastic-jobs-tsql-create-manage.md

@@ -1340,11 +1340,8 @@ Shows all members of all target groups.
 |**elastic_pool_name**|nvarchar(128)|Name of the Elastic pool contained in the target group. Specified only when target_type is 'SqlElasticPool'.|
 |**shard_map_name**|nvarchar(128)|Name of the shard maps contained in the target group. Specified only when target_type is 'SqlShardMap'.|
 
-## Resources
-
-- ![Topic link icon](/sql/database-engine/configure-windows/media/topic-link.gif "Topic link icon") [Transact-SQL Syntax Conventions](/sql/t-sql/language-elements/transact-sql-syntax-conventions-transact-sql)  
-
 ## Next steps
 
+- [Transact-SQL syntax conventions](/sql/t-sql/language-elements/transact-sql-syntax-conventions-transact-sql)  
 - [Create and manage Elastic Jobs using PowerShell](elastic-jobs-powershell-create.md)
 - [Authorization and Permissions](/dotnet/framework/data/adonet/sql/authorization-and-permissions-in-sql-server)

azure-sql/database/elastic-transactions-overview.md

@@ -265,9 +265,9 @@ The following limitations currently apply to elastic database transactions in *S
 * Only client-coordinated transactions from a .NET application are supported. Server-side support for T-SQL such as BEGIN DISTRIBUTED TRANSACTION is planned, but not yet available.
 * Transactions across WCF services aren't supported. For example, you have a WCF service method that executes a transaction. Enclosing the call within a transaction scope will fail as a [System.ServiceModel.ProtocolException](/dotnet/api/system.servicemodel.protocolexception).
 
-The following limitations currently apply to distributed transactions in *SQL Managed Instance*:
+The following limitations currently apply to distributed transactions (also known as elastic transactions or natively supported distributed transactions) in *SQL Managed Instance*:
 
-* Only transactions across databases in managed instances are supported. Other [X/Open XA](https://en.wikipedia.org/wiki/X/Open_XA) resource providers and databases outside of Azure SQL Managed Instance can't participate in distributed transactions. That means that distributed transactions can't stretch across on-premises SQL Server and Azure SQL Managed Instance. For distributed transactions on premises, continue to use MSDTC.
+* With this technology, only transactions across databases in managed instances are supported. For all other scenarios that may include [X/Open XA](https://en.wikipedia.org/wiki/X/Open_XA) resource providers and databases outside of Azure SQL Managed Instance you should configure [DTC for Azure SQL Managed Instance](../managed-instance/distributed-transaction-coordinator-dtc.md).
 * Transactions across WCF services aren't supported. For example, you have a WCF service method that executes a transaction. Enclosing the call within a transaction scope will fail as a [System.ServiceModel.ProtocolException](/dotnet/api/system.servicemodel.protocolexception).
 * Azure SQL Managed Instance must be part of a [Server trust group](../managed-instance/server-trust-group-overview.md) in order to participate in distributed transaction.
 * Limitations of [Server trust groups](../managed-instance/server-trust-group-overview.md) affect distributed transactions.

azure-sql/database/high-availability-sla.md

@@ -95,7 +95,7 @@ The zone-redundant version of the high availability architecture is illustrated
 - For zone redundant availability, choosing a [maintenance window](./maintenance-window.md) other than the default is currently available in [select regions](maintenance-window.md#azure-region-support).
 
 > [!IMPORTANT]  
-> For zone redundant availability, choosing a [maintenance window](/azure/azure-sql/database/maintenance-window) other than the default is currently available in [select regions](/azure/azure-sql/database/maintenance-window?view=azuresql&preserve-view=true#azure-region-support).
+> For zone redundant availability, choosing a [maintenance window](./maintenance-window.md) other than the default is currently available in [select regions](./maintenance-window.md?preserve-view=true&view=azuresql#azure-region-support).
 
 During preview, zone redundancy for SQL Managed Instance is available in the Business Critical service tier and supported in the following regions:
 
@@ -277,4 +277,4 @@ Azure SQL Database and Azure SQL Managed Instance feature a built-in high availa
 - Learn about [Service Fabric](/azure/service-fabric/service-fabric-overview)
 - Learn about [Azure Traffic Manager](/azure/traffic-manager/traffic-manager-overview)
 - Learn [How to initiate a manual failover on SQL Managed Instance](../managed-instance/user-initiated-failover.md)
-- For more options for high availability and disaster recovery, see [Business Continuity](business-continuity-high-availability-disaster-recover-hadr-overview.md)
+- For more options for high availability and disaster recovery, see [Business Continuity](business-continuity-high-availability-disaster-recover-hadr-overview.md)

azure-sql/database/hyperscale-database-create-quickstart.md

@@ -81,7 +81,7 @@ The Azure CLI code blocks in this section create a resource group, server, singl
 
 [!INCLUDE [quickstarts-free-trial-note](../includes/quickstarts-free-trial-note.md)]
 
-[!INCLUDE [azure-cli-prepare-your-environment.md](../includes/azure-cli-prepare-your-environment-h3.md)]
+[!INCLUDE [azure-cli-prepare-your-environment.md](~/../azure-sql/reusable-content/azure-cli/azure-cli-prepare-your-environment-h3.md)]
 
 [!INCLUDE [cli-launch-cloud-shell-sign-in.md](../includes/cli-launch-cloud-shell-sign-in.md)]