CoE ALM Accelerator for Power Platform before you start
The ALM accelerator for Microsoft Power Platform is currently in public preview. While in preview we will be prioritizing feedback and bugs via GitHub New issue. If the issue is something in the platform all we can do is funnel feedback to the responsible product teams. For more information on the current preview status of the ALM Accelerator for Power Platform follow this link.
Before you start an install of ALM Accelerator, ensure that you've the following components in place.
CoE command line
Install the CoE CLI locally or via a docker image.
|Developer||Development environments that each maker will use to create and manage source-controlled solutions.|
|ALM environment||Environment with Microsoft Dataverse enabled. Will be used to deploy managed solution.|
|ALM environment - Dataverse connection||See Maker environment Dataverse below to create the Dataverse connection.|
|Validation||Environment used to validate builds before merging into a solution branch.|
|Test||Pre-production environment used to test solutions before moving to production.|
|Production||Production environment for managed solutions.|
As a Microsoft Partner you can request access to demo tenants to test ALM Accelerators for Power Platform.
- Visit Partner Center for more information.
- Go to https://demos.microsoft.com to request a new environment.
- Select My Environments.
- Select Create Tenant.
- Select tenant location.
- Select the Dynamics 365 Customer Engagement content pack.
Sample environment from https://admin.powerplatform.microsoft.com/environments for a Demo Deployment.
Maker environment Dataverse connection
In the maker environment, you'll need a Dataverse connection created by the install user.
To create the Dataverse connection, use the following steps:
Go to https://make.powerapps.com/.
Select the maker environment that you'll deploy the ALM Accelerator for Power Platform into.
Go to to Data > Connections.
Select New Connection.
Select Microsoft Dataverse (legacy).
Ensure the user you run with has the following permissions.
|Global administrator or privileged role administrator||Grant tenant-wide admin consent to an application. More information:Grant admin consent|
The following components must be installed before the CoE CLI ALM install can begin.
|Organization||Review Add organization users to create Azure DevOps organization and add users.|
|Project||An Azure DevOps project to integrate with. This guide uses the name alm-sandbox as the project name.|
The following is set up or used as part of the install and follow on coe alm branch.
|Extensions||Review the extensions configuration that will be installed.|
|Repository||Ensure the git repository has been initialized with an initial commit.|
If installing using demo tenant, you can request a trial Azure DevOps environment.
Select Start free.
Create an initial project, for example, alm-sandbox.
Review the Azure DevOps Extensions that will be installed by the CLI application to ensure your organization gives consent for them to be installed.
Once you've verified the above:
Determine the install deployment scenario you're targeting.
Complete the Administration install.
Submit and view feedback for