diff --git a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md
index 3aaa73d650..b431ede6ef 100644
--- a/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md
+++ b/deploy-manage/tools/snapshot-and-restore/access-isolation-for-found-snapshots-repository.md
@@ -6,10 +6,16 @@ applies_to:
 
 # Access isolation for the found-snapshots repository [ec-snapshot-repository-migration]
 
-::::{note} 
-The guides in this section are only relevant for some deployments. Any newly created deployment will have access isolation set up by default. If a deployment’s repository can be updated, a notification will show up in the deployments menu under **Elasticsearch** > **Snapshots**.
-::::
+In {{ech}}, access isolation ensures that each deployment can access only its own snapshots, preventing accidental or unauthorized access to backups from other deployments within the same organization.
 
+Any newly created deployment has snapshot isolation set up by default. The guides in these section apply only to older deployments created before this default was implemented, where deployments within the same region may still have access to each other’s snapshots.
+
+If a deployment can access the snapshots of other deployments, a notification will appear in the deployments menu under **Elasticsearch > Snapshots**, prompting you to set up access isolation.
+
+The process for enabling access isolation depends on your cloud provider:
+
+* [Azure deployments](/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-aws-gcp.md)
+* [AWS & GCP deployments](/deploy-manage/tools/snapshot-and-restore/repository-isolation-on-azure.md)