First 25 files with image path updates

Author: JasonWHowell

articles/azure-netapp-files/access-smb-volume-from-windows-client.md

@@ -15,7 +15,7 @@ You can use Microsoft Entra ID with the Hybrid Authentication Management module
 >[!NOTE]
 >Using Microsoft Entra ID for authenticating [hybrid user identities](../active-directory/hybrid/whatis-hybrid-identity.md) allows Microsoft Entra users to access Azure NetApp Files SMB shares. This means your end users can access Azure NetApp Files SMB shares without requiring a line-of-sight to domain controllers from Microsoft Entra hybrid joined and Microsoft Entra joined VMs. Cloud-only identities aren't currently supported. For more information, see [Understand guidelines for Active Directory Domain Services site design and planning](understand-guidelines-active-directory-domain-service-site.md).
 
-:::image type="content" source="../media/azure-netapp-files/diagram-windows-joined-active-directory.png" alt-text="Diagram of SMB volume joined to Microsoft Entra ID." lightbox="../media/azure-netapp-files/diagram-windows-joined-active-directory.png":::
+:::image type="content" source="./media/access-smb-volume-from-windows-client/diagram-windows-joined-active-directory.png" alt-text="Diagram of SMB volume joined to Microsoft Entra ID." lightbox="./media/access-smb-volume-from-windows-client/diagram-windows-joined-active-directory.png":::
 
 ## Requirements and considerations 
 
@@ -48,7 +48,7 @@ The configuration process takes you through five process:
 1. Under **Computers**, right-click on the computer account created as part of the Azure NetApp Files volume then select **Properties**.  
 1. Under **Attribute Editor,** locate `servicePrincipalName`. In the Multi-valued string editor, add the CIFS SPN value using the CIFS/FQDN format. 
 
-:::image type="content" source="../media/azure-netapp-files/multi-value-string-editor.png" alt-text="Screenshot of multi-value string editor window." lightbox="../media/azure-netapp-files/multi-value-string-editor.png":::
+:::image type="content" source="./media/access-smb-volume-from-windows-client/multi-value-string-editor.png" alt-text="Screenshot of multi-value string editor window." lightbox="./media/access-smb-volume-from-windows-client/multi-value-string-editor.png":::
 
 <a name='register-a-new-azure-ad-application'></a>
 
@@ -59,21 +59,21 @@ The configuration process takes you through five process:
 1. Assign a **Name**. Under select the **Supported account type**, choose **Accounts in this organizational directory only (Single tenant)**.
 1. Select **Register**.
 
-:::image type="content" source="../media/azure-netapp-files/register-application-active-directory.png" alt-text="Screenshot to register application." lightbox="../media/azure-netapp-files/register-application-active-directory.png":::
+:::image type="content" source="./media/access-smb-volume-from-windows-client/register-application-active-directory.png" alt-text="Screenshot to register application." lightbox="./media/access-smb-volume-from-windows-client/register-application-active-directory.png":::
 
 1. Configure the permissions for the application. From your **App Registrations**, select **API Permissions** then **Add a permission**. 
 1. Select **Microsoft Graph** then **Delegated Permissions**. Under **Select Permissions**, select **openid** and **profile** under **OpenId permissions**.
 
-    :::image type="content" source="../media/azure-netapp-files/api-permissions.png" alt-text="Screenshot to register API permissions." lightbox="../media/azure-netapp-files/api-permissions.png":::
+    :::image type="content" source="./media/access-smb-volume-from-windows-client/api-permissions.png" alt-text="Screenshot to register API permissions." lightbox="./media/access-smb-volume-from-windows-client/api-permissions.png":::
 
 1. Select **Add permission**. 
 1. From **API Permissions**, select **Grant admin consent for...**.
 
-    :::image type="content" source="../media/azure-netapp-files/grant-admin-consent.png" alt-text="Screenshot to grant API permissions." lightbox="../media/azure-netapp-files/grant-admin-consent.png ":::
+    :::image type="content" source="./media/access-smb-volume-from-windows-client/grant-admin-consent.png" alt-text="Screenshot to grant API permissions." lightbox="./media/access-smb-volume-from-windows-client/grant-admin-consent.png ":::
 
 1. From **Authentication**, under **App instance property lock**, select **Configure** then deselect the checkbox labeled **Enable property lock**.
 
-    :::image type="content" source="../media/azure-netapp-files/authentication-registration.png" alt-text="Screenshot of app registrations." lightbox="../media/azure-netapp-files/authentication-registration.png":::
+    :::image type="content" source="./media/access-smb-volume-from-windows-client/authentication-registration.png" alt-text="Screenshot of app registrations." lightbox="./media/access-smb-volume-from-windows-client/authentication-registration.png":::
 
 1. From **Overview**, make note of the **Application (client) ID**, which is required later. 
 
