Automated publish improvement in ADF's CI/CD flow

Published 02-08-2021 05:40 PM 6,701 Views
Microsoft

The "Automated publish" improvement takes the validate all and export Azure Resource Manager (ARM) template functionality from the ADF UI and makes the logic consumable via a publicly available npm package @microsoft/azure-data-factory-utilities. This allows you to programmatically trigger these actions instead of having to go to the ADF UI and do a button click 'Publish'. This will give your CI/CD pipelines a truer continuous integration experience.

 

Current CI/CD flow

  1. Each user makes changes in their private branches.
  2. Push to master is forbidden; users must create a PR to master to make changes.
  3. Users must load ADF UI and click publish to deploy changes to Data Factory and generate the ARM templates in the Publish branch.
  4. DevOps Release pipeline is configured to create a new release and deploy the ARM template each time a new change is pushed to the publish branch.

current-ci-cd-flow.png

 

 

Manual step in current CI/ CD flow

In current CI/CD flow, the ADF UI is the intermediary to create the ARM template; therefore a user must go to ADF UI and manually click publish to start the ARM template generation and drop it in the publish branch. This manual step may be problematic for a few with different expectations around automation in the CI/CD process. 

 

 

The new CI/ CD flow

  1. Each user makes changes in their private branches.
  2. Push to master is forbidden; users must create a PR to master to make changes.
  3. Azure DevOps pipeline build is triggered every time a new commit is made to master, validates the resources and generates an ARM template as an artefact if validation succeeds.
  4. DevOps Release pipeline is configured to create a new release and deploy the ARM template each time a new build is available.

new-ci-cd-flow.png

 

For more details on implementing the new flow, check out our documentation

 

Note: You can continue to use the existing mechanism (adf_publish branch) or use the new flow. Both mechanisms will be supported, just that the latest one removes the additional 'publish' requirement using the ADF UI. Choose the flow which works better for you. 

20 Comments
Visitor

@Abhishek Narain , I've noticed that thus utility doesn't consider managedVirtualNetworks and managedPrivateEndpoints when it creates ARM templates. Because of this, I am unable to use this method to automate publishing. Do you have some solution or work around for this issue?

Microsoft

Is it possible to run validate all against a data factory in a feature branch?  Would be nice to block merges that won't pass validation before they get to master.

New Contributor

@bcassell-MSFT We use a dev branch AND a master branch, and make dev branch the Collaborative branch in our dev Data Factory resource. We make feature branches off dev, and then PR to dev first. The release pipeline in Azure DevOps deploys to the Dev environment first.

I think the issue with the old guidance is that the CI/CD diagram made it look like you must only have a master branch, and it looks like the new guidance suffers the same shortsightenness. Hopefully, someone special on the DF team is reading this.

Microsoft

@kolangareth The issue was fixed in the latest NPM package. Please update the NPM package and try.

Microsoft

@Jason Kohlhoff That's fair feedback. It should be the customer's choice. The major problem we sorted with this is the automated 'publish' and 'validate', getting rid of the adf_publish branch dependency, which was updated on publish using the collaboration branch (it could be master or any other).
We will come up with better guidance on deploying feature/ dev branches across environments and the limitless possibilities customers can use the CI/CD.    

Visitor

@Abhishek Narain  I am using the latest version 0.1.3. But the managedVirtualNetworks and managedPrivateEndpoints are not included in the Arm Template even with this version.

Microsoft

@bcassell-MSFT 

This package is not exclusive for the collaboration branch, you can generate any ARM template based on any branch.

Also, it is possible to run a build when a PR is raised and add it as a mandatory check before merging. You can do this in the branch policies section, e.g.,:

 

CesarBerard_0-1614623144737.png

 

Also note that you can also run a build every time there's a new commit in master.

Senior Member

@Abhishek Narain  I have noticed, while testing the ADF NPM utility, that the deleted pipelines are not getting undeployed from ADF environment.

 

