You have an on-premises DNS server Server1 hosting fabrikam.com. Virtual networks connect to on-premises via S2S VPNs. You must deploy Azure DNS Private Resolver so: virtual network resources can resolve fabrikam.com, Server1 can resolve contoso.com, and costs/administrative effort are minimized. What is the minimum number of resolvers required?

Two resolvers are needed. One inbound endpoint allows on-premises Server1 to query Azure DNS for contoso.com. This resolver would be linked to the virtual network containing the contoso.com resources. A second resolver with an outbound endpoint and a DNS forwarding rule is required for Azure resources to resolve fabrikam.com via Server1. This outbound endpoint would be linked to the virtual network where Azure resources need to resolve fabrikam.com. One resolver cannot simultaneously provide both inbound and outbound forwarding capabilities across different virtual networks and on-premises environments while maintaining the required resolution paths. Therefore, two distinct resolvers, each with appropriate endpoint configurations, are the minimum to satisfy all requirements.