Skip to content

Commit 4f0d9f9

Browse files
committed
ropc remediation
1 parent e9da144 commit 4f0d9f9

File tree

2 files changed

+8
-4
lines changed

2 files changed

+8
-4
lines changed

articles/virtual-network/tutorial-restrict-network-access-to-resources.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -519,12 +519,13 @@ The steps required to restrict network access to resources created through Azure
519519
}
520520
$storageAcctKey = (Get-AzStorageAccountKey @storagekey).Value[0]
521521
```
522+
523+
The key is used to create a file share in a later step. Enter `$storageAcctKey` and note the value. You manually enter it in a later step when you map the file share to a drive in a virtual machine.
522524
523-
For the purposes of this tutorial, the connection string is used to connect to the storage account. Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a high degree of trust in the application, and carries risks that aren't present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
524-
525-
For more information about connecting to a storage account using a managed identity, see [Use a managed identity to access Azure Storage](/entra/identity/managed-identities-azure-resources/tutorial-linux-managed-identities-vm-access?pivots=identity-linux-mi-vm-access-storage).
525+
> [!IMPORTANT]
526+
> Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
526527
527-
The key is used to create a file share in a later step. Enter `$storageAcctKey` and note the value. You manually enter it in a later step when you map the file share to a drive in a virtual machine.
528+
For more information about connecting to a storage account using a managed identity, see [Use a managed identity to access Azure Storage](/entra/identity/managed-identities-azure-resources/tutorial-linux-managed-identities-vm-access?pivots=identity-linux-mi-vm-access-storage).
528529
529530
### [CLI](#tab/cli)
530531

articles/virtual-network/virtual-network-service-endpoint-policies.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -592,6 +592,9 @@ az storage share create \
592592

593593
---
594594

595+
> [!IMPORTANT]
596+
> Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
597+
595598
### Deny all network access to storage accounts
596599

597600
By default, storage accounts accept network connections from clients in any network. To restrict network access to the storage accounts, you can configure the storage account to accept connections only from specific networks. In this example, you configure the storage account to accept connections only from the virtual network subnet you created earlier.

0 commit comments

Comments
 (0)