Does the ADF utility not support this feature?

 

Do we need to follow some steps apart from the utility?

Senior Member

Hello Microsoft team,

 

NPM Utility is removing Azure DevOps Git configuration from my Data Factory integration.

 

I had to set after every build. Do we have any fix for this?

Microsoft

@skammili 

 

About the resources not deleted:

Since the ARM template deployment is an incremental operation, the resources are not deleted by design. You need to use a Post deployment PS script in order to do so, this script is included in the output of the package (PrePostDeploymentScript.ps1). Here's more info about this script and how to implement it in your release definition.

 

 

Regarding the Git problem:

 

It is possible that you are including global parameters in the ARM template. Since global parameters are located in the factory entity, when they are added, the factory entity is added in the ARM template as well, however, the Git configuration is not. You can check the box to do not include them in the ARM template and use the Global Parameters post deployment script in order to update them in the target environment. This script is provided in the output of the package as well (GlobalParametersUpdateScript.ps1). Here's more info about global parameters and CICD, and here is more info about the deployment with the PS script.

Regular Visitor

Hello Microsoft team,

 

I have datafactory for Development environment. In this datafactory both collaborator and publish branch are kept as master.

I created a feature branch from master and added a new ADF pipeline with one set variable activity in this feature branch. After this generated the arm template using the npm utility.

The ARM template got generated successfully. I also verfiied that my new ADF pipeline is present in ARMTemplateForFactory.json.

 

However are performing the deployment via release pipeline using the above generated ARM template.

I am not able to find the new ADF pipeline in my DataFactory.

 

Can you tell me where I may be doing something wrong.

Let me know if you need more information.

 

Regular Visitor

Hi @Abhishek Narain @CesarBerard 

Can you help me in resolving my above query ?

Regular Visitor

Hi @Abhishek Narain @CesarBerard,

 

My issue is resolved.

Regular Visitor

Hi @Abhishek Narain @CesarBerard,

Since now we are able to create ARM template from this npm package, can you tell me if it is possible to disable the manually publish from Data Factory ? If yes then can you help with some pointers.

 

Thanks in advance !!

Occasional Visitor

Hi, is there a way of incorporating this new functionality into an Azure DevOps release pipeline? The example above and in the documentation show how to do this on the commandline, but I would like to build this step into my DevOps YAML releases.

Regular Visitor
Occasional Visitor

This has been an issue for us for a long long time. As a result we decided on a different approach and started using a slick tool based on json file deployment. It works great.

 

Check it out at https://sqlplayer.net/adftools/

 

Occasional Visitor

Hi @Abhishek Narain ,

Something is not clear for me.

We want to use this new package to validate and test the factory before the change is merged in the collaboration branch.

So: PR to collaboration branch -> build artefact produced -> deployment back in DEV and tests -> PR approved and merged -> build artefact produced for release to int and prod.

Is this correct? I understood from the documentation that this method requires this DEV deployment (which before was not needed), as a replacement of the Publish button.

How this deployment back in dev works since dev has also git integration enabled? 

I have tried it, deployment back in dev works, but I can't identify my changes in the Factory UI. There are on the feature branch and not in collaboration branch (of course, since merge did not happen at this time), but where the changes are applied after deploying back to dev?

Thank you in advance!

Occasional Visitor

Hi ,

 

I have only one instance of ADF and having different folders like Dev, QA, Pre-Prod , Prod.

 

whatever pipelines I created in Dev , Can I still use CI/CD to create the same in QA folder

 

Regards,

Amit

Occasional Visitor

Hi @Abhishek Narain,

 

This is a great utility to avoid the manual publish which has been a pan for more than an year for our team. However, this doesn't seem to be supported for the data factory pipelines in the synapse. 

 

https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment-improvements

 

Could we expected the support for Synapse anytime soon?

