Activity log for bug #2051929

Date Who What changed Old value New value Message
2024-02-01 10:55:20 Diko Parvanov bug added bug
2024-02-02 07:05:02 Diko Parvanov description Seems the current auth types are interactive, service-principal-secret, but no way to use managed identity (https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview) - it would be good to have this option, as we do with IAM roles in AWS - where we don't have to manually manage credentials, but the applications themselves trying to interact with bootstrapping a juju controller on Azure can extract such via the metadata service in an instance. Seems the current auth types are interactive, service-principal-secret, but no way to use managed identity (https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview) - it would be good to have this option, as we do with IAM roles in AWS - where we don't have to manually manage credentials, but the applications themselves trying to interact with bootstrapping a juju controller on Azure can extract such via the metadata service in an instance. This will be particularly useful when automating the bootstrapping of juju controller on Azure without any user intervention.
2024-02-22 11:24:10 Ian Booth tags azure-provider
2024-02-22 11:24:17 Ian Booth juju: status New Triaged
2024-02-22 11:24:20 Ian Booth juju: importance Undecided Wishlist