This article explains how eADM handles email address and mailbox provisioning in environments using on-premises Microsoft Exchange, and what is required when the Exchange server configuration changes.
How eADM provisions email addresses
eADM can automatically set a user's primary email address (primary SMTP) and User Principal Name (UPN) when a new user account is created, based on rules configured in the synchronisation template. These values are written to the user object in Active Directory.
In hybrid Exchange environments (on-premises Exchange + Microsoft 365), eADM can invoke a PowerShell script — typically Enable-RemoteMailbox.ps1 — to create a remote mailbox object in the on-premises Exchange organisation. This links the AD user object to the Exchange mailbox in Microsoft 365 and ensures correct mail routing.
Note: eADM does not manage Exchange directly. The integration works by writing the correct attributes to AD and, where configured, executing a PowerShell script against the on-premises Exchange server. The script connects to the Exchange server via the $exchange variable, which holds the Exchange server hostname or FQDN.
What changes when you replace an Exchange server
When an organisation replaces or upgrades its on-premises Exchange server, the hostname or FQDN of the new server must be updated in the PowerShell script used by eADM. In most standard configurations, this is the $exchange variable at the top of Enable-RemoteMailbox.ps1.
Depending on how the script was originally set up for your organisation, there may be additional connection parameters to review:
-
$exchange— the Exchange server hostname or FQDN -
Service account credentials used to connect to Exchange (if not using the current Windows session)
-
Any explicit URI or connection string in
New-PSSessionorConnect-ExchangeServer
Warning: Do not update the script in the production environment without first verifying the connection in your test environment. A misconfigured Exchange endpoint will cause mailbox provisioning to fail silently for new users until the issue is corrected.
How to update the Exchange server reference
-
Locate the
Enable-RemoteMailbox.ps1script in your eADM synchronisation configuration. -
Update the
$exchangevariable to the hostname or FQDN of the new Exchange server. -
Review any additional connection parameters (see list above).
-
Test the updated script manually against the new server before saving it to the production configuration.
-
Run a test provisioning in eADM to confirm that the remote mailbox is created correctly.
-
Contact Identum support if the script requires changes beyond the
$exchangevariable, or if you are unsure of the current script configuration.
Note: If you are not certain which variables are set in your organisation's script, contact Identum support. We can review the current configuration and confirm exactly what needs to change.
Scope of Identum support for Exchange changes
Identum can assist with the following when an Exchange server changes:
-
Reviewing and updating the
$exchangevariable and related parameters in the eADM provisioning script -
Testing the updated configuration in a sandbox environment
-
Verifying that new user accounts are provisioned correctly after the change
Identum does not manage, configure, or troubleshoot the Exchange server itself. Infrastructure changes to Exchange — including installation, migration, and certificate management — are the responsibility of the organisation's IT department or their Exchange administrator.
Related articles
This article describes how eADM handles email address and mailbox provisioning in hybrid Exchange environments, and what system administrators must do when an on-premises Exchange server is replaced or reconfigured. It covers the role of the Enable-RemoteMailbox.ps1 script, the $exchange variable, and the scope of Identum's support for Exchange-related changes. The intended audience is IT administrators at Identum's municipal customers.