Adding ZR note

Author: MashaMSFT

azure-sql/managed-instance/high-availability-sla-local-zone-redundancy.md

@@ -81,6 +81,8 @@ Whenever the database engine or the operating system is upgraded, or a failure i
 
 Next-gen General Purpose is an architectural upgrade to the existing General Purpose service tier that uses an upgraded remote storage layer that stores instance data and log files on managed disks instead of page blobs and maintains it locally.
 
+Zone redundancy isn't available for the Next-gen General Purpose service tier upgrade.
+
 ### Business Critical service tier
 
 The Business Critical service tier uses the local storage availability model, which integrates compute resources (database engine process) and storage (locally attached SSD) on a single node. Availability is achieved by replicating both compute and storage to additional nodes.
@@ -99,7 +101,7 @@ Zone-redundant availability is based on placing replicas across three Azure avai
 
 By default, the cluster of nodes for the local storage availability model is created in the same datacenter. With the introduction of [Azure Availability Zones](/azure/reliability/availability-zones-overview), SQL Managed Instance places different replicas in different availability zones in the same region. To eliminate a single point of failure, the control ring is also duplicated across multiple zones. The control plane traffic is then routed to a load balancer that is also deployed across availability zones. Traffic routing from the control plane to the load balancer is controlled by [Azure Traffic Manager (ATM)](/azure/traffic-manager/traffic-manager-overview).
 
-By using a zone-redundant configuration, you can make your Business Critical or General Purpose instances resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. You can convert any existing Business Critical or General Purpose instances to the zone-redundant configuration.
+By using a zone-redundant configuration, you can make your Business Critical or General Purpose instances resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. You can convert any existing Business Critical or General Purpose instances to the zone-redundant configuration. Zone redundancy isn't available for the [Next-gen General Purpose service tier](service-tiers-next-gen-general-purpose-use.md).
 
 Because zone-redundant instances have replicas in different datacenters with some distance between them, the increased network latency might increase the transaction commit time, and thus impact the performance of some OLTP workloads. You can always return to the single-zone configuration by disabling the zone-redundancy setting. This process is an online operation similar to the regular service tier objective upgrade. At the end of the process, the instance is migrated from a zone-redundant ring to a single-zone ring or vice versa.
 

azure-sql/managed-instance/service-tiers-next-gen-general-purpose-use.md

@@ -37,7 +37,6 @@ To upgrade an existing instance to the Next-gen General Purpose service tier in
 > [!NOTE]
 > For instances inside of a failover group, changing the service tier to, or from, the Next-gen General Purpose tier isn't supported. You must first delete the failover group before modifying either replica, and then re-create the failover group after the change takes effect.
 
-
 ## New instances 
 
 You can use the Next-gen General Purpose tier upgrade for new instances when you deploy them in the Azure portal.  To do so, follow these steps:
@@ -56,6 +55,10 @@ You can use the Next-gen General Purpose tier upgrade for new instances when you
 1. Fill out the rest of the values to configure your new instance. 
 1. Select **Review + create** to review your settings, and then select **Create** to deploy your new instance using the Next-gen General purpose tier upgrade. 
 
+## Remarks
+
+- Zone redundancy isn't available for the Next-gen General Purpose service tier upgrade.
+
 ## Next steps
 
 - To get started, see [Creating a SQL Managed Instance using the Azure portal](instance-create-quickstart.md)