Merge pull request #279808 from greg-lindsay/dns-upd

add restriction

Author: prmerger-automator[bot]

articles/dns/dns-private-resolver-overview.md

@@ -6,7 +6,7 @@ ms.custom: references_regions
 author: greg-lindsay
 ms.service: dns
 ms.topic: overview
-ms.date: 12/05/2023
+ms.date: 07/01/2024
 ms.author: greglin
 #Customer intent: As an administrator, I want to evaluate Azure DNS Private Resolver so I can determine if I want to use it instead of my current DNS resolver service.
 ---
@@ -101,6 +101,7 @@ The following limits currently apply to Azure DNS Private Resolver:
 ### Virtual network restrictions 
 
 The following restrictions hold with respect to virtual networks:
+- VNets with [encryption](/azure/virtual-network/virtual-network-encryption-overview) enabled do not support Azure DNS Private Resolver.
 - A DNS resolver can only reference a virtual network in the same region as the DNS resolver.
 - A virtual network can't be shared between multiple DNS resolvers. A single virtual network can only be referenced by a single DNS resolver.
 

articles/virtual-network/virtual-network-encryption-overview.md

@@ -55,6 +55,8 @@ Azure Virtual Network encryption has the following limitations:
 
 - **AllowUnencrypted** is the only supported enforcement at general availability. **DropUnencrypted** enforcement will be supported in the future.
 
+- Virtual networks with encryption enabled do not support [Azure DNS Private Resolver](/azure/dns/dns-private-resolver-overview).
+
 ## Next steps
 
 - For more information about Azure Virtual Networks, see [What is Azure Virtual Network?](/azure/virtual-network/virtual-networks-overview)