Merge pull request #257785 from roygara/postRel

Wave 1 post updates

Author: v-dirichards

articles/storage/elastic-san/elastic-san-create.md

@@ -4,9 +4,9 @@ description: Learn how to deploy an Azure Elastic SAN Preview with the Azure por
 author: roygara
 ms.service: azure-elastic-san-storage
 ms.topic: how-to
-ms.date: 10/19/2023
+ms.date: 11/07/2023
 ms.author: rogarana
-ms.custom: references_regions, ignite-2022, devx-track-azurepowershell, devx-track-azurecli
+ms.custom: references_regions, devx-track-azurepowershell, devx-track-azurecli
 ---
 
 # Deploy an Elastic SAN Preview
@@ -18,7 +18,7 @@ This article explains how to deploy and configure an elastic storage area networ
 - If you're using Azure PowerShell, install the [latest Azure PowerShell module](/powershell/azure/install-azure-powershell).
 - If you're using Azure CLI, install the [latest version](/cli/azure/install-azure-cli).
 - Once you've installed the latest version, run `az extension add -n elastic-san` to install the extension for Elastic SAN.
-There are no additional registration steps required.
+There are no extra registration steps required.
 
 ## Limitations
 
@@ -31,7 +31,7 @@ There are no additional registration steps required.
 1. Sign in to the Azure portal and search for **Elastic SAN**.
 1. Select **+ Create a new SAN**
 1. On the basics page, fill in the appropriate values.
-    - **Elastic SAN name** must be between 3 and 24 characters long. The name may only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character.
+    - **Elastic SAN name** must be between 3 and 24 characters long. The name can only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character.
     For best performance, your SAN should be in the same zone as your VM.
 
 1. Specify the amount of base capacity you require, and any additional capacity, then select next.
@@ -49,7 +49,7 @@ Use one of these sets of sample code to create an Elastic SAN that uses locally
 | Placeholder                      | Description |
 |----------------------------------|-------------|
 | `<ResourceGroupName>`            | The name of the resource group where the resources will be deployed. |
-| `<ElasticSanName>`               | The name of the Elastic SAN to be created.<br>*The Elastic SAN name must be between 3 and 24 characters long. The name may only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character.* |
+| `<ElasticSanName>`               | The name of the Elastic SAN to be created.<br>*The Elastic SAN name must be between 3 and 24 characters long. The name can only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character.* |
 | `<ElasticSanVolumeGroupName>`    | The name of the Elastic SAN Volume Group to be created. |
 | `<VolumeName>`                   | The name of the Elastic SAN Volume to be created. |
 | `<Location>`                     | The region where the new resources will be created. |
@@ -94,11 +94,11 @@ Use one of these sets of sample code to create an Elastic SAN that uses locally
 | Placeholder                      | Description |
 |----------------------------------|-------------|
 | `<ResourceGroupName>`            | The name of the resource group where the resources will be deployed. |
-| `<ElasticSanName>`               | The name of the Elastic SAN to be created.<br>*The Elastic SAN name must be between 3 and 24 characters long. The name may only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character.* |
+| `<ElasticSanName>`               | The name of the Elastic SAN to be created.<br>*The Elastic SAN name must be between 3 and 24 characters long. The name can only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character.* |
 | `<ElasticSanVolumeGroupName>`    | The name of the Elastic SAN Volume Group to be created. |
 | `<VolumeName>`                   | The name of the Elastic SAN Volume to be created. |
 | `<Location>`                     | The region where the new resources will be created. |
-| `<Zone>`                         | The availability zone where the Elastic SAN will be created.<br> *Specify the same availability zone as the zone that will host your workload.*<br>*Use only if the Elastic SAN will use locally-redundant storage.*<br> *Must be a zone supported in the target location such as `1`, `2`, or `3`.*  |
+| `<Zone>`                         | The availability zone where the Elastic SAN will be created.<br> *Specify the same availability zone as the zone that will host your workload.*<br>*Use only if the Elastic SAN uses locally-redundant storage.*<br> *Must be a zone supported in the target location such as `1`, `2`, or `3`.*  |
 
 The following command creates an Elastic SAN that uses **locally-redundant** storage.
 
@@ -140,7 +140,7 @@ Now that you've configured the basic settings and provisioned your storage, you
 # [Portal](#tab/azure-portal)
 
 1. Select **+ Create volume group** and name your volume group.
