
Hey, I know this one is frustrating - the good news is that error message is actually pointing at your connection credentials, not anything wrong with your flow, so that narrows it down nicely.
You've already re-added the connection, so the thing I'd try next is regenerating the key. Open your Document Intelligence resource in the Azure portal, go to Keys and Endpoint under Resource Management, hit regenerate, then copy the fresh Endpoint and Key straight from the portal into a brand-new connection - ideally using the portal's copy button rather than routing it through notepad or another app. (Azure AI Document Intelligence connector)
One quick caveat - this next bit is general HTTP knowledge rather than something I found written up in Microsoft Learn for this specific action, so I'm flagging it as such. That "Request headers must contain only ASCII characters" wording basically means a non-ASCII character snuck into a value that gets sent as a request header - for this connector that's almost always the key (sometimes the endpoint). The usual culprits are invisible passengers on a copy-paste: a zero-width space, a "smart" curly quote, or a stray newline or trailing space. Even pasting into notepad doesn't always strip those, which is why copying fresh from the portal - or regenerating outright - tends to clear it.
If a regenerated, freshly copied key still throws the same error, I'd raise it as a support ticket at that point, since it'd be pointing at something past the normal setup.
Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!
Raghav Mishra - LinkedIn | PowerAI Labs