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
- MC1558024: Microsoft 365 admin center Adds Multi-Tenant Management for Copilot, Agents, Costs, and Services

- MC1558020: Power Platform Admin Center Adds Reporting API for Copilot Credits (Preview)

- MC1558023: Microsoft Copilot in PowerPoint Adds Sales-Focused Skills for Sellers and Account Teams

- MC1558030: OneDrive for Windows and Mac Excludes node_modules Folders from Sync by Default







