This message was deleted.

this doesn't quite seem like what you're meant to do, but I've created a new pulumi project with the exact same name & stack name, with a new .yaml config where I've used

pulumi config set --secret

to set the new token, then had to create a blank index.js with a new resource of the same type. After running

up

it seems to update the cached token in the remote stack

You can fetch the config for an existing project using

pulumi config refresh

I did that - and then used

pulumi config set

to provide newer values, but it still kept trying to use the expired token when deleting resources It was only when I created a dummy resource from the same provider, did the "create" task flush out the expired token from the backend

Hi @icy-controller-6092 Came across your post while searching for something else. Using the PAT is probably not the best way to do this, since the token expires. We found that the cleanest way to do this was to use

auth_type="azure-client-secret",

and provide the client ID and client Secret as environment variables.