Removing article, fixing table, and diagram (#33591)

* A few minor changes

Fixing more things

* Update contained-availability-groups-overview.md

* Update sys-fn-hadr-backup-is-preferred-replica-transact-sql.md

The behavior change on this function leads some issues on our customer's side in one support case. We found that the change was introduced in SQL 2019 CU20 and SQL 2022 CU2 to fix another case sensitive issue. The related fix info is missing in official document for both CUs. Customer requests for the official document on this change.

fixing public PRs

added cdc errors based on conversation with jaynar

fixing date

adding the other error

rearranging errors

changing language slightly

moving link

* Update active-secondaries-backup-on-secondary-replicas-always-on-availability-groups.md

---------

Co-authored-by: Emad Al-Mousa <48997609+emad-almousa@users.noreply.github.com>
Co-authored-by: AnyiYang <47312880+AnyiYang@users.noreply.github.com>
Co-authored-by: tisun2 <62939207+tisun2@users.noreply.github.com>

Author: 4 people

.openpublishing.redirection.azure-sql.json

@@ -105,6 +105,11 @@
       "redirect_url": "/azure/azure-sql/database/high-availability-sla-local-zone-redundancy",
       "redirect_document_id": true
     },
+    {
+      "source_path_from_root": "/azure-sql/database/saas-dbpertenant-log-analytics.md",
+      "redirect_url": "/azure/azure-sql/database/monitoring-sql-database-azure-monitor",
+      "redirect_document_id": true
+    },
     {
       "source_path_from_root": "/azure-sql/managed-instance/high-availability-sla.md",
       "redirect_url": "/azure/azure-sql/managed-instance/high-availability-sla-local-zone-redundancy",

azure-sql/database/media/service-tier-hyperscale/hyperscale-architecture.png

@@ -5,7 +5,7 @@ description: Learn about the currently known issues with Azure SQL Managed Insta
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest, mathoma
-ms.date: 03/14/2025
+ms.date: 04/03/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: service-overview
 ms.topic: troubleshooting-known-issue
@@ -24,6 +24,7 @@ This article lists the currently known issues with [Azure SQL Managed Instance](
 
 | Issue | Date discovered | Status | Date resolved |
 | --- | --- | --- | --- |
+| [Interim guidance on 2024 time zone updates for Paraguay](#interim-guidance-on-2024-time-zone-updates-for-paraguay) | March 2025 | Has workaround| |
 | [Error 8992 when running DBCC CHECKDB on a SQL Server database that originated from SQL Managed Instance](#error-8992-when-running-dbcc-checkdb-on-a-sql-server-database-that-originated-from-sql-managed-instance) | March 2025 | Has workaround| |
 | [Differential backups aren't taken when an instance is linked to SQL Server](#differential-backups-arent-taken-when-an-instance-is-linked-to-sql-server) | Sept 2024 | By design | |
 | [List of long-term backups in Azure portal shows backup files for active and deleted databases with the same name](#list-of-long-term-backups-in-azure-portal-shows-backup-files-for-active-and-deleted-databases-with-the-same-name) | Mar 2024 | Has Workaround | |
@@ -70,6 +71,12 @@ This article lists the currently known issues with [Azure SQL Managed Instance](
 
 ## Has workaround
 
+### Interim guidance on 2024 time zone updates for Paraguay
+
+On October 14, 2024, the Paraguayan government announced a permanent change to the country’s time zone policy. Paraguay will remain on Daylight Saving Time (DST) year-round, effectively adopting UTC-3 as its standard time. As a result, clocks will not advance by 60 minutes at 12:00 a.m. on March 23, 2025, as previously scheduled. This change affects the Paraguay Standard Time time-zone. Microsoft has released related [Windows updates in February and March 2025](https://techcommunity.microsoft.com/blog/dstblog/paraguay-2025-time-zone-update-now-available/4386720). Azure SQL Managed Instance currently does not reflect this update. Instances using affected time zone will not reflect the changes until Azure SQL Managed Instance service absorbs the update on the OS level. 
+
+**Workaround**: If you need to alter affected time zones for your managed instances, be aware of the [limitations](timezones-overview.md#limitations) and follow the guidance from the documentation.
+
 ### Error 8992 when running DBCC CHECKDB on a SQL Server database that originated from SQL Managed Instance
 
 You may see the following error when you run the DBCC CHECKDB command on a SQL Server 2022 database after you delete an index, or a table with an index, and the database originated from Azure SQL Managed Instance, such as after restoring a backup file, or from the [Managed Instance link feature](/azure/azure-sql/managed-instance/managed-instance-link-feature-overview): 

azure-sql/database/saas-dbpertenant-log-analytics.md

@@ -149,13 +149,13 @@ Zone redundancy for SQL Managed Instance is supported in the following regions:
 | Canada Central | Germany West Central | Qatar Central | Central India |
 | Central US | Italy North | South Africa North | East Asia |
 | East US | North Europe | UAE North | Japan East |
-| East US 2 | Norway East | | Japan West |
+| East US 2 | Norway East |New Zealand North | Japan West |
 | Mexico Central | Poland Central | | Korea Central |
-| Spain Central | | New Zealand North |
-| West US 2 | Sweden Central | | Southeast Asia |
-| West US 3 | Switzerland North | | |
-| | UK South | | |
-| | West Europe | | |
+| Spain Central | Sweden Central || Southeast Asia  |
+| West US 2 | Switzerland North  | |  |
+| West US 3 | UK South  | | |
+| |West Europe  | | |
+
 
 ---
 

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

@@ -4,7 +4,7 @@ description: Learn about the time zone specifics of Azure SQL Managed Instance
 author: MladjoA
 ms.author: mlandzic
 ms.reviewer: mathoma
-ms.date: 07/13/2023
+ms.date: 04/03/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: service-overview
 ms.topic: reference
@@ -32,7 +32,7 @@ A set of supported time zones is inherited from the underlying operating system
 A list with names of the supported time zones is exposed through the [sys.time_zone_info](/sql/relational-databases/system-catalog-views/sys-time-zone-info-transact-sql) system view.
 
 > [!NOTE]
-> On August 8, 2022, the Chilean government made an official announcement about a Daylight-Saving Time (DST) [time zone change](https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/interim-guidance-on-2022-time-zone-updates-for-chile/ba-p/3598290). Starting at 12:00 a.m. Saturday, September 10, 2022, until 12:00 a.m. Saturday, April 1, 2023, the official time will advance 60 minutes. The change affects the following three time zones: **Pacific SA Standard Time**, **Easter Island Standard Time** and **Magallanes Standard Time**. Azure SQL Managed Instances using affected time zones will not reflect the changes [until Microsoft releases an OS update](https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/interim-guidance-on-2022-time-zone-updates-for-chile/ba-p/3598290) to support this and Azure SQL Managed Instance service absorbs the update on the OS level. If you need to alter affected time zones for your managed instances, please be aware of the [limitations](#limitations) and follow the guidance from the documentation.
+> On October 14, 2024, the Paraguayan government announced a permanent change to the country’s time zone policy. Paraguay will remain on Daylight Saving Time (DST) year-round, effectively adopting UTC-3 as its standard time. As a result, clocks will not advance by 60 minutes at 12:00 a.m. on March 23, 2025, as previously scheduled. This change affects the Paraguay Standard time zone. Microsoft has released related [Windows updates in February and March 2025](https://techcommunity.microsoft.com/blog/dstblog/paraguay-2025-time-zone-update-now-available/4386720). Azure SQL Managed Instance currently does not reflect this update. Instances using affected time zone will not reflect the changes until Azure SQL Managed Instance service absorbs the update on the OS level. If you need to alter affected time zones for you managed instances, please be aware of the [limitations](#limitations) and follow the guidance from the documentation. 
 
 ## Set a time zone
 

azure-sql/managed-instance/instance-zone-redundancy-configure.md

@@ -936,8 +936,6 @@
               href: database/saas-dbpertenant-provision-and-catalog.md
             - name: Monitor database performance
               href: database/saas-dbpertenant-performance-monitoring.md
-            - name: Monitor with Azure Monitor logs
-              href: database/saas-dbpertenant-log-analytics.md
             - name: Restore one tenant
               href: database/saas-dbpertenant-restore-single-tenant.md
             - name: Manage tenant schema