How to publish Synapse workspace with Pull Request generated

Christine Han 40 Reputation points Microsoft Employee
2026-01-30T00:36:49.34+00:00

We are using Git integration to publish workspaces templates to workspace_publish branch. We recently received S360 item regarding the commitWithoutPullRequest voliation from AzDO Production Readiness Check. Please suggest how to generate PR for the git push for template changes ? Thanks!

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
{count} votes

Answer accepted by question author
  1. Pilladi Padma Sai Manisha 3,470 Reputation points Microsoft External Staff Moderator
    2026-01-30T01:44:09.23+00:00

    Hi Christine Han
    This behavior is by design in Azure Synapse Analytics.

    When you use Synapse Studio > Publish, the service automatically generates ARM templates and directly commits them to the configured publish branch (for example, workspace_publish). These commits are system-generated by the Synapse service and do not support Pull Request creation.

    Currently, there is no supported way to generate a PR for publish-time template changes. The publish branch is intended to store deployment artifacts only and is not a collaboration or review branch. As a result, PR enforcement is not applicable to this branch.

    For compliance tools such as AzDO Production Readiness Check / S360 that flag commitWithoutPullRequest, the recommended and supported approach is to:

    Exclude the publish branch from PR enforcement policies

    Enforce PRs only on collaboration branches (for example, main, develop, or the Synapse collaboration branch)

    All user-authored changes should flow through PRs before publishing. The publish commit itself represents generated output, not a source change.

    This model aligns with Microsoft’s documented Synapse CI/CD guidance and is the expected operational pattern.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Christine Han 40 Reputation points Microsoft Employee
    2026-02-04T05:27:33.84+00:00

    Thaks Pilladi. We have found a solution by using two separate branches, one for publishing and one for the ADO build. So, we can apply the branch policies on the branch for ADO build. The issue is now resolved.

    We’d also suggest that the Synapse Portal support generating pull requests during the publishing.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.