Bug: `exclude_*` credentials in DefaultAzureCredential in azureml-mlflow

Apologies if this is posted in the wrong place, I'm happy to re-post if you can point me in the right direction - it's regarding `azureml-mlflow`.

The `azureml-mlflow` plugin currently uses a blank `DefaultAzureCredential()` call to generate credentials to track ML Flow runs. The `DefaultAzureCredential()` actually accepts a number of `exclude_*` arguments to avoid trying to use certain types of credentials.

Not being able to pass those `exclude_*` arguments to the `azureml-mlflow` plugin means that in some situations (experienced whilst on a customer-granted Azure hosted VM) it will try to use the machine's managed identity even when we explicitly do not want to.

Are there any plans to make those options available to us using azureml-mlflow?

Commencez par localiser où le plugin azureml-mlflow construit son DefaultAzureCredential, puis examinez les options exclude_* disponibles. Confirmez comment les appelants pourraient fournir ces options et ajoutez une couverture montrant que managed identity peut être exclue ; le travail est considéré comme terminé lorsque le plugin expose les contrôles d’identification demandés sans modifier le comportement existant.

Rédigé par le modèle d'indexation à partir du texte de l'issue.