[Feature Request]: Automatically provision Microsoft Defender for Business & onboard devices to Microsoft Defender using Microsoft Intune

[bdmcti]

Please confirm:

• I have searched existing feature requests (open and closed) and found no duplicates.
• **me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

These deployment tasks already exist in default baselines for M365 Lighthouse and would be great to include in CIPP Baseline Standards. Copying the task name and descriptions from Lighthouse:

1. Provision Microsoft Defender - This task will provision the tenant with Microsoft Defender for Business. Once provisioned, the tenant will be ready to onboard devices and use Microsoft Defender for Business capabilities. It may take a few minutes after provisioning is complete before Microsoft Defender for Business capabilities are ready for use.
2. Automatically onboard devices to Microsoft Defender using Microsoft Intune - This task sets up a connection between Microsoft Defender for Business and Microsoft Intune. All Intune-enrolled Windows devices will be automatically onboarded to Microsoft Defender for Business.

Benefits for MSPs

This will align CIPP with the same available tasks in 365 Lighthouse and automatically setup the provisioning and onboarding. These deployment tasks are requirements in order to setup Huntress Defender for Endpoint Integration

Value or Importance

• Will reduce dependence on 365 Lighthouse or manual setup natively from tenant
• Will improve cohesiveness of CIPP baseline standards
• Will automate pre-requisite work required for Defender for Endpoint Integration from our CIPP sponsor Huntress

PowerShell Commands (Optional)

No response

[github-actions]

Hello,

Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

[bdmcti]

Hello, we are a paying CIPP sponsor (CIPP-CTIGHMaster). 

[JohnDuprey]

Confirmed sponsorship