You can then modify the following PowerShell for VM creation: This VHD will be attached to your CHR, so name it accordingly. Upload the VHD to your storage account using PowerShell, or the Azure Storage Explorer. Note that your new CHR will have a blank password, so be conscious of exposing it to the internet in this configuration.

It’s also a good idea to attach a public IP address to the NIC, and set up a security group allowing winbox access, if you don’t have VPN access to your Azure environment, or a pre-existing jump host. You’ll need a resource group, NIC, and storage account if you don’t already have these. I’m time poor so I’m assuming you already know your way around the ARM portal and can connect to your Azure account with the PowerShell module.įirstly, to save you the time of converting the Mikrotik VHDX, here’s a VHD of 6.37.1 I prepared earlier. We get much better performance by using Standard VM SKUs as opposed to BasicĪs promised, here are the basic steps to get one up and running.Redeploying/resizing a CHR will result in the software ID changing.You still need to convert the Mikrotik supplied VHDX to VHD before uploading.Recent RouterOS upgrades we’ve performed have completed without issue.CHR VMs will now gracefully Start and Stop without the risk of them ending up in an inconsistent state.The latest RouterOS is 6.37 and our routers are working better than ever.

A lot has changed since I first wrote about CHR in Microsoft Azure.

Mikrotik chr azure