web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Analyze Document for ...
Power Automate
Suggested Answer

Analyze Document for Prebuilt or Custom models (v4.x API) Error

(1) ShareShare
ReportReport
Posted on by
I have followed all of the troubleshooting from Copilot, and I still cannot get around this error.
 
Deleted and added back the connection, pasting key and endpoint to notepad to ensure not special characters.  Not sure what I am missing.  According to Copilot if I am using the API key it should not be a permision issue.
 
Http request failed as there is an error: 'Request headers must contain only ASCII characters.'.
I have the same question (0)
  • Suggested answer
    RaghavMishra Profile Picture
    216 on at

    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)

    Why this usually does the trick

    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

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 462

#2
Vish WR Profile Picture

Vish WR 256

#3
David_MA Profile Picture

David_MA 242 Super User 2026 Season 1

Last 30 days Overall leaderboard