-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EXOAtpPolicyForO365] Using BlockUrls is giving a deprecated error #2204
Comments
Since we already have an EXOSafeLinksPolicy resource that uses this cmdlet, would the appropriate fix not be to remove these parameters from the EXOAtpPolicyForO365 resource altogether instead? |
Didn't think of that one :-) Agree that for this resource, we should remove the property, but: I did some further digging and unfortunately this Safe Links Policy resource is unable to configure the Tenant Allow/Block List. This (article)[https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/set-up-safe-links-policies?view=o365-worldwide#use-powershell-to-create-safe-links-policies] says:
We might need to create a new Defender resource that is able to manage these settings using these cmdlets: |
Will be removing BlockedURLs alongside other deprecated parameters and will be included in breaking change release 1.22.1005.1. Defender resources will be addressed separately at a later time. |
Details of the scenario you tried and the problem that is occurring
When using the BlockUrls parameter of the EXOAtpPolicyForO365 resource, I am getting the below error. These blocked urls are now being managed via the Tenant Allow/Block List in [Microsoft Defender)[https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/manage-tenant-allow-block-list?view=o365-worldwide].
This line is giving the error:
Microsoft365DSC/Modules/Microsoft365DSC/DSCResources/MSFT_EXOAtpPolicyForO365/MSFT_EXOAtpPolicyForO365.psm1
Line 289 in d3bbe62
Verbose logs showing the problem
Suggested solution to the issue
Use the Microsoft Defender cmdlets to create these Blocked URL lists:
https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/set-up-safe-links-policies?view=o365-worldwide#use-powershell-to-create-safe-links-policies
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
dev
The text was updated successfully, but these errors were encountered: