Invalid auth token reported as firewall issue

Sometimes user will see the following error:

But the underlying exception is:
"Microsoft.Azure.Documents.DocumentClientException: The authorization token is not valid at the current time. Please create another token and retryMicrosoft.Azure.Documents.DocumentClientException: The authorization token is not valid at the current time. Please create another token and retry"

Currently any permission error is bucketed as a firewall issue. In this case, the user to spend time trying to "fix" their firewall or ask CSS why firewall isn't working. The exception should be caught separately.

No file or test is named. Locate the error-handling path that buckets permission errors as firewall issues, then inspect how the invalid authorization-token exception is surfaced. Done means this exception is reported separately from firewall errors and the existing behavior remains covered by verification.

Written by the indexing model from the issue text.