Skip to content

Commit bc82b61

Browse files
committed
fixed note
1 parent 4f0d9f9 commit bc82b61

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -522,9 +522,6 @@ The steps required to restrict network access to resources created through Azure
522522
523523
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.
524524
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.
527-
528525
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).
529526
530527
### [CLI](#tab/cli)
@@ -561,6 +558,9 @@ The steps necessary to restrict network access to resources created through Azur
561558
562559
---
563560
561+
> [!IMPORTANT]
562+
> 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.
563+
564564
### Create a file share in the storage account
565565
566566
### [Portal](#tab/portal)

0 commit comments

Comments
 (0)