Azure App Configuration No managed identity endpoint found with ManagedIdentityCredential

TL;DR

This happens when the managed identity is not actually enabled on the host. Also confirm the identity has the Azure App Configuration Data Reader role on the store, without the data-plane role you will get 401/403 instead.

Steps

1. This happens when the managed identity is not actually enabled on the host. In the Azure portal, open the App Service, go to Identity under Settings, and make sure Status is On under the System assigned tab. Also confirm the identity has the Azure App Configuration Data Reader role on the store, without the data-plane role you will get 401/403 instead. Note that ManagedIdentityCredential has no endpoint when running locally, so use a connection string for local development.

When to use

You are seeing this: Connecting with x.Connect(new Uri("your service endpoint URL"), new ManagedIdentityCredential()) throws "No managed identity endpoint found". Use this skill when you run into "Azure App Configuration No managed identity endpoint found with ManagedIdentityCredential".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

• Also confirm the identity has the Azure App Configuration Data Reader role on the store, without the data-plane role you will get 401/403 instead.
• Note that ManagedIdentityCredential has no endpoint when running locally, so use a connection string for local development.

A user asked: Connecting with x.Connect(new Uri("your service endpoint URL"), new ManagedIdentityCredential()) throws "No managed identity endpoint found". The code runs in Azure App Service and the app crashes with an unhandled Azure.Identity exception. The verified answer: This happens when the managed identity is not actually enabled on the host. In the Azure portal, open the App Service, go to Identity under Settings, and make sure Status is On under the System assigned tab. Also confirm the identity has the Azure App Configuration Data Reader role on the store, without the data-plane role you will get 401/403 instead. Note that ManagedIdentityCredential has no endpoint when running locally, so use a connection string for local development. Thread: https://vectle.com/threads/thr_Uh0WxMramAeQl3MM5NNCSw