Using Scoop to install tools without elevated privileges on Windows 11, especially in an Enterprise setting, is super helpful but there can be some knock-on effects to other apps & configuration. One such issue I discovered was to do with Git and Git Credential Manager, so let’s take a look at that.

In a follow-up to my previous post Starship prompt for PowerShell & WSL on Windows 11, I’ll show how to configure Starship for the good old native Windows shell cmd.exe.

This error can occur when you’re trying to deploy a change to an Azure network resource, but its provisioning state, or one of its dependencies, is “Failed”. Should I start panicking now? Why does this happen? And how do I fix it?

“One Prompt to config them all,
One Prompt to style them,
One Prompt to display in all
and in the Shell bind them.”

If you receive this error when trying to deploy some changes to Azure, you would be forgiven for thinking, “That looks like a Resource Provider hasn’t been registered on a Subscription, but my Service Principal has permissions to do that…so why didn’t it work?!”

If the title of this article isn’t long enough then the rest of the blog post will make up for it, because there’s a lot to cover.