Clarify storage and IP address requirements

Author: sdwheeler

articles/cloud-shell/persisting-shell-storage.md

@@ -1,7 +1,7 @@
 ---
 description: Walkthrough of how Azure Cloud Shell persists files.
 ms.contributor: jahelmic
-ms.date: 04/25/2023
+ms.date: 09/29/2023
 ms.topic: article
 tags: azure-resource-manager
 ms.custom: devx-track-linux
@@ -38,13 +38,10 @@ This fileshare is used for both Bash and PowerShell.
 
 ## Use existing resources
 
-Using the advanced option, you can associate existing resources. When selecting a Cloud Shell region,
-you must select a backing storage account co-located in the same region. For example, if your
-assigned region is West US then you must associate a fileshare that resides within West US as well.
-
-When the storage setup prompt appears, select **Show advanced settings** to view more options. The
-populated storage options filter for locally redundant storage (LRS), geo-redundant storage (GRS),
-and zone-redundant storage (ZRS) accounts.
+Using the advanced option, you can associate existing resources. When the storage setup prompt
+appears, select **Show advanced settings** to view more options. The populated storage options
+filter for locally redundant storage (LRS), geo-redundant storage (GRS), and zone-redundant storage
+(ZRS) accounts.
 
 > [!NOTE]
 > Using GRS or ZRS storage accounts are recommended for additional resiliency for your backing file
@@ -82,9 +79,7 @@ Cloud Shell machines exist in the following regions:
 | Europe       | North Europe, West Europe          |
 | Asia Pacific | India Central, Southeast Asia      |
 
-Customers should choose a primary region, unless they have a requirement that their data at rest be
-stored in a particular region. If they have such a requirement, a secondary storage region should be
-used.
+You should choose a region that meets your requirements.
 
 ### Secondary storage regions
 
@@ -102,10 +97,9 @@ of their fileshare.
 
 ## Restrict resource creation with an Azure resource policy
 
-Storage accounts that you create in Cloud Shell are tagged with
-`ms-resource-usage:azure-cloud-shell`. If you want to disallow users from creating storage accounts
-in Cloud Shell, create an [Azure resource policy for tags][02] that is triggered by this specific
-tag.
+Storage accounts that created in Cloud Shell are tagged with `ms-resource-usage:azure-cloud-shell`.
+If you want to disallow users from creating storage accounts in Cloud Shell, create an
+[Azure resource policy for tags][02] that's triggered by this specific tag.
 
 ## How Cloud Shell storage works
 

articles/cloud-shell/quickstart-deploy-vnet.md

@@ -1,7 +1,7 @@
 ---
 description: This article provides step-by-step instructions to deploy Azure Cloud Shell in a private virtual network.
 ms.contributor: jahelmic
-ms.date: 06/29/2023
+ms.date: 09/29/2023
 ms.topic: article
 ms.custom: devx-track-arm-template
 title: Deploy Azure Cloud Shell in a VNET with quickstart templates
@@ -125,7 +125,9 @@ the **Azure Cloud Shell - VNet storage** template.
 Use the [Azure Cloud Shell - VNet][08] template to create Cloud Shell resources in a virtual
 network. The template creates three subnets under the virtual network created earlier. You may
 choose to change the supplied names of the subnets or use the defaults. The virtual network, along
-with the subnets, require valid IP address assignments.
+with the subnets, require valid IP address assignments. You need at least one IP address for the
+Relay subnet and enough IP addresses in the container subnet to support the number of concurrent
+sessions you expect to use.
 
 The ARM template requires specific information about the resources you created earlier, along with
 naming information for new resources. This information is filled out along with the prefilled

articles/cloud-shell/troubleshooting.md

@@ -1,7 +1,7 @@
 ---
 description: This article covers troubleshooting Cloud Shell common scenarios.
 ms.contributor: jahelmic
-ms.date: 05/03/2023
+ms.date: 09/29/2023
 ms.topic: article
 tags: azure-resource-manager
 ms.custom: has-azure-ad-ps-ref
@@ -123,10 +123,10 @@ Azure Cloud Shell has the following known limitations:
 
 ### Quota limitations
 
-Azure Cloud Shell has a limit of 20 concurrent users per tenant per region. Opening more than 20
-simultaneous sessions produces a "Tenant User Over Quota" error. If you have a legitimate need to
-have more than 20 sessions open, such as for training sessions, contact Support to request a quota
-increase before your anticipated usage.
+Azure Cloud Shell has a limit of 20 concurrent users per tenant. Opening more than 20 simultaneous
+sessions produces a "Tenant User Over Quota" error. If you have a legitimate need to have more than
+20 sessions open, such as for training sessions, contact Support to request a quota increase before
+your anticipated usage.
 
 Cloud Shell is provided as a free service for managing your Azure environment. It's not as a general
 purpose computing platform. Excessive automated usage may be considered in breach to the Azure Terms
@@ -141,8 +141,6 @@ considerations include:
 
 - With mounted storage, only modifications within the `clouddrive` directory are persisted. In Bash,
   your `$HOME` directory is also persisted.
-- Azure fileshares can be mounted only from within your [assigned region][05].
-  - In Bash, run `env` to find your region set as `ACC_LOCATION`.
 - Azure Files supports only locally redundant storage and geo-redundant storage accounts.
 
 ### Browser support
@@ -290,5 +288,4 @@ Azure Cloud Shell in Azure Government is only accessible through the Azure porta
 
 <!-- link references -->
 [04]: https://docs.docker.com/desktop/
-[05]: persisting-shell-storage.md#mount-a-new-clouddrive
 [06]: /powershell/microsoftgraph/migration-steps