MicrosoftMicrosoftThis is an old subject but a new problem for me once I changed my DNS forwarders to only forward privatelink.database.windows.net to the Azure Private DNS Resolver. That said I get the private IP address when I query privatelink.database.windows.net and the external IP address (external is blocked for my sql database servers) when I query the database.windows.net.
This was required as we use other (3rd Party) applications that use Microsoft resources, and we need to ensure that non-privatelink dns calls resolve to the internet addressable IP address. When we had database.windows.net as the DNS forwarder domain the Azure Private DNS would not resolve the IP address of 3rd parties Microsoft SAS resources at all.
Given all of this is there some new way to address this privatelink challenge SSL trust challenge?
Thank you!
