Merge pull request #108000 from oslake/patch-31

Update sql-database-service-tiers-vcore.md

Author: PRMerger19

articles/sql-database/sql-database-service-tiers-vcore.md

@@ -75,14 +75,16 @@ For regions where Gen4/Gen5 is available, see [Gen4/Gen5 availability](#gen4gen5
 - Depending on the workload, Fsv2-series can deliver more CPU performance per vCore than Gen5, and the 72 vCore size can provide more CPU performance for less cost than 80 vCores on Gen5. 
 - Fsv2 provides less memory and tempdb per vCore than other hardware so workloads sensitive to those limits may want to consider Gen5 or M-series instead.  
 
-For regions where Fsv2-series is available, see [Fsv2-series availability](#fsv2-series).
+Fsv2-series in only supported in the General Purpose tier.  For regions where Fsv2-series is available, see [Fsv2-series availability](#fsv2-series).
 
 
 ### M-series (preview)
 
 - M-series is a memory optimized hardware option for workloads demanding more memory and higher compute limits than provided by Gen5.
 - M-series provides 29 GB per vCore and 128 vCores, which increases the memory limit relative to Gen5 by 8x to nearly 4 TB.
 
+M-series is only supported in the Business Critical tier and does not support zone redundancy.
+
 To enable M-series hardware for a subscription and region, a support request must be opened. The subscription must be a paid offer type including Pay-As-You-Go or Enterprise Agreement (EA).  If the support request is approved, then the selection and provisioning experience of M-series follows the same pattern as for other hardware generations. For regions where M-series is available, see [M-series availability](#m-series).