-
Notifications
You must be signed in to change notification settings - Fork 532
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
Fix autofromconnector type for Intune EDR Windows10 policy #5254
Fix autofromconnector type for Intune EDR Windows10 policy #5254
Conversation
Sure, let me have a look and I'll let you know. |
No, unfortunately it still fails with: "device_vendor_msft_windowsadvancedthreatprotection_configurationtype: Selected option device_vendor_msft_windowsadvancedthreatprotection_configurationtype_autofromconnector with dependent settings doesnt contain required dependent settings. Required dependent settings are device_vendor_msft_windowsadvancedthreatprotection_onboarding_fromconnector" |
Thank you for the feedback, definitely missed the correct property name. Can you try with the latest change? I hope that works now. |
It sure does 🚀! Bad news is that now I can't test this resource in my dev tenant since the Defender connector can't be setup, oh well life... Please just don't forget to change the the throw exception you added, use $ConfigurationType instead of $DSCParams.ConfigurationType |
Silly me, always forgetting stuff you just mentioned a minute ago... Added it 👍 |
Pull Request (PR) description
This PR aims to address an issue with the
AutoFromConnector
value for theConfigurationPackageType
in theIntuneEndpointDetectionAndResponsePolicyWindows10
resource. It throws an error for the empty configuration blob, although that blob must be empty because it will be populated by the Graph endpoint.This Pull Request (PR) fixes the following issues