MHA not working - Access to ODATA is disabled about mha HOT 4 CLOSED

Stephen,
We found the solution. If you are doing EWS filtering as we are you need to include "Mozilla/*" in the list. I basically kicked off fiddler and attempted to use MHA and noticed that the user agent was "Mozilla/...". After adding that by performing the following powershell statement it all started working. Thanks for your help.

set-organizationconfig -ewsallowlist "Outlook-Android/*","Outlook-iOS/*","ExchangeServicesClient
/*","*outlook*","*MAPI*","*skype*","Microsoft+Office/*","UCCAPI/*","OC/*","OCPhone/*","Microsoft Office/*","MacOutlook/*","Mozilla/*"

from mha.

This might be the same issue as #38, which I now think was caused by moving the rest/ews calls into a frame. I'm working on pulling them back out and leaving the frames to just to rendering, which should fix #38, and then we'll see if it fixes this.

BTW - this didn't happen to be working at the start of the year did it?

from mha.

Good find - I'm reporting this to the devs - this is non-obvious...

from mha.

Hey - can you give me more details on the frame that failed for you? Perhaps send me the fiddle? You can DM me @ my twitter: https://twitter.com/sgriffin

from mha.