Skip to content
| Marketplace
Sign in
Azure DevOps>Azure Pipelines>Power Platform Release Extensions
Power Platform Release Extensions

Power Platform Release Extensions

Satya Kar

|
306 installs
| (0) | Free
Tasks for automating release into Dataverse/PowerApps
Get it free

PowerPlatform.Release.Extensions

Overview

The PowerPlatform.Release.Extensions provides tasks for use in Azure DevOps release pipelines. These tasks enable a Continuous Deployment pipeline to be created for Power Platform / Dataverse.

Tasks:

  • Update Service Endpoints

Usage

After installing, navigate to a new or existing Azure DevOps release pipeline, from there the following tasks should be available to be added and configured.

Update Service Endpoints

Update service endpoint connection details for the given serviceendpointids. The service endpoint connection string is either provided in the Config json array task property or retrieved from Power Platform enviornment variable referencing a secret stored in Azure Key Vault.

Option 1: Use of Azure KeyVault Secret is FALSE

  • Provide the serviceendpointid and connection string(inline value or ADO pipeline variable) in the Config json array task property.

Option 1

Name Description
Dataverse URL The URL for the target Dataverse environment.
Client Id The registered clientId for User from Azure AD.
Client Secret The generated secret for the clientId.
Use of Azure KeyVault Secret If false, provide the serviceendpointid and connection string in the Config json array property.
Config (A json array of serviceendpointid & service endpoint connectionstring(sb://)) [{"serviceEndpointid":"50154e6b-7cf3-47ae-be6f-d9eb650ffc63","configValue":"Endpoint=sb://xxx.servicebus.windows.net/;SharedAccessKeyName=keyname;SharedAccessKey=59Oc0=;EntityPath=demo"}]

Option 2: Use of Azure KeyVault Secret is TRUE (preview)

  • Create an Azure Key Vault and add the service endpoint connection string as secret. Create a new envionment variable to reference secret stored in Azure Key Vault. Currently this is in preview, for more details on how to setup please visit this link
  • After importing solution, update the target envionment variable for referencing the secret stored in new Azure Key Vault.

Option 2

Name Description
Dataverse URL The URL for the target Dataverse environment.
Client Id The registered clientId for User from Azure AD.
Client Secret The generated secret for the clientId.
Use of Azure KeyVault Secret If true, the task will get the service endpoint connection string from the Azure KeyVault Secret.
Config (A json array of serviceendpointid & environment variable name) [{"serviceEndpointid":"50154e6b-7cf3-47ae-be6f-d9eb650ffc63","configValue":"satkar_TestEnvironmentVaribale"}]
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft