Issues and new features in this release
https://github.com/microsoft/coe-starter-kit/milestone/16?closed=1
See what's new in this release
First Time Setup Instructions
To get started with the ALM Accelerator For Power Platform you can use the CoE CLI to automate the install at https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-almacceleratorpowerplatform-cli
Upgrade Instructions
If you are upgrading to the latest release you will need to perform the following steps.
-
Delete the existing ALM Accelerator for Advanced Makers solution.
NOTE: We've changed the internal name of the ALM Accelerator solution in this release. As a result you will need to delete the existing solution, which will cause your App Settings to reset. The history of previous commits and deployments in the app will be lost, but the history will remain in Azure DevOps.
-
Import the latest managed AA4PP Solution https://github.com/microsoft/coe-starter-kit/releases/download/CenterofExcellenceALMAccelerator-January2022/CenterofExcellenceALMAccelerator_1.0.20220114.1_managed.zip
-
Update your pipeline templates repo with the latest from https://github.com/microsoft/coe-alm-accelerator-templates/archive/refs/tags/CenterofExcellenceALMAccelerator-January2022.zip
Additional Setup Instructions
-
Update the Azure DevOps Build Service Permissions to allow the pipelines to create deployment pipelines.
NOTE: In the latest release, the pipeline which is executed when a solution is committed to source control, will create the associated deployment pipelines automatically if they don't exist. As a result the pipelines need permissions to access resources in Azure DevOps via the following configuration in Azure DevOps.
- Follow the instructions here to update the appropriate permissions (https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-almacceleratorpowerplatform#update-permissions-for-the-project-build-service)
-
Register service principal as management application
NOTE: In order for the pipelines to perform certain actions (for example, Sharing Apps) against the environments in your Power Platform tenant you will need to grant Power App Management permissions to your App registration. To do so you will need to run the following PowerShell commandlet as an interactive user that has Power Apps administrative privileges. You will need to run this command once, using an interactive user, in PowerShell after your app registration has been created. The command gives permissions to the Service Principal to be able to execute environment related functions including querying for environments and connections via Microsoft.PowerApps.Administration.PowerShell (https://docs.microsoft.com/en-us/powershell/module/microsoft.powerapps.administration.powershell/new-powerappmanagementapp?view=pa-ps-latest). For more information on the New-PowerAppManagementApp cmdlet see here https://docs.microsoft.com/en-us/powershell/module/microsoft.powerapps.administration.powershell/new-powerappmanagementapp?view=pa-ps-latest
Currently this commandlet gives elevated permissions (for example, Power Platform Admin) to the app registration. Your organization's security policies may not allow for these types of permissions. Ensure that these permissions are allowed before continuing. In the case that these elevated permissions are not allowed certain functions in the ALM Accelerator pipelines will not work.
Install-Module -Name Microsoft.PowerApps.Administration.PowerShell Install-Module -Name Microsoft.PowerApps.PowerShell -AllowClobber New-PowerAppManagementApp -ApplicationId [the Application (client) ID you copied when creating your app registration]
Change Log
- #220-AA4AM: status icons are not reset within solution gallery
- #353-[AA4AM] Better visibility / linking of a Solution to a DevOps Project / Repository
- #817-[AA4AM] Move Docs to Microsoft Docs
- #831-[AA4AM] Reconfigure CoE Starter Kit Pipelines
- #867-[AA4AM]: New-PowerAppManagementApp Provides CRUD Operations to Environments
- #926-[CoE CLI]: Add option to disable limit job authorization scope to referenced Azure DevOps repositories
- #928-[CoE CLI] Make Service Connections Available to all Pipelines
- #931-[CoE CLI]: Allow Pipeline Access to Global Variable Group in AA4AM Setup
- #955-[AA4AM] New Maker UX
- #1019-[AA4AM] Update Release Pipelines to Use a CoE Bot Account
- #1118-[AA4AM] Validation / Creation of Deployment Pipelines in Maker App
- #1121-[AA4AM] Deployment Profiles
- #1267-[ALM Accelerator - BUG]: Settings for user have disappeared.
- #1268-[ALM Accelerator - BUG]: ALM4AM does not load connection references on config
- #1272-:heavy_exclamation_mark: Canvas Unpack Fails PAC CLI Version 1.9.8 (Workaround)
- #1351-[ALM Accelerator - BUG]: Deployment Settings - Dropdown limits number of items
- #1357-[ALM Accelerator - BUG]: Solution import failed using Quickstart
- #1439-[AA4AM] January Release Docs Update
- #1480-[AA4AM] Rename Solution
- #1523-[coe-cli] Remove PowerAppManagementApp permissions from SP
- #1551-[AA4AM] Auto Assign Issues to Projects
- #1553-[AA4AM]: Canvas Unpack Failing in PAC CLI
- #1562-[ALM Accelerator - BUG]: jq already on hosted agent
- #1612-[ALM Accelerator - BUG]: Export-to-Git pipeline fails
- #1682-ALM on ADO with Advanced Maker preview or template availability?
- #1698-[coe-cli] Add required permissions for the Devops Build Service
- #1749-[AA4PP] Update aka.ms links when docs are published.
- #1757-Updating upgrade link
- #1758-[AA4PP] Update Video Links