Governance in Power Automate for desktop
You can use the Windows registry to control who can do what with Power Automate for desktop.
Caution
Modifying Windows registry settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of registry settings can be solved. Modification of these settings is at your own risk. We strongly recommend that you back up your Windows registry before proceeding.
Prevent users manually updating Power Automate for desktop
You can use the following registry entry to keep users from manually updating Power Automate for desktop and receiving update notifications.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | DisableOptionalUpdates | DWORD |
Value
- 1: Users can't manually update Power Automate for desktop.
Prevent users accessing Power Automate for desktop using certain kinds of accounts
Note
Setting any value other than 1, or not setting a value at all, in the following registry keys will allow users to sign in to Power Automate for desktop. If all the following registry keys are set to 1, users can't sign in to Power Automate for desktop using any type of account.
Prevent users accessing Power Automate for desktop using their Microsoft accounts
You can use the following registry entry to keep users from signing in to Power Automate for desktop using a Microsoft account.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | RestrictMSAAccountsSignIns | DWORD |
Value
- 1: Users can't sign in to Power Automate using their Microsoft account.
Prevent users accessing Power Automate for desktop using their work or school accounts
You can use the following registry entry to keep users from signing in to Power Automate for desktop using their work or school account without a per-user plan with attended RPA license.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | RestrictNoLicenseOrgIDAccountsSignIns | DWORD |
Value
- 1: Users can't sign in to Power Automate using their work or school account without a per-user plan with attended RPA license.
Prevent users accessing Power Automate for desktop using their work or school accounts or organization premium accounts
You can use the following registry entry to keep users from logging into Power Automate for desktop using their work or school accounts or organization premium accounts.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | RestrictOrgIDAccountsSignIns | DWORD |
Value
- 1: Users can't sign in to Power Automate using their work or school account or organization premium account.
Restrict access to Power Automate for desktop
To restrict access to Power Automate for desktop on a workstation with Windows 10 or Windows 11, use App locker.
Allow users to sign in to Power Automate for desktop using Web Account Manager (WAM)
You can use the following registry entry to allow users to sign in to Power Automate for desktop using Windows Web Account Manager (WAM).
WAM enables certain features that aren't available through the default login process, such as single sign-on (SSO).
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | UseMsalWindowsBroker | DWORD |
Values
- 1: Power Automate for desktop authenticates users using the WAM functionality.
Allow users with invalid certificates to sign in to Power Automate for desktop
You can use the following registry entry to allow users with invalid certificates to sign in to Power Automate for desktop.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | DisableCheckCertificateRevocationList | DWORD |
Values
- 1: Users with invalid certificates can sign in to Power Automate for desktop.
Allow users to select an organization in Power Automate for desktop
You can use the following registry entry to allow users to select the organization of their preference in Power Automate for desktop.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | EnableOrganizationPicker | String |
Values
"isEnabled":1: Signed-in users can select the organization of their preference through the Switch organization option in the Power Automate for desktop console.
"isEnabled":0: Signed-in users can't select the organization of their preference and the Switch organization option is disabled.
"organizationList":[OrgID(s)] (for example,
organizationList:["10z677m8-l4v6-9cm5-c6n6-r1747rp5338k","86d487j7-y1t2-9gk7-k7n2-x5079jq4619r"]): The organizations with the specified IDs are available to connect during sign-in."selectOrganizationFromListIsEnabled":1: Power Automate for desktop tries to connect to each of the organizations specified in the organizationList value, in order, during sign-in.
"selectOrganizationFromListIsEnabled":0: The specified list in the organizationList value isn't taken into consideration during sign-in.
Note
The "isEnabled" values aren't related to the organizationList and selectOrganizationFromListIsEnabled values. The isEnabled values define whether the Switch organization option is available to signed-in users, whereas the organizationList and selectOrganizationFromListIsEnabled values define the organizations that Power Automate for desktop tries to connect to automatically during sign-in.
Allow users of Power Automate for desktop to connect to a region
You can use the following registry entry to allow users to select the region they want to connect to.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | Cloud | DWORD |
Value
- 0: The user can select the region to connect to through another option in the sign-in screen.
- 1: The user is automatically connected to the first available region they're registered to.
- 2: The user will connect to the global public region.
- 3: The user will connect to the US Government GCC region.
- 4: The user will connect to the US Government GCC High region.
- 5: The user will connect to the US Government DoD region.
- 6: The user will connect to the China (operated by 21Vianet) region.
Configure Power Automate for desktop to interact with a corporate proxy server
IT administrators may set the following registry key to configure how Power Automate interacts with a corporate proxy server.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | ProxyServer | String |
Value
- ProxyAddress:Port (for example,
https://myproxy.com:3128): The proxy server and port configured override the proxy server and port configured in Windows.
Configure Power Automate for desktop to bypass a corporate proxy server
IT administrators may set the following registry key to configure the Power Automate's bypassing of a corporate proxy server.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | DisableWindowsProxy | DWORD |
Value
- 1: Power Automate for desktop doesn't honor the Windows Proxy settings and the proxy server is bypassed for Power Automate's traffic.
Configure Power Automate for desktop to authenticate to a corporate proxy server using the current user's credentials
IT administrators may set the following registry key to configure how Power Automate authenticates with a corporate proxy server.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | UseDefaultProxyCredentials | DWORD |
Value
- 1: Power Automate for desktop authenticates to the corporate proxy server using the current user's credentials.
Configure optional diagnostic usage data collection in Power Automate for desktop
You can use the following registry entry to enable or disable the collection of optional diagnostic usage data in Power Automate for desktop.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\WOW6432Node\Microsoft\Power Automate Desktop\LogShipper | AllowOptionalDataCollection | DWORD |
Value
- 0: Power Automate for desktop won't collect optional diagnostic usage data.
- 1: Power Automate for desktop collects optional diagnostic usage data.
Prevent Power Automate for desktop from taking screenshots for action logs upon error
You can use the following registry entry to prevent Power Automate for desktop from taking a screenshot for the actions logs when an error occurs during a flow run.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop\Global | DisableScreenshotCaptureOnError | DWORD |
Value
- 1: Power Automate for desktop won't take a screenshot for the action logs when an error occurs during a flow run.
Configure Power Automate for desktop notification settings
You can use the following registry entry to configure how Power Automate for desktop displays notifications and monitoring information.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_CURRENT_USER | SOFTWARE\Microsoft\Power Automate Desktop | NotificationsType | DWORD |
Value
- 1: Power Automate for desktop displays notifications through the flow monitoring window.
- 2: Power Automate for desktop uses the integrated Windows notifications.
- 3: Power Automate for desktop doesn't display notifications.
Configure Power Automate for desktop confirmation dialog when invoking flows using a URL or desktop shortcut
You can use the following registry entry to configure the behavior of the confirmation dialog when invoking flows using a URL or desktop shortcut.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_CURRENT_USER | SOFTWARE\Microsoft\Power Automate Desktop | EnableAskBeforeRunningAFlowExternally | DWORD |
Value
- 0: Power Automate for desktop doesn't display a confirmation dialog when invoking flows using a URL or desktop shortcut. The user can change this option through the console settings.
Configure Power Automate for desktop to invoke flows using a URL or desktop shortcut
You can use the following registry entry to enforce the confirmation dialog or disable invoking flows using a URL or desktop shortcut.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | ConfigureExternalRuns | DWORD |
Value
- 1: Power Automate for desktop always displays a confirmation dialog when invoking flows using a URL or desktop shortcut. Users aren't allowed to change this option through the console settings.
- 2: Users aren't allowed to invoke flows using a URL or desktop shortcut.
Configure Power Automate for desktop to keep the flow run details
You can use the following registry entry to configure Power Automate for desktop to keep the flow run detail logs in a local folder.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop | KeepRunDefinitionFilesCopy | DWORD |
Value
- 1: Power Automate for desktop creates a copy of the RunDefinition.json file, preventing the local flow run details from getting cleaned up.
Configure Power Automate for desktop to prevent cleanup of flow run action details
You can use the following registry entry to configure the cleanup of local flow run action detail logs.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop\Global | DisableRunFilesCleanup | DWORD |
Value
- 1: Flow run action details stored in the Actions.log file aren't deleted from the local disk after the run is completed.
Prevent Power Automate for desktop from running flows containing cloud connectors
You can use the following registry entry to disable the execution of flows containing cloud connectors.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\Microsoft\Power Automate Desktop\Global | DisableCloudConnectors | DWORD |
Value
- 1: The machine can't run desktop flows containing cloud connectors. An error message informs users about the limitation.
Allow users to register their machine to a different tenant in Power Automate machine-runtime app
Note
This registry entry applies to Power Automate desktop version 2.24 and later.
You can use the following registry entry to allow machine registrations to tenants that are different from the machine joined Azure Active Directory tenant.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\WOW6432Node\Microsoft\Power Automate Desktop\Registration | AllowedRegistrationTenants | String |
Value
- "AllowedRegistrationTenants": (for example,
3EF1D993-CBD4-4DEA-A50E-939AEDB23F21,5B19777D-814C-43F3-9317-CDBAD0846ED8): The tenants with the specified IDs can be used during machine registration.
Allow users to register their machine to any tenant in Power Automate machine-runtime app
Note
This registry entry applies to Power Automate desktop version 2.24 and later.
You can use the following registry entry to allow machine registrations to any tenant.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\WOW6432Node\Microsoft\Power Automate Desktop\Registration | AllowRegisteringOutsideOfAADJoinedTenant | DWORD |
Value
- 1: Machines can register to any tenant.
Allow users to switch registration of their machine to a different tenant in Power Automate machine-runtime app
Note
This registry entry applies to Power Automate desktop version 2.24 and later.
You can use the following registry entry to allow switching machine registration to a different tenant.
| Hive | Key | Name | Type |
|---|---|---|---|
| HKEY_LOCAL_MACHINE | SOFTWARE\WOW6432Node\Microsoft\Power Automate Desktop\Registration | AllowTenantSwitching | DWORD |
Value
- 1: Machine registration can switch to another tenant.
See also
Feedback
Submit and view feedback for