EXOHostedOutboundSpamFilterRule: Cannot remove policy if associated HostedOutboundSpamFilterPolicy is not present

[ricmestre]

Description of the issue

This is similar to the issue as reported on #4846, the rule cannot be removed if the associated policy is not present anymore and the fix will be similar as well.

Microsoft 365 DSC Version

1.24.703.1

Which workloads are affected

Exchange Online

The DSC configuration

EXOHostedOutboundSpamFilterRule "EXOHostedOutboundSpamFilterRule-EXOHostedOutboundSpamFilterRule_1"
        {
            ApplicationId         = $EXOApplicationId;
            CertificateThumbprint = $EXOCertThumbprint;
            Ensure                = "Absent";
            Identity              = "EXOHostedOutboundSpamFilterRule_1";
            TenantId              = $OrganizationName;
        }

Verbose logs showing the problem

PowerShell DSC resource MSFT_EXOHostedOutboundSpamFilterRule  failed to execute Set-TargetResource functionality with error message: Error attempting to create EXOHostedOutboundSpamFilterRule {EXOHostedOutboundSpamFilterRule_1}. The specified HostedOutboundSpamFilterPolicy {EXOHostedOutboundSpamFilterPolicy_1} doesn't exist. Make sure you either create it first or specify a valid policy.

Environment Information + PowerShell Version

Win11 / PS5.1