Can Private Azure SQL Server connect to Fabric with cloud connection by enabling "This connection can be used with on-premise data gateways and VNet data gateways"?After enabling this, it stills shows error like "Unable to create connection for the following reason: We could not access the data source. Please make sure you have permission to access the data source and that your credentials are correctDetails: Reason: An instance-specific error occurred while establishing a connection to SQL Server. Connection was denied since Deny Public Network Access is set to Yes (https://docs.microsoft.com/azure/azure-sql/database/connectivity-settings#deny-public-network-access). To connect to this server, use the Private Endpoint from inside your virtual network (https://docs.microsoft.com/azure/sql-database/sql-database-private-endpoint-overview#how-to-set-up-private-link-for-azure-sql-database). Please have this information handy if you choose to create a support ticket."

Hi ShairaiAli , Thank you for the follow-up. The Allow this connection to be utilized with either on-premises data gateways or VNet data gateways option is intended for hybrid scenarios where the same connection may need to work in both cloud and gateway-based contexts. Example use caseYou initially configure a Cloud connection from Fabric to an Azure SQL Database that allows public network access. Later, your organization restricts the database to a private endpoint accessible only through a gateway.By enabling this option, you can reuse the same connection and map it through an on-premises or VNet gateway, instead of creating a new one. In summary, this setting makes the connection eligible for gateway-based evaluations. Dataflows, Semantic Models, Pipelines, etc. but doesn’t change the runtime network path you still need a gateway if the source isn’t publicly accessible.Thanks,Akhil.