Scripts I Use Daily

A curated collection of PowerShell scripts for everyday tasks: Azure management, development tooling, container management, RSS reading, system administration, and more.

Scripts are organized into folders by topic. Add the root folder (and all subfolders) to your system PATH using the provided Add-DirToSystemEnv.ps1 script so you can call any script by name from any directory.

📁 Folder Structure

Folder	Description	README
Azure	Azure management scripts (VMs, networking, App Insights, email)	Azure/README.md
Codez	Development tools (build cleanup, Git pull, cheat sheets, containers)	Codez/README.md
Containers	Docker container management (SQL Server in containers)	Containers/README.md
Kubernetes	Kubernetes command references	Kubernetes/README.md
Office	Office document automation (extract images from Word)	Office/README.md
Profiles	PowerShell profile configuration	Profiles/README.md
Random	Miscellaneous utilities (weather, text-to-speech)	Random/README.md
RSS	RSS feed reader for the terminal	RSS/README.md
System	System administration (PATH, env vars, software management)	System/README.md

🚀 Getting Started

Prerequisites

• PowerShell 7+ — download and install for your platform
• Windows Terminal — recommended terminal (Windows)
• PowerToys — optional but recommended on Windows

Adding scripts to your PATH

To call scripts from anywhere without specifying the full path, add the repository root and all subfolders to your PATH:

.\System\Add-DirToSystemEnv.ps1 -PathToAdd "C:\path\to\scripts" -RestartCurrentSession

After running this, you can call any script by name:

Read-Rss.ps1
Get-WeatherInfo.ps1
Remove-ObjBin.ps1

Before:

After:

Azure scripts

Azure scripts require the Azure PowerShell module:

Install-Module -Name Az -Scope CurrentUser -Force
Connect-AzAccount

🧪 Running Tests

Each folder that contains scripts has a tests/ subfolder with Pester tests.

# Run tests for a single folder
Invoke-Pester -Path .\Azure\tests\Azure.Tests.ps1 -Output Detailed

# Run all tests
Invoke-Pester -Path .\Azure\tests, .\Codez\tests, .\Containers\tests, .\Office\tests, .\RSS\tests, .\Random\tests, .\System\tests -Output Normal

Tests validate script syntax, parameter definitions, help content, and (where possible) functional behavior — without requiring Azure credentials or external services.

📚 Additional Resources

Resource	Link
PowerShell documentation	learn.microsoft.com/powershell
PowerShell GitHub repository	github.com/PowerShell/PowerShell
Windows Terminal	learn.microsoft.com/windows/terminal
Windows Terminal GitHub	github.com/microsoft/terminal
PowerShell module authoring tips	Module authoring considerations
Azure PowerShell	learn.microsoft.com/powershell/azure
Pester testing framework	pester.dev

🤝 Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.