Managing multiple environments, such as Test and Production, when working with Azure Functions and Power Automate flows can be challenging. One common pattern is to use a Custom Connector to embed the function call and parameters into the flow. However, the challenge arises when trying to use different versions of an Azure Function with different environments. One solution is to use Azure Functions deployment slots, which provide separate versions of the function. Another solution is to use Function Proxies, which allow for the translation of API client-facing interfaces into different endpoints. By using proxies, you can create a custom connector that can work with different versions of the Azure Function based on the environment. This allows for easier deployment and management of flows across multiple environments.
Login now to access my digest by 365.Training