Merge pull request #280301 from nachoalonsoportillo/patch-20

Update concepts-index-tuning.md

Author: prmerger-automator[bot]

articles/postgresql/flexible-server/concepts-index-tuning.md

@@ -159,12 +159,24 @@ For more information on index tuning and related articles, see the documentation
 
 Index tuning feature is available in the following regions:
 
-- East Asia
+- Australia Southeast
+- Canada Central
 - Central India
+- East Asia
+- East US 2
+- France Central
+- Jio India Central
+- Korea South
+- North Central US
 - North Europe
-- Southeast Asia
+- South Africa North
 - South Central US
+- Southeast Asia
+- Sweden Central
+- Switzerland North
 - UK South
+- West Central US
+- West US
 - West US 3
 
 ### Supported tiers and SKUs
@@ -191,10 +203,6 @@ When an Azure Database for PostgreSQL - Flexible Server instance is in read-only
 
 Also, index tuning isn't supported currently on read replicas. Any recommendations seen on a read replica, were produced on the primary replica after having analyzed the workload recorded in it.
 
-### Network connectivity method
-
-Index tuning is currently supported on instances whose connectivity method is configured as [Public access (allowed IP addresses)](concepts-networking-public.md). For instances configured with [Private access (VNET Integration)](concepts-networking-private.md) the feature can be enabled, but it won't generate recommendations.
-
 ### Important considerations
 
 If you have [high availability](../../reliability/reliability-postgresql-flexible-server.md) or [read replicas](concepts-read-replicas.md) configured on your server, be aware of the implications associated with producing write-intensive workloads on the primary server when indexes recommended are implemented. Be especially careful when creating indexes whose size is estimated to be significantly large.