environments.

recall the exact syntax inside the parameter block. Even though I've created hundreds of scripts in my day, I always use a template because its much easier. Today I'm going to share with the exact Powershell template I use when creating my Powershell Scripts.

errors when the target files don't exist or already exist. Lucky for you, there are ways in PowerShell to check if a file exists before doing anything to it.

a PowerShell pipeline? By using the tips and techniques you'll learn in this article, you'll be well on your way to scripting your way to automation greatness.

needed an easy way to manage virtual desktops over many regions. This deployment actually got me thinking about how monitoring the WVD environment should be done.

basic user attributes in Active Directory. Like anyone else, I presented the idea of using RSAT to let them modify users in ADUC or ADAC. This was not an ideal solution because ADUC can become overwhelming to someone that isn't technical. They wanted something that was extremely basic, easy to follow and work in without any guidance or instructions, and did not show the user anything else that they could not modify or needed to see.

templates over and over again. When I've spent a couple of hours coding I usually end up with a folder containing multiple .bicep files that I need to compile running bicep build. But since bicep build doesn't have a --all switch or support wildcard characters on Windows (on OSX/Linux you can run bicep build *.bicep), I started using a simple PowerShell function to compile all .bicep files in a folder instead of compiling them one by one. After a couple of days using the function it escalated with more features and I decided to put together a PowerShell module that wraps Bicep CLI and share it with the community. And that's how the Bicep PowerShell Module was born.

modules (all with their own kinks) are used. However, PowerShell is very approachable and it's surprising what you can do with just a couple of lines of code. Working examples are great learning tools to help PowerShell newcomers (and maybe experienced coders) come up with solutions to problems. A couple of years ago, we created the Office 365 for IT Pros GitHub repository. Since then, we've been populating the repository with PowerShell scripts created to illustrate new features or to demonstrate how to approach solving an administrative problem in an Office 365 tenant. The repository currently holds a collection of 81 scripts.

colors are derived from the $env:COMPUTERNAME, so the colors would be different for each computer, but it would be the same color for the same computer name each time the script is ran.

receiving a number of requests to update my PowerShell module for Brickset , (which was developed against v2 and consequently had stopped working), both via a GitHub issue and some direct contact (including, surprisingly to me, internal email at work) I decided I'd better put some effort into updating it.