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
- Amazon Bedrock Managed Knowledge Base now supports Confluence Data Center as a native data source connector
- Amazon Bedrock Managed Knowledge Base adds APIs and console support for debugging document-level access control
- AWS Lambda now supports Graviton5-powered EC2 instances on Lambda Managed Instances
- AWS Systems Manager now diagnoses more issues that cause EC2 instances to be unmanaged
