Powershell works ;)

This PowerShell script retrieves Azure Automation jobs from the last 7 days for a specific runbook, enriches each job with missing details, normalizes all parameters, and exports everything to a CSV file for easy analysis. This can be incredibly useful for operational monitoring, auditing, and troubleshooting. In many environments, runbooks are triggered with dynamic input…

When writing or re-organizing PowerShell scripts, one of the first improvements I usually make is replacing hardcoded values with input parameters. At the beginning of my PowerShell journey I often wrote scripts where usernames, server names, or paths were directly written into the script itself. This works for quick tests, but very quickly those scripts…

Error handling is an important when writing scripts. Many automation scripts interact with external systems such as Active Directory, Azure services, databases, or REST APIs. When something goes wrong, the script should detect the error and react accordingly. PowerShell provides structured error handling through Try, Catch, and Finally blocks. However, there is an important detail…

PowerShell frequently works with structured data, and two common ways to store such data are Hashtables and PSCustomObjects. While both structures can look similar at first, they behave differently and serve different purposes. Understanding the differences between these two approaches helps create scripts that are easier to read, easier to maintain, and better suited for…

This is a short Blogpost, but very useful. When writing scripts, it is often important to understand how long a script or command takes to execute. Measuring script runtime can help identify slow operations, analyze performance, and improve automation processes. In many environments scripts run regularly, for example in scheduled tasks, background jobs, or Azure…