@sean I'm still experiencing the same issue.
After over a month of back and forth, Microsoft support finally came back and said "As per our engineering team, this issue was resolved.". Yet, I'm still seeing the same error.
And now they want a .HAR file generated by Chrome, which makes no sense. You can't making the API calls from Chrome due to CORS.
To reproduce the issue, I've provided CURL commands to generate the token and make an API call. What more do they need?