-    - The name must be between 3 and 63 characters long. The name may only contain lowercase letters, numbers and hyphens, and must begin and end with a letter or a number. Each hyphen must be preceded and followed by an alphanumeric character. The volume group name can't be changed once created.
+    - The name must be between 3 and 63 characters long. The name can only contain lowercase letters, numbers and hyphens, and must begin and end with a letter or a number. Each hyphen must be preceded and followed by an alphanumeric character. The volume group name can't be changed once created.
 
 1. Select **Next : Volumes**
 

articles/storage/elastic-san/elastic-san-encryption-overview.md

@@ -7,6 +7,7 @@ ms.date: 11/06/2023
 ms.topic: conceptual
 ms.author: rogarana
 ms.service: azure-elastic-san-storage
+ms.custom: references_regions
 ---
 
 # Encrypt an Azure Elastic SAN Preview
@@ -41,6 +42,10 @@ The following list explains the numbered steps in the diagram:
 1. Azure Elastic SAN wraps the data encryption key with the customer-managed key from the key vault.
 1. For read/write operations, Azure Elastic SAN sends requests to Azure Key Vault to unwrap the account encryption key to perform encryption and decryption operations.
 
+### Regional availability
+
+[!INCLUDE [elastic-san-regions](../../../includes/elastic-san-regions.md)]
+
 ## Next steps
 
 - [Configure customer-managed keys for an Elastic SAN volume group](elastic-san-configure-customer-managed-keys.md)

articles/storage/elastic-san/elastic-san-introduction.md

@@ -4,7 +4,7 @@ description: An overview of Azure Elastic SAN Preview, a service that enables yo
 author: roygara
 ms.service: azure-elastic-san-storage
 ms.topic: overview
-ms.date: 08/15/2023
+ms.date: 11/07/2023
 ms.author: rogarana
 ms.custom: ignite-2022
 ---
@@ -13,7 +13,7 @@ ms.custom: ignite-2022
 
 Azure Elastic storage area network (SAN) is Microsoft's answer to the problem of workload optimization and integration between your large scale databases and performance-intensive mission-critical applications. Elastic SAN Preview is a fully integrated solution that simplifies deploying, scaling, managing, and configuring a SAN, while also offering built-in cloud capabilities like high availability.
 
-Elastic SAN is designed for large scale IO-intensive workloads and top tier databases such as SQL, MariaDB, and support hosting the workloads on virtual machines, or containers such as Azure Kubernetes Service. Instead of having to deploy and manage individual storage options for each individual compute deployment, you can provision an Elastic SAN and use the SAN volumes as backend storage for all your workloads. Consolidating your storage like this can be more cost effective if you have a sizeable amount of large scale IO-intensive workloads and top tier databases.
+Elastic SAN is interoperable with multiple types of compute resources such as Azure Virtual Machines, Azure VMware Solutions, and Azure Kubernetes Service. Instead of having to deploy and manage individual storage options for each individual compute deployment, you can provision an Elastic SAN and use the SAN volumes as backend storage for all your workloads. Consolidating your storage like this can be more cost effective if you have a sizeable amount of large scale IO-intensive workloads and top tier databases.
 
 ## Benefits of Elastic SAN
 
@@ -45,25 +45,25 @@ The following diagram illustrates the relationship and mapping of an Azure Elast
 
 When you configure an Elastic SAN, you select the redundancy of the entire SAN and provision storage. The storage you provision determines how much performance your SAN has, and the total capacity that can be distributed to each volume within the SAN.
 
-Your Elastic SAN's name has some requirements. The name may only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character. The name must be between 3 and 24 characters long.
+Your Elastic SAN's name has some requirements. The name can only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character. The name must be between 3 and 24 characters long.
 
 ### Volume groups 
 
 Volume groups are management constructs that you use to manage volumes at scale. Any settings or configurations applied to a volume group, such as virtual network rules, are inherited by any volumes associated with that volume group.
 
-Your volume group's name has some requirements. The name may only contain lowercase letters, numbers and hyphens, and must begin and end with a letter or a number. Each hyphen must be preceded and followed by an alphanumeric character. The name must be between 3 and 63 characters long.
+Your volume group's name has some requirements. The name can only contain lowercase letters, numbers and hyphens, and must begin and end with a letter or a number. Each hyphen must be preceded and followed by an alphanumeric character. The name must be between 3 and 63 characters long.
 
 ### Volumes
 
 You partition the SAN's storage capacity into individual volumes. These individual volumes can be mounted to your clients with iSCSI.
 
-The name of your volume is part of their iSCSI IQN. The name may only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character. The name must also be between 3 and 63 characters long.
+The name of your volume is part of their iSCSI IQN. The name can only contain lowercase letters, numbers, hyphens and underscores, and must begin and end with a letter or a number. Each hyphen and underscore must be preceded and followed by an alphanumeric character. The name must also be between 3 and 63 characters long.
 
 ## Support for Azure Storage features
 
 The following table indicates support for Azure Storage features with Azure Elastic SAN.
 
-The status of items in this table may change over time.
+The status of items in this table might change over time.
 
 | Storage feature | Supported for Elastic SAN |
 |-----------------|---------|

articles/storage/elastic-san/elastic-san-networking-concepts.md

@@ -30,6 +30,10 @@ After configuring endpoints, you can configure network rules to further control
 
 You can enable or disable public Internet access to your Elastic SAN endpoints at the SAN level. Enabling public network access for an Elastic SAN allows you to configure public access to individual volume groups in that SAN over storage service endpoints. By default, public access to individual volume groups is denied even if you allow it at the SAN level. If you disable public access at the SAN level, access to the volume groups within that SAN is only available over private endpoints.
 
+### Regional availability
+
+[!INCLUDE [elastic-san-regions](../../../includes/elastic-san-regions.md)]
+
 ## Storage service endpoints
 
 [Azure Virtual Network service endpoints](../../virtual-network/virtual-network-service-endpoints-overview.md) provide secure and direct connectivity to Azure services using an optimized route over the Azure backbone network. Service endpoints allow you to secure your critical Azure service resources so only specific virtual networks can access them.

articles/storage/elastic-san/elastic-san-networking.md

@@ -191,7 +191,7 @@ Deploying a private endpoint for an Elastic SAN Volume group using PowerShell in
 1. Get the Elastic SAN Volume Group.
 1. Create a private link service connection using the volume group as input.
 1. Create the private endpoint using the subnet and the private link service connection as input.
-1. **(Optional** *if you're using the two-step process (creation, then approval))*: The Elastic SAN Network Admin approves the connection.
+1. **(Optional)** *if you're using the two-step process (creation, then approval))*: The Elastic SAN Network Admin approves the connection.
 
 Use this sample code to create a private endpoint for your Elastic SAN volume group with PowerShell. Replace the values of `RgName`, `VnetName`, `SubnetName`, `EsanName`, `EsanVgName`, `PLSvcConnectionName`, `EndpointName`, and `Location` with your own values:
 

articles/storage/elastic-san/elastic-san-performance.md

@@ -4,7 +4,7 @@ description: Learn how your workload's performance is handled by Azure Elastic S
 author: roygara
 ms.service: azure-elastic-san-storage
 ms.topic: overview
-ms.date: 10/19/2023
+ms.date: 11/06/2023
 ms.author: rogarana
 ---
 
@@ -36,7 +36,7 @@ The throughput of an Elastic SAN increases by 80 MB/s per base TiB. So if you ha
 
 ### Elastic SAN volumes
 
-The performance of an individual volume is determined by its capacity. The maximum IOPS of a volume increase by 750 per GiB, up to a maximum of 64,000 IOPS. The maximum throughput increases by 60 MB/s per GiB, up to a maximum of 1,024 MB/s. A volume needs at least 86 GiB to be capable of using 64,000 IOPS. A volume needs at least 18 GiB in order to be capable of using the maximum 1,024 MB/s. The combined IOPS and throughput of all your volumes can't exceed the IOPS and throughput of your SAN.
+The performance of an individual volume is determined by its capacity. The maximum IOPS of a volume increase by 750 per GiB, up to a maximum of 80,000 IOPS. The maximum throughput increases by 60 MB/s per GiB, up to a maximum of 1,024 MB/s. A volume needs at least 107 GiB to be capable of using 80,000 IOPS. A volume needs at least 22 GiB in order to be capable of using the maximum 1,280 MB/s. The combined IOPS and throughput of all your volumes can't exceed the IOPS and throughput of your SAN.
 
 ## Example configuration
 
@@ -55,11 +55,11 @@ Each of the example scenarios in this article uses the following configuration f
 
 |Resource  |Capacity  |IOPS  |
 |---------|---------|---------|
-|Elastic SAN     |25 TiB         |135,000 (provisioned)         |
-|AKS SAN volume     |3 TiB         | Up to 64,000         |
-|Workload 1 SAN volume     |10 TiB         |Up to 64,000         |
-|Workload 2 SAN volume     |4 TiB         |Up to 64,000         |
-|Workload 3 SAN volume     |2 TiB          |Up to 64,000         |
+|Elastic SAN     |27 TiB         |135,000 (provisioned)         |
+|AKS SAN volume     |3 TiB         | Up to 80,000         |
+|Workload 1 SAN volume     |10 TiB         |Up to 80,000         |
+|Workload 2 SAN volume     |4 TiB         |Up to 80,000         |
+|Workload 3 SAN volume     |2 TiB          |Up to 80,000         |
 
 
 ## Example scenarios
@@ -75,7 +75,7 @@ The following example scenarios depict how your Elastic SAN handles performance
 |Workload 2     |8,000         |8,000         |
 |Workload 3     |20,000         |20,000         |
 
-In this scenario, no throttling occurs at either the VM or SAN level. The SAN itself has 135,000 IOPS, each volume is large enough to serve up to 64,000 IOPS, enough IOPS are available from the SAN, none of the VM's IOPS limits have been surpassed, and the total IOPS requested is 41,000. So the workloads all execute without any throttling.
+In this scenario, no throttling occurs at either the VM or SAN level. The SAN itself has 135,000 IOPS, each volume is large enough to serve up to 80,000 IOPS, enough IOPS are available from the SAN, none of the VM's IOPS limits have been surpassed, and the total IOPS requested is 41,000. So the workloads all execute without any throttling.
 
 :::image type="content" source="media/elastic-san-performance/typical-workload.png" alt-text="Average scenario example diagram." lightbox="media/elastic-san-performance/typical-workload.png":::
 
@@ -87,9 +87,9 @@ In this scenario, no throttling occurs at either the VM or SAN level. The SAN it
 |AKS workload     |2,000         |2,000         |N/A         |
 |Workload 1     |10,000         |10,000         |N/A         |
 |Workload 2     |10,000         |10,000         |N/A         |
-|Workload 3     |64,000         |64,000         |9:00 am         |
+|Workload 3     |80,000         |80,000         |9:00 am         |
 
-In this scenario, no throttling occurs. Workload 3 spiked at 9am, requesting 64,000 IOPS. None of the other workloads spiked and the SAN had enough free IOPS to distribute to the workload, so there was no throttling. 
+In this scenario, no throttling occurs. Workload 3 spiked at 9am, requesting 80,000 IOPS. None of the other workloads spiked and the SAN had enough free IOPS to distribute to the workload, so there was no throttling. 
 
 Generally, this is the ideal configuration for a SAN sharing workloads. It's best to have enough performance to handle the normal operations of workloads, and occasional peaks.
 

articles/storage/elastic-san/elastic-san-planning.md

@@ -35,7 +35,7 @@ When allocating storage for an Elastic SAN, consider how much storage you requir
 
 You create volumes from the storage that you allocated to your Elastic SAN. When you create a volume, think of it like partitioning a section of the storage of your Elastic SAN. The maximum performance of an individual volume is determined by the amount of storage allocated to it. Individual volumes can have fairly high IOPS and throughput, but the total IOPS and throughput of all your volumes can't exceed the total IOPS and throughput your SAN has.
 
-Using the same example of a 100 TiB SAN that has 250,000 IOPS and 4,000 MB/s. Say this SAN had 100 1 TiB volumes. You could potentially have three of these volumes operating at their maximum performance (64,000 IOPS, 1,024 MB/s) since this would be below the SAN's limits. But if four or five volumes all needed to operate at maximum at the same time, they wouldn't be able to. Instead the performance of the SAN would be split evenly among them.
+Using the same example of a 100 TiB SAN that has 500,000 IOPS and 20,000 MB/s. Say this SAN had 100 1 TiB volumes. You could potentially have six of these volumes operating at their maximum performance (80,000 IOPS, 1,280 MB/s) since this would be below the SAN's limits. But if seven volumes all needed to operate at maximum at the same time, they wouldn't be able to. Instead the performance of the SAN would be split evenly among them.
 
 ## Networking