Category: Power Automate

This post is part of the New Functionality In Microsoft Power Automate 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2023 Wave 2.

The 12th of the new functionality in the Cloud Flows section is manage abandoned cloud flows.

This feature gives admins more visibility and lower risk through active management of their automation estate.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Dec 2023
General Availability: Mar 2024

Feature Details

Admins can more easily manage their automation estate with simplified reporting. They can also manage with support for bulk reassignment of flows that are running as a user who is no longer with the company. Prior to this, admins had to do this process manually per individual flow.

Admins get more visibility and can view information like the name of the last owner and number of days since the flow last ran from the Power Platform admin center. They can then perform maintenance operations like reassignment to another owner, or easily stop these flows with low effort.

My Opinion

This looks like it could be a very useful addition for managing flows after someone has left the organisation. This sort of thing can always be tricky, so exposing more information can only be a good thing.

This post is part of the New Functionality In Microsoft Power Automate 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2023 Wave 2.

The 10th of the new functionality in the Cloud Flows section is use your own encryption key for encrypting data at-rest for existing environments.

This capability allows you to meet your data and privacy policy according to your company’s or industry’s privacy guidelines.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: –
General Availability: Feb 2024

Feature Details

Use your own encryption key from your Azure Key Vault to encrypt an environment that already has running Power Automate flows. Previously, only environments without prior Power Automate usage were supported for customer-managed encryption keys.

This post is part of the New Functionality In Microsoft Power Automate 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2023 Wave 2.

The 8th of the new functionality in the Cloud Flows section is use Copilot with French language.

Makers in French speaking countries like France and Canada can use their own native language to interact with copilot.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: –
General Availability: Nov 2023

Feature Details

At this release, copilot is able to understand foreign language. It can create and edit a flow based on a foreign language prompt, or it can return content in the subject language. This can help non-English language customers to interact with copilot in the language they are most comfortable in.

This post is part of the New Functionality In Microsoft Power Automate 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2023 Wave 2.

The 9th of the new functionality in the Cloud Flows section is channel entry point for Teams workflows.

Enable users to seamlessly create flows from within Microsoft Teams.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Oct 2023
General Availability: Nov 2023

Feature Details

This feature enables a new entry point in Microsoft Teams that lets you create flows from Teams channels.

This is a convenient way to automate tasks and get notifications from tools and services that your team or organization uses. You can access this feature from the channel menu, where you can choose from a variety of templates or create your own custom flow.

My Opinion

This sounds like the functionslity added for Business central, which is a good way of adding flows to specific areas of the system.

This post is part of the New Functionality In Microsoft Power Automate 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2023 Wave 2.

The 7th of the new functionality in the Cloud Flows section is manage unpublished solution-aware cloud flows using admin APIs.

Power Automate admin APIs now have full support for solution cloud flows. This allows admins to see unpublished solution cloud flows, share solution cloud flows, and view the ownership of solution cloud flows.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: –
General Availability: Nov 2023

Feature Details

Currently, Power Automate admin APIs don’t fully support the management of solution-aware cloud flows because flows that have never been published (turned on) aren’t visible. With this feature, Power Automate admin APIs can now fully support the management of solution-aware cloud flows using Power Automate Management connector, the Power Automate for Admins connector, PowerShell for Power Platform Administrators, and the Power Platform admin center. Admins can see unpublished solution cloud flows, share solution cloud flows, and view the ownership of solution cloud flows.

This post is part of the New Functionality In Microsoft Power Automate 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2023 Wave 2.

The 6th of the new functionality in the Cloud Flows section is use versioning for solution cloud flows.

Currently, you don’t have versioning for solution cloud flows, so you lack the ability to revert to a previous version. With this feature, you can view and restore past versions of solution cloud flows. This can save you time in re-creating flows when you encounter new errors or alter plans. This ensures that your business always has a working version.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: –
General Availability: Nov 2023

Feature Details

With this feature, you can use a panel in the flow designer to view and restore previous versions of solution cloud flows if something goes wrong, or you change your mind. The draft state and version history are stored in Microsoft Dataverse. This is part of a platform-wide approach to versioning, with solution cloud flows being the first solution component to add this Dataverse-backed versioning support. This won’t provide source control integration.

My Opinion

It will be interesting to see the frequency of the versioning which this new function records. I often click save when working on a flow as I make changes and test; will each of these saves be a new version?

Although, on reflection, the announcement references it to versions of a solution so the incremental changes I make may not be recorded and the versioning only take place when the solution is published?

Lots of unanswered questions on this function which I will need to answer when I can get hands on with this function.

This post is part of the New Functionality In Microsoft Power Automate 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2023 Wave 2.

The 5th of the new functionality in the Cloud Flows section is make changes in draft mode for solution cloud flows.

Users have told us that they’re unable to begin creating or editing a flow until they have a large amount of time available because they can’t pause halfway through. Makers can now make changes to solution cloud flows in draft mode and publish when changes are complete. This allows the flexibility to create and edit regardless of the amount of time available, so you can concentrate on other tasks.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: –
General Availability: Nov 2023

Feature Details

Currently, makers can’t save a flow with errors and can’t save a draft version of a flow. With this feature, makers can make changes to solution cloud flows in draft mode, including when there are errors and publish when changes are complete.

My Opinion

Now this is the feature I have been wanting since I started working with Power Automate. It’s such a basic thing, that I have been amazed that you couldn’t save a flow part way through working on it and come back to finish it later.

This post is part of the New Functionality In Microsoft Power Automate 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2023 Wave 2.

The 4th of the new functionality in the Cloud Flows section is use the new cloud flows designer with Copilot.

With the cloud flows designer with Copilot, Power Automate cloud flow makers are able to create and edit flows that are scalable, robust, and modern.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: –
General Availability: Oct 8, 2023

Feature Details

You can create, configure, and customize your cloud flows with the classic designer or the cloud flows designer with copilot capabilities. Makers can create and edit their flows in the new cloud flows designer with Copilot experience by default.

My Opinion

I’ve not been hands on with any of the copilots yet, so it will be interesting to see how well this works, and how good the flows it designs are.

This post is part of the New Functionality In Microsoft Power Automate 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2023 Wave 2.

The 3rd of the new functionality in the Cloud Flows section is use OAuth support for HTTP request triggers.

Makers can use enhanced security measures for HTTP request triggers. For example, makers can restrict what users can trigger in this workflow by ensuring that only authenticated users can trigger this workflow. They can further define the security scope by choosing among three modes for the authentication parameter.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: –
General Availability: Oct 8, 2023

Feature Details

Prior to this feature, when makers created a flow that had an HTTP request trigger, the flow generated a shared access signature (SAS) URL. This URL was typically used by developers to trigger workflows from within their own applications or services. This feature provides added security to this trigger by enabling developers to limit who can trigger this workflow.