This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 15%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGA%3C/text%3E%3C/svg%3E)
Hi,
I have a number of Functions written in dotnet. I want to start using ARM templates (or Proj Bicep) to deploy them.
Up to this point I've used he Portal and VS2019 Publish in order to get the code on Azure.
I want to start using CI/CD in Azure Dev Ops. I can build my repo for the function code easily. But, when it comes to release pipelines I want to run a template to deploy things. The problem is, what is the best practice?
I can create storage accounts and service plans and FunctionApps in my template, but how do I get my functions (code) in to the FunctionApp?
It would be nice if my template could reference the build artifacts of the built dotnet project for the functions.
Azure Release Pipelines do have a deployment step for AzFunctions but I don't know what this is doing :(
Thanks
Graham
Hi,
You can find example here on how to deploy a function that is located on Storage account.
A few more information you can find in this tweet as well.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Thanks Stan.
I've had a quick scan through Chapter 10 of your book, as well as the temaplte code in the repo. I can see the function app and storage accounts being created, but the one thing I can't find is how the zip file is copied to the blob storage. Is this done somewhere else?
My thinking right now, is my CI/CD process would be:
Yes, in my case the function zip file is on GitHub so I do not have to upload it but in your case you probably want to be on private place so you will need to have a task for uploading thr zip to existing storage account, issue SAS token and pass the url and the SAS token to the arm template so you can add it as value to the app setting for run from package. You can use Azcopy or Az PS to do the upload. May be there was also builtin task in DevOps for that. In this case you first create the storage account - could be done trough arm template l, upload the zip to the storage account and issue SAS token. The SAS token better be for the time of usage of the function as every time the function restarts will take the package from storage and last step will be to deploy the function with ARM template and the setting for the location of the function.