Continuous Delivery is the practice of deploying a package into a non-production environment in an automated manner.

Once our Continuous Integration process is completed successfully, we can deploy a package using the Continuous Delivery practice in an automated way.

1. Click on the Releases in VSTS.

2. Click on New definition:

3. Select the Azure App Service Deployment template and click on Next:

4. Select the Project and Build definition that we created in the previous section.
5. Select the Continuous Deployment checkbox.

6. It means that whenever the associated Build definition is successfully executed, release definition will be triggered automatically. Click on Create:

• • The new Release definition is ready.
  • Let's configure it.
  • We need to configure Azure Subscription first.

7. Click on Manage:

8. Click on New Service Endpoint.
9. Select new Azure Resource Manager:

10. Provide a Connection name and select Subscription:

11. Verify the newly created endpoint:

12. Go to the Release Definitions. Refresh the list of Azure subscriptions:

13. Click on the Authorize button:

14. Refresh the list of App Service names and select the Function App created earlier.

15. Save the Release definition:

16. In the package or folder, select the location which we have given in the Publish Artifact task in the Build definition:

17. Now, we have the Build & Release definitions ready.
18. Go to the Build section and click on Queue new build.
19. Click OK:

20. Wait for the availability of Hosted Agent. Hosted Agent is a virtual machine available for use where most of the required packages are available to execute the build:

21. Once all the tasks defined in the Build definition are executed successfully, then the Build definition is successful:

22. We can click on the specific task to get the task-specific logs:

23. If in the Release definition, the trigger for Continuous Deployment is not selected, we can execute the Release definition manually too.
24. Click on Create Release:

25. Select the Build version as the source and click on Create:

26. Observe the summary of the ongoing execution of the Release definition:

27. Click on the Logs tab to see the logs related to specific tasks.
28. It will download artifacts and deploy the Azure function into the Azure Functions app:

29. Verify the Function Apps in Azure Portal:

30. Go to the Kudu editor and verify the function deployment.

31. To go to the Kudu editor, and in the Azure Function URL, add scm after the function name:

32. Now, try to upload an image in the blob container so our function gets executed.
33. Verify whether the new function is operational or not:

34. To configure Continuous Deployment automatically, we can go to the Triggers tab in the Release definition:

35. Now, once we have configured triggers for the Build or Release definitions; change the code:

36. Verify the summary of the Build definition execution and see the Associated Changes section:

37. Once the Build execution is completed successfully, the Release definition will execute immediately.

38. Verify the Summary of the Release definition and see if it is triggered by the Build definition that we have created:

39. After the Release definition is executed successfully, upload another image in the blob container and verify the logs of the Azure Function:

Done.

We have configured Continuous Integration and Continuous Delivery for Azure Functions.