Skip to content

Commit a54fed2

Browse files
authored
Update how-to-set-up-private-links.md
Add details of multiple private endpoints
1 parent 60c134f commit a54fed2

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

articles/energy-data-services/how-to-set-up-private-links.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -155,6 +155,20 @@ Use the following steps to create a private endpoint for an existing Azure Data
155155
>
156156
> [![Screenshot that shows options for rejecting or approving a request to create a private endpoint.](media/how-to-manage-private-links/private-links-10-awaiting-approval.png)](media/how-to-manage-private-links/private-links-10-awaiting-approval.png#lightbox)
157157
158+
## Manage multiple endpoints in the same virtual network
159+
### Access via IP vs DNS
160+
In the same virtual network, you can create multiple endpoints. Each end point will have a different IP. It is not possible to resolve one host name with two difference IPs.
161+
- If you access the resource via IP:
162+
- The resource will be accessible only via the latest private IP address.
163+
- All the previous private IPs in the same vnet will become dangling.
164+
- Even when you delete the latest IP, all the previous IPs still remain dangling.
165+
- If you access via DNS name: You wont see any difference.
166+
167+
### Know which endpoint the resource is connected to
168+
1. Go to any of the private endpoints, to the DNS configuration, and to Private DNS Zone associated with ADME resource. [![Screenshot that shows DNS Config.](media/how-to-manage-private-links/private-links-11-dns-config.png)](media/how-to-manage-private-links/private-links-11-dns-config.png#lightbox)
169+
2. In the private DNS zone, check the IP associated with the entry for your Azure Data Manager for Energy instance. [![Screenshot that shows DNS Zone.](media/how-to-manage-private-links/private-links-12-dns-zone.png)](media/how-to-manage-private-links/private-links-12-dns-zone.png#lightbox)
170+
3. This is the IP to which your resource is connected to.
171+
158172
## Next steps
159173
<!-- Add a context sentence for the following links -->
160174
To learn more about using Customer Lockbox as an interface to review and approve or reject access requests.

0 commit comments

Comments
 (0)