You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/key-vault/private-link-service.md
+17-18Lines changed: 17 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Azure Private Link Service enables you to access Azure Services (for example, Az
15
15
16
16
An Azure Private Endpoint is a network interface that connects you privately and securely to a service powered by Azure Private Link. The private endpoint uses a private IP address from your VNet, effectively bringing the service into your VNet. All traffic to the service can be routed through the private endpoint, so no gateways, NAT devices, ExpressRoute or VPN connections, or public IP addresses are needed. Traffic between your virtual network and the service traverses over the Microsoft backbone network, eliminating exposure from the public Internet. You can connect to an instance of an Azure resource, giving you the highest level of granularity in access control.
17
17
18
-
For more information, see [What is Azure Private Link (Preview)?](../private-link/private-link-overview.md).
18
+
For more information, see [What is Azure Private Link (Preview)?](../private-link/private-link-overview.md)
19
19
20
20
## Prerequisites
21
21
@@ -30,18 +30,17 @@ Your private endpoint and virtual network must be in the same region. When you s
30
30
31
31
Your private endpoint uses a private IP address in your virtual network.
32
32
33
-
## Create a private link connection to key vault
33
+
## Establish a private link connection to key vault
34
34
35
-
First, create a Virtual Network by following the steps in [Create a virtual network using the Azure portal](../virtual-network/quick-create-portal
36
-
.md)
35
+
First, create a virtual network by following the steps in [Create a virtual network using the Azure portal](../virtual-network/quick-create-portal.md)
37
36
38
-
You can either create a new key vault and create a private link connection, or create a private link connection to an existing key vault.
37
+
You can then either create a new key vault, or establish a private link connection to an existing key vault.
39
38
40
-
### Create a new key vault and create a private link connection
39
+
### Create a new key vault and establish a private link connection
41
40
42
41
You can create a new key Vault by following the steps in [Set and retrieve a secret from Azure Key Vault using the Azure portal](quick-create-portal.md)
43
42
44
-
After configuring vault basics, select the Networking tab and follow these steps:
43
+
After configuring the key vault basics, select the Networking tab and follow these steps:
45
44
46
45
1. Select the Private Endpoint (preview) radio button in the Networking tab.
47
46
1. Click the "+ Add" Button to add a private endpoint.
@@ -52,17 +51,16 @@ After configuring vault basics, select the Networking tab and follow these steps
52
51
1. In the "Name" field, create a descriptive name that will allow you to identify this private endpoint.
53
52
1. Select the virtual network and subnet you want this private endpoint to be created in from the dropdown menu.
54
53
1. Leave the "integrate with the private zone DNS" option unchanged.
55
-
1. Select "Ok"
54
+
1. Select "Ok".
56
55
57
-

56
+

58
57
59
-
60
58
You will now be able to see the configured private endpoint. You now have the option to delete and edit this private endpoint.
61
59
Select the "Review + Create" button and create the key vault. It will take approximately 5-10 minutes for the deployment to complete.
62
60
63
-
### Create a private link connection to an existing key vault
61
+
### Establish a private link connection to an existing key vault
64
62
65
-
If you already have a key vault, you can create a private link connection to it by following these steps:
63
+
If you already have a key vault, you can create a private link connection by following these steps:
66
64
67
65
1. Sign in to the Azure portal.
68
66
1. In the search bar, type in "key vaults"
@@ -76,14 +74,14 @@ If you already have a key vault, you can create a private link connection to it
76
74
77
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.
78
76
79
-

80
-

77
+

78
+

81
79
82
80
## Manage Private Link Connection
83
81
84
-
When you create a private endpoint, the connection must be approved. If the resource you are creating a private endpoint for is in your directory, you will be able to approve the connection request provided you have sufficient permissions. If you are connecting to an Azure resource in another directory, you must wait for the owner of that resource to approve your connection request.
82
+
When you create a private endpoint, the connection must be approved. If the resource for which you are creating a private endpoint is in your directory, you will be able to approve the connection request provided you have sufficient permissions; if you are connecting to an Azure resource in another directory, you must wait for the owner of that resource to approve your connection request.
85
83
86
-
What do the various provisioning states mean?
84
+
There are four provisioning states:
87
85
88
86
| Service Provide Action | Service Consumer Private Endpoint State | Description |
89
87
|--|--|--|
@@ -107,12 +105,13 @@ What do the various provisioning states mean?
107
105
108
106
## Validate that the private link connection works
109
107
110
-
The purpose of this test is to make sure that resources within the same subnet of the private endpoint resource are connecting to your key vault over a private IP address and have the correct private DNS zone integration.
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.
111
109
112
110
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)
113
111
114
112
In the "Networking" tab:
115
-
1. Specify Virtual network and Subnet. You can create a new Vnet or selecting an existing one. For selecting an existing one, make sure the region matches else it won’t show up.
113
+
114
+
1. Specify Virtual network and Subnet. You can create a new virtual network or select an existing one. If selecting an existing one, make sure the region matches.
116
115
1. Specify a Public IP resource.
117
116
1. In the "NIC network security group", select "None".
0 commit comments