CI CD in Azure Synapse Analytics Part 3

Published Dec 18 2020 04:45 AM 6,355 Views

Here's a quick review of the road so far:

 

CI CD in Azure Synapse Analytics Part 1

  • Creating an Azure DevOps project
  • Linking our Azure Synapse Analytics environment to that Project via Git
  • Validating that our Azure DevOps Repo was populated with our Azure Synapse Analytics environment

CI CD in Azure Synapse Analytics Part 2:

  • Create a new branch on our Repo
  • Edit our Azure Synapse Analytics environment
    • Specifically my SQL scripts have demos all over the place and Buck Woody said I have to clean up my very messy room .... Azure Synapse Analytics environment
  • Create a Pull Request in Azure Synapse Analytics to merge our new branch with the main
  • Approve the Pull Request in Azure DevOps
  • Validate our main branch is updated in our Azure Synapse Analytics Environment

This time we will:

  • Create an Artifact pipeline
    • This is to create an Artifact we can use to deploy to another environment

 

First we are going to examine a very important part of our Azure Synapse Analytics environment.  The Publish button.

 

01 CI CD part 3.png

 

Why all the arrows and boxes?  Because this is important.  This publish button saves the templates that we will use to deploy our environment to another Azure Synapse Analytics workspace.  When you click publish a few messages should appear.  Publishing In progress, Publishing completed, Generating templates, and Generating templates completed.  

 

If you get an error do not fear, validation will occur and show you where the error is in your workspace.  I've encountered this a time or two.  Eventually I will intentionally write a blog in this series where we break things just to fixt them.  For now, let us presume that everything went just fine.

 

01 CI CD part 3 image 2.png

Next we will move over to our Azure DevOps Repo.  Find the folder that is the same name as your Azure Synapse Analytics workspace.  In this picture mine is bballasw.  Under that folder you will find two files, TemplateForWorkspace.json & TemplateParametersForWorkspace.json.

 

*NOTE - these templates are not the same templates you would use to deploy a new environment.  These are only for deploying the artifacts from one environment to another.  In part 5 we will look at generating the ARM templates needed for deploying a new environment from Azure DevOps.

 

01 CI CD part 3 image 3.png

 

We will be using these files to create our artifact build pipeline.  Also highlighted is the WorkspaceDefaultSqlServer_connectionString, this string is of the type secureString.  This is important when we reach our release pipeline in Part 4, if we do not handle this string properly the release will fail.

 

For this exercise I've created another Azure Synapse Analytics Environment for us to deploy to named bballaswqa in a separate resource group from bballasw.  

 

01 CI CD part 3 image 4.png

Right now there is nothing in bballaswqa.

 

01 CI CD part 3 image 5.png

Especially compared to bballasw.

 

01 CI CD part 3 image 6.png

 

With our destination of bballaswqa in mind, we begin with our build pipeline.  Moving over to Azure DevOps we want to move to Pipelines.

 

01 CI CD part 3 image 7.png

Click New pipeline.

 

01 CI CD part 3 image 8.png

 

At the very bottom of the page, in super tiny font you will find Use the classic editor.  Make sure to click on that lin.

 

01 CI CD part 3 image 9.png

 

This is where we configure the project, repository, and the default branch for our builds.  All of this information is correct.  We are using Azure Repos Git, we will click the Continue button.

 

01 CI CD part 3 image 10.png

At the very top of our next page we have different options for our pipeline template.  We will click on the Empty job link.

 

01 CI CD part 3 image 11.png

 

Now we are finally to the pipeline.  First we will rename the default name.  I use ASW in my naming convention as it stands for Azure Synapse Workspace.  We rename the pipeline to ASW Build Pipeline.  Then we click on the Triggers section.  The Triggers section is where we will configure our CI portion of our build. 

 

01 CI CD part 3 image 12.png

 

Check the Enable continuous integration check box.  Under branch filters we want main, as that is the branch we are publishing to for all of our builds.  But we need to add a Path filter.  Ever time we merge a branch to main it would cause the build pipeline to run.  I only want the pipeline to run when we publish from our Azure Synapse Analytics environment.

 

After this return to the tasks window.

 

01 CI CD part 3 image 13.png

 

On the Agent job 1 click the + button. We need the Copy files task.  Add that to our pipeline.

 

01 CI CD part 3 image 14.png

 

