Automate the deployment, configuration, reporting and monitoring of MS365 Tenants. Despite being PowerShell it is decarative upfront, by using Desired State Configuration. Meaning you describe the desired end state rather than scripting step-by-step instructions.
The compiled configuration needs to be executed from an agent's Local Configuration Manager (LCM) (machine or container) which can communicate back remotely to Microsoft 365 via remote API calls.
See latest
Run the following PowerShell v5, as an ADMIN:
Install-Module -Name Microsoft365DSC -Scope AllUsers -Force
Update-M365DSCModule # Install dependencies like az, graph, intune, Note: best install and run using Powershell v5. For v7 read this first
Do NOT run this against your production tenant without careful setting the various permissions. Use App Registration (delegated or as app, with secret) as much as possible. For production MUST read
For information on how to get started, additional documentation or additional resources, please navigate to the official web site at Microsoft365DSC.com
🚀 Get Started
- Introduction
- Prerequisites
- Authentication and Permissions
- Authentication Examples
- How to Install
- Taking a Snapshot of Existing Tenant
- Deploying Configurations
- Securing your Compiled Configuration
- Monitoring for Configuration Drifts
- Cloning Tenant Configurations
- Generating Reports from Configurations
- Comparing Configurations
- Integrating with Azure DevOps
- Support
- Telemetry
- PowerShell 7+ Support
- Troubleshooting
🧠 Advanced
⚙️ Cmdlets
👥 Contributing
📚 Concepts
and check out the official YouTube channel Microsoft365DSC.
Microsoft365DSC captures Telemetry data about the names of the resources in which a configuration drift has been detected, along with the type of exceptions being thrown by errors in the various modules. While no sensitive data is ever captured, App Insights, which performs telemetry analytics, captures information about the city where the telemetry entries were captured by default. Users can opt-out to prevent telemetry from being sent back to the Microsoft365DSC team by running the following command:
Set-M365DSCTelemetryOption -Enabled $False