Skip to content

Commit cb6105d

Browse files
committed
Addressed acrolync feedback
1 parent c5ce1ab commit cb6105d

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/key-vault/private-link-service.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Integrate with Azure Private Link Service
3-
description: Learn how to integrate Azure Key Vaulk with Azure Private Link Service
3+
description: Learn how to integrate Azure Key Vault with Azure Private Link Service
44
author: msmbaldwin
55
ms.author: mbaldwin
66
ms.date: 01/28/2020
@@ -56,23 +56,23 @@ After configuring the key vault basics, select the Networking tab and follow the
5656
![Image](./media/private-link-service-2.png)
5757

5858
You will now be able to see the configured private endpoint. You now have the option to delete and edit this private endpoint.
59-
Select the "Review + Create" button and create the key vault. It will take approximately 5-10 minutes for the deployment to complete.
59+
Select the "Review + Create" button and create the key vault. It will take 5-10 minutes for the deployment to complete.
6060

6161
### Establish a private link connection to an existing key vault
6262

6363
If you already have a key vault, you can create a private link connection by following these steps:
6464

6565
1. Sign in to the Azure portal.
6666
1. In the search bar, type in "key vaults"
67-
1. Select the key vault which you want to add a private endpoint to from the list.
67+
1. Select the key vault from the list to which you want to add a private endpoint.
6868
1. Select the "Networking" tab under Settings
6969
1. Select the Private endpoint connections (preview) tab at the top of the page
7070
1. Select the "+ Private Endpoint" button at the top of the page.
7171

7272
![Image](./media/private-link-service-3.png)
7373
![Image](./media/private-link-service-4.png)
7474

75-
Please note, you can choose to create a private endpoint for any Azure resource in using this blade. You can either use the dropdown menus to select a resource type and select a resource in your directory, or you can connect to any Azure resource using a resource ID. Leave the "integrate with the private zone DNS" option unchanged.
75+
You can choose to create a private endpoint for any Azure resource in using this blade. You can either use the dropdown menus to select a resource type and select a resource in your directory, or you can connect to any Azure resource using a resource ID. Leave the "integrate with the private zone DNS" option unchanged.
7676

7777
![Image](./media/private-link-service-3.png)
7878
![Image](./media/private-link-service-4.png)
@@ -88,13 +88,13 @@ There are four provisioning states:
8888
| None | Pending | Connection is created manually and is pending approval from the Private Link resource owner. |
8989
| Approve | Approved | Connection was automatically or manually approved and is ready to be used. |
9090
| Reject | Rejected | Connection was rejected by the private link resource owner. |
91-
| Remove | Disconnected | Connection was removed by the private link resource owner, the private endpoint becomes informative and should be deleted for clean up. |
91+
| Remove | Disconnected | Connection was removed by the private link resource owner, the private endpoint becomes informative and should be deleted for cleanup. |
9292

93-
### How to manage a private endpoint connections to key vault
93+
### How to manage a private endpoint connection to key vault
9494

95-
1. Log in to the Azure Portal.
95+
1. Log in to the Azure portal.
9696
1. In the search bar, type in "key vaults"
97-
1. Select the key vault which you want to manage.
97+
1. Select the key vault that you want to manage.
9898
1. Select the "Networking" tab.
9999
1. If there are any connections that are pending, you will see a connection listed with "Pending" in the provisioning state.
100100
1. Select the private endpoint you wish to approve
@@ -105,7 +105,7 @@ There are four provisioning states:
105105

106106
## Validate that the private link connection works
107107

108-
You should now validate that the resources within the same subnet of the private endpoint resource are connecting to your key vault over a private IP address, and that they have the correct private DNS zone integration.
108+
You should validate that the resources within the same subnet of the private endpoint resource are connecting to your key vault over a private IP address, and that they have the correct private DNS zone integration.
109109

110110
First, create a virtual machine by following the steps in [Create a Windows virtual machine in the Azure portal](../virtual-machines/windows/quick-create-portal.md)
111111

@@ -147,7 +147,7 @@ Aliases: <your-key-vault-name>.vault.azure.net
147147

148148
## Limitations and Design Considerations
149149

150-
**Pricing:**: For pricing information, see [Azure Private Link (preview) pricing](https://azure.microsoft.com/pricing/details/private-link/).
150+
**Pricing**: For pricing information, see [Azure Private Link (preview) pricing](https://azure.microsoft.com/pricing/details/private-link/).
151151

152152
**Limitations**: Private Endpoint for Azure Key Vault is in public preview. This feature is available in all Azure public regions.
153153

0 commit comments

Comments
 (0)