Considering the age of the bug, I am guessing that you were using version of juju that had an old azure provider.
From Juju 2.0, we have moved to a new Azure provider.
Considering the age of the bug, I am guessing that you were using version of juju that had an old azure provider.
From Juju 2.0, we have moved to a new Azure provider.