Power Automate – New admin tenant setting for resubmitting Power Automate flow runs [MC975979]

Message ID: MC975979

On January 13, 2025, Power Automate will introduce a new admin tenant setting to control the resubmission of flow runs initiated by instant triggers. This feature will be widely available across all regions by the end of January 2025.

How does this affect me?
By default, this feature will disable the ability for users to resubmit flow runs that were initialized using an instant trigger unless the new setting is enabled. If no action is taken, users will be unable to resubmit flows that were previously initialized using an instant trigger.

What do I need to do to prepare?
This message is for awareness and no action is required. If you want to enable flow run resubmissions for cloud flows that were initialized by instant triggers, admins can follow the steps below:

Sign in to your tenant account.
PowerShell: Add-PowerAppsAccount -Endpoint "prod" -TenantID <Tenant_ID>
Retrieve and store your tenant settings in TenantSettings.
PowerShell: $tenantSettings = Get-TenantSettings
Set the powerPlatform.powerAutomate.disableFlowRunResubmission flag to False, to allow flow run resubmissions for cloud flows initialized by instant triggers.
Powershell: tenantSettings.powerPlatform.powerAutomate.disableFlowRunResubmission= $False
Set-TenantSettings -RequestBody $tenantSettings

If you are not familiar with running PowerShell commands for your tenant, refer to the PowerShell support for Power Automate documentation.

Source: Microsoft

Mike Rosoft

9 January 2025, 10:53 pm

The upcoming update to Power Automate regarding the new admin tenant setting for resubmitting flow runs initialized by instant triggers is set to make waves in both the admin and user communities. As of January 13, 2025, this feature will be rolled out across all regions, and while it may sound like just another tech update, its implications are quite significant.

For admins, the introduction of this setting means a new layer of control over how flows are managed within their organizations. By default, the ability for users to resubmit flows initiated by instant triggers will be disabled unless the setting is actively enabled. This gives admins the power to dictate how flexible or rigid the flow management should be, depending on their organizational needs. It’s like being the gatekeeper at a fancy event—deciding who gets to re-enter the party!

On the user side, the impact is equally notable. If admins choose not to enable the resubmission feature, users may find themselves in a bit of a pickle when a flow fails. The inability to resubmit could lead to frustration, especially if users are accustomed to having that option readily available. However, this change could also encourage users to ensure their flows are running smoothly the first time around—after all, who doesn’t love a little motivation?

Overall, the effectiveness of these changes will largely depend on how well admins communicate with their users and the decisions they make regarding the new setting. If enabled, it could lead to greater user satisfaction and efficiency. If left disabled, well, it might just spark a few more “Why can’t I resubmit?” conversations in the break room!

We’d love to hear your thoughts on this update! How do you think it will affect your day-to-day workflow? Will you be advocating for the resubmission option, or do you see the potential for a more structured approach? Share your insights in the comments below, and let’s get the conversation rolling!

For more insights and updates, check out additional posts on mwpro.co.uk!

1 Comment

Mike Rosoft


9 January 2025, 10:53 pm

The upcoming update to Power Automate regarding the new admin tenant setting for resubmitting flow runs initialized by instant triggers is set to make waves in both the admin and user communities. As of January 13, 2025, this feature will be rolled out across all regions, and while it may sound like just another tech update, its implications are quite significant.

For admins, the introduction of this setting means a new layer of control over how flows are managed within their organizations. By default, the ability for users to resubmit flows initiated by instant triggers will be disabled unless the setting is actively enabled. This gives admins the power to dictate how flexible or rigid the flow management should be, depending on their organizational needs. It’s like being the gatekeeper at a fancy event—deciding who gets to re-enter the party!

On the user side, the impact is equally notable. If admins choose not to enable the resubmission feature, users may find themselves in a bit of a pickle when a flow fails. The inability to resubmit could lead to frustration, especially if users are accustomed to having that option readily available. However, this change could also encourage users to ensure their flows are running smoothly the first time around—after all, who doesn’t love a little motivation?

Overall, the effectiveness of these changes will largely depend on how well admins communicate with their users and the decisions they make regarding the new setting. If enabled, it could lead to greater user satisfaction and efficiency. If left disabled, well, it might just spark a few more “Why can’t I resubmit?” conversations in the break room!

We’d love to hear your thoughts on this update! How do you think it will affect your day-to-day workflow? Will you be advocating for the resubmission option, or do you see the potential for a more structured approach? Share your insights in the comments below, and let’s get the conversation rolling!

For more insights and updates, check out additional posts on mwpro.co.uk!

1 Comment

Leave a Reply Cancel reply