Export Microsoft 365 configs — Intune, M365DSC, SharePoint, Exchange, Power Platform, Entra ID, Security & Compliance. PowerShell emitted locally.
About this edition
Eight configuration-export tools for infrastructure-as-code workflows. Deterministic snapshots of policies, controls, and dial plans — same output on desktop and cloud.
What you get
Intune Export — 26 configuration categories including policies, profiles, and apps
M365DSC Export — Microsoft 365 Desired State Configuration
SharePoint Permissions Export — site and item-level
Power Platform Export — Power Apps and Power Automate flows
Exchange, Teams Voice, Entra ID, Security & Compliance exports
Six tools emit PowerShell scripts locally — no cloud-only runtime
Who it's for
M365 platform engineer. Pulling tenant configs into a Git repo so they can be reviewed, diffed, and PR’d like code — Deterministic exports per category — drop the output into your IaC pipeline and treat config as artefacts.
Compliance auditor. Need to evidence current Intune and conditional-access posture for a SOC 2 review — One run per tool produces a timestamped JSON/PS1 snapshot matching what’s live in the tenant.
Pre-migration consultant. Capturing the source tenant’s config baseline before a tenant-to-tenant cut-over — All eight configs in a single workflow; pair with the Migration SKU for the data side of the move.
Edition identity
SKU id: config.
Tools included: 8.
Tagline: Snapshot Intune, M365DSC, Exchange, Entra ID, and Power Platform configs..
Limitations & out-of-scope
Blueprint: Blueprint is a read-only configuration export — never writes back to the tenant. Apply / restore is a manual operation by an administrator. Tenant-wide settings stored outside Microsoft Graph (legacy admin centers, classic SharePoint) fall outside the export envelope.