Today, we are excited to announce a new capability for this trigger. Customers can now add OAuth authentication to such HTTP request triggered workflows, to add an additional layer of control to this workflow. With a single parameter within the trigger, makers can restrict only users within their tenant can trigger this workflow by sending an HTTP request to the URL. This will be the default option for this trigger moving forward, to ensure customers create secured endpoints by default.

Customers can further lock down who can trigger this workflow to specific users within the tenant. This list could contain specific user ids or service principal object ids, on whose context the workflow might be triggered.

Once either of these parameters are added to this trigger, then only those requests that contain the specific claims (tenant id, user id or object id) in the http requests will be allowed to trigger the flow.

You can learn more about this capability here. It is also recommended to check out the Microsoft Authentication Library (MSAL) to understand how you add the right claims in your HTTP request, depending on the language and framework you are using within your application or service.

Please feel free to provide your questions and feedback in the Power Automate community.

Happy Automating!

The post Deeper control over HTTP invocation of flows appeared first on Microsoft Power Platform Blog.

Customers can now leverage Azure’s market-leading application performance monitoring (APM) capabilities to diagnose and monitor their workflows running on Microsoft Power Automate. Customers would be able to leverage the out-of-the box capabilities available on Application Insights and directly use it to analyze cloud flow telemetry. This includes metrics dashboards, out-of-the box and custom alerts, performance diagnostics and custom analysis of cloud flow telemetry via log analytics.

Customers can select to emit cloud flow runs, triggers and action-level data from an environment to application insights. The connection can be set up in just a few steps from the Power Platform Admin Center, and the step-by-step wizard instructions can be found here.

Customers can connect multiple environments into a single instance of Application Insights. If you do not have an Application Insights instance already set up, you can do so by following the steps here.

Once the connection is set up, all the events should start flowing from the power platform environment to the application insights instance. On the Application Insights side, cloud flow runs data are stored in the requests table, and the triggers and action level data are stored in the dependencies table. You can then perform monitoring, alerting, custom debugging etc. from Application Insights. Step-by-step instructions on how to diagnose the cloud flow telemetry data are documented here.

We’re excited to bring this detailed and holistic visibility of Power Automate telemetry at scale. We appreciate the feedback we’ve received from our private preview participants and are excited to open this capability to everyone.

Please feel free to provide your questions and feedback in the Power Automate community. Happy Automating!

The post Announcing the integration of Power Automate telemetry data with Azure Application Insights appeared first on Microsoft Power Platform Blog.

With CMK, customers leverage an encryption key from their own Azure Key Vault, which Microsoft does not have access to. Then, they can configure an enterprise policy with that encryption key and apply it to any Power Platform environment. Once this policy is applied, all the services that have support for CMK will be encrypted using customer’s key. This operation is purely an admin-led operation and is totally invisible to low code developers and other makers who continue to use the service exactly the way they do today.

Once CMK is applied, all the core Power Automate assets like flow definitions, flow run history etc are encrypted using the customer’s encryption keys. For such environments, Power Automate flows would be running on a dedicated infrastructure, ensuring isolation of customer assets at both rest and runtime. At preview, we support only environments that do not contain any flows for CMK. If the CMK operation is performed on an environment that already contain flows, the flows will continue to be encrypted with the default Microsoft-managed keys. You can read more details about Power Automate support for customer managed encryption keys here.

You can find the step-by step instructions on how to use Azure Key Vault to generate a key, and then apply an enterprise policy using that key to leverage CMK here.

If an admin chooses to “lock” an environment, then all the assets that were encrypted with customer’s encryption keys would be inaccessible to Microsoft services, ensuing total lockdown of your data, even when they are stored in the Microsoft cloud. You can find more about operations like Lock and Unlock environments here.

Please feel free to provide your questions and feedback in the Power Automate Community. Happy Automating!

The post Announcing public preview of customer managed encryption keys for Power Automate appeared first on Microsoft Power Platform Blog.

As multiple users work on automating a business process, these capabilities will be critical in helping makers collaborate seamlessly and efficiently. We believe that these would result in helping build complex automations faster

Users can add comments by selecting ‘…’ within each action card or by simply clicking on the comments pane from the top.

Within the comment pane, one can simply @mention a colleague to invite them to help with a problem.

Upon posting those comments, if the flow is not already shared with your colleague, you will be prompted with a ‘Share and notify’ option that would not only share the flow but also send an email notification.

