Last batch of image path fixes

Author: JasonWHowell

articles/azure-netapp-files/create-volumes-dual-protocol.md

@@ -83,7 +83,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
 1.	Click the **Volumes** blade from the Capacity Pools blade. Click **+ Add volume** to create a volume. 
 
-    ![Navigate to Volumes](../media/azure-netapp-files/azure-netapp-files-navigate-to-volumes.png) 
+    ![Navigate to Volumes](./media/shared/azure-netapp-files-navigate-to-volumes.png) 
 
 2.	In the Create a Volume window, click **Create**, and provide information for the following fields under the Basics tab:   
     * **Volume name**      
@@ -122,7 +122,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
         
         If you have not delegated a subnet, you can click **Create new** on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select **Microsoft.NetApp/volumes** to delegate the subnet for Azure NetApp Files. In each VNet, only one subnet can be delegated to Azure NetApp Files.   
     
-        ![Create subnet](../media/azure-netapp-files/azure-netapp-files-create-subnet.png)
+        ![Create subnet](./media/create-volumes-dual-protocol/azure-netapp-files-create-subnet.png)
 
     * **Network features**  
         In supported regions, you can specify whether you want to use **Basic** or **Standard** network features for the volume. See [Configure network features for a volume](configure-network-features.md) and [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md) for details.
@@ -137,7 +137,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
         For information about creating a snapshot policy, see [Manage snapshot policies](snapshots-manage-policy.md).
 
-        ![Show advanced selection](../media/azure-netapp-files/volume-create-advanced-selection.png)
+        ![Show advanced selection](./media/shared/volume-create-advanced-selection.png)
 
 3. Click the **Protocol** tab, and then complete the following actions:  
     * Select **Dual-protocol** as the protocol type for the volume.   
@@ -180,7 +180,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
     * Optionally, [configure export policy for the volume](azure-netapp-files-configure-export-policy.md).
 
-    ![Specify dual-protocol](../media/azure-netapp-files/create-volume-protocol-dual.png)
+    ![Specify dual-protocol](./media/create-volumes-dual-protocol/create-volume-protocol-dual.png)
 
 4. Click **Review + Create** to review the volume details. Then click **Create** to create the volume.
 
@@ -200,13 +200,13 @@ The **Allow local NFS users with LDAP** option in Active Directory connections e
 
 2. On the **Edit Active Directory settings** window that appears, select the **Allow local NFS users with LDAP** option.  
 
-    ![Screenshot that shows the Allow local NFS users with LDAP option](../media/azure-netapp-files/allow-local-nfs-users-with-ldap.png)  
+    ![Screenshot that shows the Allow local NFS users with LDAP option](./media/shared/allow-local-nfs-users-with-ldap.png)  
 
 ## Manage LDAP POSIX Attributes
 
 You can manage POSIX attributes such as UID, Home Directory, and other values by using the Active Directory Users and Computers MMC snap-in.  The following example shows the Active Directory Attribute Editor: 
 
-![Active Directory Attribute Editor](../media/azure-netapp-files/active-directory-attribute-editor.png) 
+![Active Directory Attribute Editor](./media/shared/active-directory-attribute-editor.png) 
 
 You need to set the following attributes for LDAP users and LDAP groups: 
 * Required attributes for LDAP users:   
@@ -221,7 +221,7 @@ You need to set the following attributes for LDAP users and LDAP groups:
 
 The values specified for `objectClass` are separate entries. For example, in Multi-valued String Editor, `objectClass` would have separate values (`user` and `posixAccount`) specified as follows for LDAP users:   
 
-![Screenshot of Multi-valued String Editor that shows multiple values specified for Object Class.](../media/azure-netapp-files/multi-valued-string-editor.png) 
+![Screenshot of Multi-valued String Editor that shows multiple values specified for Object Class.](./media/shared/multi-valued-string-editor.png) 
 
 Microsoft Entra Domain Services doesn’t allow you to modify the objectClass POSIX attribute on users and groups created in the organizational AADDC Users OU. As a workaround, you can create a custom OU and create users and groups in the custom OU.
 
