Connecting to a shared mailbox via Microsoft 365 Graph

  • Used Zammad version: 6.5.0
  • Used Zammad installation type: docker-compose
  • Operating system: Linux Ubuntu 24.04.1
  • Browser + version: Firefox 138.0.1

Expected behavior:

  • The M365 Graph connection allows a shared mailbox to be monitored for incoming emails

Actual behavior:

  • It appears that the email being monitored is the user that is used to authenticate, and there doesn’t appear to be an option to monitor any shared mailbox that that user has access (Full + send as) to.

Steps to reproduce the behavior:

  • Create your 365 Graph API connection
  • Connect
  • Send a test email to the shared mailbox
  • Send a test email to the user you used to connect to the shared mailbox with

Edited to add additional info:

My Zammad instance is running behind an nginx-proxy for SSL termination using a Self-Signed Certificate (we do not plan on having Zammad accessible outside of our LAN)

I have the same issue, it doesn’t matter if I select shared mailbox or which mailbox I fill in on the form it always adds just the user’s mailbox once the authentication is complete.

Hello. I did not think through this issue, but first thing what come to my head is:

  • use user mailbox for primary email (general group) (or do not use this email)
  • add shared mailbox with another email for any other group (group send from email).
    Add account - Account type “shared mailbox”, and so on.

I do not think, what MS “allows” user (Zammad app) to use shared (free) mailboxes without payment in form of payed user mailbox (speaking technically or pure in legal terms).
HTH.

Normally, you need only the correct mailbox during the “shared mailbox” setup, and the user who is used for authentication needs the delegated permission for this shared mailbox.

In our tests, this always works fine and no need for any payments for the shared mailbox.

We would need some more information, when there is really a problem on our side.

deleted 1234567801234567890

Can we please leave LLM responses out? I don’t think they’re helpful in this matter. Also, you seem to mix in the different alias parts from your other thread into this one which is, in my opinion, also not helpful in this situation.

This was resolved once I resolved the CSRF token validation issues, which I found the workflow from a different thread on. As soon as that was resolved, I was able to add the mailbox and have this work as expected - unfortunately I don’t know enough about the root issue to determine why that may be or if it was just coincidence.

Thank you