![Power Platform – Associate dev environments in default deployment pipeline [MC1079761]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-dominikagregus-992320-1024x683.webp "Power Platform - Associate dev environments in default deployment pipeline [MC1079761] 1")
Message ID: MC1079761
We are announcing the ability to associate development environments in default deployment pipeline in Power Platform resulting in scalable, healthy application lifecycle management (ALM). This feature will reach general availability on June 16, 2025.
How does this affect me?
The default deployment pipeline rule empowers admins to configure a pipeline for all makers in the development environments of their environment group by:
- Selecting a (custom) pipelines host.
- Selecting a pipeline.
- In the future, selecting a specific team to share pipeline access with.
- In the future, locking down the target environments to any unmanaged customizations (imports) outside of this pipeline.
What action do I need to take?
This message is for awareness and no action is required.
Source: Microsoft
Latest Posts
- (Updated) Microsoft Viva Glint: Use Feature Access Management in Viva for Microsoft 365 Copilot in Glint [MC1004409]
- (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions [MC1019312]
- Microsoft Teams: New bilateral chat policy for restricting external group chats to a maximum of two organizations [MC1080690]
- Dynamics 365 Project Operations – Enable number sequences in expense management [MC1079742]
![Power Platform admin center – Dark Mode in the new PPAC [MC1079777]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-olly-914931-150x150.webp "Power Platform admin center – Dark Mode in the new PPAC [MC1079777] 6")
![Power Apps – Edit new and existing tables in Plan designer [MC1079753]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-161702-150x150.webp "Power Apps – Edit new and existing tables in Plan designer [MC1079753] 7")