Ross ROSS = Recommend OSS · open-source software intelligence for agents

Microsoft365DSC/Microsoft365DSC

Some data may be outdated — see provenance labels.

Manages, configures, extracts and monitors Microsoft 365 tenant configurations observed · 2026-09-21

github.com/Microsoft365DSC/Microsoft365DSC · homepage · PowerShell · MIT (permissive) observed · 2026-09-21

Health v2 · maintenance only

91/100

  • Activity 95
  • Release rhythm 82
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.

  • gap_med: 7
  • age_days: 2890
  • days_rel: 40
  • days_push: 30
  • n_releases_24m: 76

Full methodology

Adoption not part of the score

2393 stars · 676 forks observed · 2026-09-21

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Microsoft365DSC is an open-source PowerShell Desired State Configuration (DSC) module that lets organizations automate the deployment, configuration, extraction, and monitoring of Microsoft 365 tenant settings. It covers all major M365 workloads including Exchange Online, Teams, SharePoint, Power Platform, Intune, and Security & Compliance, with drift detection and reporting capabilities.

Use cases

  • automate deployment of Microsoft 365 tenant configurations as code
  • extract a full configuration snapshot of an existing M365 tenant
  • monitor tenant configuration and detect configuration drift
  • compare configurations of two or more Microsoft 365 tenants
  • manage Exchange Online, Teams, SharePoint, and Intune settings declaratively
  • notify admins or auto-remediate when tenant settings change
  • manage Defender for Office 365 anti-phishing policies via DSC

When to choose

  • you manage Microsoft 365 tenants and want configuration-as-code with DSC
  • you need drift detection and continuous monitoring of M365 settings
  • you want to export and document an existing tenant's configuration
  • you run multi-tenant M365 environments and need to compare or replicate configurations
  • your team uses PowerShell and DevOps pipelines for change management

When to avoid

  • you need to manage non-Microsoft clouds or on-premises infrastructure
  • you prefer imperative scripting over declarative DSC configurations
  • your tenant lacks the licenses required for certain resources (e.g., Defender for Office 365 needs E5)
  • you need a GUI-based tenant management tool rather than PowerShell
  • you cannot run an agent with internet connectivity to Microsoft 365 APIs

Facets

library · maturity active

configuration-management monitoring deployment infrastructure-as-code developer-tools cloud-computing self-hosted security windows cli cloud microsoft365 desired-state-configuration powershell-dsc tenant-configuration exchange-online sharepoint teams intune azure-ad configuration-drift office365 devops automation

10 sources

Member repositories

RepositoryRoleHealth v2
Microsoft365DSC/Microsoft365DSCmain91

For agents

markdown · JSON · MCP: product_card(name="Microsoft365DSC/Microsoft365DSC")

Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem