Merge pull request #311058 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-29 12:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-netapp-files/modify-active-directory-connections.md

@@ -44,7 +44,7 @@ For more information, see [Understand guidelines for Active Directory Domain Ser
 | Username | Username of the Active Directory domain administrator | Yes | None* | Credential change to contact DC |
 | Password | Password of the Active Directory domain administrator | Yes | None* <br></br> Password can't exceed 64 characters. | Credential change to contact DC |
 | Kerberos Realm: AD Server Name | The name of the Active Directory machine. This option is only used when creating a Kerberos volume.  | Yes | None* | |
-| Kerberos Realm: KDC IP | Specifies the IP address of the Kerberos Distribution Center (KDC) server. KDC in Azure NetApp Files is an Active Directory server. You can only modify a KDC IP by editing the AD setting. | Yes | None | A new KDC IP address will be used |
+| Kerberos Realm: KDC IP | Specifies the IP address of the Kerberos Distribution Center (KDC) server. KDC in Azure NetApp Files is an Active Directory server. You can only modify a KDC IP by editing the AD setting. | Yes | ANF requires DNS SRV records to discover the authoritative Key Distribution Centre (KDC) for the domain. Before changing the KDC IP addresses, ensure that the DNS SRV records exist for new KDC. | A new KDC IP address will be used |
 | Region | The region where the Active Directory credentials are associated | No | None | N/A |
 | User DN | User domain name, which overrides the base DN for user lookups Nested userDN can be specified in `OU=subdirectory, OU=directory, DC=domain, DC=com` format.​ | Yes | None* | User search scope gets limited to User DN instead of base DN. |
 | Group DN | Group domain name. groupDN overrides the base DN for group lookups. Nested groupDN can be specified in `OU=subdirectory, OU=directory, DC=domain, DC=com` format.​ | Yes | None* | Group search scope gets limited to Group DN instead of base DN. |

articles/azure-netapp-files/troubleshoot-volumes.md

@@ -6,7 +6,7 @@ author: b-hchen
 ms.service: azure-netapp-files
 ms.custom:
 ms.topic: troubleshooting
-ms.date: 01/28/2025
+ms.date: 01/12/2026
 ms.author: anfdocs
 # Customer intent: "As a system administrator, I want to troubleshoot volume errors for Azure NetApp Files, so that I can ensure reliable performance and resolve issues effectively."
 ---
@@ -49,6 +49,7 @@ If a volume create-read-update-delete (CRUD) operation is performed on a volume
 |`Hostname lookup failed`  	| You need to create a reverse lookup zone on the DNS server, and then add a PTR record of the AD host machine in that reverse lookup zone. <br> For example, assume that the IP address of the AD machine is `10.1.1.4`, the hostname of the AD machine (as found by using the hostname command) is `AD1`, and the domain name is `contoso.com`. The PTR record added to the reverse lookup zone should be `10.1.1.4 -> AD1.contoso.com`. |
 |`Volume creation fails due to unreachable DNS server`  | Two possible solutions are available: <br> <ul><li> This error indicates that DNS isn't reachable. The cause can be an incorrect DNS IP or a networking issue. Check the DNS IP entered in the AD connection and make sure that the IP is correct. </li> <li> If you're using Basic network features, ensure that the AD and the volume are in same region and in same VNet. If they are in different VNets, ensure that VNet peering is established between the two VNets. <br> See [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md#azure-native-environments) for details. </li></ul> |
 |NFSv4.1 Kerberos volume creation fails with an error similar to the following example: <br> `Failed to enable NFS Kerberos on LIF "svm_e719cde8d6d0413fbd6adac0636cdecb_7ad0b82e_73349613". Failed to bind service principal name on LIF "svm_e719cde8d6d0413fbd6adac0636cdecb_7ad0b82e_73349613". SecD Error: server create fail join user auth.`	|The KDC IP is wrong and the Kerberos volume has been  created. Update the KDC IP with a correct address. <br> You need to re-create the volume. |
+|`The KDC IP or AD Name operation fails because the Service Principal Name (SPN) already exists` | <ol><li> Navigate to **Active Directory Users and Computers** from the Server Manager. </li> <li> Delete the NFS machine account and change the KDC IP. <br> You can locate the required NFS machine account for this volume by referring to the mount instructions where the mount path is specified. <br> Example mount instruction: `sudo mount -vvv -t nfs -o sec=krb5,rw,hard,rsize=262144,wsize=262144,vers=4.1,tcp DHR-4EC7.contoso.com:/kerb-vol kerb-vol` <br> In this example, the machine account name is NFS-DHR-4EC7.</li>|
 
 ## Errors for LDAP volumes
 

articles/backup/backup-azure-sap-hana-database.md

@@ -2,7 +2,7 @@
 title: Back up an SAP HANA database to Azure with Azure Backup 
 description: In this article, learn how to back up an SAP HANA database to Azure virtual machines with the Azure Backup service.
 ms.topic: how-to
-ms.date: 01/09/2026
+ms.date: 01/29/2026
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -142,49 +142,52 @@ At the Recovery Services vault, you can enable Cross Region Restore. Learn [how
 
 ## Discover the databases
 
-1. In the Azure portal, go to **Backup center** and select **+Backup**.
+1. In the [Azure portal](https://portal.azure.com/), go to **Resiliency** and select **+Configure protection**.
 
-   :::image type="content" source="./media/backup-azure-sap-hana-database/backup-center-configure-inline.png" alt-text="Screenshot showing to start checking for SAP HANA databases." lightbox="./media/backup-azure-sap-hana-database/backup-center-configure-expanded.png":::
+1. On the **Configure protection** pane, select **Datasource type** as **SAP HANA in Azure VM**, and then select **Continue**.
 
-1. Select **SAP HANA in Azure VM** as the datasource type, select a Recovery Services vault to use for backup, and then select **Continue**.
+   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-select-datasource-type.png" alt-text="Screenshot that shows the selection of SAP HANA in Azure VM as datasource type.":::
 
-   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-select-vault.png" alt-text="Screenshot showing to select an SAP HANA database in Azure VM.":::
+1. On the **Start: Configure Backup** pane, for **Vault** selection, click **Select vault** to use for backup, and then select **Continue**.
 
-1. Select **Start Discovery**. This initiates discovery of unprotected Linux VMs in the vault region.
+   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-select-vault.png" alt-text="Screenshot that shows the selection of a Recovery Services vault for SAP HANA database backup.":::
+
+1. On the **Backup Goal** pane, select **Start Discovery**. This initiates discovery of unprotected Linux VMs in the vault region.
 
    * After discovery, unprotected VMs appear in the portal, listed by name and resource group.
    * If a VM isn't listed as expected, check whether it's already backed up in a vault.
    * Multiple VMs can have the same name but they belong to different resource groups.
 
-   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-discover-databases.png" alt-text="Screenshot showing to select Start Discovery.":::
+   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-discover-databases.png" alt-text="Screenshot that shows how to select Start Discovery.":::
 
 1. In **Select Virtual Machines**, select the link to download the script that provides permissions for the Azure Backup service to access the SAP HANA VMs for database discovery.
 1. Run the script on each VM hosting SAP HANA databases that you want to back up.
 1. After running the script on the VMs, in **Select Virtual Machines**, select the VMs. Then select **Discover DBs**.
 1. Azure Backup discovers all SAP HANA databases on the VM. During discovery, Azure Backup registers the VM with the vault, and installs an extension on the VM. No agent is installed on the database.
 
-   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-select-virtual-machines-inline.png" alt-text="Screenshot showing the discovered SAP HANA databases." lightbox="./media/backup-azure-sap-hana-database/hana-select-virtual-machines-expanded.png":::
+   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-select-virtual-machines.png" alt-text="Screenshot that shows the discovered SAP HANA databases." lightbox="./media/backup-azure-sap-hana-database/hana-select-virtual-machines.png":::
 
 ## Configure backup  
 
 Now enable backup.
 
 1. In Step 2, select **Configure Backup**.
 
-   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-configure-backups.png" alt-text="Screenshot showing to configure Backup.":::
+   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-configure-backups.png" alt-text="Screenshot that shows the configuration of Backup.":::
 
-2. In **Select items to back up**, select all the databases you want to protect > **OK**.
+2. On the **Select items to back up** pane, select all the databases you want to protect > **OK**.
 
-   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-select-databases-inline.png" alt-text="Screenshot showing to select databases to back up." lightbox="./media/backup-azure-sap-hana-database/hana-select-databases-expanded.png":::
+   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-select-databases.png" alt-text="Screenshot that shows how to select databases to back up." lightbox="./media/backup-azure-sap-hana-database/hana-select-databases.png":::
 
-3. In **Backup Policy** > **Choose backup policy**, create a new backup policy for the databases, in accordance with the instructions below.
+3. For **Backup Policy**, choose a backup policy, or create a new backup policy for the databases, in accordance with the instructions below.
 
-   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-policy-summary.png" alt-text="Screenshot showing to choose backup policy.":::
+   :::image type="content" source="./media/backup-azure-sap-hana-database/hana-policy-summary.png" alt-text="Screenshot that shows the selection of a backup policy.":::
 
 4. After creating the policy, on the **Backup** menu, select **Enable backup**.
 
-    ![Enable backup](./media/backup-azure-sap-hana-database/enable-backup.png)
-5. Track the backup configuration progress in the **Notifications** area of the portal.
+    ![Screenshot showing how to enable backup.](./media/backup-azure-sap-hana-database/enable-backup.png)
+
+You can track the backup configuration progress in the **Notifications** area of the portal.
 
 ### Create a backup policy