[BUG] Getting random error on initialization on Azure Container Instance Managed Identity: ManagedIdentityCredential authentication failed: 'R' is an invalid start of a value

[vikramdadwal]

Library name and version

Azure.Identity 1.5.0

Describe the bug

I have a logic App which creates a Azure Container Group on the fly and attached a Managed User Identity with the container Group. I have the following code written in the Program.cs:

Most of the time above logic works fine. But many times it fails with the following error:

Startup Exception occurred: ManagedIdentityCredential authentication failed: 'R' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.
See the troubleshooting guide for more information. https://aka.ms/azsdk/net/identity/managedidentitycredential/troubleshoot

Expected behavior

Code should throw no error while initializing the App Configuration connection using managed identity.

Actual behavior

Throwing error at startup:

Startup Exception occurred: ManagedIdentityCredential authentication failed: 'R' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.
See the troubleshooting guide for more information. https://aka.ms/azsdk/net/identity/managedidentitycredential/troubleshoot

Reproduction Steps

Its really very random. Hard to reproduce.

Environment

OS Type: Linux
Code running in container inside Azure Container Instances

[vikramdadwal]

Here is a stack overflow thread for the same issue: https://stackoverflow.com/questions/64020927/azure-container-instance-managed-user-assigned-identity-not-able-to-fetch-keyv/64035955#64035955

[jsquire]

//cc: @schaabs

[jsquire]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[christothes]

This should have been addressed in #32272 and will be available in the next release of Azure.Identity.

[ghost]

Hi @vikramdadwal. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[ghost]

Hi @vikramdadwal, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.