ServiceBusTrigger ignoring the DefaultAzureCredentialOptions set in DefaultAzureCredentials about azure-functions-dotnet-worker HOT 3 OPEN

@ganiths Can you describe the impact you're seeing as a result of this?

Based on current implementation, there is a separation that would currently prevent customization of that credential from impacting the setup of the extensions. But even if MI probing were still enabled, the system should fall back and use VisualStudioCredential already.

from azure-functions-dotnet-worker.

@mattchenderson My local machine is currently sitting behind a proxy that requires authentication. When i try to run the application locally, i am getting 407 proxy authentication error when defaultazurecredentials tries to do managedidentity authentication. After the error, its not proceeding in checking the next set of credentials and hence am unable to run the application locally

My application was initially written using .Net6 in process function app and am currently in the process of migrating to .Net 8 isolated worker and due to this error am unable to proceed further with the migration as we cannot test the application locally

in .Net 6 in process function app, i used to disable the managed identity during webjobstartup. But an equivalent one is missing in isolated worker function app.

 public class LocalDevelopmentWebJobsStartup : IWebJobsStartup
    {
        public void Configure(IWebJobsBuilder builder)
        {
            var credOptions = new DefaultAzureCredentialOptions();

            // For Local devlopment, Exclude managed identity authentication from default azure credentials
            // Otherwise it gives 407 Authentication required error
            // Also webjobs startup is required only for local development.
            var isLocalDevelopmentSetting = Environment.GetEnvironmentVariable("IsLocalDevelopment");

            var isConversionSuccess = bool.TryParse(isLocalDevelopmentSetting, out bool isLocalDevelopment);

            if (isConversionSuccess && isLocalDevelopment)
            {
                credOptions.ExcludeManagedIdentityCredential = true;

                builder.Services.AddAzureClients(clientBuilder =>
                {
                    clientBuilder.UseCredential(new DefaultAzureCredential(credOptions));
                });

            }
        }

    }

from azure-functions-dotnet-worker.

AFAIK The latest Azure Identity packages has some fixes regarding quick failure if it can't get to the MI endpoint

from azure-functions-dotnet-worker.