---
title: Azure App Registration (Power Automate Desktop)
slug: blueprint/azure-app-registration-power-automate-desktop
createdAt: 2026-04-17T18:28:54.237Z
---

:::hint{type="warning"}
These instructions apply only to integration with Power Automate Desktop (PAD).
:::

Blueprint integrates with Power Automate Desktop to accelerate and scale robot development and orchestration. Users can seamlessly export and upload aligned and prioritized business processes along with all related constraints into PAD, to provide robot developers with a head start and unparalleled visibility and context.

To enable export to PAD and certain ALC features, you must first create an Azure App Registration.

***

# How to Create an Azure App Registration

1. Navigate to the [App Registrations section of the Azure Portal](https://portal.azure.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade).
2. Select **New Registration** at the top of the page.

   ![](https://files.helpdocs.io/4rdnduk17o/articles/xbnop03w2f/1630090701992/image.png)
3. Name your app (e.g., "Blueprint-PAD Integration").
4. Within the **Supported Account Types** section:
   - Select **Accounts in this organizational directory only.**
5. Within the **Redirect URI (Optional)** section:
   - From the dropdown menu, select **Single Page Application (SPA)**
   - In the text field, enter your Blueprint URL with a **trailing slash** (e.g., https\://YourBlueprintSite.acme.com/)
6. Select **Register** at the bottom of the page.

::Image[]{src="https://files.helpdocs.io/4rdnduk17o/articles/xbnop03w2f/1631826198168/image.png" size="100" isUploading="false" width="1652" height="915" darkWidth="1652" darkHeight="915" showCaption="false" indent="1"}

7. Your app should now be registered. You will need the enter the Application (client) ID and Directory (tenant) ID values into Blueprint to complete the configuration.

:::hint{type="info"}
See here for how to [Microsoft Connection](docId\:ZoxcTj3VK7aGp9feDw-Te)
:::

***

# Permissions Required

Once you've configured your Azure App Registration for Blueprint, users who are part of an organization's Azure Active Directory and already have access to the provided PAD environment won't need any additional permissions manually assigned. (For Default PAD environments, access is automatically granted to everyone by default.)

During the configuration process in Azure App Registration, the only permission required is **Microsoft Graph -> User.Read**. This permission is automatically created by default and can be located under the **API Permissions** tab.

![](https://files.helpdocs.io/cvxv0fr0i5/articles/flqgdbg3ge/1704208073093/image.png)

Blueprint will request additional permissions the first time a user attempts to export to PAD or import Flows to ALC. Users will need to accept these permissions to export to PAD.

::Image[]{src="https://api.archbee.com/api/optimize/HRPaq4oJ2h9pHAfcjJGa6/9Z9zu9RYMi22JwG1BtZlD_image.png" size="30" isUploading="false" width="879" height="1136" darkWidth="879" darkHeight="1136" showCaption="false"}

**Flow Permissions Requested by Blueprint:**

- **Flows.Read.All**: Allows the application to see which environments does this user have, and what flows are in them
- **user\_impersonation**: Allows the application to act on Dataverse as the signed-in user 
  - The app gets to call the Dataverse API with your identity and do anything you're allowed to do there, specifically reading and writing flows

***

# Admin Permissions Error: Need Admin Approval

Some organization may encounter a **Need admin approval **error as shown below.

::Image[]{src="https://files.helpdocs.io/cvxv0fr0i5/articles/flqgdbg3ge/1706719261527/image.png" size="60" width="1407" height="1109" darkWidth="1407" darkHeight="1109" position="center" showCaption="false"}

As an Azure Admin, this issue can be solved in one of two ways:

## Admin Permissions Fix - Option 1

1. In your Azure Portal, navigate to Enterprise Applications -> Consent and Permissions -> User Consent
   - If setting "User consent for applications" is set to "Do not allow user consent", consider switching to "Allow user consent for apps from verified publishers, for selected permissions (Recommended)"

![](https://files.helpdocs.io/cvxv0fr0i5/articles/flqgdbg3ge/1706719748805/image.png)


If option 1 is not a possibility for your organization, please try Option 2.

## Admin Permissions Fix - Option 2

1. In your Azure Portal, navigate to Enterprise Applications -> click your Blueprint app registration > Permissions
   - Click the blue "Grant admin consent for" button

![](https://files.helpdocs.io/cvxv0fr0i5/articles/flqgdbg3ge/1706719712506/image.png)