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

Author: markingmyname

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/service-tier-hyperscale-replicas.md

@@ -201,11 +201,11 @@ Geo-replication for Hyperscale database has following current limitations:
 
 - Only one geo-replica can be created (in the same or different region).
 - Point in time restore of the geo-replica is not supported.
-- Secondary of a secondary (also known as "geo-replica chaining") is not supported.
+- Creating geo-replica of a geo-replica (also known as "geo-replica chaining") is not supported.
 
 ## Next steps
 
 - [Hyperscale service tier](service-tier-hyperscale.md)
 - [Active geo-replication](active-geo-replication-overview.md)
 - [Configure Security to allow isolated access to Azure SQL Database Hyperscale Named Replicas](hyperscale-named-replica-security-configure.md)
-- [Azure SQL Database Hyperscale named replicas FAQ](service-tier-hyperscale-named-replicas-faq.yml)
+- [Azure SQL Database Hyperscale named replicas FAQ](service-tier-hyperscale-named-replicas-faq.yml)

azure-sql/managed-instance/auto-failover-group-sql-mi.md

@@ -1,10 +1,10 @@
 ---
 title: Auto-failover groups overview & best practices
 description: Auto-failover groups let you manage geo-replication and automatic / coordinated failover of all user databases on a managed instance in Azure SQL Managed Instance.
-author: MladjoA
-ms.author: mlandzic
+author: MilanMSFT
+ms.author: mlazic
 ms.reviewer: mathoma
-ms.date: 09/29/2022
+ms.date: 12/28/2022
 ms.service: sql-managed-instance
 ms.subservice: high-availability
 ms.topic: conceptual
@@ -262,7 +262,9 @@ Be aware of the following limitations:
 - Failover groups can't be created between two instances in the same Azure region.
 - Failover groups can't be renamed. You will need to delete the group and re-create it with a different name.
 - A failover group contains exactly two managed instances. Adding additional instances to the failover group is unsupported. 
-- An instance can participate only in one failover group at any moment. 
+- An instance can participate only in one failover group at any moment.
+- A failover group can't be created between two instances belonging to different Azure tenants.
+- A failover group between two instances belonging to different Azure subscriptions can't be created using Azure portal or Azure CLI. Use Azure PowerShell or REST API instead to create such a failover group. Once created, cross-subscription failover group is regularly visible in Azure portal and all subsequent operations including failovers can be inititiated from Azure portal or Azure CLI. 
 - Database rename isn't supported for databases in failover group. You will need to temporarily delete failover group to be able to rename a database.
 - System databases aren't replicated to the secondary instance in a failover group. Therefore, scenarios that depend on objects from the system databases such as Server Logins and Agent jobs, require objects to be manually created on the secondary instances and also manually kept in sync after any changes made on primary instance. The only exception is Service master Key (SMK) for SQL Managed Instance that is replicated automatically to secondary instance during creation of failover group. Any subsequent changes of SMK on the primary instance however will not be replicated to secondary instance. To learn more, see how to [Enable scenarios dependent on objects from the system databases](#enable-scenarios-dependent-on-objects-from-the-system-databases).
 - Failover groups can't be created between instances if any of them are in an instance pool.

azure-sql/managed-instance/doc-changes-updates-known-issues.md

