PowerShell

In my monthly summary, I will summarize all the Azure infrastructure news from April, which appeared to be a month for security announcements.

Microsoft released the generally available (1.0) version of the Teams PowerShell module on April 24. The Get-Team cmdlet receives a big makeover (and slowdown), but overall the module is solid and you shouldn’t need to make too many changes to scripts.

Two themes this month. PNP PowerShell is awesome and got more awesome and what is old is new. The PowerShell is pretty self-explanatory but the old is new is fun. We get back connected web parts (circa 2003), we can do templates, and the News capability (which reminds me of 2003 portals) are all covered…

How to run code on a remote Windows Device from Visual Studio Code using PowerShell Remoting.

A year is a long time in Office 365. Lots changes in that time, so it’s good to go back and look at some PowerShell written to report Teams and Groups activity. Improvements can be made, advantage taken of changes made by Microsoft, and generally the whole thing can be tidied up and upgraded. PowerShell makes it easy to do – and to change if you don’t like what I’ve done.

Looking for help with your migration in a hybrid cloud world? These tools can help you on your path ahead.

It was another busy month for Azure, here’s a wrap-up of what you need to know for January.

Russell explains how to use Puppet Bolt to run commands remotely on Windows Server.

Learn about the new Az PowerShell module for managing and deploying resources in Microsoft Azure.

Russell explains whether there is a difference between WMI and CIM.