We have an SaaS solution that attaches to our Exchange service and extracts emails from various departmental mailboxes, from which it creates work items for our users. The connection is made using the username and password of the AD account associated with each mailbox (one account per mailbox) and works fine. Now, however, we are no longer allowed (by company policy) to allow the accounts associated with departmental mailboxes to have interactive logon privileges and so the new setup is:
- Department mailbox “department 1 emails” is owned by user
department1@company.com. - Service account
svc_Dept1_emails@company.comis created, granted logon privileges, and given delegate access to the “department 1 emails” mailbox. - User
svc_Dept1_emails@company.comis set up in the SaaS solution as the logon to use to connect to Exchange
The connection works, but it isn’t possible to specify in the SaaS solution which mailbox to look at – it just opens the specified user’s mailbox and look there, so the actual departmental mailbox is not being read.
We cannot change the SaaS solution to allow for configurable mailbox names – it works the way it works and that’s that. We also very probably cannot change the “no logon for mailbox accounts” policy (we are trying but without much hope). I don’t need to hear about how ill-advised the policy is, I need to work around it and I was therefore wondering the following:
Is it possible to configure an account in Exchange so that its default mailbox is not its own mailbox, but another mailbox to which it has delegated access? I don’t need to automap the other mailbox so it appears in the folder bar in Outlook, I need the other mailbox to “be” that service account’s mailbox to all intents and purposes.
If that is an achievable goal, please provide the details of exactly how to configure that setup in Exchange online.
