Skip to content

Commit b258b22

Browse files
authored
Update wording for clarity on copy operations
Updated "secured" to "storage" account.
1 parent e9ec661 commit b258b22

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/storage/common/security-restrict-copy-operations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.custom:
1818

1919
# Restrict the source of copy operations to a storage account
2020

21-
For security reasons, storage administrators might want to limit the environments from which data can be copied to secured accounts. Limiting the scope of permitted copy operations helps prevent the infiltration of unwanted data from untrusted tenants or virtual networks.
21+
For security reasons, storage administrators might want to limit the environments from which data can be copied to storage accounts. Limiting the scope of permitted copy operations helps prevent the infiltration of unwanted data from untrusted tenants or virtual networks.
2222

2323
This article shows you how to limit the source accounts of copy operations to accounts within the same tenant as the destination account, or with private links to the same virtual network as the destination.
2424

0 commit comments

Comments
 (0)