A user-friendly graphical interface for managing Microsoft Defender for Identity (MDI) configurations using PowerShell.
This PowerShell script provides a comprehensive WPF-based GUI wrapper around the Microsoft Defender for Identity PowerShell module. It simplifies the configuration, testing, and management of MDI deployments through an intuitive interface, eliminating the need to remember complex PowerShell commands.
Publisher: Thomas Verheyden
Release Date: November 21, 2025
- Set MDI configurations for Domain or LocalMachine mode
- All (all configurations)
- AdfsAuditing
- AdRecycleBin
- AdvancedAuditPolicyCAs
- AdvancedAuditPolicyDCs
- CAAuditing
- ConfigurationContainerAuditing
- EntraConnectAuditing
- RemoteSAM
- DomainObjectAuditing
- NTLMAuditing
- ProcessorPerformance
- Test MDI configurations
- Validate specific audit policies
- Support for both Domain and LocalMachine testing modes
- Generate comprehensive HTML configuration reports
- Customizable output path
- Automatic report opening option
- Domain and LocalMachine report modes
- Configure MDI sensor proxy settings
- Support for authenticated proxies
- Get current proxy configuration
- Clear proxy settings
- Test sensor API connectivity
- Create DSA accounts
- Test DSA permissions and delegations
- View current MDI configuration
- Operating System: Windows 10/11 or Windows Server 2016+
- PowerShell: Version 5.1 or later
- Module: DefenderForIdentity PowerShell module
- Permissions: Administrator rights required for most operations
Open PowerShell as Administrator and run:
Install-Module -Name DefenderForIdentity -ForceClone this repository or download the MDI-configurator.ps1
Ensure your PowerShell execution policy allows script execution:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser.\MDI-configurator.ps1- The script will automatically check if the DefenderForIdentity module is installed
- If not found, it will prompt you with installation instructions
- After installing the module, restart the application
- Select your deployment mode (Domain or LocalMachine)
- Check the configuration items you want to apply & Choose if you want to use GPOprefix or GPOlinking
- Click Apply Configuration
- Monitor the output in the result pane
- Choose the test mode (Domain or LocalMachine)
- Select which configuration to test & Choose if you want to use GPOprefix or GPOlinking
- Click Run Test
- Review test results in the output pane
- Specify the output path (default:
C:\Temp) - Select report mode
- Optionally enable automatic report opening
- Click Generate Report
- Enter proxy URL (e.g.,
http://proxy.contoso.com:8080) - Optionally provide proxy credentials
- Use the buttons to:
- Set Proxy - Apply proxy configuration
- Get Proxy - View current settings
- Clear Proxy - Remove proxy configuration
- Test Sensor API Connection - Verify connectivity
- Enter DSA username and password
- Click Create gMSA to create the account
- Use Test gMSA to validate permissions
- Click Get MDI Configuration to view current settings
- Credentials: Passwords are handled using PowerShell's
SecureStringfor secure credential management - Permissions: Most operations require Domain Admin or equivalent privileges
- Logging: All command outputs are displayed in the GUI for transparency
- Best Practice: Run on a secure administrative workstation
Contributions are welcome!
- Microsoft Defender for Identity team for the PowerShell module
- The PowerShell community for WPF examples and best practices
For issues, questions, or suggestions, please open an issue on GitHub.
- Initial release
- Full GUI implementation for MDI PowerShell module
- Support for all major MDI configuration operations
- Comprehensive testing and reporting capabilities
- Proxy and DSA management features
Note: This tool is a community-developed GUI wrapper and is not officially supported by Microsoft. Always test in a non-production environment first.