Multiple Service Desk Queues - Do we need an Oauth Configuration for every Service Desk Queue?
Hello everybody,
After we switched to Exchange Online, the "ticket via Mail" function no longer works for 2 of our 3 Service Desk Queues.
I have created shared mailboxes for the corresponding queues and stored them in the mail settings for each queue in KACE.
For our main queue, I configured the Oauth configuration. The forwarding and creation of tickets by email works with the main queue. However, since the switch to Exchange Online, this no longer works for our other two queues.
Do I have to create an Oauth configuration for each queue or do you know why the forwarding via email for the other two service desk queues no longer works?
Thanks in advance and best regards
Olaf
Answers (2)
Anything on that matter ?
I'm facing the same configuration puzzle or issue where we want to have multiple Office 365 email queues (Shared mailbox a possibility if with a Basic licence attached to it or does it have to be a regular email absolutely? an old procedure stated it couldn't be a shared mailbox but without much more details) ... it seems to be one hell of a puzzle to do something that seems rather simple on paper!
The helps and documentation aren'T very clear or explicit on the multiple queue situation.
We'd love some help and feedback on the how to if it's doable!
Jo
I found the solution, yes you have to make separate Oauth for each. You can use the same AzureAD subscription with the same Application ID and Secret (if you noted it down, or create a new one) and when linking it all you have to log into office 365 with the shared email you configured that you when to associate to that queue/Oauth (it needs to be licenced and have a password set for login). When login back into Kace, you can use any admin user I think.
Configured 3 queues that way so far.