%3CLINGO-SUB%20id%3D%22lingo-sub-2117350%22%20slang%3D%22en-US%22%3EAutomated%20publish%20improvement%20in%20ADF's%20CI%2FCD%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2117350%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EThe%20%22%3CSTRONG%3EAutomated%20publish%3C%2FSTRONG%3E%22%20improvement%20takes%20the%20%3CSTRONG%3Evalidate%20all%3C%2FSTRONG%3E%20and%20%3CSTRONG%3Eexport%20Azure%20Resource%20Manager%20(ARM)%20template%3C%2FSTRONG%3E%20functionality%26nbsp%3Bfrom%20the%20ADF%20UI%20and%20makes%20the%20logic%20consumable%20via%20a%20publicly%20available%20npm%20package%20%3CA%20href%3D%22https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40microsoft%2Fazure-data-factory-utilities%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%40microsoft%2Fazure-data-factory-utilities%3C%2FA%3E.%20This%20allows%20you%20to%20programmatically%20trigger%20these%20actions%20instead%20of%20having%20to%20go%20to%20the%20ADF%20UI%20and%20do%20a%20button%20click%20'Publish'.%20This%20will%20give%20your%20CI%2FCD%20pipelines%20a%20truer%20continuous%20integration%20experience.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22current-cicd-flow%22%20class%3D%22heading-anchor%22%20id%3D%22toc-hId-1971024408%22%20id%3D%22toc-hId-1971054163%22%20id%3D%22toc-hId-1971054163%22%20id%3D%22toc-hId-1971054163%22%20id%3D%22toc-hId-1971054163%22%20id%3D%22toc-hId-1971054163%22%20id%3D%22toc-hId-1971054163%22%20id%3D%22toc-hId-1971054163%22%20id%3D%22toc-hId-1971054163%22%20id%3D%22toc-hId-1970188330%22%3ECurrent%20CI%2FCD%20flow%3C%2FH3%3E%0A%3COL%3E%0A%3CLI%3EEach%20user%20makes%20changes%20in%20their%20private%20branches.%3C%2FLI%3E%0A%3CLI%3EPush%20to%20master%20is%20forbidden%3B%20users%20must%20create%20a%20PR%20to%20master%20to%20make%20changes.%3C%2FLI%3E%0A%3CLI%3EUsers%20must%20load%20ADF%20UI%20and%20click%20publish%20to%20deploy%20changes%20to%20Data%20Factory%20and%20generate%20the%20ARM%20templates%20in%20the%20Publish%20branch.%3C%2FLI%3E%0A%3CLI%3EDevOps%20Release%20pipeline%20is%20configured%20to%20create%20a%20new%20release%20and%20deploy%20the%20ARM%20template%20each%20time%20a%20new%20change%20is%20pushed%20to%20the%20publish%20branch.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22current-ci-cd-flow.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F253174i05A2D07676C0696B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22current-ci-cd-flow.png%22%20alt%3D%22current-ci-cd-flow.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH3%20class%3D%22heading-anchor%22%20id%3D%22toc-hId-163569945%22%20id%3D%22toc-hId-163599700%22%20id%3D%22toc-hId-163599700%22%20id%3D%22toc-hId-163599700%22%20id%3D%22toc-hId-163599700%22%20id%3D%22toc-hId-163599700%22%20id%3D%22toc-hId-163599700%22%20id%3D%22toc-hId-163599700%22%20id%3D%22toc-hId-163599700%22%20id%3D%22toc-hId-162733867%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22manual-step%22%20class%3D%22heading-anchor%22%20id%3D%22toc-hId--1643884518%22%20id%3D%22toc-hId--1643854763%22%20id%3D%22toc-hId--1643854763%22%20id%3D%22toc-hId--1643854763%22%20id%3D%22toc-hId--1643854763%22%20id%3D%22toc-hId--1643854763%22%20id%3D%22toc-hId--1643854763%22%20id%3D%22toc-hId--1643854763%22%20id%3D%22toc-hId--1643854763%22%20id%3D%22toc-hId--1644720596%22%3EManual%20step%20in%20current%20CI%2F%20CD%20flow%3C%2FH3%3E%0A%3CP%3EIn%20current%20CI%2FCD%20flow%2C%20the%20ADF%20UI%20is%20the%20intermediary%20to%20create%20the%20ARM%20template%3B%20therefore%20a%20user%20must%20go%20to%20ADF%20UI%20and%20manually%20click%20publish%20to%20start%20the%20ARM%20template%20generation%20and%20drop%20it%20in%20the%20publish%20branch.%20This%20manual%20step%20may%20be%20problematic%20for%20a%20few%20with%20different%20expectations%20around%20automation%20in%20the%20CI%2FCD%20process.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22manual-step%22%20class%3D%22heading-anchor%22%20id%3D%22toc-hId-843628315%22%20id%3D%22toc-hId-843658070%22%20id%3D%22toc-hId-843658070%22%20id%3D%22toc-hId-843658070%22%20id%3D%22toc-hId-843658070%22%20id%3D%22toc-hId-843658070%22%20id%3D%22toc-hId-843658070%22%20id%3D%22toc-hId-843658070%22%20id%3D%22toc-hId-843658070%22%20id%3D%22toc-hId-842792237%22%3EThe%20new%20CI%2F%20CD%20flow%3C%2FH3%3E%0A%3COL%3E%0A%3CLI%3EEach%20user%20makes%20changes%20in%20their%20private%20branches.%3C%2FLI%3E%0A%3CLI%3EPush%20to%20master%20is%20forbidden%3B%20users%20must%20create%20a%20PR%20to%20master%20to%20make%20changes.%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3EAzure%20DevOps%20pipeline%20build%20is%20triggered%20every%20time%20a%20new%20commit%20is%20made%20to%20master%2C%20validates%20the%20resources%20and%20generates%20an%20ARM%20template%20as%20an%20artefact%20if%20validation%20succeeds.%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3EDevOps%20Release%20pipeline%20is%20configured%20to%20create%20a%20new%20release%20and%20deploy%20the%20ARM%20template%20each%20time%20a%20new%20build%20is%20available.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22new-ci-cd-flow.png%22%20style%3D%22width%3A%20977px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F253175iCF616C289B81AC39%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22new-ci-cd-flow.png%22%20alt%3D%22new-ci-cd-flow.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20class%3D%22alert-title%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22alert-title%22%3E%3CSTRONG%3EFor%20more%20details%20on%20implementing%20the%20new%20flow%2C%20check%20out%20our%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fdata-factory%2Fcontinuous-integration-deployment-improvements%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Edocumentation%3C%2FA%3E.%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20class%3D%22alert-title%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22alert-title%22%3E%3CEM%3ENote%3A%26nbsp%3BYou%20can%20continue%20to%20use%20the%20existing%20mechanism%20(adf_publish%20branch)%20or%20use%20the%20new%20flow.%20Both%20mechanisms%20will%20be%20supported%2C%20just%20that%20the%20latest%20one%20removes%20the%20additional%20'publish'%20requirement%20using%20the%20ADF%20UI.%20Choose%20the%20flow%20which%20works%20better%20for%20you.%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2117350%22%20slang%3D%22en-US%22%3E%3CP%3EAutomated%20publish%20improvement%20allows%20you%20to%20publish%20the%20code%20changes%20without%20having%20to%20manually%20publish%2F%20generate%20ARM%20templates%20for%20deployments%20using%20the%20ADF%20UI.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2117350%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Data%20Factory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECICD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EContinuous%20Integration%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2162736%22%20slang%3D%22en-US%22%3ERe%3A%20Automated%20publish%20improvement%20in%20ADF's%20CI%2FCD%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2162736%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F241953%22%20target%3D%22_blank%22%3E%40Abhishek%20Narain%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3BI've%20noticed%20that%20thus%20utility%20doesn't%20consider%20managedVirtualNetworks%20and%20managedPrivateEndpoints%20when%20it%20creates%20ARM%20templates.%20Because%20of%20this%2C%20I%20am%20unable%20to%20use%20this%20method%20to%20automate%20publishing.%20Do%20you%20have%20some%20solution%20or%20work%20around%20for%20this%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2163670%22%20slang%3D%22en-US%22%3ERe%3A%20Automated%20publish%20improvement%20in%20ADF's%20CI%2FCD%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2163670%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20possible%20to%20run%20validate%20all%20against%20a%20data%20factory%20in%20a%20feature%20branch%3F%26nbsp%3B%20Would%20be%20nice%20to%20block%20merges%20that%20won't%20pass%20validation%20before%20they%20get%20to%20master.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2166710%22%20slang%3D%22en-US%22%3ERe%3A%20Automated%20publish%20improvement%20in%20ADF's%20CI%2FCD%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2166710%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977820%22%20target%3D%22_blank%22%3E%40bcassell-MSFT%3C%2FA%3E%26nbsp%3BWe%20use%20a%20dev%20branch%20AND%20a%20master%20branch%2C%20and%20make%20dev%20branch%20the%20Collaborative%20branch%20in%20our%20dev%20Data%20Factory%20resource.%20We%20make%20feature%20branches%20off%20dev%2C%20and%20then%20PR%20to%20dev%20first.%20The%20release%20pipeline%20in%20Azure%20DevOps%20deploys%20to%20the%20Dev%20environment%20first.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20the%20issue%20with%20the%20old%20guidance%20is%20that%20the%20CI%2FCD%20diagram%20made%20it%20look%20like%20you%20must%20only%20have%20a%20master%20branch%2C%20and%20it%20looks%20like%20the%20new%20guidance%20suffers%20the%20same%20shortsightenness.%20Hopefully%2C%20someone%20special%20on%20the%20DF%20team%20is%20reading%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2167822%22%20slang%3D%22en-US%22%3ERe%3A%20Automated%20publish%20improvement%20in%20ADF's%20CI%2FCD%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2167822%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F977243%22%20target%3D%22_blank%22%3E%40kolangareth%3C%2FA%3E%26nbsp%3BThe%20issue%20was%20fixed%20in%20the%20latest%20NPM%20package.%20Please%20update%20the%20NPM%20package%20and%20try.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2167828%22%20slang%3D%22en-US%22%3ERe%3A%20Automated%20publish%20improvement%20in%20ADF's%20CI%2FCD%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2167828%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F212549%22%20target%3D%22_blank%22%3E%40Jason%20Kohlhoff%3C%2FA%3E%26nbsp%3BThat's%20fair%20feedback.%20It%20should%20be%20the%20customer's%20choice.%20The%20major%20problem%20we%20sorted%20with%20this%20is%20the%20automated%20'publish'%20and%20'validate'%2C%20getting%20rid%20of%20the%20adf_publish%20branch%20dependency%2C%20which%20was%20updated%20on%20publish%20using%20the%20collaboration%20branch%20(it%20could%20be%20master%20or%20any%20other).%20%3CBR%20%2F%3EWe%20will%20come%20up%20with%20better%20guidance%20on%20deploying%20feature%2F%20dev%20branches%20across%20environments%20and%20the%20limitless%20possibilities%20customers%20can%20use%20the%20CI%2FCD.%20%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2174208%22%20slang%3D%22en-US%22%3ERe%3A%20Automated%20publish%20improvement%20in%20ADF's%20CI%2FCD%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2174208%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F241953%22%20target%3D%22_blank%22%3E%40Abhishek%20Narain%3C%2FA%3E%26nbsp%3B%20I%20am%20using%20the%20latest%20version%200.1.3.%20But%20the%26nbsp%3B%3CSPAN%3EmanagedVirtualNetworks%20and%20managedPrivateEndpoints%20are%20not%20included%20in%20the%20Arm%20Template%20even%20with%20this%20version.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Feb 07 2021 10:41 PM
Updated by: