Configure the ALM Accelerator using the admin app

You can configure the components of the ALM Accelerator for Power Platform either using its administration app or manually. This article guides you through using the admin app and is structured in seven sections:


Before you install the ALM Accelerator for Power Platform, make sure you've met the following prerequisites.

  • The ALM Accelerator must be installed in a Power Platform environment that has a Microsoft Dataverse database. All the environments you use the ALM Accelerator to deploy solutions to also require a Dataverse database.


    The ALM Accelerator isn't compatible with Dataverse for Teams. Both the ALM Accelerator app and the associated pipelines assume that you're using the full version of Dataverse in all environments.

    We recommend you install the ALM Accelerator in the same environment as other CoE Starter Kit solutions. Learn more about how to determine the best strategy for your organization:

  • The ALM Accelerator uses Azure DevOps for source control and deployments. If you don't have an Azure DevOps organization, sign up for free for up to five users on the Azure DevOps site.

  • To complete the steps in this section, you need the following users and permissions in Azure, Azure DevOps, and Power Platform:

    • A licensed Azure user with permissions to create and view Azure Active Directory (Azure AD) groups, create app registrations, and grant admin consent to app registrations in Azure AD
    • A licensed Azure DevOps user with permissions to create and manage pipelines, service connections, repos, and extensions
    • A licensed Power Platform user with permissions to create application users and grant them administrative permissions
  • The following connectors must be available to be used together in the environment into which the ALM Accelerator is imported:

  • Install the Creator Kit in the environment where you install the ALM Accelerator.

Configure Azure AD app registrations

The following steps are general to the functionality of the ALM Accelerator and aren't specific to any project or solution.

Create an app registration in your Azure AD environment

Create an app registration for the ALM Accelerator to grant the app and associated pipelines permissions required to perform operations in Azure DevOps and Power Apps or Dataverse. You only need to do this once.

The following steps show how to create a single app registration with permissions for both Dataverse and Azure DevOps. However, you might want to create separate app registrations to divide responsibilities. You should consider how separate app registrations affect both maintenance and security before you decide on an app registration strategy.

Create the app registration

  1. Sign in to the Azure portal.

  2. Select Azure Active Directory > App registrations.

  3. Select + New registration, and then give the registration a name, such as ALMAcceleratorServicePrincipal.

  4. Leave all other options at their default values, and select Register.

Add permissions to the app registration

  1. In the left side panel, select API permissions.

  2. Select + Add a permission.

  3. Select Dynamics CRM, and then select Delegated permissions and user_impersonation.

  4. Select Add permissions to add the Dynamics CRM API user_impersonation permission to the app registration.

  5. Select + Add a permission again.

  6. Select the APIs my organization uses tab. Search for and select PowerApps-Advisor, and then select Delegated permissions and Analysis.All (admin consent not required).

    This permission is required to run static analysis through the app checker.

  7. Select Add permissions to add the PowerApps-Advisor API Analysis.All permission to the app registration.

  8. Select + Add a permission again.

  9. On either the Microsoft APIs tab or the APIs my organization uses tab, select Azure DevOps, and then select Delegated permissions and user_impersonation.

    This permission is required for connecting to Azure DevOps through the custom connector in the ALM Accelerator app.

  10. If you added the Azure DevOps permission from the APIs my organization uses tab, copy the Application (client) ID for use later in this procedure.

    You'll use it as the DevOps Application (client) ID, which is different from the Application (client) ID you'll copy later in this procedure.

    Screenshot of the Request API permissions window, with the APIs my organization uses tab and Application (client) ID highlighted.

    If you can't find the Azure DevOps permission on the APIs my organization uses tab, follow these steps to get the DevOps Application (client) ID:

    1. Open a private browser window and go to<your devops organization>/_apis.
    2. On the sign-in page, copy the value of the client_id parameter in the URL.

    Screenshot of an Azure DevOps organization sign-in page, with the client_id parameter in the URL highlighted.

  11. Select Add permissions to add the Azure DevOps API user_impersonation permission to the app registration.

  12. Select Grant admin consent for <your tenant>.

Configure the client secret and redirect URI

  1. In the left side panel, select Certificates & secrets.

  2. Select + New client secret.

  3. Select an expiration date, and then select Add.

  4. Copy the client secret Value for use later. This is the only time you can copy the value. Be sure to do so before you leave the page.

  5. In the left side panel, select Overview.

  6. Copy the Application (client) ID and Directory (tenant) ID.

  7. Select Add a Redirect URI.

  8. Select + Add a Platform, and then select Web.

  9. For the redirect URI of the application, enter

    You might need to change this value after you install the ALM Accelerator app and configure the Azure DevOps custom connector. If the redirect URI that's populated in the custom connector is different from what you enter here, change this URI to match the one in the custom connector.

  10. Select Configure.

Give Power App Management permission to your app registration

Grant Power App Management permissions to your app registration so that the pipelines can perform the actions they need to in your environments. To do that, run the following PowerShell cmdlet as an interactive user that has Power Apps administrative privileges. You only need to run this command once, after you create your app registration.


The following PowerShell cmdlet gives the app registration elevated permissions like Power Platform Admin. Your organization's security policies may not allow these types of permissions. Make sure they're allowed before you continue. If they aren't allowed, certain capabilities don't work in the ALM Accelerator pipelines.

Install-Module -Name Microsoft.PowerApps.Administration.PowerShell
Install-Module -Name Microsoft.PowerApps.PowerShell -AllowClobber
New-PowerAppManagementApp -ApplicationId <the Application (client) ID you copied when you created the app registration>

Install Azure DevOps extensions

The ALM Accelerator uses several Azure DevOps extensions, including some third-party extensions that are available in the Azure DevOps marketplace. The website of each third-party extension and a link to their source code are provided in the following instructions. Learn how to evaluate a Marketplace extension publisher.

  1. Sign in to Azure DevOps.

  2. Select Organization settings.

  3. Select General > Extensions.

  4. Search for and install the following extensions:

Import the solution and configure the app

Import the ALM Accelerator canvas app into your Power Platform environment, and then configure the included custom connector for Azure DevOps.

Install the ALM Accelerator in Dataverse

  1. Download the latest managed solution file from GitHub. Scroll down to Assets and select CenterofExcellenceALMAccelerator_<latest version>

  2. Sign in to Power Apps, and then select the environment you want to host the ALM Accelerator app.

  3. In the left side panel, select Solutions.

  4. Select Import solution > Browse, and then browse to the location of the managed solution you downloaded and select the file.

  5. Select Next, and then select Next again.

  6. On the Connections page, select or create a connection to connect the CDS DevOps connection to Dataverse.

    When you create a connection for HTTP with Azure AD, use Microsoft Graph for both parameters.

  7. Select Import.

Configure the DevOps custom connector

  1. Select Data > Custom Connectors > CustomAzureDevOps.

  2. Select Edit.

  3. On the Security tab, select Edit, and then set the following values:

    Name Value
    Authentication Type OAuth 2.0
    Identity provider Azure Active Directory
    Client ID The Application (client) ID you copied when you created the app registration
    Client secret The Application (client) secret value you copied when you created the app registration
    Tenant ID Leave the default value, common
    Resource URL The DevOps Application (client) ID you copied when you added permissions to your app registration
  4. Select Update connector.

  5. Confirm that the Redirect URL on the Security page is

    If it isn't, copy the URL. Return to the app registration you created earlier and replace the redirect URI there with the copied URL.

Test the custom connector

  1. Open the Test menu.

  2. Select New Connection, and then follow the prompts to create a connection.

  3. In Power Apps, select your environment, and then select Dataverse > Custom Connectors > CustomAzureDevOps.

  4. Select Edit, go to the Test page, and then find the GetOrganizations operation.

  5. Select Test operation.

  6. Confirm the Response Status returned is 200 and that the Response Body is a JSON representation of your Azure DevOps organization.

    Screenshot of test security settings for a custom Azure DevOps connector.

Set up your first Azure DevOps project for use with the ALM Accelerator

Use the included wizard to set up your Azure DevOps project to deploy Power Platform solutions using the ALM Accelerator. You can configure an existing empty project or create one.

  1. Open the ALM Accelerator administration app.

  2. In the left side panel, select Projects in the Azure DevOps group.

  3. If you're prompted to update Release Tags, select Okay.

  4. Select your Azure DevOps organization in the list.

  5. In the Projects List, select New.

  6. Select Project Wizard.

  7. In the Project step, enter the name of your project. Optionally, enter a description and enable preview features.

  8. Select Next.

  9. In the Pipeline Templates step, select Next to install templates in your project.

    The app installs the pipeline templates into a new repository in the project. Alternatively, you can configure the project to use templates from a project that already has them installed.

  10. In the Service Connections steps, select the environments for which you want to create a service connection.

    You can select multiple environments and create service connections for all of them at the same time. To use different app registrations for your environments, create a service connection for each app registration individually.

  11. After you configure a service connection for an app registration, select Add.

  12. After you've configured all the service connections, select Next.

  13. In the Generic Pipelines step, select Next to create the pipelines and variable group and set the Azure DevOps permissions the project needs for ALM Accelerator functionality.

Create an app user in your Dataverse environments

Create an application user in your environments to allow the pipelines to connect to Dataverse. Do this in each environment you plan to use the ALM Accelerator to deploy to.

  1. Sign in to the Power Platform admin center.

  2. Select your development environment, and then select Settings.

  3. Select Users + permissions > Application users.

  4. Select + New app user.

  5. Select + Add an app, select the app registration you created earlier, and then select Add.

  6. Select the Business Unit.

  7. Select the pencil icon to the right of Security roles, and then select security roles for the app user.

    We recommend you give the app user system administrator security role privileges, so the user can perform the required functions in each environment.

  8. Select Create.

Repeat these steps in your validation, test, and production environments.

Set up makers to use the ALM Accelerator app

Read more