Skip to content

Commit 7f9c95a

Browse files
authored
Update link to Azure guidance for secure isolation
adding relative link
1 parent b4d6b28 commit 7f9c95a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/storage/file-sync/file-sync-planning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Each Windows Server can only be registered to one Storage Sync Service. After re
5959

6060
When designing Azure File Sync topologies, ensure that you isolate data clearly at the Storage Sync Service level. For example, if your enterprise requires separate Azure File Sync environments for two distinct business units, and you need strict data isolation between these groups, you should create a dedicated Storage Sync Service for each group. Avoid placing sync groups for both business groups within the same Storage Sync Service, as that would not ensure complete isolation.
6161

62-
For additional guidance on data isolation using separate subscriptions or resource groups in Azure, refer to the following Azure documentation: Review the [Azure guidance for secure isolation](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#resource-scope-and-lifecycle) for more details.
62+
For additional guidance on data isolation using separate subscriptions or resource groups in Azure, refer to the following Azure documentation: Review the [Azure guidance for secure isolation](/azure/azure-resource-manager/management/resource-providers-and-types#resource-scope-and-lifecycle) for more details.
6363

6464
## Plan for balanced sync topologies
6565

0 commit comments

Comments
 (0)