@@ -121,15 +121,15 @@ The configuration process takes you through five process:
         * Value name: KERBEROS.MICROSOFTONLINE.COM
         * Value: .contoso.com
 
-    :::image type="content" source="../media/azure-netapp-files/define-host-name-to-kerberos.png" alt-text="Screenshot to define how-name-to-Kerberos real mappings." lightbox="../media/azure-netapp-files/define-host-name-to-kerberos.png":::
+    :::image type="content" source="./media/access-smb-volume-from-windows-client/define-host-name-to-kerberos.png" alt-text="Screenshot to define how-name-to-Kerberos real mappings." lightbox="./media/access-smb-volume-from-windows-client/define-host-name-to-kerberos.png":::
 
 ### Mount the Azure NetApp Files SMB volumes 
 
 1. Log into to the Microsoft Entra joined VM using a hybrid identity account synced from AD DS.
 2. Mount the Azure NetApp Files SMB volume using the info provided in the Azure portal. For more information, see [Mount SMB volumes for Windows VMs](mount-volumes-vms-smb.md).
 3. Confirm the mounted volume is using Kerberos authentication and not NTLM authentication. Open a command prompt, issue the `klist` command; observe the output in the cloud TGT (krbtgt) and CIFS server ticket information.
 
-    :::image type="content" source="../media/azure-netapp-files/klist-output.png" alt-text="Screenshot of CLI output." lightbox="../media/azure-netapp-files/klist-output.png":::
+    :::image type="content" source="./media/access-smb-volume-from-windows-client/klist-output.png" alt-text="Screenshot of CLI output." lightbox="./media/access-smb-volume-from-windows-client/klist-output.png":::
 
 ## Further information 
 

articles/azure-netapp-files/application-volume-group-add-hosts.md

@@ -41,7 +41,7 @@ Building a multiple-host SAP HANA database always starts with creating a volume
 
     Click **Next: Volume Group**.
 
