Exchange | EWSMailbox DC XML Configs baked in DC

What is a one sentence summary of your feature request?

The Exchange solution set has the EWSMailbox data collector that can be modified, via job xml ,to ensure connectivity is reaching a valid endpoint.

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

The Exchange jobs utilizing the EWSMailbox data collector often fail (assuming all other prereqs are met) because autodiscover is failing to find a valid endpoint. This requires end users to modify the Job’s XML to properly reach out to the tenant and successfully collect data. A nice improvement is to have these configurations baked into the EWS data collector to prevent delays with implementation and support.

How do you currently solve the challenges you have by not having this feature?

End users are required to configure the job xml for any jobs utilizing the EWSMailbox DC and manually test 3 of the possible configurations for a successful scan.