Comment 2 for bug 1773359

We don't have a way of knowing that the machine is actually an instance from Azure (vs being any other machine that you might have running on some other cloud, or in some other data center).

It would be good to understand why it was necessary to bring it up manually, and understand what mechanisms we should be providing. Would it be better to "juju add-machine azure:instance-id" so that we know it is part of the same group, rather than adding it by IP address.

I'm also wondering *how* you added the machine. Did you "juju add-machine PUBLIC_IP" which is then why we advertise "this machine is known as PUBLIC_IP" to everyone else. We may know a private IP on the machine, but we don't necessarily know that the private IP is actually in the same network segment as the private IPs of other machines in your model.

It is true that Juju's modeling of what network spaces a manually added machine is part of is limited. IIRC, we only really use the one address you gave as part of the 'add-machine' call.