Does ASEv3 / Isolatedv2 still support Private Endpoint connectivity?

Question

Hello,

We're working on a usecase that uses the ASEv3 for isolated app-hosting, now that it has become GA. It uses an Isolatedv2 serviceplan.
The usecase takes advantage of UDR for outbound connectivity on the subnet used for the ASE.

As the ASE itself requires a sizable subnet, and we have a requirement to significantly limit (routed) IP-footprint, we are looking to use Private Endpoint for selective disclosure of apps on other subnets. Peered connectivity to the apps is successful, however, connections to ASEv3-hosted apps over PE's currently fail.

Q: Are PE's still supported for ASEv3? I can find docs on PE's used on ASEv2 but nothing yet regarding v3.

Thanks!

Answer 1

Hi @mdosolv ,

however, connections to ASEv3-hosted apps over PE's currently fail.

If you recreated your ASEv3 before 6/4, please check this guidance to see if private endpoint ASEv3 has been replaced. If it has, per the guidance, adjust your DNS entry to match the new IP. If this resolves your issue, you should've received a notification about this change. The email address it would've been sent to is on the Cost Management + Billing blade. Please let me know if this does or doesn't resolve your issue.

Are PE's still supported for ASEv3? I can find docs on PE's used on ASEv2 but nothing yet regarding v3.

I will get further clarification from the product group with regards to use of private endpoints inside ASEv3 and update this post with my findings.

---------
EDIT: I've heard from the product group. Currently, ASEv3 doesn't support private endpoints. There is current work being done to add that support but not ETA for when to expect those changes.