Follow-up: Azure Container Apps VNet DNS resolution defect (previous thread locked)

Context:

This post is a follow-up to a previous Microsoft Q&A discussion regarding Azure Container Apps DNS resolution failures affecting VNet-integrated environments:

https://learn.microsoft.com/en-us/answers/questions/5568259/azure-container-apps-cannot-resolve-azure-openai-h

Microsoft engineers previously confirmed the analysis and indicated that the issue had been escalated to the Azure Container Apps product engineering team. Unfortunately, the earlier thread was automatically locked following a moderation event, which prevented further updates or confirmation of resolution status.

Current Status:

• The DNS resolution issue persists for Azure Container Apps with VNet integration.
• Direct-IP testing confirms the problem is isolated to ACA internal DNS.
• Non-VNet ACA instances and control VMs in the same environment resolve the same endpoints successfully.
• A complete diagnostic evidence package is retained and can be provided for verification if required.

Request for Update:

1. Has this known issue been assigned an internal engineering case or tracking ID?
2. Is there an ETA or interim guidance for Azure Container Apps DNS resolution failures within VNet-integrated environments?

Impact:

This issue continues to block ACA workloads that depend on Azure OpenAI and other private endpoints, as name resolution within the container environment fails while external resolution operates normally.

Thank you for any guidance or official update the product team can share regarding the current status of this defect.