- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2025 07:57 AM
First post on the community (yay!) so hopefully I don't mangle this and apologies if I'm missing key info.
I'm in the process of setting up Integration Hub on our development instance and I am encountering an issue specifically with the mailbox management actions, namely "Create/Delete/Enable/Lookup Mailbox". These actions are the ones which run via PowerShell on the MID server and hence my understanding is, don't rely on API permissions and the OAuth authentication via the client secret.
The current standpoint is:
- We're on Washington - moving to Xanadu in the coming month
- Exchange setup is hybrid
- MFA is enforced on our admin accounts and the account I'm using currently to test the setup in DEV is my own Exchange Admin role assigned account
- App registration is created in Azure and setup - we can run other non-mailbox actions without issue
- MID server has Exchange Online PowerShell module installed and is working
- I can log into the PowerShell module successfully if I RDP to the MID server and log in using my Exchange Online admin credentials (exactly the same as what we have in ServiceNow credential records)
The issue we face is that when attempting to run "Lookup Mailbox" for example, the below failure occurs.
I really want to get this working so I can look at writing custom actions for distribution list management - if anyone has any pointers of that one too that would be appreciated.
I'm currently working with our Microsoft admins to create a new cloud-only (we're hybrid on-prem AD/Entra) Exchange Admin account which is excluded from MFA, just in case ServiceNow cannot handle the MFA request when authenticating to the PowerShell module.
In the mean time, if anyone has any suggestions on what might be preventing successful execution of actions, that would be appreciated. If the standalone service account works, I'll reply here and people will benefit from my head-banging.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 05:58 AM
We managed to solve this one - the fault was with our version of the Exchange Online Management powershell module on our MID servers.
Downgrading from 3.7.1 to 3.6.0 of the module resolved this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2025 07:11 AM
Hi Richard,
Good day.
I'm also working on SN - Exchange Server integration and I'm facing a different issue. I'm using mailbox email id as user_name input parameters for "Look up mailbox" action and getting invalid parameters error.
Could please help me to understand the valid input parameters format?
Eg: For OOB Look up mail box action, we can provide two inputs, user_name & parameters.
I couldn't find any docs which explains the input parameter formats.
Thanks,
Siva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 05:57 AM
I'm afraid I'm not able to advise specifically on this one - but for me, 'Look Up Mailbox' action returns all mailboxes in our Exchange Online. Are you definitely using the Exchange Online spoke, rather than the Exchange Spoke (as in On-Prem?)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 08:34 AM
We are using Exchange Server spoke. The issue has been fixed by providing local admin role to the service account.
Thanks for your response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 05:58 AM
We managed to solve this one - the fault was with our version of the Exchange Online Management powershell module on our MID servers.
Downgrading from 3.7.1 to 3.6.0 of the module resolved this.