Plantronics + Polycom. Now together as Poly Logo

OTD and Exchange on-prem - "Calendar access not permitted"

Valued Contributor

OTD and Exchange on-prem - "Calendar access not permitted"



Customer is trying to test OTD service. Integrated with Exchange on-prem, version 2016

Service account is created according to guide, integration between OTD and Exchange is done and OTD is showing that it is integrated.
Service account is set to have rights "Reviewer" to mailbox accounts. Device account is configured as Room Resource and has configuration done with Set-CalendarProcessing as needed.

Now, when trying to integrate Group Series device with OTD - it shows for some time error about wrong domain, username or password, then after some time device shows in OTD but with error "Calendar access not permitted".

OTD help is not very useful here, just saying "The service account used to integrate this calendar with One Touch Dial does not have permissions to access the calendar. Update the permissions of the service account used to integrate the calendar with the One Touch Dial application."

As I said, service account has Reviewer rights and that was double checked.


Now one interesting thing is - if they change that account to standard User, not Resource, then OTD is quickly showing that Calendar is connected. But still, no matter what configuration - Group is not showing any meeting notification, when Calendaring service is set to


Any suggestions?




Message 1 of 3

Re: OTD and Exchange on-prem - "Calendar access not permitted"

We have experienced exactly the same errors when using the otd.account, created as per the documentation provided as well as testing with the administrator and Exchange Admin accounts.

Any suggestions would be welcomed.


Many thanks

Message 2 of 3
Occasional Visitor

Re: OTD and Exchange on-prem - "Calendar access not permitted"

Hello fellow LKVer 


Did you find any solution for this problem? I'm facing exactly the same situation, except for the fact that we are using O365. I just have followed all commands and requirements "by the book", but error is still happening.


Any comments, pls!



Message 3 of 3