Skip to content

Commit 758042f

Browse files
author
Michael Bender
committed
small fixes to style and layout
1 parent f44c80a commit 758042f

File tree

2 files changed

+41
-41
lines changed

2 files changed

+41
-41
lines changed

articles/private-link/create-network-security-perimeter-cli.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ Get started with network security perimeter by creating a network security perim
1919

2020
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
2121
- The [latest Azure CLI](/cli/azure/install-azure-cli), or you can use Azure Cloud Shell in the portal.
22-
- This article requires version 2.38.0 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
23-
- After upgrading to the latest version, you can import the network security perimeter commands using `az extension add --name nsp`.
24-
- Re-register the Microsoft.Network resource provider with the following command:
22+
- This article **requires version 2.38.0 or later** of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
23+
- After upgrading to the latest version of Azure CLI, import the network security perimeter commands using `az extension add --name nsp`.
24+
- Re-register the `Microsoft.Network` resource provider with the following command:
2525

2626
```azure
2727
az provider register --namespace Microsoft.Network
@@ -30,7 +30,6 @@ Get started with network security perimeter by creating a network security perim
3030
[!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
3131
3232
33-
3433
[!INCLUDE [network-security-perimeter-add-preview](../../includes/network-security-perimeter-add-preview.md)]
3534
3635

articles/private-link/create-network-security-perimeter-powershell.md

Lines changed: 38 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,10 @@ Get started with network security perimeter by creating a network security perim
2222
[!INCLUDE [network-security-perimeter-add-preview](../../includes/network-security-perimeter-add-preview.md)]
2323

2424
- The latest version of the Azure PowerShell module with tools for network security perimeter.
25-
```azurepowershell
26-
Install-Module -Name Az.Tools.Installer -Repository PSGallery
27-
```
25+
26+
```azurepowershell
27+
Install-Module -Name Az.Tools.Installer -Repository PSGallery
28+
```
2829
2930
- Use `Az.Tools.Installer` to install the preview build of the `Az.Network`:
3031
@@ -121,47 +122,47 @@ In this step, you create a new profile and associate the PaaS resource, the Azur
121122

122123
1. Create a new profile for your network security perimeter with the following command:
123124

124-
```azurepowershell-interactive
125-
# Create a new profile
126-
127-
$nspProfile = @{
128-
Name = 'nsp-profile'
129-
ResourceGroupName = $rgParams.name
130-
SecurityPerimeterName = $nsp.name
131-
}
132-
133-
$demoProfileNSP=New-AzNetworkSecurityPerimeterProfile @nspprofile
134-
```
125+
```azurepowershell-interactive
126+
# Create a new profile
127+
128+
$nspProfile = @{
129+
Name = 'nsp-profile'
130+
ResourceGroupName = $rgParams.name
131+
SecurityPerimeterName = $nsp.name
132+
}
133+
134+
$demoProfileNSP=New-AzNetworkSecurityPerimeterProfile @nspprofile
135+
```
135136
136137
2. Associate the Azure Key Vault (PaaS resource) with the network security perimeter profile with the following command:
137138
138-
```azurepowershell-interactive
139-
# Associate the PaaS resource with the above created profile
139+
```azurepowershell-interactive
140+
# Associate the PaaS resource with the above created profile
141+
142+
$nspAssociation = @{
143+
AssociationName = 'nsp-association'
144+
ResourceGroupName = $rgParams.name
145+
SecurityPerimeterName = $nsp.name
146+
AccessMode = 'Learning'
147+
ProfileId = $demoProfileNSP.Id
148+
PrivateLinkResourceId = $keyVault.ResourceID
149+
}
140150
141-
$nspAssociation = @{
142-
AssociationName = 'nsp-association'
143-
ResourceGroupName = $rgParams.name
144-
SecurityPerimeterName = $nsp.name
145-
AccessMode = 'Learning'
146-
ProfileId = $demoProfileNSP.Id
147-
PrivateLinkResourceId = $keyVault.ResourceID
148-
}
149-
150-
New-AzNetworkSecurityPerimeterAssociation @nspassociation | format-list
151-
```
151+
New-AzNetworkSecurityPerimeterAssociation @nspassociation | format-list
152+
```
152153
153154
3. Update association by changing the access mode to `enforced` with the `Update-AzNetworkSecurityPerimeterAssociation` command as follows:
154155
155-
```azurepowershell-interactive
156-
# Update the association to enforce the access mode
157-
$updateAssociation = @{
158-
AssociationName = $nspassociation.AssociationName
159-
ResourceGroupName = $rgParams.name
160-
SecurityPerimeterName = $nsp.name
161-
AccessMode = 'Enforced'
162-
}
163-
Update-AzNetworkSecurityPerimeterAssociation @updateAssociation | format-list
164-
```
156+
```azurepowershell-interactive
157+
# Update the association to enforce the access mode
158+
$updateAssociation = @{
159+
AssociationName = $nspassociation.AssociationName
160+
ResourceGroupName = $rgParams.name
161+
SecurityPerimeterName = $nsp.name
162+
AccessMode = 'Enforced'
163+
}
164+
Update-AzNetworkSecurityPerimeterAssociation @updateAssociation | format-list
165+
```
165166
166167
## Create and update network security perimeter access rules
167168

0 commit comments

Comments
 (0)