Usually when I’m writing PowerShell scripts I do it from a development virtual machine with a known environment state. However, yesterday I was trying to do something simple and quick and was writing it on my everyday laptop.
My script was using Windows Management Framework 5.0 and I was creating a new burn environment in AzureRM. I was authenticated and could query and enumerate most of my AzureRM environment, however I was getting erroneous responses on some cmdlets and was unable to create a new resource group. Essentially whenever I tried to perform anything of value to what I was trying to achieve PowerShell would return ”Run Login-AzureRmAccount to login.”
I was authenticated and all looks as it should.
Query ARM RG and get the error, ”Run Login-AzureRmAccount to login.”
I started digging to find out what my environment was looking like. Did I have WMF5 installed? $PSVersionTable showed I did and all looked as it should.
What modules did I have installed? Get-InstalledModule | Out-GridView
Lots of differing versions is what I saw *Note: screenshot above is after resolving my issue.
So what fixed my issue? I ran Update-Module and watched PowerShell update my modules and get my environment back into spec. A restart of my laptop and back in action.
What caused my issue? I’m thinking I updated an individual module at some point and dependencies were missed.
Hope this helps someone else and saves some of those “this should just be working, why isn’t it” moments.
Today, I’m super excited to finally announce the Beta release of EntraPulse Lite – a…
I'm excited to share some significant authentication enhancements I've contributed to the Lokka MCP Server…
Last month I had the pleasure of speaking at the Sydney event for Global Azure.…
Model Context Protocol (MCP) is a powerful framework that extends AI clients like Claude and…
I've just completed participating in the Azure AI Developer Hackathon that was looking to provide…
Updated: July 2025 v1.0.2 Fixes issue setting D365SalesGlobals enabling session management for D365 Sales API…
This website uses cookies.