Can we please use a subclass of TokenCredential, rather than use DefaultAzureCredential always?

Reason being it is easier to use ChainedTokenCredential and force auth to resolve auth using only ManagedIdentityCredential and EnvironmentCredential for example. Without the use of ChainedTokenCredential, you have to use a whole bunch of exclude flags on DefaultAzureCredentialOptions (see example below). To me, this feels bit clunky.

There was a survey I filled recently on LinkedIn on this topic, and I thought I will log this as a discussion item today.