{"id":126096,"date":"2024-10-14T08:08:00","date_gmt":"2024-10-14T15:08:00","guid":{"rendered":""},"modified":"2025-05-14T18:26:47","modified_gmt":"2025-05-15T01:26:47","slug":"exciting-new-updates-for-pipelines-in-power-platform","status":"publish","type":"post","link":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/2024\/10\/14\/exciting-new-updates-for-pipelines-in-power-platform\/","title":{"rendered":"Exciting New Updates for Pipelines in Power Platform"},"content":{"rendered":"\n

This month, we’ve got a lot of game-changing features lined up for Pipelines, and in this blog, I’ll be going over the latest and greatest updates that Makers and Admins can both get excited about.<\/p>\n\n\n\n

Make your Custom Pipelines Host Discoverable by Default<\/h2>\n\n\n\n

If you as an admin want to enable your makers to discover your custom host instead of the tenant-wide platform host when they navigate to Pipelines, this is the feature you\u2019ve been waiting for. Since a change made earlier this year, the platform host and its capabilities became the landing pad for any maker going to the Pipelines page due to its out-of-the-box readiness.<\/p>\n\n\n\n

Before, if admins wanted makers to use centrally governed pipelines in a custom host instead of using personal pipelines in the platform host, they would have to first set up a custom host and associate makers\u2019 development environments with it. With a default custom host set, those with pipelines create-access and owners of existing pipelines in that custom host can associate new development environments easily by simply going to the Pipelines experience in those development environments and deploying through a pipeline in the host (new or existing).<\/p>\n\n\n

\"\"Use<\/figure>\n\n\n\n

\u201cUse a custom pipelines host\u201d Setting<\/h3>\n\n\n\n

Now, when tenant admins navigate to the Deployment Pipeline Configuration app for the platform host (by clicking \u201cManage pipelines\u201d from the Pipelines page in make.powerapps.com), they will see a new setting under Advanced Settings<\/strong>. Admins can then provide the environment ID for a custom pipelines host to use instead of the platform host when makers are using pipelines in an environment that has not yet associated with a pipelines host.<\/p>\n\n\n\n

If makers already used the platform host to deploy, it is important to note that the environments in use must be disassociated from that host before they can be used in the newly assigned custom host.<\/p>\n\n\n\n

A new world of possibilities for ALM readiness<\/h3>\n\n\n\n

Now that admins can assign custom hosts as the default host for their makers\u2019 Pipelines experience, they can also granularly control who can create personal pipelines (within that custom host) when they land on Pipelines in any development environment, even if it’s not already associated with the host. Admins can achieve this by assigning the \u201cDeployment pipeline default\u201d role to users or groups within their custom host who they wish to enable personal pipeline creation for. And, of course, makers who don\u2019t have pipelines create-access can use any pipelines that are shared with them by an admin!<\/p>\n\n\n\n

Copilot-generated deployment notes are now available worldwide in 20 supported languages<\/h2>\n\n\n\n

Finally, Copilot-generated deployment notes are available in 20 major languages* for Makers outside of the U.S. Now, depending on your language settings in the Power Platform page you’re deploying from, Copilot will generate deployment notes in that language. Of course, this also means that Copilot can read and process solutions that aren’t just in English!<\/p>\n\n\n\n

*supported languages include English, Chinese (Simplified), Czech, Danish, Dutch, Finnish, French, German, Greek, Italian, Japanese, Korean, Norwegian (Bokm\u00e5l), Polish, Portuguese (Brazil), Russian, Spanish, Swedish, Thai, and Turkish.<\/p>\n\n\n\n

Import solutions from the environment’s associated pipelines host<\/h2>\n\n\n\n

Need to hydrate a development environment with a solution that you’ve deployed via Pipelines in the past? Or maybe you’re an admin and one of your makers left the organization along with their personal dev environment? Now, you don’t have to look for the solution manually or upload a .zip file! All solutions deployed through pipelines are now easily accessible in the solution import experience.<\/p>\n\n\n

\"\"<\/figure>\n\n\n\n

Makers can view any solution that they have deployed, while admins can view all deployed solutions in the organization by toggling on Show shared solution deployments<\/strong>. Makers can use this toggle too, but only if enabled through a new admin-controlled Advanced Setting in the Deployment Pipeline Configuration app.<\/p>\n\n\n

\"\"<\/figure>\n\n\n\n

Coming soon<\/h2>\n\n\n\n

Stay tuned for more exciting Power Platform ALM features coming later this year, and be sure to check out Microsoft Ignite taking place November 18\u201322, 2024 for highly anticipated announcements!<\/p>\n\n\n\n

Learn more about Pipelines and ALM<\/h2>\n\n\n\n