Az.DnsResolver with peered vnets in a separate tenant

[dingmeng-xue]

Discussed in #20098

^{Originally posted by AnikaAaron November 13, 2022}
I was checking out the Az.DnsResolver PowerShell command "New-AzDnsForwardingRulesetVirtualNetworkLink" (and in the portal) and was noticing that I'm unable to create a virtual network link to a peered vnet that is a separate tenant. The peering has been up, and P2S vpn traffic flows. Created the rule set, but the subscriptions only show in the portal for a singular tenant. When attempting to pass the vnet resource ID (like when creating the initial cross tenant vnet peering) the PowerShell command fails with a permission issue "however the current tenant
'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXX' is not authorized to access linked subscription".
Is cross tenant dns not available at this time?

[ghost]

Thank you for your feedback. This has been routed to the support team for assistance.

[tspearconquest]

We are also interested in this as we have 2 isolated tenants and need to manage DNS for both from a single tenant.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dnssuppgithub.