-    [ ![Screenshot that shows the HANA section for adding hosts.](../media/azure-netapp-files/application-multiple-hosts-sap-hana.png) ](../media/azure-netapp-files/application-multiple-hosts-sap-hana.png#lightbox)
+    [ ![Screenshot that shows the HANA section for adding hosts.](./media/application-volume-group-add-hosts/application-multiple-hosts-sap-hana.png) ](./media/application-volume-group-add-hosts/application-multiple-hosts-sap-hana.png#lightbox)
 
 3. In the **Volume group** tab, provide identical input as you did when you created the first HANA host.  
 
@@ -56,17 +56,17 @@ Building a multiple-host SAP HANA database always starts with creating a volume
 
     Click **Next: Review + Create**.  
 
-    [ ![Screenshot that shows the Volumes section for adding hosts.](../media/azure-netapp-files/application-multiple-hosts-volumes.png) ](../media/azure-netapp-files/application-multiple-hosts-volumes.png#lightbox)
+    [ ![Screenshot that shows the Volumes section for adding hosts.](./media/application-volume-group-add-hosts/application-multiple-hosts-volumes.png) ](./media/application-volume-group-add-hosts/application-multiple-hosts-volumes.png#lightbox)
 
 4. In the **Review + Create** tab, the `{HostId}` placeholder is replaced with the individual numbers for each of the volume groups that will be created. 
 
     You can click **Next Group** to navigate through all volume groups that are being created (one for each host). You can also click a particular volume to view its details.
 
-    [ ![Screenshot that shows the Review and Create section for adding hosts.](../media/azure-netapp-files/application-multiple-review-create.png) ](../media/azure-netapp-files/application-multiple-review-create.png#lightbox)
+    [ ![Screenshot that shows the Review and Create section for adding hosts.](./media/application-volume-group-add-hosts/application-multiple-review-create.png) ](./media/application-volume-group-add-hosts/application-multiple-review-create.png#lightbox)
 
 5. After you navigate through the volume groups, click **Create All Groups** to create all the volumes for the HANA hosts you are adding. 
 
-    [ ![Screenshot that shows the Create All Groups button.](../media/azure-netapp-files/application-multiple-create-groups.png) ](../media/azure-netapp-files/application-multiple-create-groups.png#lightbox)
+    [ ![Screenshot that shows the Create All Groups button.](./media/application-volume-group-add-hosts/application-multiple-create-groups.png) ](./media/application-volume-group-add-hosts/application-multiple-create-groups.png#lightbox)
 
     The **Create Volume Group** page shows the added volume groups with the "Creating" status.
 

articles/azure-netapp-files/application-volume-group-add-volume-secondary.md

@@ -23,7 +23,7 @@ The HANA System Replication (HSR) functionality enables SAP HANA databases to sy
 
 The following diagram illustrates the concept of HSR: 
 
- ![Diagram that explains HANA System Replication.](../media/azure-netapp-files/application-hana-system-replication.png) 
+ ![Diagram that explains HANA System Replication.](./media/application-volume-group-add-volume-secondary/application-hana-system-replication.png) 
 
 
 To enable HSR, the configuration of the secondary SAP HANA system must be identical to the primary SAP HANA system. That is, if the primary system is a single-host HANA system, then the secondary SAP HANA system also needs to be a single-hosts system. The same applies for multiple host systems.
@@ -61,7 +61,7 @@ This section shows an example of creating a single-host, secondary SAP HANA syst
 
     Click **Next: Volume Group** to continue.
 
-    [ ![Screenshot that shows the HANA section in HSR configuration.](../media/azure-netapp-files/application-secondary-sap-hana.png) ](../media/azure-netapp-files/application-secondary-sap-hana.png#lightbox)
+    [ ![Screenshot that shows the HANA section in HSR configuration.](./media/application-volume-group-add-volume-secondary/application-secondary-sap-hana.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-sap-hana.png#lightbox)
 
 3.	In the **Volume group** tab, provide information for creating the volume group:  
 
@@ -92,19 +92,19 @@ This section shows an example of creating a single-host, secondary SAP HANA syst
 
     Click **Next: Volumes**.
 
-    [ ![Screenshot that shows the Tags section of the Volume Group tab.](../media/azure-netapp-files/application-secondary-volume-group-tags.png) ](../media/azure-netapp-files/application-secondary-volume-group-tags.png#lightbox)
+    [ ![Screenshot that shows the Tags section of the Volume Group tab.](./media/application-volume-group-add-volume-secondary/application-secondary-volume-group-tags.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-volume-group-tags.png#lightbox)
 
 6. The **Volumes** tab displays information about the volumes that are being created.  
 
     The volume naming convention includes an `"HA-"` prefix to indicate that the volume belongs to the secondary system of an HSR setup.
 
-    [ ![Screenshot that shows the Volume Group tab.](../media/azure-netapp-files/application-secondary-volumes-tags.png) ](../media/azure-netapp-files/application-secondary-volumes-tags.png#lightbox)
+    [ ![Screenshot that shows the Volume Group tab.](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tags.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tags.png#lightbox)
 
 7. In the **Volumes** tab, you can select each volume to view or change the volume details, including the protocol and tag for the volume.
 
     In the **Tags** section of a volume, you can populate the `HSRPartnerStorageResourceId` tag with the resource ID of the corresponding primary volume. This action only marks the primary volume; it does not validate the provided resource ID.
 
-    [ ![Screenshot that shows the tag details.](../media/azure-netapp-files/application-secondary-volumes-tag-details.png) ](../media/azure-netapp-files/application-secondary-volumes-tag-details.png#lightbox)
+    [ ![Screenshot that shows the tag details.](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tag-details.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tag-details.png#lightbox)
 
     Click **Volumes** to return to the Volumes overview page.  
 

articles/azure-netapp-files/application-volume-group-delete.md

@@ -20,11 +20,11 @@ This article describes how to delete an application volume group.
 
 1. Click **Application volume groups**. Select the volume group you want to delete.
 
-    [![Screenshot that shows Application Volume Groups list.](../media/azure-netapp-files/application-volume-group-list.png) ](../media/azure-netapp-files/application-volume-group-list.png#lightbox)
+    [![Screenshot that shows Application Volume Groups list.](./media/application-volume-group-delete/application-volume-group-list.png) ](./media/application-volume-group-delete/application-volume-group-list.png#lightbox)
 
 2. To delete the volume group, click **Delete**. If you are prompted, type the volume group name to confirm the deletion.  
 
-    [![Screenshot that shows Application Volume Groups deletion.](../media/azure-netapp-files/application-volume-group-delete.png)](../media/azure-netapp-files/application-volume-group-delete.png#lightbox) 
+    [![Screenshot that shows Application Volume Groups deletion.](./media/application-volume-group-delete/application-volume-group-delete.png)](./media/application-volume-group-delete/application-volume-group-delete.png#lightbox) 
 
 ## Next steps