Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Power Platform WorkbenchNew to Visual Studio Code? Get it now.
Power Platform Workbench

Power Platform Workbench

Caleb J. Rhodenbaugh

|
3 installs
| (0) | Free
Inspect metadata, prepare exact component packages, verify deployments, and manage developer change sets.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Power Platform Workbench

Review the changes before you deploy. Power Platform Workbench brings component diffing, deployment, data queries and diagnostics into VS Code. Compare local files with your selected environment, inspect each change and deploy the components that are ready.

Start with Explorer → right-click a file or package manifest → Power Platform Workbench: Diff. Diff Review is the place to review changes, retrieve Target files and manually deploy your checked selection.

Version: 0.62.1. Release notes · Workflow guide · Agent guide · Report an issue · Development board · Donate

Diff first, then deploy

  1. Choose the files. Save your changes, then right-click the exact files, a folder or a package manifest and choose Power Platform Workbench: Diff. A folder selects its files; a manifest makes a repeatable selection explicit.
  2. Review what changed. Diff Review lists changed files with change status and links to their diffs. Identical files are omitted. Check only the ready changes; your selection stays intact when you switch tabs.
  3. Verify the destination. Review the captured Target, account and solution or Azure resource. Power Apps components use the app solution configured in Accounts. Power Pages components use the separate Power Pages solution configured there for that Target.
  4. Deploy the reviewed selection. Click Deploy, review the final scope and confirm manually. Use Retrieve instead to replace the reviewed local files with their Target versions. Inspect the recorded outcome before retrying an incomplete or uncertain operation.

Package manifests contain one object with a paths list. For example, in a workspace-root manifest:

{
  "paths": [
    "solutions/Example/src/WebResources/sample_script.js",
    "solutions/Example/src/WebResources/sample_styles.css"
  ]
}

Existing solution-relative and website-relative change manifests are also supported. Required unchanged packaging companions come from Target. For supported new components, Diff can include the exact required paired descriptor and show it in the review; it does not silently select unrelated local dependencies.

Deployment coverage

Component family Review and deployment behavior
Dataverse solution files Supported native component mappings include web resources, flows/processes, forms, views, apps and schema components. Review exact file changes and the selected solution before import/publication.
Power Pages Compare website YAML and content files, deploy the checked changes and verify membership in the independently selected Power Pages solution.
PCF controls An authored PCF project represents a complete control. Unmanaged PCF deployment uses Publish All after import; confirmation discloses that this publishes all pending customizations in the environment.
Azure Function Apps Script apps support exact file selections. Compiled .NET apps deploy as a complete application; readable source diffs use an explicitly supplied original source folder. Azure DLLs do not supply the original C# source.
Standard Logic Apps Diff and deploy one workflow definition without selecting the app's other workflows.
Azure infrastructure and settings Review Bicep templates before Incremental deployment, or review app-setting keys before merging the checked settings into the current Target configuration.

Azure project Diff remembers the verified app and slot for each local Function project or Logic App workflow in its account and Target environment. On first use, choose from resources in the saved subscription/resource group. Later comparisons reuse that destination. Accounts lists saved destinations and lets you forget a mapping before choosing another; filenames alone never determine where deployment goes.

Coverage depends on the component and operation; a readable metadata row is not proof that it can be deployed or deleted independently. See the capability matrix. A successful upload alone does not prove activation, publication or solution membership; retained outcomes distinguish those stages.

If a Power Pages upload succeeds but solution membership fails, use Review Target Configuration → Review Solution Membership for the captured Power Pages solution. Review and add only the missing selected components; do not upload unchanged website content again solely to repair membership.

The same membership review offers Remove from solution for an unmanaged solution. Review the selected members before confirming. This removes only their membership in that solution; it does not delete the components from the environment.

Component Recycle Bin retains verified recovery packages for supported Workbench deletions, including captured writable data. Retention defaults to 30 days and is configurable in Settings. Restore is reviewed and manual; it cannot recreate immutable audit history or data that was not captured. Restore Deleted Records is a separate tool using Dataverse's native deleted-record support.

Start here

  1. Install Power Platform Workbench from publisher Caleb-J-Rhodenbaugh, or install a supplied release VSIX using Extensions → Install from VSIX. Run Developer: Reload Window after an update so commands and menus load. Open a trusted local workspace. Use Windows desktop VS Code. On first use of a tool that needs PowerShell, Workbench looks for PowerShell 7.5 or later. Choose Install PowerShell to install or upgrade it with WinGet, or Installation instructions to use Microsoft's installer. Install PAC for Power Platform tasks and Azure CLI for Azure tasks. Builds require the selected project's SDKs. See the supported host matrix.
  2. Open the Power Platform Workbench pane and click its Accounts icon. Sign in separately to Dataverse and Azure. The page groups each account, its sign-in status and its configuration together. A saved connection is not necessarily an active session. After successful sign-in, Workbench walks through missing provider selections and reuses saved choices. Canceling a selector keeps the account signed in and retains choices already confirmed; finish the remaining selections on Accounts when ready.
  3. In Accounts, select Source, Target, the Power Apps Solution and the separate Power Pages solution. Environment profiles remember local connection and resource selections for each Target; selecting another profile restores its saved defaults. Changing an Azure subscription guides you through its dependent resources in the same flow. The solution picker includes managed and unmanaged solutions; managed solutions support read-only membership review, while direct website deployment and membership changes require an unmanaged solution. Retained reviews keep their captured identity; changing defaults cannot redirect an old review.
  4. Open a tool in Data, Develop, Test or Deploy. Quick actions start empty; pin the tools you use. The command inventory explains where every command lives, including contextual actions and Component Recycle Bin.