In Azure DevOps there are some reserved variables.  One of the Build variables is Build.ArtifactStagingDirectory, for a full list see this Docs article Predefined variables - Azure Pipelines | Microsoft Docs. This defines a local path on a build agent and this is where we want our build files deployed to.  In part 4 we will build a Release Pipeline and that Release will be linked to the artifacts we produce.  

 

We will change our Display name to Copy ARM Template Files to: $(Build.ArtifactStagingDirectory).  When you use a variable in Azure DevOps you invoke it with $(variableName).  Now click on the three ellipsis next to the Source Folder text box.

 

01 CI CD part 3 image 15.png

 

We will select the folder that has the same name as our Azure Synapse Analytics workspace that has our Template JSON files.

 

01 CI CD part 3 image 16.png

We finish configuring this task by setting our contents to *.json.  This will pull in only the JSON files under our folder.  We set the Target Folder to $(Build.ArtifactsStagingDirectory)/ARM.

 

We don't need the folder path.  At this time there are no other object in my build pipeline.  If we ever want to add them we can have additional subfolders, but for now my OCD won and I created a folder.

 

01 CI CD part 3 image 17.png

 

Now click on the + sign on Agent Job 1.  We need to add the Publish Pipeline Artifacts task.  

 

01 CI CD part 3 image 18.png

 

Our File or Directory path will be $(Build.ArtifactsStagingDirectory).  Our Artifact name will be ASW_Drop. 

 

Hit Save & queue.

 

01 CI CD part 3 image 19.png

 

Enter a save comment, click Save and run. 

 

01 CI CD part 3 image 20.png

 

Click on the Agent job 1 section of the page and open the build agent window.

 

 

01 CI CD part 3 image 21.png

OH WOW!  IT ALL TURNED GREEN AND WORKED!!! .....it's not like I did this a few 100 times failing miserably until I figured it out......  Now click on the small arrow next to the Jobs run to return to the pipeline.

 

01 CI CD part 3 image 22.png

 

Under the header Related 0 work items click on 1 published; 1 consumed. 

 

01 CI CD part 3 image 23.png

 

Expand the arrow next to ASW_Drop, ARM, and we can see our Template files.  Success we have a build artifact that we can now call in a Release pipeline.

 

Ok Dear Reader, it's late and we are done for today.  In our next blog we will cover the release pipeline and look at what was deployed to our QA environment!

 

As always, thank you for stopping by.

 

 

11 Comments
Established Member

Hello,

This has been really helpful! Thanks a mill.

I was wondering when parts 4 and 5 would be coming out ;) ?

Thanks.

Senior Member

Hi Bradley I'm waiting your next post about deployment task.

I'm trying to deploy Azure Synapse Analytics in a different resource group and I couldn't. 

 

Hi KeyBee & Sidney, sorry for the delay.  I'll be writing these up this weekend and posting them next week. 

Established Member

Hi Bradley,

That would be Epic! I just can't get this right, even my contact at MSFT is struggling with it! 

Thanks a mill.

 

Senior Member

Hey Brad!

 

Great series.

 

I noticed that your ARM template directory (bballasw) is in the root of the main branch, which is also used as your collaboration branch. In Part 1 of this series, you used the default workspace_publish as your publish branch.

 

I may have missed something but can you please clarify if you changed your publish branch between parts 1 and 3, or if you completed a PR to merge workspace_publish into main?

 

Cheers

Senior Member

Hello Bradley,

 

It's a very interesting series of articles. I have some questions about the CI/CD process. 

Is there a way to include the SQL pool data model in the flow, like using dacpac?

Also is anyway to protect your Github publish branch with approvals or something similar? 

Having in consideration that publish branch is the one used to promote your changes to upper environments, this seems critical in term of security

 

Cheers

@chrisdaws Hi Chris, You are spot on.  I meant to change workspace_publish to main and should have done so on the blog.  I need to check with Buck, I do not have the ability to edit the post.  My preference is for the JSON generated with the workspace to go straight to main.  This can trigger a new build process in a more automated fashion consistent with CICD principals. 

You can change this by going into the Manage option, selecting git configuration, then clicking on the gear box for Settings.  The only option you CAN change in Settings is the Publish Branch.  If that is not main, please set it to main.   

I will follow up with another post on this!

Hi @qzhou you've got some good questions, let me take then one at a time.

It's a very interesting series of articles. I have some questions about the CI/CD process. 

Is there a way to include the SQL pool data model in the flow, like using dacpac?

 

