If that isn't the case, is there a way to use the settings in the yaml file when creating the provider?

Looking at the

ProviderArgs

I wonder how I do I set the default

location

when doing it programmatically? The

location

doesn't seem to be a property on the

ProviderArgs

.

I did discover this when I was missing the

location

on the provider causing it to fail... when I then tried to set the

location

I couldn't find the

location

among the arguments when creating the provider, so what is the default way of setting the default

location

for a provider so I don't have to specify it on the resources?

** I’ve not tested this, but think it should work

So back to your original question - perhaps when you’re creating an explicit provider, it doesn’t pull from the config file – or it uses a different key prefix.

The way I checked which clientId that was used was by calling

getClientConfig

with the provider and it returned the client id for my user and not the SP I had configured in the config file.

I can update the ticket with the inconsistencies and how I would expect it to work.

Ok - have confirmed that the behaviour you’re seeing is by-design – only the default provider uses the config file. Providers instantiated explicitly will only use ENV variables or the explicit args which are passed in to the provider constructor

Interestingly, on my journey through the I’ve also noticed that if you just set the location on your root resource group, then the resources which reference it can inherit its location.