The ARM Templates now supports artifacts… (and images)

Update 2021/2/10: BcContainerHelper has replaced NavContainerHelper. This blog post still reference NavContainerHelper, which is outdated.

I know a lot of partners and customers are using the Business Central ARM templates to create an Azure VM, which runs a specific version of Business Central (or NAV). This blog post describes what changed.

Images still supported

First of all, the ARM templates still supports docker images. This means that if you are provisioning Azure VMs using the ARM templates through a PowerShell script, that script should still run.

By default, the artifactUrl is specified to return the latest version and the docker image setting is blank. If you however specify a docker image in the template, it will ignore the artifactUrl setting (hence allowing your script to still run).

The ARM template short URLs

There are currently 6 short Urls for creating Azure VMs with Business Central or NAV. In all templates you can replace the artifactUrl to a different artifact, but by default, the shortUrls will give you the following: an Azure VM with the latest on-premises W1 build of Business Central (simplified template) an Azure VM with the latest on-premises W1 build of Business Central (extended template) an Azure VM with the latest W1 build of NAV (simplified template) an Azure VM with the latest W1 build of NAV (extended template) an Azure VM with the latest US build of Business Central (sandbox) a number of Azure VMs with the latest US build of Business Central (sandbox)

As a special option, you can add the number 2 to all Urls to get an insider version (the dev branch). While writing this blog post, the 2 branches are identical and I recommend that you use the Urls above.

The ArtifactUrl setting

When you launch any of those short Urls, you will be asked to login to the your Azure Subscription (i.e. the subscription which pays the cost of your Azure VM). After this, you will see a template, which you need to fill out. see this blog post for more general information about this:

The only new field is artifactUrl and it is defaulted as described under Get-BcArtifactUrl in this blog post:

Again – if you enter a docker image, the artifactUrl is ignored. You can either enter a full artifact Url (returned by Get-BcArtifactUrl) or you can enter the parameters for the function (like above) separated by a slash like:


This means that this value:

and this:


Yields the same Business Central version (but you probably already guessed that)


If you login to the Azure VM to see what is going on, you will discover that the ContainerHelper is using the mode, where is generates the image and saves it locally on the machine before running it:

The image is named mybc:<version>-<country>

The github repository

All the ARM templates are open source and you are very welcome to clone and change them for your own needs. The github repository is here:

The short Urls are calling an Azure Function to embed parameters into the template. You can reuse that, or you can create a direct Url to deploy your template. You will need a URL to your template json file, like:

You need to data string encode this url and append it to – then you will have a direct URL, that launches your template:

You can also use the azure function, which also is used by the short urls:

This offers the advantage to specify parameters and build out a string, which can deploy exactly the Azure VM you need (example setting the VmName)

You get the picture…


Freddy Kristiansen
Technical Evangelist

3 thoughts on “The ARM Templates now supports artifacts… (and images)

  1. Freddy, perhaps a stupid question from me, I’m using this for my development and that works great, but if I read correctly we can use this also to roll-out a specific Azure VM, using MFA, SSO voor a D365 BC Production instance in a specific version and specific localisation? Or do you advise not to use this for production sites. It seems to create an Azure VM and a container running at that VM or am I wrong.

    Second how can we then map the certificates and for instance the domainname\bc\) using the ARMtemplates?

    Third, would it not be great if we can also point to an additional script which is upgrading an existing Azure SQL database and connect it to the created new Azure VM.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s