Yes this can absolutely be done.  I plan to blog on this, but the short answer is you would create a folder for the database project, sync your project to that repo folder, and then have a build pipeline that will create a dacpac for deployment similar to other database projects.

 

Also is anyway to protect your Github publish branch with approvals or something similar? 

In Azure DevOps you can absolutely have requirements for approval gates. There is a lot you can do with Azure DevOps, this is a good link to get started with: Understand approvals, gates, and checks - Azure Pipelines | Microsoft Docs




Regular Visitor

Hi Brad, great series of articles. This is the most comprehensive tutorial that anyone can follow and works like charm.    Now the part that I am struggling with the most which i didn't anticipate it was going to be was creating a synapse workspace with just built-in serverless pool using ARM template.   I used the portal to generate the template and downloaded it and setup a Arm template deployment task in release pipeline in devop.   It's creating the synapse space and storage and all, but i am getting an error.

 

 'Authorization failed for template resource 'datalakegen2synapseacct/Microsoft.Authorization/5dc0d056-0e65-53d3-89fc-6e17ac29d7e7' of type 'Microsoft.Storage/storageAccounts/providers/roleAssignments'. The client '4656517f-f949-417d-a1f8-3271ccbcc404' with object id '4656517f-f949-417d-a1f8-3271ccbcc404' does not have permission to perform action '...   
 
I would think this has something to do with the Service principal not having sufficient privilege or something.. but I can not resolve it.   I would think this should just work with out of box with imported templates.
Visitor

" folder that is the same name as your Azure Synapse Analytics workspace." we will see the folder only when we create the pull request and commit the changes post publish. otherwise will not able to see the folder workspace in repo.

Senior Member

In part 5 we will look at generating the ARM templates needed for deploying a new environment from Azure DevOps.

Is still there a part 5?

%3CLINGO-SUB%20id%3D%22lingo-sub-1993201%22%20slang%3D%22en-US%22%3ECI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1993201%22%20slang%3D%22en-US%22%3E%3CP%3EHere's%20a%20quick%20review%20of%20the%20road%20so%20far%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdata-architecture-blog%2Fci-cd-in-azure-synapse-analytics-part-1%2Fba-p%2F1964172%22%20target%3D%22_self%22%3ECI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%201%3C%2FA%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3ECreating%20an%20Azure%20DevOps%20project%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3ELinking%20our%20Azure%20Synapse%20Analytics%20environment%20to%20that%20Project%20via%20Git%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3EValidating%20that%20our%20Azure%20DevOps%20Repo%20was%20populated%20with%20our%20Azure%20Synapse%20Analytics%20environment%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-message-read%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdata-architecture-blog%2Fci-cd-in-azure-synapse-analytics-part-2%2Fba-p%2F1991060%22%20target%3D%22_self%22%3ECI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%202%3C%2FA%3E%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3ECreate%20a%20new%20branch%20on%20our%20Repo%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3EEdit%20our%20Azure%20Synapse%20Analytics%20environment%3C%2FSPAN%3E%3CUL%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3ESpecifically%20my%20SQL%20scripts%20have%20demos%20all%20over%20the%20place%20and%20Buck%20Woody%20said%20I%20have%20to%20clean%20up%20my%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20style%3D%22text-decoration%3A%20line-through%3B%22%3Every%20messy%26nbsp%3Broom%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E....%20Azure%20Synapse%20Analytics%20environment%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3ECreate%20a%20Pull%20Request%20in%20Azure%20Synapse%20Analytics%20to%20merge%20our%20new%20branch%20with%20the%20main%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3EApprove%20the%20Pull%20Request%20in%20Azure%20DevOps%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3EValidate%20our%20main%20branch%20is%20updated%20in%20our%20Azure%20Synapse%20Analytics%20Environment%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-message-read%22%3EThis%20time%20we%20will%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3ECreate%20an%20Artifact%20pipeline%3C%2FSPAN%3E%3CUL%3E%0A%3CLI%3E%3CSPAN%20class%3D%22lia-message-read%22%3EThis%20is%20to%20create%20an%20Artifact%20we%20can%20use%20to%20deploy%20to%20another%20environment%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFirst%20we%20are%20going%20to%20examine%20a%20very%20important%20part%20of%20our%20Azure%20Synapse%20Analytics%20environment.%26nbsp%3B%20The%20Publish%20button.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203.png%22%20style%3D%22width%3A%20628px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241481iC325A4F7B1510C8E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203.png%22%20alt%3D%2201%20CI%20CD%20part%203.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhy%20all%20the%20arrows%20and%20boxes%3F%26nbsp%3B%20Because%20this%20is%20important.%26nbsp%3B%20This%20publish%20button%20saves%20the%20templates%20that%20we%20will%20use%20to%20deploy%20our%20environment%20to%20another%20Azure%20Synapse%20Analytics%20workspace.%26nbsp%3B%20When%20you%20click%20publish%20a%20few%20messages%20should%20appear.%26nbsp%3B%20Publishing%20In%20progress%2C%20Publishing%20completed%2C%20Generating%20templates%2C%20and%20Generating%20templates%20completed.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20get%20an%20error%20do%20not%20fear%2C%20validation%20will%20occur%20and%20show%20you%20where%20the%20error%20is%20in%20your%20workspace.%26nbsp%3B%20I've%20encountered%20this%20a%20time%20or%20two.%26nbsp%3B%20Eventually%20I%20will%20intentionally%20write%20a%20blog%20in%20this%20series%20where%20we%20break%20things%20just%20to%20fixt%20them.%26nbsp%3B%20For%20now%2C%20let%20us%20presume%20that%20everything%20went%20just%20fine.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%202.png%22%20style%3D%22width%3A%20578px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241482i4CC13D5831B163BB%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%202.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%202.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3ENext%20we%20will%20move%20over%20to%20our%20Azure%20DevOps%20Repo.%26nbsp%3B%20Find%20the%20folder%20that%20is%20the%20same%20name%20as%20your%20Azure%20Synapse%20Analytics%20workspace.%26nbsp%3B%20In%20this%20picture%20mine%20is%20bballasw.%26nbsp%3B%20Under%20that%20folder%20you%20will%20find%20two%20files%2C%20TemplateForWorkspace.json%20%26amp%3B%20TemplateParametersForWorkspace.json.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E*NOTE%20-%20these%20templates%20are%20not%20the%20same%20templates%20you%20would%20use%20to%20deploy%20a%20new%20environment.%26nbsp%3B%20These%20are%20only%20for%20deploying%20the%20artifacts%20from%20one%20environment%20to%20another.%26nbsp%3B%20In%20part%205%20we%20will%20look%20at%20generating%20the%20ARM%20templates%20needed%20for%20deploying%20a%20new%20environment%20from%20Azure%20DevOps.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%203.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241483i3EA93432DD9A531F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%203.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%203.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20will%20be%20using%20these%20files%20to%20create%20our%20artifact%20build%20pipeline.%26nbsp%3B%20Also%20highlighted%20is%20the%20WorkspaceDefaultSqlServer_connectionString%2C%20this%20string%20is%20of%20the%20type%20secureString.%26nbsp%3B%20This%20is%20important%20when%20we%20reach%20our%20release%20pipeline%20in%20Part%204%2C%20if%20we%20do%20not%20handle%20this%20string%20properly%20the%20release%20will%20fail.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20this%20exercise%20I've%20created%20another%20Azure%20Synapse%20Analytics%20Environment%20for%20us%20to%20deploy%20to%20named%20bballaswqa%20in%20a%20separate%20resource%20group%20from%20bballasw.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%204.png%22%20style%3D%22width%3A%20844px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241484i0B2712DC27C77F5F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%204.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%204.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3ERight%20now%20there%20is%20nothing%20in%20bballaswqa.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%205.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241485iF3A38B67FB2A0B8D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%205.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%205.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EEspecially%20compared%20to%20bballasw.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%206.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241486i063107BFB0C1BD71%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%206.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%206.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20our%20destination%20of%20bballaswqa%20in%20mind%2C%20we%20begin%20with%20our%20build%20pipeline.%26nbsp%3B%20Moving%20over%20to%20Azure%20DevOps%20we%20want%20to%20move%20to%20Pipelines.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%207.png%22%20style%3D%22width%3A%20562px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241493i6C709B615555D285%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%207.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%207.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EClick%20New%20pipeline.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%208.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241494i488B789F7B075548%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%208.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%208.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAt%20the%20very%20bottom%20of%20the%20page%2C%20in%20super%20tiny%20font%20you%20will%20find%20Use%20the%20classic%20editor.%26nbsp%3B%20Make%20sure%20to%20click%20on%20that%20lin.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%209.png%22%20style%3D%22width%3A%20945px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241495i502B99FFD9B58B33%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%209.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%209.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20where%20we%20configure%20the%20project%2C%20repository%2C%20and%20the%20default%20branch%20for%20our%20builds.%26nbsp%3B%20All%20of%20this%20information%20is%20correct.%26nbsp%3B%20We%20are%20using%20Azure%20Repos%20Git%2C%20we%20will%20click%20the%20Continue%20button.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2010.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241497i774E5477579206CB%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2010.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2010.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EAt%20the%20very%20top%20of%20our%20next%20page%20we%20have%20different%20options%20for%20our%20pipeline%20template.%26nbsp%3B%20We%20will%20click%20on%20the%20Empty%20job%20link.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2011.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241498i3F9367BDA8F99E32%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2011.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2011.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%20we%20are%20finally%20to%20the%20pipeline.%26nbsp%3B%20First%20we%20will%20rename%20the%20default%20name.%26nbsp%3B%20I%20use%20ASW%20in%20my%20naming%20convention%20as%20it%20stands%20for%20Azure%20Synapse%20Workspace.%26nbsp%3B%20We%20rename%20the%20pipeline%20to%20ASW%20Build%20Pipeline.%26nbsp%3B%20Then%20we%20click%20on%20the%20Triggers%20section.%26nbsp%3B%20The%20Triggers%20section%20is%20where%20we%20will%20configure%20our%20CI%20portion%20of%20our%20build.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2012.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241500iFD23585725F65E35%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2012.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2012.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheck%20the%20Enable%20continuous%20integration%20check%20box.%26nbsp%3B%20Under%20branch%20filters%20we%20want%20main%2C%20as%20that%20is%20the%20branch%20we%20are%20publishing%20to%20for%20all%20of%20our%20builds.%26nbsp%3B%20But%20we%20need%20to%20add%20a%20Path%20filter.%26nbsp%3B%20Ever%20time%20we%20merge%20a%20branch%20to%20main%20it%20would%20cause%20the%20build%20pipeline%20to%20run.%26nbsp%3B%20I%20only%20want%20the%20pipeline%20to%20run%20when%20we%20publish%20from%20our%20Azure%20Synapse%20Analytics%20environment.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20this%20return%20to%20the%20tasks%20window.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2013.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241502i4D91E450614FB569%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2013.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2013.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOn%20the%20Agent%20job%201%20click%20the%20%2B%20button.%20We%20need%20the%20Copy%20files%20task.%26nbsp%3B%20Add%20that%20to%20our%20pipeline.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2014.png%22%20style%3D%22width%3A%20900px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241510i11EEF990D9076F0A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2014.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2014.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20Azure%20DevOps%20there%20are%20some%20reserved%20variables.%26nbsp%3B%20One%20of%20the%20Build%20variables%20is%20Build.ArtifactStagingDirectory%2C%20for%20a%20full%20list%20see%20this%20Docs%20article%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Fpipelines%2Fbuild%2Fvariables%3Fview%3Dazure-devops%26amp%3Btabs%3Dyaml%23build-variables-devops-services%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPredefined%20variables%20-%20Azure%20Pipelines%20%7C%20Microsoft%20Docs%3C%2FA%3E.%20This%20defines%20a%20local%20path%20on%20a%20build%20agent%20and%20this%20is%20where%20we%20want%20our%20build%20files%20deployed%20to.%26nbsp%3B%20In%20part%204%20we%20will%20build%20a%20Release%20Pipeline%20and%20that%20Release%20will%20be%20linked%20to%20the%20artifacts%20we%20produce.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20will%20change%20our%20Display%20name%20to%20Copy%20ARM%20Template%20Files%20to%3A%20%24(Build.ArtifactStagingDirectory).%26nbsp%3B%20When%20you%20use%20a%20variable%20in%20Azure%20DevOps%20you%20invoke%20it%20with%20%24(variableName).%26nbsp%3B%20Now%20click%20on%20the%20three%20ellipsis%20next%20to%20the%20Source%20Folder%20text%20box.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2015.png%22%20style%3D%22width%3A%20965px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241512i82921773B3220AF9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2015.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2015.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20will%20select%20the%20folder%20that%20has%20the%20same%20name%20as%20our%20Azure%20Synapse%20Analytics%20workspace%20that%20has%20our%20Template%20JSON%20files.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2016.png%22%20style%3D%22width%3A%20500px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241513iB88190BA7A3C16F1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2016.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2016.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EWe%20finish%20configuring%20this%20task%20by%20setting%20our%20contents%20to%20*.json.%26nbsp%3B%20This%20will%20pull%20in%20only%20the%20JSON%20files%20under%20our%20folder.%26nbsp%3B%20We%20set%20the%20Target%20Folder%20to%20%24(Build.ArtifactsStagingDirectory)%2FARM.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20don't%20need%20the%20folder%20path.%26nbsp%3B%20At%20this%20time%20there%20are%20no%20other%20object%20in%20my%20build%20pipeline.%26nbsp%3B%20If%20we%20ever%20want%20to%20add%20them%20we%20can%20have%20additional%20subfolders%2C%20but%20for%20now%20my%20OCD%20won%20and%20I%20created%20a%20folder.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2017.png%22%20style%3D%22width%3A%20971px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241514i392FA91D90FBF91E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2017.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2017.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%20click%20on%20the%20%2B%20sign%20on%20Agent%20Job%201.%26nbsp%3B%20We%20need%20to%20add%20the%20Publish%20Pipeline%20Artifacts%20task.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2018.png%22%20style%3D%22width%3A%20981px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241515iD2F675AB19057CDA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2018.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2018.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOur%20File%20or%20Directory%20path%20will%20be%20%24(Build.ArtifactsStagingDirectory).%26nbsp%3B%20Our%20Artifact%20name%20will%20be%20ASW_Drop.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHit%20Save%20%26amp%3B%20queue.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2019.png%22%20style%3D%22width%3A%20985px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241516iB47F9ECE182DA366%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2019.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2019.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEnter%20a%20save%20comment%2C%20click%20Save%20and%20run.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2020.png%22%20style%3D%22width%3A%20480px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241517i84283C2D89562AFA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2020.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2020.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EClick%20on%20the%20Agent%20job%201%20section%20of%20the%20page%20and%20open%20the%20build%20agent%20window.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2021.png%22%20style%3D%22width%3A%20970px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241520i87704DF45B043574%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2021.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2021.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EOH%20WOW!%26nbsp%3B%20IT%20ALL%20TURNED%20GREEN%20AND%20WORKED!!!%20....%3CSTRIKE%3E.it's%20not%20like%20I%20did%20this%20a%20few%20100%20times%20failing%20miserably%20until%20I%20figured%20it%20out%3C%2FSTRIKE%3E......%26nbsp%3B%20Now%20click%20on%20the%20small%20arrow%20next%20to%20the%20Jobs%20run%20to%20return%20to%20the%20pipeline.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2022.png%22%20style%3D%22width%3A%20981px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241519iEB7C00594879B6E6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2022.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2022.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUnder%20the%20header%20Related%200%20work%20items%20click%20on%201%20published%3B%201%20consumed.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%2201%20CI%20CD%20part%203%20image%2023.png%22%20style%3D%22width%3A%20965px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241521i275F340A6B194282%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%2201%20CI%20CD%20part%203%20image%2023.png%22%20alt%3D%2201%20CI%20CD%20part%203%20image%2023.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EExpand%20the%20arrow%20next%20to%20ASW_Drop%2C%20ARM%2C%20and%20we%20can%20see%20our%20Template%20files.%26nbsp%3B%20Success%20we%20have%20a%20build%20artifact%20that%20we%20can%20now%20call%20in%20a%20Release%20pipeline.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOk%20Dear%20Reader%2C%20it's%20late%20and%20we%20are%20done%20for%20today.%26nbsp%3B%20In%20our%20next%20blog%20we%20will%20cover%20the%20release%20pipeline%20and%20look%20at%20what%20was%20deployed%20to%20our%20QA%20environment!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20always%2C%20thank%20you%20for%20stopping%20by.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1993201%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20this%20edition%20of%20our%20series%20we%20will%20create%20an%20Artifact%20%2F%20Build%20pipeline%2C%20create%20a%20Release%20pipeline%2C%20deploy%20our%20Azure%20Synapse%20Analytics%20environment%20from%20Dev%20to%20QA.%26nbsp%3B%20Review%20what%20was%20created%20and%20what%20was%20NOT%20created.%26nbsp%3B%20Also%20pause%20your%20SQL%20Pools%20if%20you%20are%20not%20using%20them.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1993201%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EData%20Architecture%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EData%20Pipelines%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2036584%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2036584%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EThis%20has%20been%20really%20helpful!%20Thanks%20a%20mill.%3C%2FP%3E%3CP%3EI%20was%20wondering%20when%20parts%204%20and%205%20would%20be%20coming%20out%20%3B)%3C%2Fimg%3E%26nbsp%3B%3F%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2095970%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2095970%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Bradley%20I'm%20waiting%20your%20next%20post%20about%20deployment%20task.%3C%2FP%3E%3CP%3EI'm%20trying%20to%20deploy%20Azure%20Synapse%20Analytics%20in%20a%20different%20resource%20group%20and%20I%20couldn't.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2102437%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2102437%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20KeyBee%20%26amp%3B%20Sidney%2C%20sorry%20for%20the%20delay.%26nbsp%3B%20I'll%20be%20writing%20these%20up%20this%20weekend%20and%20posting%20them%20next%20week.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2102465%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2102465%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Bradley%2C%3C%2FP%3E%3CP%3EThat%20would%20be%20Epic!%20I%20just%20can't%20get%20this%20right%2C%20even%20my%20contact%20at%20MSFT%20is%20struggling%20with%20it!%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20a%20mill.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115415%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115415%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Brad!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreat%20series.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20noticed%20that%20your%20ARM%20template%20directory%20(bballasw)%20is%20in%20the%20root%20of%20the%20main%20branch%2C%20which%20is%20also%20used%20as%20your%20collaboration%20branch.%26nbsp%3BIn%20Part%201%20of%20this%20series%2C%20you%20used%20the%20default%20workspace_publish%20as%20your%20publish%20branch.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20may%20have%20missed%20something%20but%20c%3CSPAN%3Ean%20you%20please%20clarify%20if%20you%20changed%20your%20publish%20branch%20between%20parts%201%20and%203%2C%20or%20if%20you%20completed%20a%20PR%20to%20merge%20workspace_publish%20into%20main%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2123619%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2123619%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Bradley%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20a%20very%20interesting%20series%20of%20articles.%20I%20have%20some%20questions%20about%20the%20CI%2FCD%20process.%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20include%20the%20SQL%20pool%20data%20model%20in%20the%20flow%2C%20like%20using%20dacpac%3F%3C%2FP%3E%3CP%3EAlso%20is%20anyway%20to%20protect%20your%20Github%20publish%20branch%20with%20approvals%20or%20something%20similar%3F%26nbsp%3B%3C%2FP%3E%3CP%3EHaving%20in%20consideration%20that%20publish%20branch%20is%20the%20one%20used%20to%20promote%20your%20changes%20to%20upper%20environments%2C%20this%20seems%20critical%20in%20term%20of%20security%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2159997%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2159997%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F918568%22%20target%3D%22_blank%22%3E%40chrisdaws%3C%2FA%3E%26nbsp%3BHi%20Chris%2C%20You%20are%20spot%20on.%26nbsp%3B%20I%20meant%20to%20change%20workspace_publish%20to%20main%20and%20should%20have%20done%20so%20on%20the%20blog.%26nbsp%3B%20I%20need%20to%20check%20with%20Buck%2C%20I%20do%20not%20have%20the%20ability%20to%20edit%20the%20post.%26nbsp%3B%20My%20preference%20is%20for%20the%20JSON%20generated%20with%20the%20workspace%20to%20go%20straight%20to%20main.%26nbsp%3B%20This%20can%20trigger%20a%20new%20build%20process%20in%20a%20more%20automated%20fashion%20consistent%20with%20CICD%20principals.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20can%20change%20this%20by%20going%20into%20the%20Manage%20option%2C%20selecting%20git%20configuration%2C%20then%20clicking%20on%20the%20gear%20box%20for%20Settings.%26nbsp%3B%20The%20only%20option%20you%20CAN%20change%20in%20Settings%20is%20the%20Publish%20Branch.%26nbsp%3B%20If%20that%20is%20not%20main%2C%20please%20set%20it%20to%20main.%26nbsp%3B%20%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EI%20will%20follow%20up%20with%20another%20post%20on%20this!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2160014%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2160014%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F964250%22%20target%3D%22_blank%22%3E%40qzhou%3C%2FA%3E%26nbsp%3Byou've%20got%20some%20good%20questions%2C%20let%20me%20take%20then%20one%20at%20a%20time.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EIt's%20a%20very%20interesting%20series%20of%20articles.%20I%20have%20some%20questions%20about%20the%20CI%2FCD%20process.%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EIs%20there%20a%20way%20to%20include%20the%20SQL%20pool%20data%20model%20in%20the%20flow%2C%20like%20using%20dacpac%3F%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYes%20this%20can%20absolutely%20be%20done.%26nbsp%3B%20I%20plan%20to%20blog%20on%20this%2C%20but%20the%20short%20answer%20is%20you%20would%20create%20a%20folder%20for%20the%20database%20project%2C%20sync%20your%20project%20to%20that%20repo%20folder%2C%20and%20then%20have%20a%20build%20pipeline%20that%20will%20create%20a%20dacpac%20for%20deployment%20similar%20to%20other%20database%20projects.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3EAlso%20is%20anyway%20to%20protect%20your%20Github%20publish%20branch%20with%20approvals%20or%20something%20similar%3F%26nbsp%3B%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20Azure%20DevOps%20you%20can%20absolutely%20have%20requirements%20for%20approval%20gates.%20There%20is%20a%20lot%20you%20can%20do%20with%20Azure%20DevOps%2C%20this%20is%20a%20good%20link%20to%20get%20started%20with%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Fpipelines%2Frelease%2Fapprovals%2F%3Fview%3Dazure-devops%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EUnderstand%20approvals%2C%20gates%2C%20and%20checks%20-%20Azure%20Pipelines%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2245534%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2245534%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Brad%2C%20great%20series%20of%20articles.%20This%20is%20the%20most%20comprehensive%20tutorial%20that%20anyone%20can%20follow%20and%20works%20like%20charm.%26nbsp%3B%20%26nbsp%3B%20Now%20the%20part%20that%20I%20am%20struggling%20with%20the%20most%20which%20i%20didn't%20anticipate%20it%20was%20going%20to%20be%20was%20creating%20a%20synapse%20workspace%20with%20just%20built-in%20serverless%20pool%20using%20ARM%20template.%26nbsp%3B%20%26nbsp%3BI%20used%20the%20portal%20to%20generate%20the%20template%20and%20downloaded%20it%20and%20setup%20a%20Arm%20template%20deployment%20task%20in%20release%20pipeline%20in%20devop.%26nbsp%3B%20%26nbsp%3BIt's%20creating%20the%20synapse%20space%20and%20storage%20and%20all%2C%20but%20i%20am%20getting%20an%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CDIV%3E%3CSPAN%3E%26nbsp%3B'Authorization%26nbsp%3Bfailed%26nbsp%3Bfor%26nbsp%3Btemplate%26nbsp%3Bresource%26nbsp%3B'datalakegen2synapseacct%2FMicrosoft.Authorization%2F5dc0d056-0e65-53d3-89fc-6e17ac29d7e7'%26nbsp%3Bof%26nbsp%3Btype%26nbsp%3B'Microsoft.Storage%2FstorageAccounts%2Fproviders%2FroleAssignments'.%26nbsp%3BThe%26nbsp%3Bclient%26nbsp%3B'4656517f-f949-417d-a1f8-3271ccbcc404'%26nbsp%3Bwith%26nbsp%3Bobject%26nbsp%3Bid%26nbsp%3B'4656517f-f949-417d-a1f8-3271ccbcc404'%26nbsp%3Bdoes%26nbsp%3Bnot%26nbsp%3Bhave%26nbsp%3Bpermission%26nbsp%3Bto%26nbsp%3Bperform%26nbsp%3Baction%26nbsp%3B'...%26nbsp%3B%20%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3EI%20would%20think%20this%20has%20something%20to%20do%20with%20the%20Service%20principal%20not%20having%20sufficient%20privilege%20or%20something..%20but%20I%20can%20not%20resolve%20it.%26nbsp%3B%20%26nbsp%3BI%20would%20think%20this%20should%20just%20work%20with%20out%20of%20box%20with%20imported%20templates.%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2363876%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2363876%22%20slang%3D%22en-US%22%3E%3CP%3E%22%3CSPAN%3E%26nbsp%3Bfolder%20that%20is%20the%20same%20name%20as%20your%20Azure%20Synapse%20Analytics%20workspace.%22%20we%20will%20see%20the%20folder%20only%20when%20we%20create%20the%20pull%20request%20and%20commit%20the%20changes%20post%20publish.%20otherwise%20will%20not%20able%20to%20see%20the%20folder%20workspace%20in%20repo.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2478241%22%20slang%3D%22en-US%22%3ERe%3A%20CI%20CD%20in%20Azure%20Synapse%20Analytics%20Part%203%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2478241%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EIn%20part%205%20we%20will%20look%20at%20generating%20the%20ARM%20templates%20needed%20for%20deploying%20a%20new%20environment%20from%20Azure%20DevOps.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EIs%20still%20there%20a%20part%205%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Dec 18 2020 04:45 AM