Comment 1 for bug 1343410

From a duplicate bug:

From email:

> When creating an Azure environment, the availability-set-enabled setting is
> "true" by default. This prevents some Juju commands to run, especially the
> co-location commands (juju deploy --to X <charm> doesn't work)
>
> However, when the flag is turned to "false" those commands are enabled
> again.
>
> juju-quickstart doesn't seem to follow the same logic. Its documentation
> says that it's going to *try* to colocate the state server and the GUI. On
> Azure, it apparently decides that it's never possible to colocate, which
> means quickstart always end up with 2 units.
>
> Is there a way that can be changed so that when the availability set is
> false, then GUI gets deployed to machine 0 (and in this case I can write a
> feature request) or is there a good reason for that to happen as it does?