Exception of type 'Microsoft.Fast.Profile.Core.Exception.ProfileBadRequestException' was thrown

Matt Perry 80

We've had a flow running in production for about a month now that updates associate images using the Graph. This week we are seeing issues where the Base64 image is throwing an error. Permissions haven't changed. We tried going directly through Graph Explorer but seeing the same error. I've validated that the image string is good using an online tool.

"code": "InvalidImage",
    "message": "Exception of type 'Microsoft.Fast.Profile.Core.Exception.ProfileBadRequestException' was thrown."

Besir Suleyman Öz 15 Reputation points

2024-05-08T14:05:34.6266667+00:00

We are running into the same error. Would be nice to get a help!
Phinehas Bynum 85 Reputation points

2024-05-08T15:59:18.31+00:00

We are also running into the same error -- the same thing is happening where we made no changes to our flow but it is now erroring out. Has the API endpoint changed?
Matt Perry 80 Reputation points

2024-05-08T17:15:47.0133333+00:00

I have a ticket in with MS. Hope to get this resolved soon.
Ted Sager 10 Reputation points

2024-05-15T12:55:51.7833333+00:00

Any luck with that ticket? Seeing the same behavior.
Matt Perry 80 Reputation points

2024-05-16T17:07:05.93+00:00

@Ted Sager They escalated to the Product Group team but didn't give me a timeline as to when to expect a resolution. They did say though that it wouldn't be fast.

I've seen issues on the PowerShell side updating profile pictures as well.
Chip Valentine 0 Reputation points

2024-05-20T14:46:13.9+00:00

We are also having this issue, flow mysteriously broke relating to updating images.
Ivan Kulušić EXTERNAL 0 Reputation points

2024-07-04T07:41:02.9866667+00:00

Same issue here. Do you guys have any workaround? From Postman, update photo api works with binary body type, but I can't make it work from logic app. Always getting this same error. Currently only option that I see could work for us is different technology, probably PowerShell.
Matt Perry 80 Reputation points

2024-07-05T14:53:06.2566667+00:00

I think the best workaround right now is to utilize Invoke-MgGraphRequest. https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.authentication/invoke-mggraphrequest?view=graph-powershell-1.0. I utilize Azure Function App to run this.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Accepted answer

Phinehas Bynum 85 Reputation points

2024-07-17T19:22:42.7466667+00:00

This has been a big pain for us, but we found a fix! If you don't base64 encode the image contents, you can use a content header of image/jpeg and a raw body of the image content and it works as it did before. In the past, we had to base64 encode the body. Thanks for the idea to try in Postman @Ivan, this is how we discovered the change. Fingers crossed that it doesn't break again. For those at Microsoft, pretty please document future changes to the Graph API 🫠!
Please sign in to rate this answer.

1 person found this answer helpful.
Ivan Kulušić EXTERNAL 0 Reputation points

2024-07-26T08:57:18.6+00:00

Great, thank you @Phinehas, it works for me as well. Logic apps function base64toBinary(<base64 encoded results from get blob api>) solved the issue here.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

2 additional answers

Admin - Carsten Isak Nielsen 0 Reputation points

2024-06-04T07:23:14.7333333+00:00

Yes another old issue that Microsoft is not going to fix, its been over a year since this occurred first time and its still there so would not hold my breath.

See comments here from a year ago https://www.youtube.com/watch?v=GxY0RV5iGAY
Please sign in to rate this answer.
Chip Valentine 0 Reputation points

2024-06-04T14:30:48.4933333+00:00

This error started occurring for us after the latest MSFT graph update that seems to coincide with when this post was created.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

Exception of type 'Microsoft.Fast.Profile.Core.Exception.ProfileBadRequestException' was thrown

2 additional answers

Your answer