Issue Testing “Look up Mailbox” Action in Microsoft Exchange Online Spoke

[Mukul_Kolhe]

Hi everyone,

I’m currently setting up the Microsoft Exchange Online spoke integration on our ServiceNow instance and I’ve run into an issue I’m hoping someone here can help me with.

Here’s what I’ve done so far:
--> Configured OAuth credentials (client ID, tenant ID, secret) for Microsoft Graph.
--> Set up Windows credentials for mailbox actions.
--> Configured connection & credential aliases (Microsoft Exchange Online MID) and ensured they point to the correct MID Server and credentials.
--> MID Server is online and has the EXO V2 PowerShell module installed.

Now, I am trying to test the Look up Mailbox action directly from Flow Designer using the test option (providing just the User ID field, e.g., Adam.Edmondson@xyz.com).

However, I consistently receive the following error in logs:

Failed while executing ExchangeSpoke-GetMailbox.ps1
Invalid parameter

My Questions:

1. Has anyone successfully tested this action without building a full flow?
2. Are there additional parameters I should pass explicitly when using the test option in Flow Designer?
3. Any tips or best practices for testing Exchange Online spoke actions to make sure all necessary values are passed to the PowerShell scripts?

I’ve cross-checked the official integration docs, and everything looks correct on the configuration side, so I’m looking for community insights or similar experiences.

Any help or pointers would be greatly appreciated!

[Mukul_Kolhe]

Hi @J Siva 

Thank you for your response and the suggestion. I will check if it’s feasible to run the PowerShell script manually from the MID Server host to verify the connection with EXO.

Additionally, I had a quick follow-up:
While testing the "Look up Mailbox" action directly from Flow Designer (by just providing the User ID), I consistently receive the “Invalid parameter” error in the logs. I wanted to check:

• Are there any additional parameters that need to be passed explicitly to test this action outside of a complete flow?

• Is this the recommended way to test such spoke actions, or is there a better approach to ensure all required parameters are passed correctly to the PowerShell script?

Any guidance on this would really help clarify the proper testing strategy.

Thanks again for your support!

Best regards,
Mukul Kolhe