Hopefully my final edit... @PeteFromDenver alerted us that Microsoft has added a "Mailbox Address" field to Outlook actions. You can enter the address of the shared mailbox in this field to get back to original functionality. I'm keeping all previous solution details below just in case.
I've accepted the solution provided by @Anonymous on page 3. As a note for future users running into this issue, this solution requires a premium account. This will not be the best solution for a number of users (myself included), but it's the Microsoft-supported fix and (hopefully) the least likely to fail in the future.
For more information on the Graph API solution, check the posts by @jonathanford on pages 5 and 6.
If you do not have a premium account, the solution on page 3 offered by @Mindaugas is your best bet. You will need to add a new connection to Flow for the shared mailbox and then select that account as the connection for your Flow step. @RHCC gives more details on page 4 - you will also most likely need to add a password to the shared mailbox which is not intuitive.
This is by far the easiest solution, but I'm concerned how long it will work before Microsoft breaks functionality in an update. They do not support shared mailbox connections in Flows that don't specifically use that language, which is a frustrating response given how many users were relying on these Flows for their daily business.
Original post below:
Hi all - I'm having an issue with a couple Flows that were previously working without error.
When a new email arrives in a shared mailbox runs in a separate Flow and creates a SharePoint list item. One of the attributes added is the id of the trigger email (MessageId from the triggerBody).
I have two other Flows that will reply to this initial email using Reply to email. The stored MessageId is used to reply to the correct email. This has been working for 4+ months without error, but started failing today with the error shown in the Subject (Item Id doesn't belong to the current mailbox).
Myself and one other user are not having this failure. I had a user who was experiencing the failure check their connections in Flow and all apps were still connected. I also had them check their access to the shared inbox in Outlook and they still had full access.
Has anyone run into something similar or have any suggestions? It seems like it must be a user connection to the shared inbox but I'm not sure what else to look into. Thanks!
**Editing to note that the Get email step is also failing when referencing the ID of an email in a shared mailbox.
Solved! Go to Solution.
I found a "solution". Which is actually just doing what Microsoft is advising us to do: Use the Graph API.
First step is to use the HTTP with Azure AD connector: Invoke an HTTP request:
Then you have to create a new connection. In the documentation, Microsoft specifies that we must use "https://graph.microsoft.com/" as both the Base Resource URL and the Azure Resource URI:
Then simply click on "Sign In", and use your personal credentials.
Now you can simply refer to the Outlook REST API documentation (or the rest of Microsoft Graph).
Example on how to flag an e-mail:
Remember to change the shared mailbox in the URL: ENTERSHAREDMAILBOX@HERE.COM should of course be replaced with the shared mailbox that you are working with.
My premier support tech just sent me the following message
I just wanted to provide you an update that after passing the feedback to the Product team that multiple users complained about existing functionality breaking,
The Product team has deployed a fix for this where an optional parameter is added to the outlook actions to specify the shared mailbox address.
This should provide the support and users should not see the error that they were seeing earlier.
Can you try removing the connection and adding it back? If the connection has any hickups, it will be corrected. Also, any changes to the a/c to the shared inbox will be refreshed.
Please let us know if this helps you.
@rsaikrishna Thank you for the suggestion - I've had that solve issues in the past before. No such luck though, the Flow is still failing with the same error message.
I am having the same issue. I my flow is create an item in SharePoint from a shared mailbox, then delete the email. The error is "Item Id doesn't belong to the current mailbox."
I'm having the same issue as well. My flow have been running for +2 months without any issues, now all are failing with the error:
"Item Id doesn't belong to the current mailbox.", when I am trying to "Flag E-mail"
Th same issue "Item Id doesn't belong to the current mailbox. on "Get Attachments" , did not any chnage and worked for 3 month
@Stewartjohn100 Is the When a new email arrives in a shared mailbox trigger failing for you? Or a later flow that references the ID of the email in the shared mailbox? I haven't had any failures on the trigger so far.
@EmilBSP Thank you for submitting the ticket. Hopefully that will get some attention on this error.
I'm also seeing the issue.
The trigger works but when trying to save the attachment in the mail I get the error:
My flow starts with "When a new email arrives in a shared mailbox" and then does some interim steps to capture data from the email and output it to a SharePoint. The final step in the flow is to Mark the email as 'Read' (Mark as read or unread (V2)) - It's this final step that is failing - the error details are "Item Id doesn't belong to the current mailbox."
It appears that the problem lies with the Action Get Email (V2)
If I create a basic flow using the trigger "When a new email arrives in a shared mailbox (v2)"
and use the action "Send a mail from a shared mailbox" to forward to my own mailbox - it works.
But if I try to do anything else with the email (copy the attachments via sftp in this case) using "Get email (v2)" I get the error - This only started happening today and the flow has been running for a long time.
I've started having the same error "Itme Id doesn't belong to current mailbox" since yesterday evening. This was working fine for a long time.
I am having the same issue this morning. I have 2 separate flows that get emails from 2 different Shared Inboxes and Create the email in a SharePoint list. Both are giving the error message below on the Get Email step. This has been working for almost 2 years without issue and just started last night. Need this fixed ASAP as it is holding up Business Critical operations.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Did you know that you could restore a deleted flow? Check out this helpful article.
Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.