AzurePowerShellModulesCleanUp
My Ultimate Azure PowerShell Module Cleanup Script
Install / Use
/learn @WorkingHardInIT/AzurePowerShellModulesCleanUpREADME
🔍 Az PowerShell Module Cleanup Script
A PowerShell utility for cleaning up old or duplicate versions of Azure PowerShell (Az) modules across Windows PowerShell and PowerShell Core. It ensures that only the latest version of each Az module is retained—keeping your environment clean, fast, and free from version conflicts.
⚙️ Features
- ✅ Detects all installed
AzandAz.*modules - 🧩 Groups by PowerShell edition and installation scope (
CurrentUservsAllUsers) - ⛔ Skips removal of
AllUsersmodules if not run as Administrator - 🔄 Keeps only the latest installed version of each module
- 📋 Logs results to both Markdown and HTML
- 🎨 Color-coded output with emoji support in PowerShell Core, fallback labels in Windows PowerShell
- 🏃♂️ Dry Run mode to simulate the cleanup process without making any changes
- 🔧 Automatically switches between
Uninstall-ModuleandUninstall-PSResourcebased on PowerShell edition
🧰 Requirements
- PowerShell 5.1 (Windows PowerShell) or PowerShell Core (7+)
- Administrator privileges (for full cleanup including
AllUsersmodules) Azmodules already installed viaInstall-Moduleor, in case of PowerShell Core, via Install-PSResource
🛠️ Installation
Clone this repo or download the .ps1 script:
git clone https://github.com/WorkingHardInIT/AzurePowerShellModulesCleanUp.git
Or simply download CleanupOldAzurePowerShellModulesWorkingHardInIT.ps1.
🚀 Usage
Run the script directly in a PowerShell session:
.\CleanupOldAzurePowerShellModulesWorkingHardInIT.ps1
💡 Dry Run Mode
The script includes a -DryRun parameter that simulates the cleanup process without making any actual changes to your system. To run the script in dry run mode, use:
.\CleanupOldAzurePowerShellModulesWorkingHardInIT.ps1 -DryRun $true
In dry run mode:
- No modules will be uninstalled.
- The script will output what would happen, but no changes will be made to your environment.
💡 If not run as Administrator, the script will prompt to elevate. If declined, only
CurrentUsermodules will be cleaned.
📝 Logs
After execution, logs are saved in the following directory:
<Script Directory>\AzModuleCleanupLogs\
Each run creates:
AzCleanup_<timestamp>.md– Markdown log (GitHub friendly)AzCleanup_<timestamp>.html– HTML log (colored, styled)
📦 Example Output
🔍 Scanning for duplicate Az module versions by scope and edition...
📌 Az.Accounts (PowerShellCore in AllUsers):
🧩 Versions Installed: 3
❗ Versions to Remove: 2
📋 All Versions: 2.2.0, 2.1.0, 1.9.5
✅ Successfully uninstalled Az.Accounts version 2.1.0
✅ Successfully uninstalled Az.Accounts version 1.9.5
✅ Cleanup complete. Only the latest versions of Az modules are retained.
⚠️ Notes
- Dry Run Mode: When the
-DryRunparameter is used, the script simulates the cleanup, showing what would happen without making any changes to the system. - Deletion of modules done via either
Uninstall-ModuleorUninstall-PSResourcedepending on whether that is available and appropriate (it can only be used for PowerShell Core modules). - To force elevation in PowerShell Core,
wt.exe(Windows Terminal) is used to relaunch with admin rights. This also takes the DryRun parameter into account.
📄 License
This project is licensed under the MIT License.
🙌 Credits
Crafted with care by Didier Van Hoye
