Getting hostedContents value from Teams channel message using Graph API

(1) Share

Report

Posted on by VilPel

287

Hello community,

I am trying to get the contents (images) of a Teams channel message in Power Apps / Power Automate. I have been following the documentation provided here: https://learn.microsoft.com/en-us/graph/api/chatmessagehostedcontent-get?view=graph-rest-1.0&tabs=http

Using the Graph Explorer to get the hosted contents works fine:

I am using the Teams HTTP connector in Power Automate. When I enter the same URL in there with the Content-Type as image/png (which is the actual content type), I get this error:

Everything works fine in Power Automate until I use the /$value parameter. What could be the mistake here and how do I fix it?

Error: Http request failed as the content was not valid: 'Unable to translate bytes [89] at index 0 from specified code page to Unicode.'.

Categories:

Using connectors

I have the same question (0)

All responses (5)

Answers (0)

Expiscornovus 33,189 Most Valuable Professional on at

Like (0)

Report

Have you tried the application/json Content-Type header instead in your Teams action to see if it returns the contentbytes and content type?

Was this reply helpful? Yes No
AP-06101159-0 2 on at

Like (0)

Report

I'm running in to the same issue, with Content-Type header set to json or image. Hope somebody has a solution.

Was this reply helpful? Yes No
Amardeep Raj 18 on at

Like (0)

Report
Hi

This is the permission issue you need to appropriate permission for this according to doc.
Get chatMessageHostedContent - Microsoft Graph v1.0 | Microsoft Learn

Graph API Permissions: Reading chat messages requires specific Graph API permissions.

Admin Consent Needed: The permission "ChannelMessage.Read.All" requires admin consent.

No Direct Access via Teams Connector: You cannot access hosted message content directly through the Teams HTTP connector.

Steps to Follow:

Register Application: Register your app in Azure Active Directory (AAD).

Grant Permissions: Assign the necessary permissions to your app.

Create Custom Connector: Set up a custom connector for authentication.

Access Endpoint: Use the endpoint directly through the custom connector.

If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

Was this reply helpful? Yes No
AB-06120138-0 2 on at

Like (0)

Report

were you able to make it work?

Was this reply helpful? Yes No
Suggested answer

gbb Microsoft Employee on at

Like (0)

Report

This should be fixed for allowed paths for the connector. Please try it again.

Was this reply helpful? Yes No