Multiple Microsoft 365 Graph Email APIs

Technical assistance
1
  1. What is your original issue/pain point you want to solve?

We are doing support for different schools and all the schools have their own M365 Tenants. So every school has their own, support, facilities, secretary etc. and so we need to be able to connect to multiple Mailaccounts from different tenants.

  1. Which are one or two concrete situations where this problem hurts the most?

well, the current situation makes it impossible to use Zammad for multiple M365 Tenants, eg multiple customers.

  1. What is your expectation/what do you want to achieve?

we just need to be able to add multiple M365 Graph Email APIs. We need to add at least three different tenants.

I think this change can’t be to complicated and would make our live much easier.

2

But the App you use could support multi tenant as long as the individual tennant allows that…?

I don’t see the issue right now to be honest.

3

I really can’t see how this should work. I mean I can allow accounts of tenant B to authenticate through the app on tenant A, but the app on tenant A only has access to the mailboxes in tenant A and not to the mailboxes on tenant B. I would need the same app with identical app ids and secrets on both tenants, which isn’t really possible or advisable.
What am I overlooking?

4

I changed this threads category to “technical assistance”, because this is what this clearly is.
The documentation tells you about the different scenarios, and if you’d use “help me choose” during the app registration, it might get even clearer. Here’s a screenshot of the current UI:

image
image1556×626 114 KB

You can allow the app to be available to any Microsoft account or general several (or specific) tennants, depending on what you’re trying to achieve. It is crucial to stay consistent in wording.

You can use the same app on different Zammad instances with different secrets.
You can use a Microsoft 365 App, allowing several tenants (or all Microsoft 365 accounts), to login to Zammad or even hook up Microsoft 365 based email channels to a Zammad instance.

If the different Microsoft tenants do not allow that, then you’ll have to adjust the security configuration of the tenant to allow / trust that specific app.

This is not a Zammad issue, but a Microsoft matter.

5

thanks I got it running. I still would prefer multiple m365 api connections, but it works for now.