Add CSN tag based configuration

Author: pjw711

articles/operator-nexus/concepts-storage-multiple-appliances.md

@@ -82,7 +82,7 @@ Azure Operator Nexus provides a shared filesystem storage solution for container
 
 You can create the shared storage service on either storage appliance when the CSN is created. All nexus-shared PVCs using that shared storage service consume storage from the storage appliance backing the shared service. You can't place a specific nexus-shared PVC on a specific storage appliance. If no storage appliance configuration is provided at CSN creation time, or if the configuration doesn't match a storage appliance, the shared storage service uses the first storage appliance.
 
-See [How to create shared storage on a specific storage appliance](howto-storage-multi-appliance-nfs.md) for instructions on creating the shared storage service on a specific storage appliance.
+See [Prerequisites for deploying tenant workloads](/quickstarts-tenant-workload-prerequisites.md#create-a-cloud-services-network) for instructions on creating the shared storage service on a specific storage appliance.
 
 #### Nexus-shared limitations
 

articles/operator-nexus/quickstarts-tenant-workload-prerequisites.md

@@ -167,13 +167,15 @@ To create an Operator Nexus virtual machine (VM) or Operator Nexus Kubernetes cl
 While the cloud services network automatically enables access to essential platform endpoints, you need to add others, such as docker.io, if your application requires them. Configuring the cloud services network proxy is a crucial step in ensuring a successful connection to your desired endpoints. To achieve this, you can add the egress endpoints to the cloud services network during the initial creation or as an update, using the `--additional-egress-endpoints` parameter. While wildcards for the URL endpoints might seem convenient, it isn't recommended for security reasons. For example, if you want to configure the proxy to allow image pull from any repository hosted off docker.io, you can specify `.docker.io` as an endpoint.
 
 The egress endpoints must comply with the domain name structures and hostname specifications outlined in RFC 1034, RFC 1035, and RFC 1123. Valid domain names include alphanumeric characters, hyphens (not at the start or end), and can have subdomains separated by dots. The endpoints can be a single FQDN, or a subdomain (domain prefix with a `.`). Here are a few examples to demonstrate compliant naming conventions for domain and hostnames.
-  
+
 - `contoso.com`: The base domain, serving as a second-level domain under the .com top-level domain.
 - `sales.contoso.com`: A subdomain of contoso.com, serving as a third-level domain under the .com top-level domain.
 - `web-server-1.contoso.com`: A hostname for a specific web server, using hyphens to separate the words and the numeral.
 - `api.v1.contoso.com`: Incorporates two subdomains (`v1` and `api`) above the base domain contoso.com.
 - `.api.contoso.com`: A wildcard for any subdomain under `api.contoso.com`, covering multiple third-level domains.
 
+Deployments with multiple storage appliances support selecting the storage appliance to use to provide shared filesystem storage to containerized workloads. The CSN manages the shared storage service that enables shared filesystem storage. You can only select the storage appliance when you create the CSN. All subsequent attempts to change the configuration will have no effect. The storage appliance name must match the Azure Resource Manager name of a storage appliance managed by your Nexus cluster. If no storage appliance name is provided, or if the configuration does not match a storage appliance in the Nexus instance, Azure Operator Nexus defaults to using the first storage appliance.
+
 ### [Azure CLI](#tab/azure-cli)
 
 ```azurecli-interactive
@@ -183,6 +185,7 @@ The egress endpoints must comply with the domain name structures and hostname sp
     --extended-location name="<ClusterCustomLocationId >" type="CustomLocation" \
     --location "<ClusterAzureRegion>" \
     --additional-egress-endpoints "[{\"category\":\"<YourCategory >\",\"endpoints\":[{\"<domainName1 >\":\"< endpoint1 >\",\"port\":<portnumber1 >}]}]"
+    --tags "storageApplianceName": "<YourStorageApplianceName>""
 ```
 
 ### [Azure PowerShell](#tab/azure-powershell)
@@ -198,6 +201,7 @@ $additionalEgressEndpoint = New-AzNetworkCloudEgressEndpointObject `
   -Category "YourCategory" `
   -Endpoint $endpointList
 $endpointEgressList+= $additionalEgressEndpoint
+$tags @{"storageApplianceName"="<YourStorageApplianceName>"}
 
 New-AzNetworkCloudServicesNetwork -CloudServicesNetworkName "<YourCloudServicesNetworkName>" `
 -ResourceGroupName "<YourResourceGroupName>" `
@@ -206,7 +210,8 @@ New-AzNetworkCloudServicesNetwork -CloudServicesNetworkName "<YourCloudServicesN
 -ExtendedLocationType "CustomLocation" `
 -Location "<ClusterAzureRegion>" `
 -AdditionalEgressEndpoint $endpointEgressList `
--EnableDefaultEgressEndpoint "False"
+-EnableDefaultEgressEndpoint "False" `
+-Tag $tags
 ```
 
 ---