@@ -20,6 +20,7 @@ This article lists the currently known issues with [Azure SQL Managed Instance](
 
 |Issue  |Date discovered  |Status  |Date resolved  |
 |---------|---------|---------|---------|
+|[Increased number of system logins used for Transactional Replication](#increased-number-of-system-logins-used-for-transactional-replication)|Dec 2022|No resolution||
 |[msdb table for manual backups does not preserve the username](#msdb-table-for-manual-backups-does-not-preserve-the-username)|Nov 2022|No resolution||
 |[Interim guidance on 2022 time zone updates for Chile](#interim-guidance-on-2022-time-zone-updates-for-chile)|Aug 2022|Has Workaround||
 |[Querying external table fails with 'not supported' error message](#querying-external-table-fails-with-not-supported-error-message)|Jan 2022|Resolved|Sep 2022|
@@ -276,6 +277,10 @@ using (var scope = new TransactionScope())
 
 ## No resolution
 
+### Increased number of system logins used for Transactional Replication
+
+Azure SQL Managed Instance service is creating system login for purposes of Transactional Replication. This login can be found in SSMS (in Object explorer in Security, Logins section) or in system view sys.syslogins. Login name format looks like 'DBxCy\WF-abcde01234QWERT' and login has public server role. Under certain conditions, this login is recreated, and due to a fault in the system previous login isn't deleted. This may lead to increased number of logins. These logins don't represent a security threat. They can be safely ignored. These logins shouldn't be deleted because at least one of them is being used for Transactional Replication.
+
 ### msdb table for manual backups does not preserve the username
 
 We have recently introduced support for auto backups in msdb. Doing so, we removed accidentaly the username from the manual backups. The fix is ready and it will be deployed with the next release.

azure-sql/managed-instance/point-in-time-restore.md

@@ -17,7 +17,7 @@ ms.custom: devx-track-azurepowershell
 Use point-in-time restore (PITR) to create a database as a copy of another database from some time in the past. This article describes how to do a point-in-time restore of a database in Azure SQL Managed Instance.
 
 > [!NOTE]
-> The [Create or Update v02.01.2022](/rest/api/sql/2022-02-01-preview/managed-databases/create-or-update) is being deprecated. Starting January 2022, use the [Create or Update v5.0.2022](/rest/api/sql/2022-05-01-preview/managed-databases/create-or-update) replacement API call for all database restore operations. 
+> The [Create or Update v02.01.2022](/rest/api/sql/2022-02-01-preview/managed-databases/create-or-update) has been deprecated. Starting in January 2023, use the replacement [Create or Update v5.0.2022](/rest/api/sql/2022-05-01-preview/managed-databases/create-or-update) API call for all database restore operations. 
 
 ## Overview
 

azure-sql/managed-instance/transact-sql-tsql-differences-sql-server.md

@@ -350,11 +350,8 @@ Undocumented DBCC statements that are enabled in SQL Server aren't supported in
 
 ### Distributed transactions
 
-Partial support for [distributed transactions](../database/elastic-transactions-overview.md) is generally available. Distributed transactions are supported under following conditions (all of them must be met):
-* all transaction participants are Azure SQL Managed Instances that are part of the [Server trust group](./server-trust-group-overview.md).
-* transactions are initiated either from .NET (TransactionScope class) or Transact-SQL.
-
-Azure SQL Managed Instance currently does not support other scenarios that are regularly supported by MSDTC on-premises or in Azure Virtual Machines.
+[T-SQL and .NET based distributed transactions across managed instances](../database/elastic-transactions-overview.md#transactions-for-sql-managed-instance) are generally available.
+Additional scenarios, such as XA transactions, distributed transactions between managed instances and other participants and more, are supported with [DTC for Azure SQL Managed Instance](./distributed-transaction-coordinator-dtc.md), which is available in public preview.
 
 ### Extended Events
 
@@ -391,7 +388,6 @@ For more information, see [FILESTREAM](/sql/relational-databases/blob/filestream
 [Linked servers](/sql/relational-databases/linked-servers/linked-servers-database-engine) in SQL Managed Instance support a limited number of targets:
 
 - Supported targets are SQL Managed Instance, SQL Database, Azure Synapse SQL [serverless](https://devblogs.microsoft.com/azure-sql/linked-server-to-synapse-sql-to-implement-polybase-like-scenarios-in-managed-instance/) and dedicated pools, and SQL Server instances. 
-- Distributed writable transactions are possible only among SQL Managed Instances. For more information, see [Distributed Transactions](../database/elastic-transactions-overview.md). However, MS DTC is not supported.
 - Targets that aren't supported are files, Analysis Services, and other RDBMS. Try to use native CSV import from Azure Blob Storage using `BULK INSERT` or `OPENROWSET` as an alternative for file import, or load files using a [serverless SQL pool in Azure Synapse Analytics](https://devblogs.microsoft.com/azure-sql/linked-server-to-synapse-sql-to-implement-polybase-like-scenarios-in-managed-instance/).
 
 Operations: