Fixing broken links.

Author: roygara

articles/storage/elastic-san/elastic-san-connect-aks.md

@@ -31,8 +31,7 @@ The iSCSI CSI driver for Kubernetes is [licensed under the Apache 2.0 license](h
 - Use either the [latest Azure CLI](/cli/azure/install-azure-cli) or install the [latest Azure PowerShell module](/powershell/azure/install-azure-powershell)
 - Meet the [compatibility requirements](https://github.com/kubernetes-csi/csi-driver-iscsi/blob/master/README.md#container-images--kubernetes-compatibility) for the iSCSI CSI driver
 - [Deploy an Elastic SAN](elastic-san-create.md)
-- [Configure a virtual network endpoint](elastic-san-networking.md)
-- [Configure virtual network rules](elastic-san-networking.md#configure-virtual-network-rules)
+- Configure either [private endpoints](elastic-san-configure-private-endpoints.md) or [service endpoints](elastic-san-configure-service-endpoints.md).
 
 ## Limitations
 

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

@@ -48,13 +48,9 @@ Here's an example of how an autoscale policy works. Say you have an elastic SAN
 
 ## Networking
 
-In the Elastic SAN, you can enable or disable public network access at the Elastic SAN level. You can also configure access to volume groups in the SAN over both public [Storage service endpoints](../../virtual-network/virtual-network-service-endpoints-overview.md) and [private endpoints](../../private-link/private-endpoint-overview.md) from selected virtual network subnets. Once network access is configured for a volume group, the configuration is inherited by all volumes belonging to the group. If you disable public access at the SAN level, access to the volume groups within that SAN is only available over private endpoints, regardless of individual configurations for the volume group.
+To configure networking access for an individual volume group, you must either [Configure private endpoints for Azure Elastic SAN](elastic-san-configure-private-endpoints.md) or [Configure service endpoints for Azure Elastic SAN](elastic-san-configure-service-endpoints.md). Once network access is configured for a volume group, the configuration is inherited by all volumes belonging to the group. If you disable public access at the SAN level, access to the volume groups within that SAN is only available over private endpoints, regardless of individual configurations for the volume group.
 
-To configure networking access for an individual volume group, you must either [Configure private endpoints for Azure Elastic SAN](elastic-san-configure-private-endpoints.md) or [Configure service endpoints for Azure Elastic SAN](elastic-san-configure-service-endpoints.md). 
-
-fix this
-
- then [setup a network rule](elastic-san-networking.md#configure-virtual-network-rules) on the volume group for any service endpoints. You don't need a network rule to allow traffic from a private endpoint since the storage firewall only controls access through public endpoints. You can then mount volumes from [AKS](elastic-san-connect-aks.md), [Linux](elastic-san-connect-linux.md), or [Windows](elastic-san-connect-windows.md) clients in the subnet with the [internet Small Computer Systems Interface](https://en.wikipedia.org/wiki/ISCSI) (iSCSI) protocol.
+Once you've either configured private endpoints or service endpoints for your volume groups, you can then mount volumes from [AKS](elastic-san-connect-aks.md), [Linux](elastic-san-connect-linux.md), or [Windows](elastic-san-connect-windows.md) clients in the subnet with the [internet Small Computer Systems Interface](https://en.wikipedia.org/wiki/ISCSI) (iSCSI) protocol.
 
 ## Redundancy
 

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

@@ -28,15 +28,15 @@ This article lists common issues related to Azure Elastic SAN. It also provides
 
 ## Unable to connect to your Elastic SAN via service endpoints
 
-- [Enable](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-public-network-access) Public Network Access on the SAN 
+- [Configure public network access](elastic-san-configure-service-endpoints.md#configure-public-network-access) on the SAN 
 ```powershell
 # Set the variable values.
 $RgName       = "<ResourceGroupName>"
 $EsanName     = "<ElasticSanName>"
 # Update the Elastic San.
 Update-AzElasticSan -Name $EsanName -ResourceGroupName $RgName -PublicNetworkAccess Enabled
 ```
-- [Configure](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-an-azure-storage-service-endpoint) service endpoints on the volume group 
+- [Enable the storage service endpoint](elastic-san-configure-service-endpoints.md#enable-the-storage-service-endpoint) on the volume group 
 ```powershell
 # Define some variables
 $RgName = "<ResourceGroupName>" 
@@ -51,8 +51,8 @@ $Vnet | Set-AzVirtualNetworkSubnetConfig -Name $SubnetName -AddressPrefix $Subne
 ## Elastic SAN volume performance or latency isn't as expected
 
 - Check your SAN size and configuration via portal (SAN homepage -> Configuration blade) and ensure that the I/O per second (IOPS) and throughput numbers can handle the requirements of the workload
--  Check your VM throughput and IOPS limits and ensure that the VM can handle the workload requirements
-- Ensure that you're following the best practices outlined in this [document](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-best-practices). 
+- Check your VM throughput and IOPS limits and ensure that the VM can handle the workload requirements
+- Ensure that you're following the best practices outlined in [Optimize the performance of your Elastic SAN](elastic-san-best-practices.md). 
 
 
 ## Unable to establish connectivity from new nodes in a cluster
@@ -89,8 +89,7 @@ Variables:
 
 
 ## Next steps
-- [Deploy an Elastic SAN](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-create)
-- [Connect to Windows](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-connect-windows)
-- [Connect to Linux](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-connect-linux)
-- [Connect to Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/configure-azure-elastic-san?toc=/azure/storage/elastic-san/toc.json)
-
+- [Deploy an Elastic SAN](elastic-san-create.md)
+- [Connect to Windows](elastic-san-connect-windows.md)
+- [Connect to Linux](elastic-san-connect-linux.md)
+- [Use Azure VMware Solution with Azure Elastic SAN](../../azure-vmware/configure-azure-elastic-san.md?toc=/azure/storage/elastic-san/toc.json)