You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-sql/managed-instance/doc-changes-updates-known-issues.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ This article lists the currently known issues with [Azure SQL Managed Instance](
35
35
|[msdb table for manual backups doesn't preserve the username](#msdb-table-for-manual-backups-doesnt-preserve-the-username)| Nov 2022 | Resolved | Aug 2023 |
36
36
|[When using SQL Server authentication, usernames with '@' aren't supported](#when-using-sql-server-authentication-usernames-with--arent-supported)| Oct 2021 | Resolved | Feb 2022 |
37
37
|[Misleading error message on Azure portal suggesting recreation of the Service Principal](#misleading-error-message-on-azure-portal-suggesting-recreation-of-the-service-principal)| Sep 2021 || Oct 2021 |
38
-
|[Changing the connection type doesn't affect connections through the failover group endpoint](#changing-the-connection-type-doesnt-affect-connections-through-the-failover-group-endpoint)| Jan 2021 |Has Workaround ||
38
+
|[Changing the connection type doesn't affect connections through the failover group endpoint](#changing-the-connection-type-doesnt-affect-connections-through-the-failover-group-endpoint)| Jan 2021 |Resolved | Nov 2025|
39
39
|[Distributed transactions can be executed after removing SQL managed instance from Server Trust Group](#distributed-transactions-can-be-executed-after-removing-sql-managed-instance-from-server-trust-group)| Oct 2020 | Has Workaround ||
40
40
|[Can't create SQL Managed Instance with the same name as logical server previously deleted](#cant-create-sql-managed-instance-with-the-same-name-as-logical-server-previously-deleted)| Aug 2020 | Has Workaround ||
41
41
|[Service Principal can't access Microsoft Entra ID and AKV](#service-principal-cant-access-azure-ad-and-akv)| Aug 2020 | Has Workaround ||
@@ -143,12 +143,6 @@ GO
143
143
```
144
144
145
145
146
-
### Changing the connection type doesn't affect connections through the failover group endpoint
147
-
148
-
If an instance participates in a [failover group](failover-group-sql-mi.md), changing the instance's [connection type](connection-types-overview.md) doesn't take effect for the connections established through the failover group listener endpoint.
149
-
150
-
**Workaround**: Drop and recreate failover group after changing the connection type.
### Distributed transactions can be executed after removing SQL managed instance from Server Trust Group
@@ -264,6 +258,12 @@ Error logs that are available in SQL Managed Instance aren't persisted, and thei
264
258
265
259
## Resolved
266
260
261
+
### Changing the connection type doesn't affect connections through the failover group endpoint
262
+
263
+
**(Resolved in November 2025)**
264
+
265
+
If an instance participates in a [failover group](failover-group-sql-mi.md), changing the instance's [connection type](connection-types-overview.md) doesn't take effect for the connections established through the failover group listener endpoint.
266
+
267
267
### Temporary instance inaccessibility using the failover group listener during scaling operation
0 commit comments