@@ -234,7 +234,7 @@ On a Windows system, you can access the Active Directory Attribute Editor as fol
 1. Click **Start**, navigate to **Windows Administrative Tools**, and then click **Active Directory Users and Computers** to open the Active Directory Users and Computers window.  
 2.	Click the domain name that you want to view, and then expand the contents.  
 3.	To display the advanced Attribute Editor, enable the **Advanced Features** option in the Active Directory Users Computers **View** menu.   
-    ![Screenshot that shows how to access the Attribute Editor Advanced Features menu.](../media/azure-netapp-files/attribute-editor-advanced-features.png) 
+    ![Screenshot that shows how to access the Attribute Editor Advanced Features menu.](./media/create-volumes-dual-protocol/attribute-editor-advanced-features.png) 
 4. Double-click **Users** on the left pane to see the list of users.
 5. Double-click a particular user to see its **Attribute Editor** tab.
  

articles/azure-netapp-files/cross-region-replication-create-peering.md

@@ -24,7 +24,7 @@ Before you begin, ensure that you have reviewed the [requirements and considerat
 You need to obtain the resource ID of the source volume that you want to replicate. 
 
 1. Go to the source volume, and select **Properties** under Settings to display the source volume resource ID.   
-    ![Locate source volume resource ID](../media/azure-netapp-files/cross-region-replication-source-volume-resource-id.png)
+    ![Locate source volume resource ID](./media/cross-region-replication-create-peering/cross-region-replication-source-volume-resource-id.png)
 
 2. Copy the resource ID to the clipboard.  You will need it later.
 
@@ -45,7 +45,7 @@ You can also select an existing NetApp account in a different region.
 
 4. Create the data replication volume by selecting **Volumes** under Storage Service in the destination NetApp account. Then select the **+ Add data replication** button.  
 
-    ![Add data replication](../media/azure-netapp-files/cross-region-replication-add-data-replication.png)
+    ![Add data replication](./media/cross-region-replication-create-peering/cross-region-replication-add-data-replication.png)
 
 5. In the Create a Volume page that appears, complete the following fields under the **Basics** tab:
     * Volume name
@@ -65,11 +65,11 @@ For the NFS protocol, ensure that the export policy rules satisfy the requiremen
 
 8. Under the **Replication** tab, paste in the source volume resource ID that you obtained in [Locate the source volume resource ID](#locate-the-source-volume-resource-id), and then select the desired replication schedule. There are three options for the replication schedule: every 10 minutes, hourly, and daily.
 
-    ![Create volume replication](../media/azure-netapp-files/cross-region-replication-create-volume-replication.png)
+    ![Create volume replication](./media/cross-region-replication-create-peering/cross-region-replication-create-volume-replication.png)
 
 9. Select **Review + Create**, then select **Create** to create the data replication volume.   
 
-    ![Review and create replication](../media/azure-netapp-files/cross-region-replication-review-create-replication.png)
+    ![Review and create replication](./media/cross-region-replication-create-peering/cross-region-replication-review-create-replication.png)
 
 ## Authorize replication from the source volume  
 
@@ -81,13 +81,13 @@ To authorize the replication, you need to obtain the resource ID of the replicat
 
 3. Select the replication destination volume, go to **Properties** under Settings, and locate the **Resource ID** of the destination volume. Copy the destination volume resource ID to the clipboard.
 
-    ![Properties resource ID](../media/azure-netapp-files/cross-region-replication-properties-resource-id.png) 
+    ![Properties resource ID](./media/cross-region-replication-create-peering/cross-region-replication-properties-resource-id.png) 
 
 4. In Azure NetApp Files, go to the replication source account and source capacity pool. 
 
 5. Locate the replication source volume and select it. Navigate to **Replication** under Storage Service then select **Authorize**.
 
-    ![Authorize replication](../media/azure-netapp-files/cross-region-replication-authorize.png) 
+    ![Authorize replication](./media/cross-region-replication-create-peering/cross-region-replication-authorize.png) 
 
 6. In the Authorize field, paste the destination replication volume resource ID that you obtained in Step 3, then select **OK**.
 

articles/azure-netapp-files/cross-region-replication-delete.md

@@ -33,7 +33,7 @@ You can terminate the replication connection between the source and the destinat
 
     4.	Type **Yes** when prompted and click **Break**. 
 
-        ![Break replication peering](../media/azure-netapp-files/cross-region-replication-break-replication-peering.png)
+        ![Break replication peering](./media/shared/cross-region-replication-break-replication-peering.png)
 
 
 1. To delete volume replication, select **Replication** from the source or the destination volume.  
@@ -42,7 +42,7 @@ You can terminate the replication connection between the source and the destinat
 
 3. Confirm deletion by typing **Yes** and clicking **Delete**.   
 
-    ![Delete replication](../media/azure-netapp-files/cross-region-replication-delete-replication.png)
+    ![Delete replication](./media/cross-region-replication-delete/cross-region-replication-delete-replication.png)
 
 ## Delete source or destination volumes
 
@@ -52,7 +52,7 @@ If you want to delete the source or destination volume, you must perform the fol
 
 2. Delete the destination or source volume as needed by right-clicking the volume name and select **Delete**.   
 
-    ![Screenshot that shows right-click menu of a volume.](../media/azure-netapp-files/cross-region-replication-delete-volume.png)
+    ![Screenshot that shows right-click menu of a volume.](./media/cross-region-replication-delete/cross-region-replication-delete-volume.png)
 
 ## Next steps  
 

articles/azure-netapp-files/cross-region-replication-display-health-status.md

@@ -36,7 +36,7 @@ You can view replication status on the source volume or the destination volume.
 
     * **Total progress** – Shows the total number of cumulative bytes transferred over the lifetime of the relationship. This amount is the actual bytes transferred, and it might differ from the logical space that the source and destination volumes report.  
 
-    ![Replication health status](../media/azure-netapp-files/cross-region-replication-health-status.png)
+    ![Replication health status](./media/cross-region-replication-display-health-status/cross-region-replication-health-status.png)
 
 > [!NOTE] 
 > Replication relationship shows health status as *unhealthy* if previous replication jobs are not complete. This status is a result of large volumes being transferred with a lower transfer window (for example, a ten-minute transfer time for a large volume). In this case, the relationship status shows *transferring* and health status shows *unhealthy*.
@@ -58,7 +58,7 @@ Create [alert rules in Azure Monitor](../azure-monitor/alerts/alerts-overview.md
     * If your replication schedule is daily, enter 103,680 (24 hours * 60 minutes * 60 seconds * 1.2).
 9.	Select **Review + create**. The alert rule is ready for use.
 
-:::image type="content" source="../media/azure-netapp-files/alert-config-signal-logic.png" alt-text="Screenshot of the Azure interface that shows the configure signal logic step with a backdrop of the Create alert rule page." lightbox="../media/azure-netapp-files/alert-config-signal-logic.png":::
+:::image type="content" source="./media/cross-region-replication-display-health-status/alert-config-signal-logic.png" alt-text="Screenshot of the Azure interface that shows the configure signal logic step with a backdrop of the Create alert rule page." lightbox="./media/cross-region-replication-display-health-status/alert-config-signal-logic.png":::
 
 ## Next steps
 

articles/azure-netapp-files/cross-region-replication-manage-disaster-recovery.md

@@ -37,7 +37,7 @@ When you need to activate the destination volume (for example, when you want to
 
 4.	Type **Yes** when prompted and click the **Break** button. 
 
-    ![Break replication peering](../media/azure-netapp-files/cross-region-replication-break-replication-peering.png)
+    ![Break replication peering](./media/shared/cross-region-replication-break-replication-peering.png)
 
 5.	Mount the destination volume by following the steps in [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md).   
     This step enables a client to access the destination volume.
@@ -58,7 +58,7 @@ After disaster recovery, you can reactivate the source volume by performing a re
 
 2. Type **Yes** when prompted and click **OK**. 
 
-    ![Resync replication](../media/azure-netapp-files/cross-region-replication-resync-replication.png)
+    ![Resync replication](./media/cross-region-replication-manage-disaster-recovery/cross-region-replication-resync-replication.png)
 
 3. Monitor the source volume health status by following steps in [Display health status of replication relationship](cross-region-replication-display-health-status.md).   
     When the source volume health status shows the following values, the reverse resync operation is complete, and changes made at the destination volume are now captured on the source volume: