Add w3wp to Defender exclusions, remove code to avoid duplication w3w…#2452
Merged
Conversation
dpaulson45
approved these changes
Oct 17, 2025
Member
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
dpaulson45
approved these changes
Oct 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add w3wp to Defender exclusions, remove code to avoid duplication w3wp in Test script
Issue:
Defender injects his modules to w3wp. This is not supported per https://learn.microsoft.com/en-us/troubleshoot/exchange/administration/avoid-unsupported-integration-methods This will nor prevent AMSI module(s) to be
Reason:
Load Defender's AMSI module in supported way.
Fix:
Add w3wp to processes exclusions list
Validation:
manual add to script in lab