Answered

Shared Mailbox Trigger (V2) Trigger issues with Service Account

(0) Share

Report

Posted on by Neurobotic

Morning.
I have built a flow that triggers using the When a new email arrives in a shared mailbox (V2) trigger. However when I try and run it, I am receiving the following error.

Screenshot 2023-01-25 101124.png

Considerations are as follows:
1. The flow is being run from a Service Account (SA) with an E5 license within the non-default environment

2. The SA has been granted access permissions to the shared mailbox, and has send as/send on behalf of permissions (not that this is relevant to this issue)

3. I am using the SA connector with the trigger, as I do not have the direct access credentials for the shared mailbox account. But the SA has access to the mailbox, so this shouldn't be an issue.

4. I am aware of other users within our organisation who have experienced the same issue with this trigger when attempting to run it through a SA

Any insight on what the problem could be? The flow is literally failing at the trigger as shown in the screen grab above.

Thanks in advance for any help hivemind!

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (1)

Chriddle 8,443 Super User 2025 Season 2 on at

Like (0)

Report

Have you already tried selecting the inbox again in the trigger?

Was this reply helpful? Yes No
Neurobotic 12 on at

Like (0)

Report

I have yes.
Another thing that I found oddly suspicious is when setting up the trigger, having inputted the Original Mailbox Address, and then looking for the folder options, The drop down list was empty, not even showing the inbox, even though that is autopopulated within the trigger.

Was this reply helpful? Yes No
Verified answer

Neurobotic 12 on at

Like (0)

Report

Update: I have now solved this issue.
It turns out that the Mailbox User account had been disabled in the Active Directory, AND didn't have any licenses assigned to it.

It took a lot of digging, but I found the issue!
If you have this problem, make sure that the account is enabled AND that it has at least an F3 license assigned to it in order to process the flow actions.

Hope this helps anyone else who encounters this problem in future. 🙂

Was this reply helpful? Yes No