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.

Overview

Power Platform Managed Identity utilizes workload identities based on Federated Identity Credentials (FIC). You have the option to provision either a User Assigned Managed Identity (UAMI) or an Application Registration and configure Federated Identity Credentials (FIC). Application Registration enables you to apply Azure policies to Power Platform resources, such as Dataverse plug-ins.

You have two options for provisioning of managed identities:

1. User Assigned Managed Identity (UAMI): You can provision a User Assigned Managed Identity (UAMI) in Azure. Dataverse plug-ins can use this identity to connect to Azure resources that support managed identity. In this case, you cannot enforce Azure policies.
2. Application Registration: By provisioning the application in Microsoft Entra ID, you establish an application context and Identity that can connect to Azure resources supporting managed identity.  This allows you to apply Azure policies to the application, ensuring that Power Platform resources, such as Dataverse plug-ins, adhere to these policies.

You need to configure Federated Identity Credentials (FIC) in both options to enable managed identity.

Supported scenario

Currently, Power Platform Managed Identity supports Dataverse plug-ins. This means that Dataverse plug-ins can connect to Azure resources that support managed identities without the need to manage credentials. By leveraging managed identities, the connection process becomes more secure and streamlined, as it eliminates the risks associated with credential management. This feature ensures that Dataverse plug-ins can access necessary Azure resources seamlessly and securely, enhancing overall efficiency and security.

Today we support Managed Identity for Independent Software Vendor (ISV) plug-ins within the context of their environment. For example, an ISV plug-in installed in the environment, will have access to the resources within the scope of the environment. However, it will not have to access resources within the ISV tenant.

Availability

Power Platform Managed Identity support for Dataverse plug-ins is available in public preview to all our customers in public cloud.

Call to action

• Start by following the step-by-step instructions – Set up Managed Identity support for Dataverse plug-ins
• Learn more about Power Platform Managed Identity
• Share your feedback

The post Announcing public preview of Power Platform Managed Identity support for Dataverse Plug-ins appeared first on Microsoft Power Platform Blog.

New!! Preview: Pac Connector command

Now introducing the new connector command in the Power Platform CLI. This Power Platform version works against Dataverse. You will now be able to create custom connectors as a code first component directly into Dataverse. If you have custom connectors already created and the pac connector list command does not show it in its output, it is because the custom connector is not in Dataverse. To put it Dataverse, you need just add the connector to a solution.

New!! Certificate AUTH support for Service Principal

From this release onwards you can use certificate-based authentication for Service Principal accounts. This was a widely asked feature from our DevOps users. This is now available.

New!! Assign-user operation can now assign an application ID

When we released the assign user capability last month, we got your feedback loud and clear. Some of you have scenarios where the environment is not owned by a user but by another service principal who is different from the service principal account that is running a pipeline. This kind of a situation occurs when the environment in production is not to be owned by a single user account but by a service principal. I am glad to report that from this release onwards, including in Azure DevOps and GitHub actions, the assign user can now accept an application user (service principal)

New!! Data import capability in Power Platform CLI

For a long time, our users have been asking to get the Data migration tool into the Power Platform CLI. Now you can use the data import capability instead of the data migration tool. Just as move solutions across environments, the corresponding data for such solutions that use their data from Dataverse, we can now move them too. We have introduced the option to export and import and the data can be in a zip file or in a directiory

Moving towards JUST –ENVIRONMENT no more URL or Envid, provide the one that suits with a single parameter

In most of the commands recently you would have noticed that we are removing references to –url or –environmentid to just –environment. So, whether you pass the url or the id, the command will resolve itself from the information provided on whether the parameter passed is a url or an id.

Keeping with that model, we have updated the pac application list and install commands with this capability now

And other commands like solution list and connector list and many more are following a similar path. Going forward all you need to do is provide the –env flag and pass either the url of the environment or the id of the environment and the system will figure out the right one for you.

Just added… the ability to provide runtime settings for packages

During package deployment, although the API allows you to submit runtime settings for the package, such which solution to run first etc. We had unfortunately not exposed that, now we can do that with this release, thereby making a lot of folks who deploy power platform packages happy.

And in addition, for plugin developers, you can now opt-in for strong name signing for your plugin library.

As you can see, we have introduced a number of new capabilities in this update. As always we are looking forward to your feedback on these new capabilities. The forums are the same for feedback, please reach out to us via the following forums ISVFeedback@Microsoft.com or The PowerUsers community. Raise the issue and bugs at the following location in GitHub https://aka.ms/powerplatform-vscode

The post Power Platform Developer Tools monthly release update (August Refresh) appeared first on Microsoft Power Platform Blog.

The post Improve monitoring of Dataverse plugins using Application insights appeared first on Microsoft Power Platform Blog.