Anyone had issues with using managed service identity as the auth to run Pulumi rather than a service principal? I have set the "ARM_USE_MSI" env variable, but it's failing with the error below:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.

---> System.AggregateException: One or more errors occurred. (Status(StatusCode="Unknown", Detail="invocation of azure-nextgen:authorization/latest:getClientConfig returned an error: transport is closing", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1628073936.146857126","description":"Error received from peer ipv4:127.0.0.1:43909","file":"/var/local/git/grpc/src/core/lib/surface/call.cc","file_line":1063,"grpc_message":"invocation of azure-nextgen:authorization/latest:getClientConfig returned an error: transport is closing","grpc_status":2}"))

---> Grpc.Core.RpcException: Status(StatusCode="Unknown", Detail="invocation of azure-nextgen:authorization/latest:getClientConfig returned an error: transport is closing", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1628073936.146857126","description":"Error received from peer ipv4:127.0.0.1:43909","file":"/var/local/git/grpc/src/core/lib/surface/call.cc","file_line":1063,"grpc_message":"invocation of azure-nextgen:authorization/latest:getClientConfig returned an error: transport is closing","grpc_status":2}")

Is it just

getClientConfig

failing for you, or anything at all?

difficult to say, getClientConfig is one of the first things it does

That’s a bug then - I believe we never tested it with MSI

yep, no problem