You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MDE extension deployment is returning the error below. I tried the deployment using Azure DevOps first and then did the manual ARM deployment through Azure Portal.
Status Message: VM has reported a failure when processing extension 'MDE.Windows'. Error message: "Failed to configure Microsoft Defender for Endpoint: Protected Setting defenderForEndpointOnboardingScript does not exist, please use mdeOnboardings API to retreive it (https://docs.microsoft.com/en-us/rest/api/securitycenter)"
The text was updated successfully, but these errors were encountered:
Hopefully, someone can look into this issue soon. Here are some additional troubleshooting details that I did.
When I looked at one of the older VMs that we have I saw the following files for the Extension:
In this case, the extension was provisioned successfully and we didn’t see any issues.
Here is a screenshot from a new VM where the extension is failing:
You can see that WindowsDefenderATPOnboardingScript file is missing, which is exactly what the error message is complaining about:
MDE extension deployment is returning the error below. I tried the deployment using Azure DevOps first and then did the manual ARM deployment through Azure Portal.
Status Message: VM has reported a failure when processing extension 'MDE.Windows'. Error message: "Failed to configure Microsoft Defender for Endpoint: Protected Setting defenderForEndpointOnboardingScript does not exist, please use mdeOnboardings API to retreive it (https://docs.microsoft.com/en-us/rest/api/securitycenter)"
The text was updated successfully, but these errors were encountered: