azure-quickstart-templates | Azure Quickstart Templates | Azure library

This behavior seems to be poorly documented, but from the documentation page for the Windows custom script extension:

The name of the resource has to be in the format virtualMachineName/extensionName, if this extension is used as a standalone resource in the Azure Resource Manager template.

Which seems to imply that the resolution for where the custom script extension should be executed is based on the name. I imagine this is the case for Linux VMs too.

For the particular example that you are looking at, the name of one of the vms is:

I tested this on my environment and I noticed that simply changing the uri in publish_content_link doesn't really do any changes in the runbook script.

In order to apply the changes in the script you have to change the name of the runbook too instead of only changing the uri.

So, after you change the name and uri both in the terraform code and do a apply. It will recreate the runbook with the new name and content in the portal.

Outputs:

OR

If you want to change just the content and not the name , then you can save the script from that link locally and pass the content to the already created runbook and it will successfully update the content.

I tested this as well with the below code:

The error is valid, below are the possible values available for the databaseAccount kind

• 'GlobalDocumentDB'
• 'MongoDB'
• 'Parse'

To create a serverless account, you need to pass the capabilities parameter as below under properties

You need to extract the autoscalesettings into a dedicated variable and conditionally include that in the template depending on your parameters.

Full example: https://mattfrear.com/2020/06/17/conditionally-specify-a-property-in-an-arm-template/

Rough sketch on how this could look like (probably contains some small errors).

In the same repo, check out the azuredeploy.parameters.json file, and you'll see an example of the vNets object it's looking for.

You can use the parameters file as-is and deploy it to your subscription or feel free to customize the names, address spaces, etc. by adjusting the properties

You can find the relevant documentation in the ManagedClusterProperties object

The trick here is to get the resource name and you can find the relevant documentation from the ARM documentation by mapping the reosurce

I have an example here that I built decompiling the arm template sample you showed into bicep.

https://github.com/markjbrown/azure-quickstart-templates/tree/sql-sp/quickstarts/microsoft.documentdb/cosmosdb-sql-container-sprocs

I have not yet had a chance to complete the PR I have on this updated sample but this will get published where the ARM template you pointed to lives. But if you need an example that works to unblock you this is what you need.

UPDATE: Apologies for the empty bicep file. Not sure how that happened.

To get an example of how to deploy a UDF using bicep you can take the ARM template located here and then pass it to bicep's decompile function. Example below.

There are some mistakes in your ARM template such as the value of WORDPRESS_DB_HOST should be "127.0.0.1:3306" instead of "127.0.0.0:3306" and the port number should be "port": 3306 instead of "port": "3306". Also, the image wordpress does not work for me, instead, using the image wordpress:4.9-apache works.

Sample

I was able to mitigate the issue by myself. It's not exactly clear what caused incomplete deletion, but the following code worked: