Do not count "will not implement" requirements in feature effort estimate

What is the challenge?

If a requirement is listed as "will not implement" the detailed estimate is still counted in the feature effort calculation

What is the impact?

Currently need to manually adjust requirements to 0, in ADO if we mark the user story as removed it takes it out of the feature estimate

Describe your idea

Do not cout "will not implement" requirements in feature effort estimate