Skip to content

Commit b858b4b

Browse files
ryepupJTorreG
andauthored
fix: remove NSP warning (#950)
remove NSP warning This note is no longer needed. From https://learn.microsoft.com/en-us/azure/private-link/network-security-perimeter-concepts: > Network security perimeter is now generally available in all Azure public cloud regions. Co-authored-by: Jon Torre <[email protected]>
1 parent fba154b commit b858b4b

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

content/nginxaas-azure/quickstart/security-controls/certificates.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -164,8 +164,6 @@ For more information on using NGINX to secure traffic to upstream servers, refer
164164

165165
If you want to disable public access to your key vault, you can configure a [Network Security Perimeter (NSP)](https://learn.microsoft.com/en-us/azure/private-link/network-security-perimeter-concepts). This will allow you to configure access rules to allow NGINXaaS to fetch certificates from your key vault while ensuring all other public access is denied.
166166

167-
{{< call-out "note" >}} Network Security Perimeter is currently in public preview. Refer to [Azure's NSP documentation](https://learn.microsoft.com/en-us/azure/private-link/network-security-perimeter-concepts) for details on its current capabilities. {{< /call-out >}}
168-
169167
1. Follow [Azure's documentation on prerequisites](https://learn.microsoft.com/en-us/azure/private-link/create-network-security-perimeter-portal#prerequisites) to ensure you are registed to create an NSP.
170168
1. In the Search box, enter **Network Security Perimeters** and select **Network Security Perimeters** from the search results.
171169
1. Select {{< fa "plus">}}**Create**.
@@ -198,4 +196,4 @@ By default, the key vault will be associated to the NSP in [Learning mode](https
198196
1. Select the `nginxaas-kv` resource association.
199197
1. Select **Change access mode**, set to **Enforced**, and select **Apply**.
200198

201-
{{< call-out "note" >}} If you are using the Azure portal to add certificates, you will also need to add an inbound access rule to allow your IP address, so the portal can list the certificates in your key vault. {{< /call-out >}}
199+
{{< call-out "note" >}} If you are using the Azure portal to add certificates, you will also need to add an inbound access rule to allow your IP address, so the portal can list the certificates in your key vault. {{< /call-out >}}

0 commit comments

Comments
 (0)