Pronestor Planner can be integrated with your Exchange environment so that your meetings are synchronized. This is done with a service account that has the right application impersonation in Exchange.
We don't directly support this, as it is done in Exchange and not in Pronestor, but we have gathered some knowledge and frequently asked questions to help you set it up, as well as some links to guides on the internet.
If you want to know more about how Pronestor Planner and Exchange works and why the service account needs application impersonation rights, please see this guide instead: https://helpdesk.pronestor.com/hc/en-us/articles/360028374592-Application-impersonation-rights-in-exchange-for-Pronestor-
Table of contents
- What does the service account need?
- How to check whether the service account has the correct access
- Microsofts Guides
- Our bare bones guide for office 365
- Third party guides
- Administrative rights in your Exchange
What does the service account need?
For Pronestor Planner, the service account needs to have application impersonation rights on all users and all meeting rooms connected to Pronestor Planner.
The Exchange service account must have a mailbox and the primary email address for that account must be the original one and not an alias.
If you want, you can limit the scope of the account to just the users using Pronestor Planner and just the meeting rooms you have imported. For instance, if your active directory contains users for your entire organization, but you only use Pronestor on one location. We don't recommend it, as you risk a lot of meetings on your fallback user in Pronestor Planner.
How to check whether the service account has the correct access
You can check whether the service account has the correct access by running a script in PowerShell. This has to be done on your Exchange server.
Get-ManagementRoleAssignment -roleassignee "firstname.lastname@example.org" -role applicationimpersonation
The results of the script. The "email@example.com" has the application impersonation rights. The "UserWithoutRights@pronestor.com" is a regular employee without application impersonation rights. If your account has application impersonation, the response of the script will show you the role applicationimpersonation.
New-ManagementRoleAssignment -Name PronestorServiceGroup -Role applicationImpersonation -User firstname.lastname@example.org
Our bare bones guide for Office 365
- Go to web portal - with administrator permissions
- Create a new user (ex. "service")
- Go to Exchange Admin Center
- Choose Permissions in left menu
- Choose "Admin Roles"
- Create a new "Role Group"
- Name : Pronestor Service Group
- Roles : add "ApplicationImpersonation"
- Members : add the "service"-user from above
Third party guides
Here are some very helpful third party guides we found. Please note that Pronestor is not responsible for the content of these guides.