Stoped working after 2 years (401) Unauthorized.

[sve0901]

Worked fine for 2 years, but over the last weekend it just stopped working.

Reason: The request failed. The remote server returned an error: (401) Unauthorized.

I tried setting it up from scratch, but it’s still not working. Probably some updates on Microsoft’s end broke it.

[AngusWarren]

I've found the cause of this issue and have submitted a pull request. I've compiled an updated version for Windows here: https://github.com/AngusWarren/basicToOauth/releases/download/v1.0.4/basicToOauth.exe

[mmalcek]

Hello Angus, many thanks for identify the issue. I've merged your PR and I've also added some hardening around. v1.0.4 released

[hitunespt]

Does anyone still have (401) Unauthorized? It worked but now the error started again.

[mmalcek]

This time I'm afraid issue can be different I've just found by coincidence when setting up Synology NAS that MS is completly retyring Exchange web services :/ https://kb.synology.com/en-us/APM/tutorial/Troubleshooting_EWS_migration Unfortunately thistool is just "header replacer" fully depends on EWS and translating EWS to Graph is absolutely out of scope, likely not even possible. Check the Synology KB topic, you can buy some time, but it seems this is over... Nice that many companies just rewriten their flows to EWS, and now they can migrate again to Graph :D

[mmalcek]

I've added epitaph to README and quick guide how to buy some time but that's all I can do :/

[mmalcek]

I've added one more note to README. It's certainly not easy to rewrite and certainly not whole EWS, but if you don't have any other option and you can specify subset of EWS services that you need I'm open to discussion for custom development but on chargeable basis.