The other user can click on the comment link within the email to directly navigate to the comment within the flow.

Users can added threaded replies to comments within the flow.  The number of comment threads in an action or trigger are denoted by indicator within the action card. As users work through finishing their flow, they can resolve and delete comments and comment threads.

Moreover, recently launched co-presence feature provide users with a visual indicator of other makers who are currently editing the flow, and provide ways to minimize conflicts.

We hope you find these features useful. You can learn more about the feature here. Please do not forget to share any feedback at the Power Automate Community Forum

The post Collaborative comments in Power Automate appeared first on Microsoft Power Platform Blog.

Collaborating with your colleagues often helps you in developing complex workflows faster. Through our sharing feature, users can share flows with other users in their organization for co-developing workflows together.  With the introduction of co-presence in Power Automate, each user can know in near real-time which other users are currently editing the flow. The user avatars are refreshed periodically to show the updated slate of concurrent editors in the flow

If multiple users make changes to the flow simultaneously, we detect conflicts during the flow save operation, and present appropriate options to the user to minimize conflicts. A user can choose to refresh the flow definition or save a copy of the flow to not lose the changes.

We hope you find this feature useful. This is one among the many exciting features we will be rolling out within the collaboration space over the next few months. Please do not forget to share any feedback at the Power Automate Community Forum. 

The post Announcing co-presence in Power Automate appeared first on Microsoft Power Platform Blog.

With this feature, users can add variables to perform multiple actions within your UI automation. You can use variables for data types such as integer, float, array, string etc.

For example, you can use a variable to count how many times an operation was performed in a loop. Or you can use variables to create a string array with screen recordings done in a UI flow loop.

Here are the steps to create and use variables in a UI flow.

1.  Go to the beginning of the UI flow and select Add an action

2.  Search for variable and select Initialize variable action

Once initialized, you may use variables within your UI automation to perform multiple actions.

For example, if your UI automation scenario involves reading values from a screen in a loop, you could achieve this by initializing the variable as an array type. Then, within the UI flow, simply select the Append to array variable action and use the output of Get Text action from dynamic content

Please do not forget to share any feedback at the Power Automate Community Forum and use “UI flows” label.

Happy automating!

The post Announcing Variable support in UI flows appeared first on Microsoft Power Platform Blog.

With this feature, we are providing the ability to add a loop to your UI automation as a post-recording activity. You will be able to pass an array object as input variable from an API flow to a UI flow, and then create a loop within UI flow script to perform repetitive action within your UI automation.

Here are the steps to create a loop within UI flows using an array input

• Create a UI flow by launching the recorder
• Navigate to the input section of the newly created UI flow script. Add an Array as your input by providing the name, sample value and  description

• Navigate to the UI flow script and add “Apply to each” action at the location where you want to start the loop
• Use the previously created array as the token from the Dynamic content
• Drag and drop the recorded actions you want to repeat into the ‘Apply to each’ scope

• Replace the input tokens created during recording with the array values as needed. These can be input using either dynamic content or expressions

For more details on this feature, please see the documentation here

Please do not forget to share any feedback at the Power Automate Community Forum and use “UI flows” label.

Happy automating!

The post Announcing support for Loops and Array inputs in UI flows appeared first on Microsoft Power Platform Blog.

We are excited to announce the availability of error handling and control logic for UI automation scripts.

With error handling, you can add resilience and robustness to your UI flows by adding parallel branches of execution.  If there are certain steps within your UI automation that are more susceptible to failures or timeouts, you can add a parallel branch and define an alternate set of actions.  Your parallel branch action could either be a new recording or a set of manual actions defined to handle the error in the previous UI flow step.

You can follow step-by-step instructions for introducing advanced error handling in your UI flows here.

With control logic, you can bring intelligence directly into your UI automation scripts.  You can use control logic actions like condition, switch case and terminate actions directly within a UI flow. This would enable you to use dynamic content and expressions to route your UI flow execution based on different inputs. Those inputs could be values passed on from a flow triggering the UI flow or an output defined from a previous UI flow recording step.

You can follow step-by-step instructions for using advanced controls in your UI flows here.

Please do not forget to share any feedback at the Power Automate Community Forums and use “UI flows” label.

Happy automating!

The post Error handling and control logic for UI flows appeared first on Microsoft Power Platform Blog.