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/private-link/manage-private-endpoint.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ You should receive an output similar to the below example.
69
69
70
70
## Custom properties
71
71
72
-
Network interface rename and static IP address assignment are custom properties that can be set on a private endpoint when it's created.
72
+
Network interface rename and static IP address assignment are custom properties that can be set on a private endpoint during creation.
73
73
74
74
### Network interface rename
75
75
@@ -134,7 +134,7 @@ az network private-endpoint create \
134
134
135
135
### Static IP address
136
136
137
-
By default, when a private endpoint is created the IP address for the endpoint is automatically assigned. The IP is assigned from the IP range of the virtual network configured for the private endpoint. A situation may arise when a static IP address for the private endpoint is required. The static IP address must be assigned when the private endpoint is created. The configuration of a static IP address for an existing private endpoint is currently unsupported.
137
+
By default, when a private endpoint is created the IP address for the endpoint is automatically assigned. The IP is assigned from the IP range of the virtual network configured for the private endpoint. A situation can arise when a static IP address for the private endpoint is required. The static IP address must be assigned when the private endpoint is created. The configuration of a static IP address for an existing private endpoint is currently unsupported.
138
138
139
139
For procedures to configure a static IP address when creating a private endpoint, see [Create a private endpoint using Azure PowerShell](create-private-endpoint-powershell.md) and [Create a private endpoint using the Azure CLI](create-private-endpoint-cli.md).
140
140
@@ -153,14 +153,17 @@ There are two connection approval methods that a Private Link service consumer c
153
153
-**Manual**: If the service consumer doesn’t have Azure Role Based Access Control permissions on the service provider resource, the consumer can choose the manual approval method. The connection request appears on the service resources as **Pending**. The service provider has to manually approve the request before connections can be established.
154
154
In manual cases, service consumer can also specify a message with the request to provide more context to the service provider. The service provider has following options to choose from for all private endpoint connections: **Approve**, **Reject**, **Remove**.
155
155
156
-
The below table shows the various service provider actions and the resulting connection states for private endpoints. The service provider can change the connection state at a later time without consumer intervention. The action will update the state of the endpoint on the consumer side.
156
+
> [!IMPORTANT]
157
+
> To approve connections with a private endpoint that is in a separate subscription or tenant, ensure that the provider subscription or tenant has registered **Microsoft.Network**. The consumer subscription or tenant should also have the resource provider of the destination resource registered.
158
+
159
+
The below table shows the various service provider actions and the resulting connection states for private endpoints. The service provider can change the connection state at a later time without consumer intervention. The action updates the state of the endpoint on the consumer side.
157
160
158
161
| Service provider action | Service consumer private endpoint state | Description |
159
162
|---------|---------|---------|
160
163
| None | Pending | Connection is created manually and is pending for approval by the Private Link resource owner. |
161
-
| Approve | Approved | Connection was automatically or manually approved and is ready to be used. |
162
-
| Reject | Rejected |Connection was rejected by the private link resource owner. |
163
-
| Remove | Disconnected |Connection was removed by the private link resource owner, the private endpoint becomes informative and should be deleted for clean-up. |
164
+
| Approve | Approved | Connection is automatically or manually approved and is ready to be used. |
165
+
| Reject | Rejected |The private link resource owner rejects the connection.|
166
+
| Remove | Disconnected |The private link resource owner removes the connection, causing the private endpoint to become disconnected and it should be deleted for clean-up. |
164
167
165
168
## Manage private endpoint connections on Azure PaaS resources
0 commit comments