how to disable copilot mode in power automate

[PulkitM]

how to disable copilot mode in power automate

[Srini007]

Hi @PulkitM 

You can go to Power Platform Admin Center -> Settings->Tenant settings->Click on Copilot (preview)->on the side bar you have toggle bar as On, If you change it to Off this will helps you

If you find this reply helpful, please consider giving it a LIKE AND

If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION

Thanks,

Srini

[PulkitM]

Unable to find Tenant settings in Power Platform Admin Center 

[Srini007]

Ok, go to Admin centers and check if you have option as All admin centres or directly you have power Automate click on that then you able to see the settings and when select setting Tentant settings will be displayed

If you find this reply helpful, please consider giving it a LIKE AND

If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION

Thanks,

Srini

[PulkitM]

I can't see either of them.

[Srini007]

Oh okay, now I think I got, can you go to the Environments and there you can see the settings and product choose features  there you can see the Copilot

If you find this reply helpful, please consider giving it a LIKE AND

If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION

Thanks,

Srini

[PulkitM]

I can't see that option.

[stefstaedter]

Hi @PulkitM,

there is a powershell setting "PowerAutomate.disableCopilot" in the power platform tenant settings. Set it to "true", then the copilot in Power Automate will be disabled.

[chapmangs]

It seems the tenant setting, nor the PowerShell command to disableCopilot and disableCopilotwithBing disable the 'Edit with Copilot (preview)' functionality. Are there other settings to disable this?

The ability to add Copilot controls to Power Apps appears to be at the Environment level.  Does anyone know how to change the 'Default' setting to be Off, so it doesn't have to be changed individually in all Environments?

[stefstaedter]

Hi chapmangs,

I had the same experience with the PowerShell command to disableCopilot, this didn't work. The Power Apps copilot can be disabled in the Power Platform Admin Center on tenant level https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/ai-overview#disable-copilot-in-power-... and on environment level you have the option for Power Apps Ideas that is in my case by default disabled.

Copilot control for Power Apps seems to be a feature in the app that can be enabled, should be disabled by default. https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/add-ai-copilot

[chapmangs]

Thanks for the response.  The first setting is disabled, and that did disable the ability to create with copilot.  However, the functionality to 'Edit with Copilot (Preview)' was recently added and that tenant setting has not impacted it. 

[PulkitM]

I found the solution to this problem, looks like we have to change impacted flows one by one into Classic mode. 

1. Open one of the impacted flow, it will open in Co Pilot mode.
2. You will see triple dots on top right corner.
3. Click on it.
4. It will give the option to 'Switch to Classic Designer'. 
5. Save.

[CheasonUK]

A script is required to disable Power Automate (The previous solutions only work for Power Apps) This is the script provided by Microsoft:

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)" 

""
It requires two modules to be installed:
Install-Module -Name Microsoft.PowerApps.Administration.PowerShell
Install-Module -Name Microsoft.PowerApps.PowerShell -AllowClobber

[stefstaedter]

unfortunately this tenant setting doesn't work correctly at the moment. You can set it to true but nothing happens. 😞

[stefstaedter]

I must correct my last post. It disables the copilot functionality in the new designer and in the home page. 🙂

[eliotcole]

This is madness, to be honest.

Whether a tenant wishes it to be available or not a user should have the option to have none of their data be utilised by CoPilot.

Giving it a lovely name does not an acceptable 'always on' practice make.

[tgraham]

Thanks @PulkitM, you're a lifesaver.

[kbirstein]

 I read all the comments above but I'm unclear about whether anything is working to disable copilot and the new designer tenant wide, which is what I want.

FIRST ISSUE:

How to disable new designer when creating a Power Automate flow? Yes, the user can click the three dots up at the upper right hand corner to switch to Classic Designer but most users do not see that and end up creating a support ticket. The new designer MAY be something we want to use in the future but right now it would require A LOT of training to teach citizen developers how to use it. Sending a simply email presents the user with five options, four of which normal citizen developers will never use, so why complicate things by showing them? Very intimidating for citizen devs. . .

SECOND ISSUE:

2. How to get rid of the CoPilot panel that pops out in the new designer. Again a huge training task to teach citizen devs how to use CoPilot and for 90% of their flow needs, CoPilot doesn't add any value. And it's a premium feature, which means even if it does add value, many companies will not want to pay for it when the majority of their flows are very simple. It seems that the script CheasonUK was provided does not work and in any case, is tenant-wide, which is not desirable.

What would be best is for both of these features to be enabled by ENVIRONMENT, so that more sophisticated users could use 1. the new designer and 2. CoPilot when desired.

Microsoft, please provide easy to use settings to enable and disable these features on the environment level in the Admin Center!

[eliotcole]

@kbirstein I do agree ... but even if either *are* enabled per environment they should also be optional per user.

[RichardP]

With that fact the new interface introduces flow errors in working flows, then it needs to be disabled.

I wasted 2 days on corrupted PDF files attached to an email from a SharePoint document library to learn that it was caused by the new interface "adding code" where it doesn't need to.

Unbelievable!!!