{"id":27798,"date":"2024-04-11T08:00:16","date_gmt":"2024-04-11T16:00:16","guid":{"rendered":""},"modified":"2025-06-11T07:41:53","modified_gmt":"2025-06-11T14:41:53","slug":"alm-for-your-entire-organization-april-2024-update","status":"publish","type":"post","link":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-apps\/alm-for-your-entire-organization-april-2024-update\/","title":{"rendered":"April 2024 ALM blog: What\u2019s new and what it means for you"},"content":{"rendered":"

With enterprises rapidly expanding Power Platform adoption, and non-traditional and traditional developers building business critical solutions, we\u2019ve needed to re-imagine enterprise ALM in Power Platform. As this story unfolds, customers can adopt a unified ALM strategy across their entire portfolio while drastically reducing overhead, complexity, and failure points. This post outlines various new capabilities materializing under this vision and how to align your organization\u2019s ALM strategy for the next generation of growth.<\/p>\n

\"ALM<\/div>\n
\n

Initiate<\/h2>\nAdmins empower makers<\/strong> to get started easily, by configuring environment groups and rules<\/a> to automatically route<\/a> them to an appropriate development environment, set sharing limits<\/a> to prevent use of development environments for shadow production, configure secure pipelines and approvals<\/a> to ensure least privileged access<\/strong>, and block customization in test and production<\/a> for added protection. This ensures production environments are secure<\/strong> and all changes are approved<\/strong> via governed SDLC processes.<\/div>\n
\u00a0<\/div>\n
With these updates, we’re excited to announce the general availability of delegated deployments <\/a><\/strong>for pipelines in Power Platform! \n
\"Animated<\/figure>\nAdditionally, admins can now enable pipelines<\/a> for multi-geo support<\/strong>, making it easy to centrally administer global deployments within a single management plane. \"Cross-geo\n

Build<\/h2>\nAs makers develop, customizations are automatically saved to their preferred solution<\/a> (no need to understand or navigate to solutions). This avoids downstream deployment issues, painful debugging steps, and other common mishaps.\n
\"Setting<\/div>\n\u00a0When authoring solution cloud flows, drafts and versioning<\/strong><\/a> provides a history for each published version of the flow. Makers can view <\/strong>the version history, restore prior versions<\/strong>, and save draft changes<\/strong> without publishing them live – even if the flow has errors<\/strong>! Then, the flow can be published <\/strong>when they are ready to run the flow. Please leave your drafts and versioning comments and feedback here<\/a>.<\/em> \"Drafts\n

Test<\/h2>\nAdmins can improve quality by ensuring solution checker runs on every deployment<\/a>, and configure issue tolerance levels for different environments. Pipelines can be extended<\/a> to run additional code and security scanning tools, or automated tests<\/a> by integrating your source control systems. Functional user acceptance testing is also recommended after deployment to test environments.<\/div>\n
We recommend starting with pipelines in Power Platform and using extensions if you need to integrate more advanced workloads running in Azure DevOps, GitHub, etc. Similarly, if taking dependencies on test automation, we recommend Test Engine.<\/em>\n

Release<\/h2>\nMakers are guided to deploy at the right time<\/strong>. For example, when manually exporting and importing solutions or blocked by sharing limits<\/strong>.\n
\"sharing<\/div>\n
Instead, sharing is<\/strong> requested during deployment<\/strong> to target<\/span> environments, like production, where it’s appropriate to share broadly. Admins simply need to approve the combined deployment and sharing request, and the rest happens automatically. Sharing is rolling out for canvas apps and soon for cloud flows and security roles.<\/em>\n
\"sharing\"<\/div>\n
Makers can also update existing environment variables and connection references<\/strong><\/a> in pipelines and solution import. Combined, these capabilities protect production assets with least privileged access, reduce admin burden, and train makers to submit all updates via your organization\u2019s change management process. If admins haven\u2019t configured pipelines and governance policies, makers are empowered to create their own pipeline<\/a><\/strong> to environments (they must already have access to manually import solutions. Pipelines doesn’t escalate permissions).<\/em> \"Pipelines Admins can apply additional governance controls and manage security within the default host and custom hosts. There’s a new entry point within the solution experience to Manage pipelines <\/em>and a\u00a0Security Teams<\/strong> section in the app to manage pipelines access. Note: we currently recommend using a custom pipelines host when more advanced control is desired.<\/em>\n
\u00a0<\/div>\n
Why pipelines vs manual export\/import?<\/strong> Unlike manual export\/import, pipelines<\/a> stores backups for every version of every solution deployed, and admin accessible audit logs describing who, what, when, where, and why (AI provided). Pipelines deployments enjoy higher success rates<\/strong> by pre-validating solutions against target environments and sequencing<\/strong>\u00a0multiple deployments <\/strong>to avoid conflicts.\u00a0<\/strong><\/div>\n
\u00a0<\/div>\n
Solution simplification<\/strong> remains an ongoing effort. Recent improvements include streamlined dependency management<\/a> and automatic conversion of unmanaged to managed solution objects (see moving from unmanaged to managed solutions<\/a>).<\/div>\n
\u00a0<\/div>\n
What if breaking changes are inadvertently deployed?<\/strong> Now makers and admins can now re-deploy prior solution versions<\/strong><\/a> using pipelines or developer tooling.<\/div>\n<\/div>\n
\n
\u00a0<\/div>\n
\"redeploy\"<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\u00a0<\/div>\n
Disclaimer: Some capabilities are still rolling out and may not be available yet in your region. Some require admin opt-in, and others can be enabled by installing the latest version of the Power Platform Pipelines application or Power Platform CLI. Documentation updates have a different lifecycle than blogs – please be patient if you don’t see something on docs right away. Thank you!<\/em><\/div>\n
\n

Developers<\/h2>\n
\n
We’re incredibly excited for the Microsoft Build conference next month. We have big announcements planed that we think you’ll love!<\/div>\n
\u00a0<\/div>\n
Connect with the product team during the Power Platform Developer Office Hours: https:\/\/aka.ms\/ProDevCommunity<\/a><\/div>\n
\u00a0<\/div>\n
Developer tooling release notes for every version are published at the below locations:<\/div>\n