It is great that single tenant support is on its way in version 4.1. I think one more way to improve usability of the Microsoft 365 channels is to make the api endpoint + scopes configurable so that both graph- and outlook apis can be used.
We try to keep UI and settings as clean as possible.
Your suggested functionality would add quite some overhead and potentially even dangerous settings.
Dangerous as in people taking arrows in their knees.
Right now I can’t see a situation where our current scopes don’t work.
Maybe I just don’t see the scope possibly.
Nothing new that Microsoft keeps shooting young things down fast.
Im not saying that the scopes should be completely configurable. The only thing that is needed to be configurable is a switch between outlook.office.com and graph.microsoft.com in both API endpoint and scope domain. In above example everything is the same other than the desired microsoft API.
I would be surprised if such config parameter would have a major effect on the zammad source code.
The use case is that some Microsoft 365 tenants only use the graph API and have completely disabled the outlook API.