What’s new since preview?

While the most impactful improvements are better reliability, performance, and usability, there’s many new and noteworthy capabilities.

• Disconnect from Git – You can easily disconnect your environment or solution from Git and reconnect to a different source code location or branch.
• Support for existing solutions and large solutions – These critical preview limitations are now addressed. Connect existing solutions in your environment and you won’t be limited by solution size when committing large solutions.
• Public API’s – Now you can interact with Git using Dataverse API’s and build automations to scale the process.
• Support for more object types – most solution components are now supported and we’re incrementally onboarding the remaining legacy components / objects.
• Delete when pulling – when an object is deleted in Git, you now have the option to delete it from your environment or remove from your solution on pull.
• Better user experiences – Git integration is available in Copilot studio (and other maker portals), with improved discoverability, usability, and columns showing who changed what and when.
• Geo availability – Git integration is GA in all public geos and coming soon to sovereign clouds.

Source Control your Canvas Apps

Dataverse Git Integration is the new standard, replacing the experimental Power Apps integration. If you’re still using the old setup, we recommend migrating to the new integration as soon as possible.

With Dataverse Git Integration, you get complete visibility into your source code – no conversions required. You can use pa.yaml files in your repository to manage source control and review changes made in Power Apps Studio, all without the clutter of noisy diffs.

The schema for canvas source code (pa.yaml files) is now published, and no breaking changes are anticipated moving forward.

What’s next?

General availability doesn’t indicate a feature is done – or that it’s without limitations. Rather, Microsoft is confident in the quality for production use. It’s important to evaluate whether current functionality meets your requirements.

Next up is unlocking code-first development. Soon, developer tools will support the new (YAML) format, which is easier to read, understand, and merge. Modern developers can then build and deploy solutions and code from source control with less effort and without prior domain knowledge.

For canvas apps, we will also start to enable (as preview) the capability to edit pa.yaml files directly in your repository.

We’ll be showing code-first demos at Microsoft Build next month, plus many other new and exciting Managed Operations and other capabilities.

Learn more

Setup Git Integration

FAQ

Source Code files for canvas apps

The post Git Integration is Generally Available appeared first on Microsoft Power Platform Blog.

Maker Deployment page

Makers can now view all their deployments in one place, regardless of solution or pipeline. If their deployment began from (or was deployed to) the current environment, they will be able to view the run history status of it. Failed Deployments and Active Deployments are highlighted in a convenient overview, so you don’t have to go looking for them either!

In addition to deployment visibility, we’ve included a Get started section that will evolve over time. For now, it will link to documentation to help a maker begin their journey to healthy application lifecycle management (ALM).

To further improve understanding of what healthy ALM looks like, we’ll soon be adding recommendations, where makers are alerted to resolve any potentially unhealthy ALM-related behavior, such as housing high-use apps outside of a solution.

Admin Deployment page

The Deployment page in the new admin center provides a streamlined experience to help administrators learn about, setup, and operation best-in-class ALM. The initial preview provides a central location to view all deployments in the tenant, approve deployment requests, and troubleshoot failures.

Select a pipelines host from the picker to see all the pipelines and deployment history managed with that host. A dedicated Failed deployments view helps admins quickly identify and troubleshoot failures and trending issues.

Admins can approve or reject deployment requests assigned to them. First setup Delegated deployments with service principals as the recommended way to deploy securely.

It is important that admins review changes in the solution and the sharing request. With the help of Copilot-generated deployment notes visible in the request, this becomes easier, but if you want a more granular look, be sure to set up Source control integration and link the repository to the approval.

Managed Operations

The Deployment pages are an offering of Managed Operations, allowing all who make or administrate to gain further insight into their Application Lifecycle Management to ensure that business solutions are reliable and performant in production. Aside from just deployment pipelines, these maker and admin experiences will evolve over the coming months and include many more Managed Operations intersections to take advantage of. So, stay tuned for more updates and please leave your feedback below!

Learn more

Admin Deployment page

Maker Deployment page

Managed Operations

New Power Platform Admin Center

The post Introducing Maker and Admin Deployment Pages appeared first on Microsoft Power Platform Blog.

It just takes a few seconds to connect your Dataverse environment to Git. You can connect and use Git integration within Power Apps, Microsoft Copilot Studio, Power Automate, and Power Pages. You’ll also need access to an Azure DevOps Git repository.

Rollout is in-progress. Git integration is currently available in public geos outside the US. Your environment must be enabled for early access and accessed at https://make.preview.powerapps.com.

As the team develops, Dataverse tracks everyone’s changes. When ready, commit your changes to a branch in the connected Azure DevOps Git repository. A commit link is provided to view the changes within the repository and compare diffs. You’ll notice solutions and solution objects are now stored in human readable formats in the repo.

Professional developers can work in source control while others work in one or more environments. It’s easy to pull others’ changes into other development environments which are connected to the same source code location. This allows team members to build without others editing in their environment and share changes once they’re ready. Connect multiple development environments using the same repo, branch, and folder. Then, in each environment create or import an unmanaged solution with the same name and publisher.

When committing and pulling changes, conflicts may be detected – meaning someone else made conflicting changes to the same object. You’ll need to choose whether to keep the version that’s in your environment or bring the version from source control into your environment. You can also revert changes in the repository, then pull the prior version into your environment.

When the team is ready to deploy to test or production, you can use Pipelines in Power Platform for the release. Building and deploying using developer tools isn’t available yet for this new format.

We hope you enjoy the preview. There are many current limitations and you shouldn’t use this feature in environments or Git folders where you’re developing production solutions. Please leave your feedback below, in the community forums, on social media, or another outlet of choice. We look forward to hearing what you’d like to see prioritized next.

Learn more

Overview of Power Platform Git integration

Setup Git integration

The post Introducing Git Integration in Power Platform (preview) appeared first on Microsoft Power Platform Blog.