Applies to Product - Dynamics 365 Commerce
What’s happening?
Customers are experiencing difficulties connecting their Dynamics 365 environment to an Azure SQL Server privately without enabling public IPs on the SQL Server firewall.
Reason:
The underlying cause of this is related to the configuration of the connection between Dynamics 365 and Azure SQL Server, specifically regarding the use of public IPs and firewall settings.
Resolution:
- It is possible to connect Dynamics 365 to Azure SQL Server privately, without enabling public IPs on the SQL Server firewall. To achieve this, you can use Azure Private Link.
- Azure Private Link allows access to Azure services, such as Azure SQL Server, through a private endpoint within the virtual network, ensuring that communication between Dynamics 365 and Azure remains private and does not traverse the public internet.
- To connect Dynamics 365 to a virtual network (VNet) from Azure, the following steps should be taken:
- Create virtual networks and subnets in Azure, ensuring that the Azure region matches the region of Power Platform.
- Download and run the PowerShell script to delegate the subnet to the company policy, ensuring that the subnet is used exclusively by Power Platform.
- If the primary and failover virtual networks are in different Azure subscriptions, create a virtual network peering between the virtual networks to allow resources in different virtual networks to communicate as if they were in the same virtual network.
- Use Dataverse plugins and connectors to securely connect to private resources protected by endpoints in Azure, such as Azure SQL or SQL Server, without exposing them to the internet.
- For additional details, refer to the official documentation on Azure Private Link and how to create your own private connection service:
- What is Azure Private Link service? | Microsoft Learn
- Tutorial: Create a private endpoint for Azure SQL Database
- VNet integration for Azure services