diff --git a/content/en/docs/deployment/mx-azure/mx-azure-backups.md b/content/en/docs/deployment/mx-azure/mx-azure-backups.md
index 60e76a5091b..61353b5e3b6 100644
--- a/content/en/docs/deployment/mx-azure/mx-azure-backups.md
+++ b/content/en/docs/deployment/mx-azure/mx-azure-backups.md
@@ -65,6 +65,10 @@ To delete a backup snapshot, perform the following steps:
 
 ## Restoring a Backup Snapshot {#restore-backup}
 
+{{% alert color="warning" %}} 
+Restoring a backup is only supported within the same cluster. For the workaround to restore backups across clusters, see [Known Limitations](#known-limitations).
+{{% /alert %}}
+
 {{% alert color="info" %}} 
 Restore requires **Manage Apps Backups** and **Stop Apps** permissions on the namespace. 
 {{% /alert %}}
@@ -135,8 +139,15 @@ Automatic backups only run when the app is deployed.
 
 If the first nightly backup occurs after the first Sunday, no monthly backup will be retained that month. Download a nightly or weekly backup to extend retention.
 
-## Known Limitations
+## Known Limitations {#known-limitations}
 
 * Partial data restoration may occur if a restore process fails.
 * No API support exists currently for backup and restore.
-* Although the portal UI suggests cross-namespace restores, only restores within the same namespace are supported.
+* Although the portal UI suggests that cross-cluster backup restorations are, only restorations within the same cluster are actually supported.
+
+As a workaround, you can restore a backup across clusters by performing the following steps:
+
+1. Download the backup snapshot from your source environment to your local machine.
+2. Upload the downloaded backup snapshot from your local machine to the target environment.
+3. Begin the restore process within the target environment using the newly uploaded backup snapshot.
+