EARLY ACCESS · Free to explore · Payments unavailable
Tradescore LABS

TRADESCORE LABS / NO.1 FEATURED TOOL

Less hunting.
More PowerShell.

Find a support task. Tailor the values. Take a readable script into your own environment.

Exchange OnlineActive DirectoryMicrosoft GraphWindows
PS >_2

support tasks & workflows

One entry per task; report formats do not inflate the count.
50,000 distinct scripts remains an unfinished target.

START WITH THE PROBLEM

What do you need to fix?

Search in plain English, use a command name, or narrow the library using the filters below.

Browse web-sourced candidates awaiting review ↗

COMPATIBILITY

REQUIRES

IMPACT

Connection and preparation
Use an account authorised for the target environment. Existing session required; these scripts do not install modules or authenticate automatically.
1. Tailor to your environment
Replace the example values below, then edit any part of the script in the box. Nothing runs on this website.
Values stay in this browser. Use sample values, not passwords or secrets.
2. Edit your draft
Click inside the script to edit it. Check the commands and permissions, then copy your final draft into your own PowerShell window.
Original library scripts were syntax checked locally; your edits need a fresh check. Not executed against a production tenant. Read-only queries can expose sensitive information in their output. Export scripts write local files.
3. CHECK BEFORE YOU COPY
Check your script
Checks use the current editor text. They flag common patterns; they are not a PowerShell parser, execution test or security certification.
  • Run checks after tailoring your script.
Check PowerShell syntax locally without running the script
Download your draft first. In your own PowerShell window, set this path to that downloaded file and run the checker below. It parses the file; it does not execute it. Valid syntax does not prove correct parameters, permissions or behaviour.
$draftPath = 'C:\Temp\your-tailored-script.ps1'
$tokens = $null
$parseErrors = $null
$null = [System.Management.Automation.Language.Parser]::ParseFile(
    $draftPath, [ref]$tokens, [ref]$parseErrors
)
if ($parseErrors.Count) {
    $parseErrors | Select-Object Message,
        @{Name='Line';Expression={$_.Extent.StartLineNumber}}
} else {
    'No syntax errors found. Script was not executed.'
}
For behaviour testing, use an authorised non-production environment. Check Get-Help CommandName -Full before relying on -WhatIf; not every command supports it.
Module required: . The browser cannot verify installation, credentials, network access or tenant permissions.
Microsoft command reference ↗
LEARN THE FOUNDATIONS
How to use PowerShell modules.
A module is a package of commands. Install puts it on your computer; import makes its commands available in a session; connect signs in to a service when needed. Importing trusted modules can run their initialisation code.
When a module or command cannot be found
  • Check $PSVersionTable: Windows PowerShell 5.1 and PowerShell 7 have different compatibility and module paths.
  • Compare Get-Module (loaded now) with Get-Module -ListAvailable (discoverable installations).
  • Check your organisation’s approved repository and installed package manager. These examples use PowerShellGet; PSResourceGet uses different installation commands.
  • Restart your shell after an update if an older assembly remains loaded. Test version changes before using production scripts.
  • ActiveDirectory, DHCP and other Windows role modules generally come through Windows features or RSAT, rather than a similarly named Gallery package.
  • If a policy blocks loading, follow your organisation’s approval process. Do not disable policy or bypass publisher checks just to make an example work.
Check the package publisher, licence and prerequisites before installation. Install and update examples change your local module files; connection examples can trigger sign-in and consent. Only grant the permissions your task needs.
Sources, checked 11 October 2026: Install · Import · Update · Exchange requirements · Graph installation · PnP installation · PnP sign-in
YOUR REPEATABLE ROUTINE
My support runbook
Save tailored steps locally. Download a handover pack to take with you.
Browser storage only on this site. No cloud sync or customer access checks are enabled.
ENGINEER’S TOOLKIT
More than a list of commands.
Incident handover
A reusable brief for symptoms, scope, evidence and next owner.
Change checklist
Capture approval, rollback, validation and maintenance window before a change.