Exchange Requirements
Exchange Specific Requirements (on-premises)
- The Activate Orchestrator Account must be a member of the Exchange Organisational Management and Recipient Management Roles
- If creating Distribution Lists, then the Activate Orchestrator Account needs to be a member of the Security Group Creation and Membership Role in Exchange
- FQDN of the Exchange Server configured for remote PowerShell, due to session management requirements this must be a specific exchange server rather than a load balancer.
- The Exchange Server will have to be configured to allow the Activate Provisioning Server to run remote PowerShell commands
Exchange Online Specific Requirements
- Office 365 Tenant Username, Password or Application ID with Admin Privileges will be required depending on what Azure Services you are wanting to manage using Activate. It is strongly recommended to use a separate Account or App ID for each instance of Activate you install (Production, UAT) to avoid exceeding the maximum number of simultaneous PowerShell connections implemented by Azure.
- Refer to Azure/EntraID and Activate for more information on configuring Activate to integrate with Azure
Exchange 2013/2016/2019 on-premises
Windows Remote Management and PowerShell 3.0 must be installed on the Activate Server
The Activate Orchestrator AD Account must be a member of the Exchange Organizational Management and Recipient Management Roles
You may have to give permissions to the Activate Orchestrator Account to run remote PowerShell commands on your Exchange Servers – see Control remote PowerShell access to Exchange servers | Microsoft Learn
Please see the “Microsoft Exchange Server and Office 365 Support” article on the Activate Support Portal for more information about Activate and Microsoft Exchange. Microsoft Exchange Server and Office 365 Support
Office 365
You may need an Office 365 Tenant Username and Password or Application ID with Admin Privileges and Full Licensing for Exchange. It is recommended that there is one Account or App ID per Activate instance (Prod, UAT, Dev) to avoid exceeding the maximum number of simultaneous PowerShell connections enforced by Azure.
NOTE: Office 365 – The features are dependent on how the organisation has integrated with Office 365 and the licences they are entitled to.