A company runs an on-premises SQL Server database that contains product inventory data. A Copilot Studio agent needs to query this database to answer customer questions about product availability. The SQL Server is behind a corporate firewall with no inbound internet access. What is the required network component to enable this integration?

The on-premises data gateway is a Microsoft-supported agent software installed on a Windows Server inside the corporate network. It establishes outbound connections to Azure Service Bus relay endpoints, then forwards requests from cloud services (Power Automate, Power BI, Logic Apps) to on-premises data sources like SQL Server, Oracle, SAP, and file systems.

Option B is correct. The gateway requires no inbound firewall rule changes — it initiates outbound HTTPS/TCP connections to Azure. Once the gateway is registered with a Power Platform environment, it appears as a selectable data gateway option when configuring the SQL Server connector in Power Automate. The Copilot Studio topic calls a Power Automate cloud flow, which uses the SQL Server connector with the on-premises gateway to execute queries.

Option A is incorrect. While a VPN gateway could theoretically provide connectivity, it requires significant network infrastructure changes and ongoing management. The on-premises data gateway is the supported, purpose-built solution for this scenario and requires far less infrastructure.

Option C is incorrect. Creating a synchronized Azure SQL replica is complex, adds data freshness latency, doubles storage costs, and introduces data synchronization failure risks. If real-time inventory accuracy matters, a replica updated hourly is also unacceptable.

Option D is incorrect. Azure API Management with hybrid connections is an engineering-heavy solution not aligned with the Power Platform low-code approach. APIM is designed for API gateway patterns, not as a data gateway replacement for direct database connectivity.