Omit NTLM handshake 401 responses from Application Insights Failures
So when requesting any resource that requires windows authentication (username, password, domain) from say a webjob running within an app service, the first 2 responses are 401 setting up the ntlm handshake (nonce, etc). These should not be considered failures. They're cluttering up the reporting with false negatives, as the 3rd part, the actual authenticated request, returns non-401.
Thanks for the feedback. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.