Applies to Product - Microsoft Dataverse
What’s happening?
The customer is facing an issue with triggering Azure Functions that are not publicly exposed when associated with an Azure Virtual Network (VNet) from Dynamics 365 Sales. They require a GCC-compliant method to establish this connection.
Reason:
The Azure Functions are not publicly exposed due to their association with the VNet, which restricts access from external sources, including Dynamics 365 Sales in commercial clouds.
Resolution:
- The customer is advised to engage consulting services for assistance with the implementation of a GCC-compliant method to connect to the VNet.
- It was noted that the customer plans to use Plug-ins to trigger the Azure Functions instead of Power Apps connectors.