Simple PowerShell GUI for Microsoft Defender for Endpoint API machine actions.
- Create Azure AD application as described here: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/apis-intro?view=o365-worldwide
- Grant the following API permissions to the application:
| Permission | Description |
|---|---|
| AdvancedQuery.Read.All | Run advanced queries |
| Machine.Isolate | Isolate machine |
| Machine.ReadWrite.All | Read and write all machine information (used for tagging) |
| Machine.Scan | Scan machine |
- Create application secret.
- Connect with AAD Tenant ID, Application Id and Application Secret of the application created earlier.
- Get Devices that you want to perform actions on, using one of the following methods:
- Advanced Hunting query (query result should contain DeviceName and DeviceId fields)
- CSV file (single Name column with machine FQDNs)
- Devices list separated with commas
- Confirm selection in PowerShell forms pop-up.
- Choose action that you want to perform on Selected Devices, the following actions are currently available:
- Specify device tag in text box and Apply tag.
- Run AV Scan.
- Isolate/Release device.
- Verify actions result with Logs text box.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.