Merge pull request #297856 from sfiguemsft/azure-docs-pr

Update to remove delegation content

Author: prmerger-automator[bot]

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

@@ -125,6 +125,7 @@ Outbound endpoints have the following limitations:
 
 ### Other restrictions
 
+- Linking rulesets cross-tenant is not supported.
 - IPv6 enabled subnets aren't supported.
 - DNS private resolver doesn't support Azure ExpressRoute FastPath.
 - DNS private resolver isn't compatible with [Azure Lighthouse](/azure/lighthouse/overview).

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

@@ -50,9 +50,6 @@ Create a private zone with at least one resource record to use for testing. The
 
 In this article, the private zone **azure.contoso.com** and the resource record **test** are used. Autoregistration isn't required for the current demonstration.
 
-> [!IMPORTANT]
-> A recursive server is used to forward queries from on-premises to Azure in this example. If the server is authoritative for the parent zone (contoso.com), forwarding is not possible unless you first create a delegation for azure.contoso.com.
-
 [ ![View resource records](./media/private-resolver-hybrid-dns/private-zone-records-small.png) ](./media/private-resolver-hybrid-dns/private-zone-records.png#lightbox)
 
 **Requirement**: You must create a virtual network link in the zone to the virtual network where you deploy your Azure DNS Private Resolver. In the following example, the private zone is linked to two VNets: **myeastvnet** and **mywestvnet**. At least one link is required.