Power Automate Versioning and Source Control - Export Tag Track

Описание и применение

В Power Automate отсутствует встроенная версияция отдельных потоков. Экспортируйте определения потоков в Git через интеграцию Dataverse Git или pac CLI, чтобы получить полноценный контроль версий, сравнение, тегирование и PR‑обзор.

Задача

Power Automate lacks built‑in version control for individual flows, making it hard to track changes, compare versions, and govern at scale.

Результат

Flows become first‑class code artifacts in git, enabling granular versioning, diffing, tagging, and PR reviews, which improves governance and reduces production breakage.

Рабочий процесс

• Export solution as ZIP via pac CLI or Dataverse Git integration
• Unpack ZIP to individual component files (flows become JSON files in Workflows/ folder)
• Commit changes to git with meaningful messages
• Tag releases to match solution version
• Create pull requests for flow changes
• Merge PRs and deploy from git to test/production via pipelines

Доказательства

Power Automate has no built‑in version control for individual flows. Export flow definitions to git using Dataverse Git integration (Azure DevOps) or pac CLI (any git host).

Источник

From the maker portal (or via API), commit changes to the connected git repo. Each component gets its own file. Flows land as individual JSON definitions.

Источник

The key commands: pac solution export, pac solution unpack, pac solution pack, pac solution create-settings.

Источник