Update README.mds for all Network Secured Templates (#234)

* Update README.md
* fixing all readmes

Author: fosteramanda

samples/microsoft/infrastructure-setup-terraform/15a-private-network-standard-agent-setup/README.md

@@ -14,8 +14,21 @@ languages:
 
 # Azure AI Agent Service: Standard Agent Setup with E2E Network Isolation
 
-> **Note:** Class A subnet support is only available in a limited number of regions and requires your subscription id be allowlisted. Please reach out to [email protected] if you are interested in getting access. Regions with class A support: westus, eastus us, eastus 2, and central us
-
+> **IMPORTANT**
+> 
+> Class A subnet support is only available in a limited number of regions and requires your subscription id be allowlisted. Please reach out to [email protected] if you are interested in getting access. **Regions with Class A Subnet Support:** westus, eastus us, eastus 2, central us, [NEW] japan east, [NEW] france central
+>
+> Class B and C subnet support is already GA and available in all regions supported by Azure AI Foundry Agent Service. No subscription allowlisting is required. Deployment templates and setup steps are identical for Class A, B, and C subnets; Class A remains in private preview solely because of its limited region coverage.
+ 
+## Key Information
+
+**Limited Region Support for Class A Subnet IPs**
+- Class A subnet support is only available in select regions and requires allowlisting of your subscription ID. Supported regions: westus, eastus us, eastus 2, central us, [NEW] japan east, [NEW] france central
+
+**Region and Resource Placement Requirements**
+- **All Foundry workspace resources should be in the same region as the VNet**, including CosmosDB, Storage Account, AI Search, Foundry Account, Project, Managed Identity. The only exception is within the Foundry Account, you may choose to deploy your model to a different region, and any cross-region communication will be handled securely within our network infrastructure.
+  - **Note:** Your Virtual Network can be in a different resource group than your Foundry workspace resources
+  
 This infrastructure-as-code (IaC) solution deploys a network-secured Azure AI agent environment with private networking and role-based access control (RBAC). It supports scenarios where you want a standalone solution for proof-of-concepts. For deployment to existing environments enterprise environments use the [15b-private-network-standard-agent-setup-byovnet deployment](../15b-private-network-standard-agent-setup-byovnet/README.md).
 
 ## Prerequisites

samples/microsoft/infrastructure-setup-terraform/15b-private-network-standard-agent-setup-byovnet/README.md

@@ -13,7 +13,20 @@ languages:
 
 # Azure AI Agent Service: Standard Agent Setup with E2E Network Isolation with Bring-Your-Own Virtual Network
 
-> **Note:** Class A subnet support is only available in a limited number of regions and requires your subscription id be allowlisted. Please reach out to [email protected] if you are interested in getting access. Regions with class A support: westus, eastus us, eastus 2, and central us
+> **IMPORTANT**
+> 
+> Class A subnet support is only available in a limited number of regions and requires your subscription id be allowlisted. Please reach out to [email protected] if you are interested in getting access. **Regions with Class A Subnet Support:** westus, eastus us, eastus 2, central us, [NEW] japan east, [NEW] france central
+>
+> Class B and C subnet support is already GA and available in all regions supported by Azure AI Foundry Agent Service. No subscription allowlisting is required. Deployment templates and setup steps are identical for Class A, B, and C subnets; Class A remains in private preview solely because of its limited region coverage.
+ 
+## Key Information
+
+**Limited Region Support for Class A Subnet IPs**
+- Class A subnet support is only available in select regions and requires allowlisting of your subscription ID. Supported regions: westus, eastus us, eastus 2, central us, [NEW] japan east, [NEW] france central
+
+**Region and Resource Placement Requirements**
+- **All Foundry workspace resources should be in the same region as the VNet**, including CosmosDB, Storage Account, AI Search, Foundry Account, Project, Managed Identity. The only exception is within the Foundry Account, you may choose to deploy your model to a different region, and any cross-region communication will be handled securely within our network infrastructure.
+  - **Note:** Your Virtual Network can be in a different resource group than your Foundry workspace resources
 
 This infrastructure-as-code (IaC) solution deploys a network-secured Azure AI agent environment with private networking and role-based access control (RBAC). It supports scenarios where a customer has a pre-existing virtual network deployed to a workload subscription which is connected to a platform landing zone where the platform components (such as Private DNS Zones) are stored in the same or a separate subscription.
 

samples/microsoft/infrastructure-setup/15-private-network-standard-agent-setup/README.md

@@ -14,11 +14,11 @@ languages:
 
 > **IMPORTANT**
 > 
-> Class A subnet support is only available in a limited number of regions and requires your subscription id be allowlisted. Please reach out to [email protected] if you are interested in getting access.
+> Class A subnet support is only available in a limited number of regions and requires your subscription id be allowlisted. Please reach out to [email protected] if you are interested in getting access. **Regions with Class A Subnet Support:** westus, eastus us, eastus 2, central us, [NEW] japan east, [NEW] france central
 >
-> **Regions with Class A Subnet Support:** westus, eastus us, eastus 2, central us, [NEW] japan east, [NEW] france central
+> Class B and C subnet support is already GA and available in all regions supported by Azure AI Foundry Agent Service. No subscription allowlisting is required. Deployment templates and setup steps are identical for Class A, B, and C subnets; Class A remains in private preview solely because of its limited region coverage.
  
-## Important Information
+## Key Information
 
 **Limited Region Support for Class A Subnet IPs**
 - Class A subnet support is only available in select regions and requires allowlisting of your subscription ID. Supported regions: westus, eastus us, eastus 2, central us, [NEW] japan east, [NEW] france central
@@ -27,9 +27,6 @@ languages:
 - **All Foundry workspace resources should be in the same region as the VNet**, including CosmosDB, Storage Account, AI Search, Foundry Account, Project, Managed Identity. The only exception is within the Foundry Account, you may choose to deploy your model to a different region, and any cross-region communication will be handled securely within our network infrastructure.
   - **Note:** Your Virtual Network can be in a different resource group than your Foundry workspace resources 
 
-**Reminder**
-- Class B and C subnet support is already GA and available in all regions supported by Azure AI Foundry Agent Service. No subscription allowlisting is required. The setup process and templates are identical across Class A, B, and C subnet IPs, this is why the same templates are used regardless of subnet class.
-
 ## Overview
 This infrastructure-as-code (IaC) solution deploys a network-secured Azure AI agent environment with private networking and role-based access control (RBAC).