Get started with Raidiness

Before you start

Use PowerShell 7.2 or newer for the core module. Optional workload modules can require a newer PowerShell version or Windows. You also need approved access to the tenant you intend to assess; installing Raidiness does not grant that access.

Start with Microsoft Graph and add the workloads relevant to your assessment. Review consent requests against your organization's policy, and choose an approved folder for the results.

Install Raidiness

Install the published module for your current user:

Install-Module Raidiness -Scope CurrentUser

Check the installed version and available command help:

Get-Module -ListAvailable Raidiness |
    Select-Object Name, Version
Get-Help Invoke-Raidiness -Full

PowerShell Gallery is the place to check published versions. Add -AllowPrerelease only when you deliberately want a published prerelease.

Choose the command for your version

I have simplified the entry point in the 0.5 development workflow to Invoke-Raidiness. The published 0.4.5 package uses Invoke-RaidinessCheckup for a complete assessment. The commands below distinguish these workflows so an older installation does not stop after collection.

Current 0.5 development workflow

If you have a build with the new guided workflow, start with:

Invoke-Raidiness

It offers additional workloads, checks local requirements, asks for an output location and offers file-based intake. It then signs in as needed, collects evidence and generates the report. Intake answers are edited in a CSV or JSON file.

For customer work, I recommend naming the tenant explicitly:

Invoke-Raidiness -TenantId 'contoso.onmicrosoft.com' -Customer 'Contoso'

These instructions describe the 0.5 workflow in my current source code. Installing the latest stable Gallery package does not guarantee that it includes those changes.

Published 0.4.5 workflow

For the 0.4.5 release, use the complete checkup command:

Invoke-RaidinessCheckup -TenantId 'contoso.onmicrosoft.com' -Customer 'Contoso' -Modules MsGraph

In that version, Invoke-Raidiness is the lower-level collection command. Report generation and intake behavior also differ from 0.5. Follow the help for the version you installed. You can inspect the published 0.4.5 checkup command on PowerShell Gallery.

Add only the workloads you need

Microsoft Graph is the core source. Optional modules add Exchange Online and Purview, Teams, SharePoint or Power Platform evidence. They require their own management modules and approved sign-in context.

The SharePoint and Power Platform adapters require Windows in the current workflow. Check the installed module's requirements before adding these sources. A local prerequisite check does not establish remote permissions, consent or licensing.

Read the report with its gaps

Start with the findings and the evidence that could not be collected. Not measured means there is insufficient evidence to evaluate that check. Review the reason before drawing a conclusion.

The current 0.5 workflow produces HTML, printable HTML, Markdown, JSON and CSV findings. The CSV retains the filename action-list.csv, but contains findings rather than generated recommendations. Older releases have different report and export behavior.

Keep the results in approved storage and review them before sharing. They can contain tenant and personal information. The default Documents location may be synchronized by OneDrive; use -Path when you need a different location.

For the assessment approach behind the commands, read my AI Readiness Check. For a question or feedback, get in touch with the module version and a sanitized error rather than a complete tenant export.