Merge pull request #299012 from ankitaduttaMSFT/TS2904

AAD tenant ID

Author: prmerger-automator[bot]

articles/site-recovery/azure-to-azure-troubleshoot-replication.md

@@ -1,11 +1,10 @@
 ---
 title: Troubleshoot replication of Azure VMs with Azure Site Recovery
-description: Troubleshoot replication in Azure VM disaster recovery with Azure Site Recovery
+description: Troubleshoot replication in Azure VM disaster recovery with Azure Site Recovery.
 author: ankitaduttaMSFT
 ms.author: ankitadutta
-manager: rochakm
 ms.topic: troubleshooting
-ms.date: 09/04/2024
+ms.date: 05/07/2025
 ms.service: azure-site-recovery
 ms.custom: engagement-fy23
 ---
@@ -102,7 +101,7 @@ Following are some of the most common issues.
 
 ### Known issue in SQL Server 2016 and 2017
 
-**How to fix**: Refer to the article [Cumulative Update 16 for SQL Server 2017](https://support.microsoft.com/help/4508218/cumulative-update-16-for-sql-server-2017).
+**How to fix**: Cumulative Update 16 for SQL Server 2017.
 
 ### You're using Azure Storage Spaces Direct Configuration
 
@@ -164,6 +163,33 @@ Restart the following services:
 - Azure Site Recovery VSS Provider.
 - VDS service.
 
+#### Update TenantId and ClientId manually in source machine
+
+**How to fix**: To fix no Mobility Service heartbeat error due to expired tenant, follow these steps:
+    
+1. Execute the **GET Protected item** API and retrieve the values for `mobilityAgentTenantIdToUpdate` and `mobilityAgentClientIdToUpdate` from the output.
+    
+      
+    ```powershell
+    GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/replicationProtectedItems/{replicatedProtectedItemName}?api-version=2025-01-01
+    ```
+1.  Open the RCMInfo.conf file on the source machine. The location of the file is as follows:
+
+   - Windows: `C:\ProgramData\Microsoft Azure Site Recovery\Config\RCMInfo.conf`
+   - Linux: `/usr/local/InMage/config/RCMInfo.conf`
+1. Update the `AADTenantId`, `AADClientId`, and tenantid of `AADAudienceUri` with the new tenant details fetched from step 1 and save the file by using the following format:
+
+   ```
+   AADTenantId=<mobilityAgentTenantIdToUpdate>
+   AADClientId=<mobilityAgentClientIdToUpdate>
+   AADAudienceUri=api://<mobilityAgentTenantIdToUpdate>/RecoveryServiceContainer/eastus2euap/1394977864085472368/3134366
+   ```
+1. Restart the following services:
+   - **Windows**: "InMage Scout VX Agent - Sentinel/Outpost", "InMage Scout Application Service"
+   - **Linux**: vxagent, appservice
+
+
+
 ## Next steps
 
 [Replicate Azure VMs to another Azure region](azure-to-azure-how-to-enable-replication.md).