Limitation of Data Factory portal endpoint

Question

"Currently, there's only one Data Factory portal endpoint, so there's only one private endpoint for the portal in a DNS zone. Attempting to create a second or subsequent portal private endpoint overwrites the previously created private DNS entry for portal." Is there any work around of this limitation?

Answer 1

@JayaPriya - Thanks for the question and using MS Q&A platform.

There is no workaround for this limitation. Currently, there can only be one private endpoint for the Data Factory portal endpoint in a DNS zone. If you attempt to create a second or subsequent portal private endpoint, it will overwrite the previously created private DNS entry for the portal.

For more details, refer to Azure Private Link for Azure Data Factory.

Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Instead of relying on Azure default private DNS zone, you can manage your own DNS service. By doing so, you can have more control over how DNS names are resolved and handle multiple private endpoints. However, this would require configuring your own DNS server to manage the portal private DNS entries across different networks.

If you need multiple private endpoints for the Azure Data Factory portal, consider setting up separate virtual networks (VNets) for each endpoint. Since each VNet would have its own private DNS zone, this would prevent the overwriting of DNS entries.