feat(m365): add exchange_organization_delicensing_resiliency_enabled security check

[HugoPBrito]

Context

Without Delicensing Resiliency, removing or reassigning an Exchange Online license causes immediate mailbox inaccessibility, leading to potential data loss and business disruption during routine organizational changes such as role transitions or license optimizations. This misconfiguration is particularly risky during large-scale license migrations where administrators need time to manage transitions without losing access to critical mailbox data.

Description

This check evaluates whether Delayed Delicensing is enabled in the Exchange Online organization configuration. It examines the delayed_delicensing_enabled property on the organization config and reports a PASS when the setting is enabled (providing a grace period for license removals) or a FAIL when disabled (meaning mailboxes immediately lose access upon license removal). Remediation involves running Set-OrganizationConfig -DelayedDelicensingEnabled $true via Exchange Online PowerShell.

Steps to review

1. Review the check implementation at prowler/providers/m365/services/exchange/exchange_organization_delicensing_resiliency_enabled/
2. Review the metadata file for correct severity, remediation, and compliance mappings
3. Review compliance framework mappings in prowler/compliance/m365/ to ensure the check is correctly mapped to relevant requirements
4. Run the check tests: poetry run pytest tests/providers/m365/services/exchange/exchange_organization_delicensing_resiliency_enabled/ -v
5. Run the check against a real environment (if possible):

   prowler m365 --check exchange_organization_delicensing_resiliency_enabled

Checklist

Community Checklist

• This feature/issue is listed in here or roadmap.prowler.com
• Is it assigned to me, if not, request it via the issue/feature in here or Prowler Community Slack

• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md
• Ensure new entries are added to CHANGELOG.md, if applicable.

SDK/CLI

• Are there new checks included in this PR? Yes
  • If so, do we need to update permissions for the provider? Please review this carefully.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

Compliance Mapping Review

This PR adds new checks. Please verify that they have been mapped to the relevant compliance framework requirements.

New checks already mapped in this PR

• exchange_organization_delicensing_resiliency_enabled (m365): iso27001_2022_m365

Use the no-compliance-check label to skip this check.

[codecov]

Codecov Report

❌ Patch coverage is 77.38095% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 88.04%. Comparing base (bc3fd79) to head (00e33ad).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #10608      +/-   ##
==========================================
- Coverage   88.07%   88.04%   -0.04%     
==========================================
  Files         125      127       +2     
  Lines        5251     5335      +84     
==========================================
+ Hits         4625     4697      +72     
- Misses        626      638      +12     

Flag	Coverage Δ
prowler-py3.10-m365	88.02% <77.38%> (-0.06%)	⬇️
prowler-py3.11-m365	87.91% <77.38%> (-0.17%)	⬇️
prowler-py3.12-m365	88.00% <77.38%> (-0.08%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
prowler	88.04% <77.38%> (-0.04%)	⬇️
api	∅ <ø> (∅)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

🔒 Container Security Scan

Image: prowler:cd4bd4d
Last scan: 2026-04-14 11:35:36 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	4
Total	4

4 package(s) affected

⚠️ Action Required

Critical severity vulnerabilities detected. These should be addressed before merging:

• Review the detailed scan results
• Update affected packages to patched versions
• Consider using a different base image if updates are unavailable

---

📋 Resources:

• Download full report (see artifacts)
• View in Security tab
• Scanned with Trivy