{"title":"Application lifecycle management for Power Apps in Business Central (preview)","url":"https://jonas-paprotka.de/docs/dev-itpro/powerplatform/power-apps-alm/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/powerplatform/power-apps-alm, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/powerplatform/power-apps-alm","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn how to use AL-Go to implement application lifecycle management (ALM) for your Power Apps","date":"2023-04-21","meta":{"topic":"article"},"outline":[{"level":1,"title":"Application lifecycle management for Power Apps in Business Central (preview)","slug":"application-lifecycle-management-for-power-apps-in-business-central-preview","at":0,"chars":4307},{"level":2,"title":"New and updated workflows","slug":"new-and-updated-workflows","at":1625,"chars":1652},{"level":3,"title":"CI/CD","slug":"cicd","at":1783,"chars":239},{"level":3,"title":"Create Release","slug":"create-release","at":2022,"chars":219},{"level":3,"title":"Publish to Environment","slug":"publish-to-environment","at":2241,"chars":289},{"level":3,"title":"Pull Power Platform changes","slug":"pull-power-platform-changes","at":2530,"chars":355},{"level":3,"title":"Push Power Platform changes","slug":"push-power-platform-changes","at":2885,"chars":392},{"level":2,"title":"How to connect your AL-Go for GitHub repository to your Power Platform environment","slug":"how-to-connect-your-al-go-for-github-repository-to-your-power-platform-environment","at":3277,"chars":383},{"level":2,"title":"Known limitations","slug":"known-limitations","at":3660,"chars":385},{"level":2,"title":"Next steps","slug":"next-steps","at":4045,"chars":262}],"text":"# Application lifecycle management for Power Apps in Business Central (preview)\n> IMPORTANT\n> Some or all of the functionality noted in this article is available as part of a preview release. The content and the functionality are subject to change.\nWhen you're building and distributing software services, application lifecycle management (ALM) is key. For Power Platform, ALM means having your artifacts in a Power Platform solution and using a designated tool to manage its lifecycle.\nSolutions are the basis of all ALM in the Power Platform now and going forward. This methodology also applies to Power Apps. To learn more about solutions and ALM in the Power Platform, see Develop an application lifecycle management strategy<https://learn.microsoft.com/training/modules/application-lifecycle-management-strategy/> module on Microsoft Training.\nBusiness Central offers full ALM support for Power Platform solutions in our Al-Go for GitHub template. The integration lets you store your AL and Power Platform artifacts in a single repository&mdash;where you can manage it with a unified set of tools. This setup means you can add Power Platform artifacts to your offering without any extra management and setup cost.\nThe Al-Go for GitHub template is open source and based on the GitHub Actions for Microsoft Power Platform<https://github.com/marketplace/actions/powerplatform-actions>. For now, we only support per-tenant extensions, not Marketplace extensions. To learn more, about the template and how to use it, go to https://github.com/microsoft/AL-Go/tree/PPPreview<https://github.com/microsoft/AL-Go/tree/PPPreview>.\n## New and updated workflows\nAs part of the new support for Power Platform solutions, we have updated the following workflows and added a couple of new ones:\n### CI/CD\nThe CI/CD workflow has been updated with more steps to support Power Platform solutions. If you have added any configuration for a Power Platform solution to your Al-go settings, they're automatically part of your CI/CD process.\n### Create Release\nThe Create Release workflow has been updated to support Power Platform solutions. The workflow creates a GitHub release and uploads the Power Platform solution and AL artifacts to the repo as assets.\n### Publish to Environment\nThe Publish to environment workflow has been updated to support Power Platform solutions. The workflow now has more steps that check that the AL extension has been successfully deployed, and then deploys the Power Platform solution to the environment specified.\n### Pull Power Platform changes\nThe Pull Power Platform changes workflow is a new workflow that makes working with Power Platform solutions easier. The workflow pulls the latest published changes to a Power Platform solution into your repository. The flow can either do direct commits to the main branch or create a PR with the latest changes for review.\n### Push Power Platform changes\nThe Push Power platform changes workflow is a new workflow that makes working with Power Platform solutions easier. The workflow lets you push your latest Power Platform solution changes to a specified environment.\nThis workflow is especially useful when working multiple people on feature branches, where you don't have release or CI/CD artifacts to publish.\n## How to connect your AL-Go for GitHub repository to your Power Platform environment\nTo connect your Al-Go for GitHub environment to Power Platform, you need to create an authentication context, and update the Al-GO Settings file with the relevant connection information.\nFor detailed step-by-step guide, see the Al-go ReadMe file: https://github.com/microsoft/AL-Go/tree/PPPreview\n## Known limitations\n Hard-coded Business Central connection information\n  The connection to Business Central is hard coded into the Power App files, which means that you must use the Publish Environment or Push Power Platform changes actions to deploy the package. If you manually deploy the package, you need to update the connection references manually inside the maker experience.\n## Next steps\n Use the available sample apps as an easy starting point to try Business Central and Power Platform. See power-apps-samples.\n Review the Best practices for Power Apps with Business Central<power-apps-best-practices> for tips on building Power Apps."}