Skip to content

Commit 133e586

Browse files
author
Michael Bender
committed
updated pre-reqs
1 parent c19656a commit 133e586

File tree

3 files changed

+19
-4
lines changed

3 files changed

+19
-4
lines changed

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

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,27 @@ author: mbender-ms
55
ms.author: mbender
66
ms.service: azure-private-link
77
ms.topic: quickstart
8-
ms.date: 09/16/2024
8+
ms.date: 10/30/2024
99
#CustomerIntent: As a network administrator, I want to create a network security perimeter for an Azure resource using Azure CLI, so that I can control the network traffic to and from the resource.
1010
---
1111

12-
# Quickstart: Create a network security perimeter - Azure CLI
12+
# Quickstart: Create a network security perimeter - Azure CLI~
1313

1414
Get started with network security perimeter by creating a network security perimeter for an Azure key vault using Azure CLI. A [network security perimeter](network-security-perimeter-concepts.md) allows [Azure PaaS (PaaS)](./network-security-perimeter-concepts.md#onboarded-private-link-resources)resources to communicate within an explicit trusted boundary. Next, You create and update a PaaS resources association in a network security perimeter profile. Then you create and update network security perimeter access rules. When you're finished, you delete all resources created in this quickstart.
1515

1616
[!INCLUDE [network-security-perimeter-preview-message](../../includes/network-security-perimeter-preview-message.md)]
1717

18-
[!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment.md)]
18+
## Prerequisites
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.
2222
- This article requires version 2.38.0 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
2323
- After upgrading to the latest version, you can import the network security perimeter commands using `az extension add --name nsp`.
2424

25+
[!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
26+
27+
28+
2529
[!INCLUDE [network-security-perimeter-add-preview](../../includes/network-security-perimeter-add-preview.md)]
2630

2731

@@ -33,13 +37,18 @@ To get started, connect to [Azure Cloud Shell](https://shell.azure.com) or use y
3337
1. If you installed CLI locally, sign in with the following command:
3438

3539
```azurecli-interactive
40+
# Sign in to your Azure account
3641
az login
3742
```
3843
3944
1. Once in your shell, select your active subscription locally with the following command:
4045
4146
```azurecli-interactive
47+
# List all subscriptions
4248
az account set --subscription "Azure Subscription"
49+
50+
# Register the Microsoft.Network resource provider
51+
az provider register --namespace Microsoft.Network
4352
```
4453
4554
## Create a resource group and key vault

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,13 +53,19 @@ Install-Module -Name Az.Tools.Installer -Repository PSGallery
5353
To begin your configuration, sign in to your Azure account:
5454
5555
```azurepowershell
56+
# Sign in to your Azure account
5657
Connect-AzAccount
5758
```
5859

5960
Then, connect to your subscription:
6061

6162
```azurepowershell
63+
# List all subscriptions
6264
Set-AzContext -Subscription <subscriptionId>
65+
66+
# Register the Microsoft.Network resource provider
67+
Register-AzResourceProvider -ProviderNamespace Microsoft.Network
68+
6369
```
6470

6571
## Create a resource group and key vault

articles/private-link/network-security-perimeter-diagnostic-logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ You can store the diagnostic logs in the following locations:
4040
| **Service** | **Description** |
4141
| --- | --- |
4242
| **Log Analytic workspace** | Log Analytic workspaces are recommended since they allow you to use the predefined queries, visualizations, and set alerts based on specific log conditions. |
43-
|** Azure Storage account** | Storage accounts are best used for logs when logs are stored for a longer duration and reviewed when needed. |
43+
|**Azure Storage account** | Storage accounts are best used for logs when logs are stored for a longer duration and reviewed when needed. |
4444
| **Azure Event Hubs** | Event hubs are a great option for integrating with other security information and event management (SIEM) tools to get alerts on your resources. |
4545

4646
## Enable logging through the Azure portal

0 commit comments

Comments
 (0)