Azure Backup – 'Last Refreshed At' Stuck on Old Timestamp

Hi, it's (almost certainly) a metadata/portal issue, not a backup issue: with MARS, the "Last Refreshed At / Latest Backup Start Time" time shows the last status refresh the agent sent to the vault, while the Recovery Points and Success status prove that the jobs are running. To realign it: 1) on the server, open the Microsoft Azure Recovery Services (MARS) Agent, verify you have the latest version (update if necessary), and restart the "Microsoft Azure Recovery Services Agent" service; run a short Back Up Now (even just a test folder). 2) In the portal, on the vault → Backup items → Azure Backup Agent → select the item → Refresh at the top and wait 15–60 minutes for the indicator to update. 3) If it remains blocked, perform a "Renew vault credentials" from the MARS Agent (do not unregister): download a new .vaultcredentials file from the vault and use the "Update/Renew" procedure to re-establish the reporting channel. 4) Check that the proxy/firewall allows the agent to exit to the Azure Backup endpoints (if blocked, jobs can complete but the "refresh" does not arrive). 5) Check the real-time times via PowerShell: Get-AzRecoveryServicesBackupJob and Get-AzRecoveryServicesBackupItem (if everything is updated here, it is only the UI). If after these steps the time remains unchanged, open an Azure Backup ticket attaching the Vault name/region, Backup Item, Job ID, and the incorrect time: this is a known portal discrepancy that Microsoft can fix on the backend.