Query and work with records

Open Data → Query Data, select one base table, choose columns and filters, then Run query. Related tables, joins, summaries and advanced filters stay in that same workspace. The URL, JSON and XML editors represent that definition; XML is native FetchXML. When a definition requires coordinated native requests or Workbench calculations, the selected URL/XML document is only one piece; JSON and Save Query preserve the complete execution plan.

Results support selected-record edits, reviewed updates/deletes and CSV/JSON/Excel export. Export includes current grid edits without saving them to Dataverse. Profile, audit, relationship and file/image actions use the selected table or record. Their direct tools retain independent tasks, such as opening a known record GUID that is not in a result set. Diagnostic metadata stays read-only.

For data files, use Import Data or right-click Import/Diff. Both use mapping and a changed-record review. Choose the exact records to import; incomplete or uncertain writes retain their outcomes and are not retried automatically. Reconciliation reads current Target state and does not replay writes.

Inspect, develop and verify

Tool What it helps you do
Inspect Metadata Browse components, columns, keys, relationships, dependencies and solution layers. Filter by latest modifier/date and use the established component review actions.
Flow Explorer Inspect Power Automate flows and Standard/Consumption Logic App workflows, including retained runs and action evidence.
Azure Diagnostics Query Application Insights and Log Analytics, inspect Azure activity and follow available correlation evidence from a workflow run.
Review Target Configuration Inspect environment variables and connection references; review Current Value and app/Power Pages solution membership changes.
Power Pages Diagnostics Inspect website diagnostics and perform a reviewed restart when configuration needs a cache refresh.
Diff Content Compare pasted text or local content side by side, merge changes and save the right-side output.
Retrieve Solution / Create Component Retrieve selected solution or website source into a new folder, or scaffold components using the selected solution's publisher prefix.
Local UI Preview Preview isolated HTML/CSS/JavaScript before deploying. Server Liquid, authentication and remote APIs are not emulated.

Inspect Metadata's default latest-modifier and two-week date filters describe the latest change, not every developer who changed a component. Schema attribution can be unavailable; the schema toggle retains the date bounds. Diagnostics can read only the logs that the selected service collected and still retains.

Search tools in the pane and pin the ones you use. Shared forms, progress indicators and result controls keep each workflow familiar. Accounts owns the selectors and saved defaults; tool pages have no navigation header or completed-status banner. A command blocked by another running operation reports an informational cancellation. Local tools open without contacting an environment, and tools that need a connection request sign-in before starting when required.

History in supported tools restores locally captured results across VS Code restarts. Save selections and Saved selections restore form choices without running the tool. Query Data retains Save Query, Saved Queries and recent query history. Deployment History and Saved Work retain their domain-specific evidence and presets; Diff Content intentionally has no history. See evidence and retention for what is stored locally.

Use the capability matrix for operation coverage and the workflow reference for specialist tasks. Retained reports/snapshots describe captured evidence, not current live state. The release and manual verification matrix distinguishes mocked local tests from tenant validation.

Connect an AI agent

In trusted local workspaces, Workbench registers MCP with supported VS Code hosts and maintains only its owned project entries in .codex/config.toml and .cursor/mcp.json. Other clients can use Settings → Agent Access → Configure Agent Access to obtain transport configuration. The Workbench host must remain open; client trust/approval policies still apply. Stop Agent Access disables the bridge without rewriting client policies.

Agents discover the tool catalog, request schemas, submit structured inputs to background sessions and page through retained results. They can reveal the same session in the user interface at any point with workbench_session and action: "show", without rerunning it. A visible session can be released for the user to continue; Query Data results remain editable after handoff. Accounts, secrets, sign-in and remote writes require the human.

See the agent guide for discovery, session continuation, complete result reading and user handoff, and the privacy disclosure before connecting clients to business data.

Support development

Use the heart Donate button in the pane header, immediately to the left of Settings and Accounts, or donate here.

Help and feedback

Report a bug or request a feature or follow its progress on the development board. Before sharing screenshots or logs, remove credentials, signed URLs and business records.

Release notes · Privacy · Security · MIT license

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft