Skip to content

Commit 02cceba

Browse files
committed
step numbers
1 parent 6b90be5 commit 02cceba

1 file changed

Lines changed: 1 addition & 4 deletions

File tree

articles/api-management/using-network-security-perimeter.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,6 @@ A network security perimeter provides a supported, centralized perimeter to expl
4545

4646
1. Add an inbound access rule to allow API Management traffic.
4747

48-
1. Test the API call from API Management to confirm access with network security perimeter.
49-
5048
1. Move network security perimeter access mode from **transition** to **enforced**.
5149

5250
## Step 1. Configure API Management to call Azure Storage by using managed identity
@@ -130,7 +128,6 @@ Test that the API operation can no longer reach the storage account.
130128
Expected result:
131129
- The call fails with a `403 Forbidden` response.
132130

133-
134131
## Step 3. Create a network security perimeter profile and associate the storage account
135132

136133
1. In the Azure portal, search for **Network Security Perimeters** and select it.
@@ -165,7 +162,7 @@ To allow API Management to reach the storage account through the perimeter, add
165162

166163
:::image type="content" source="media/using-network-security-perimeter/public-access-settings.png" alt-text="Screenshot of public access settings in the storage account in the portal.":::
167164

168-
## Step 5. Test access from API Management
165+
### Test the API operation
169166

170167
Test that the API operation can reach the storage account in the network security perimeter.
171168

0 commit comments

Comments
 (0)