Matt Richardson

Looks similar to https://github.com/Azure/azure-xplat-cli/issues/1966.

I worked around it by editing the file in Sublime Text, so its not a blocker for me.

In the absence I've finding a supported solution, I ended up creating a nodejs app that can be used to set this property. https://github.com/OctopusDeploy/azure-linux-helpers/tree/master/SetProvisionGuestAgentFlag. I'd still like to see this...

I'm also facing this issue. Any news, team?

Yep, happens with 1.3.0: ``` Vagrant.configure(2) do |config| hostname = "vagrantdsc.local" config.vm.guest = :windows config.vm.communicator = "winrm" config.vm.synced_folder ".", "/vagrant", disabled: true if Vagrant.has_plugin?("vagrant-multi-hostsupdater") config.multihostsupdater.aliases = {ip_address => [hostname]} end...

Unfortunately, not for my scenario, as I need to test against both ASM and ARM modes (its for an Azure VM extension).

It looks like its not releasing the lease on the disk - not sure why

Thats the approach I took: ```sh disk_name=`azure vm disk list VM_NAME --json | grep -i "mediaLink" | sed 's/.*vhds\/\(.*\)\",/\1/'` echo "Running 'vagrant destroy -f'" vagrant destroy -f echo "Cleaning up...

I'm kind of happy with the up/provisioning side of it. If it fails, you can just run `vagrant up` again, and it works re-runs with the new template (which is...

Turns out adding a `Install-PackageProvider nuget -force` makes it work. Keeping it open as it the exception message should be improved for this scenario.