Not happy with Copilot constantly populating in Power Automate? Every time you open/edit a flow, open a flow that is currently running, or open a flow that already ran, Copilot opens, hogging RAM and slowing down your time to be able to interact with the flow. This can be extremely irritating and frustrating for some users.
The most common proposed solution is to disable the New Designer by toggling it off and view the flow in Classic mode.
However, if history serves as an indicator, it is only a matter of time before Microsoft will remove Classic mode completely.
The good news is that there is a tenant-wide solution to disable Copilot from populating in Power Automate. Please note, that as this modification is tenant-wide, all users in your tenant will no longer have Copilot populate in Power Automate, so check with your team before implementing to minimize any adverse impact.
To disable Copilot, you must be an Administrator for your tenant and run a PowerShell script to either disable or enable it (should you ever want to re-enable Copilot).
The PowerShell script requires two modules to be installed prior to running the script:
- Install-Module -Name Microsoft.PowerApps.Administration.PowerShell
- Install-Module -Name Microsoft.PowerApps.PowerShell -AllowClobber
Script
param(
[parameter(Mandatory, HelpMessage="Enter a boolean value (true|false)")]
[ValidateSet("false", "true")]
$disableCopilot
)
$value = [System.Convert]::ToBoolean($disableCopilot)
$settingName = "PowerAutomate.disableCopilot"
try {
$settings = Get-TenantSettings
"Current value for $($settingName) is: $($settings.powerPlatform.powerAutomate.disableCopilot)"
# update the setting
"Now setting $($settingName) to be: $($value) ..."
$settings.powerPlatform.powerAutomate.disableCopilot = $value
Set-TenantSettings -RequestBody $settings
}
catch {
"Failed to set $($settingName)"
$_.Exception
return
}
# see the updated setting
$updatedSettings = Get-TenantSettings
""
"The value for $($settingName) is now: $($updatedSettings.powerPlatform.powerAutomate.disableCopilot)"
The script will ask you for the parameter value of “disableCopilot.” Use the value "True" (without quotes) to disable or “False” to enable Copilot in the Power Automate designer.
Press Enter to execute the disableCopilot script.
You will see the current value for Power Automate disableCopilot and the value that it was set to.
For you to notice the modification take hold in your Environment, it will typically take approximately 1 minute. It is best practice to close all browsers and sign out and back into your Power Automate Environment to remove any cache of Copilot.
You are now ready to enjoy Power Automate sans Copilot. Enjoy!
FAQ: Disabling Copilot in Power Automate
1. What is the impact of disabling Copilot tenant-wide?
Disabling Copilot tenant-wide means that all users within your organization will no longer have Copilot suggestions appear in the Power Automate designer. This can be beneficial for users who find Copilot's suggestions distracting or unhelpful, but it also means that users who find Copilot valuable may no longer have access to its features.
2. Can I re-enable Copilot after disabling it?
Yes, you can re-enable Copilot by running the same PowerShell script with the "disableCopilot" parameter set to "False". However, please keep in mind that this will re-enable Copilot for all users in your tenant.
3. Are there any other alternatives to disabling Copilot?
If disabling Copilot tenant-wide in New designer is not the best option for you, you can switch to the Classic designer by toggling the "New Designer" option off. However, Microsoft may eventually remove the Classic designer altogether.
COO at Connecting Software
Author:
I am the Chief Operating Officer for Connecting Software, managing the day-to-day operations throughout our various locations. I am passionate about continuous improvement and increasing efficiency. If you want to join our amazing team either in Slovakia or Madeira, please reach out.