Item Id doesn't belong to the current mailbox

[EGreen]

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.

[jonathanford]

@frano72 

I had to google it myself. I’m going to try and throw a guide together tomorrow. But to your question...

Simply treat it as any other user:

https://graph.microsoft.com/v1.0/users/sharedaddress@microsoft.com/messages

Make sure you have the right permissions set (Mail.Read.Shared)

[jonathanford]

@Anonymous @Anonymous 

I can help tomorrow.

Kummarraj88, I am parsing .eml’s that are attached to emails with my flow and didn’t have to change much of anything after I had the JSON figured out and the connection working. 

Tom,

I gathered info from lots of different sources to make it happen. I’ll see if I can put it in one place. 

[frano72]

thanks @jonathanford  - had just stumbled across it myself.

i left out the /users bit.....thats 66 minutes of googling time i'll never get back !

[Anonymous]

@jonathanford , Thanks Jonathan. If you can publish a guide on how to retrieve attachments from SHared Mailbox using Graph API or  premium connected, it will be awesome. 

[jonathanford]

Here's a quick guide. 

https://www.jford.net/post/616923454656200704/ms-graph-api-power-automate-connector

[teqs]

Hello,

same error for us. Our flows run fine for several months, now we get errors without changes in the flows: Connectors "get Email", "mark as read", "delete"... on everything which makes changes to a "shared mailbox email arrived"-trigger.

"Item Id doesn't belong to the current mailbox"

{
"status": 404,
"message": "Item Id doesn't belong to the current mailbox.\r\nclientRequestId: <ID>\r\nserviceRequestId: <ID>",
"error": {
"message": "Item Id doesn't belong to the current mailbox.",
"code": "ErrorInvalidMailboxItemId",
"originalMessage": "Item Id doesn't belong to the current mailbox."
},
"source": "office365-we.<HOST>"
}

This thread has a lot of pages already. Just as a advice for the next one who come to this topic: 

You can find a idea for a solution on page 3 from User Mindaugas, Link https://powerusers.microsoft.com/t5/Connecting-To-Data/Item-Id-doesn-t-belong-to-the-current-mailbox...

I will try it now.

But I have two questions about your opinion:

- Even if the solution of Mindaugas works, it is still a bug in PowerAutomate, because when the used User-Connection should have access to the shared mailbox, then it should work also without adding a direct shared-mailbox connection. Or do you think it's correct as it is now?

- Would be good to get this kind of changes before MS release that. We do not use Flows/PowerAutomate for fun, but for our business processes which have to work fine (same as most user here). Any idea how we can make sure to get this detail of changes before having a week of problems?

best regards

[jonathanford]

Microsoft's official word from several different reps is using Outlook actions on Shared Mailboxes aren't supported unless the action has Shared Mailbox in the name. To my knowledge, the only action with Shared Mailbox in the name is a trigger. So, you use the Message ID from that trigger to drive use of the Graph API. 

[VictorIvanidze]

Hi @jonathanford,

in fact there exists an action named "Send an email from a shared mailbox (V2)"  and a trigger "When a new email arrives in a shared mailbox (V2)" you have mentioned.

[Anonymous]

The issue here has nothing to do with service accounts or connections... I've had 23 flows running for months with no trouble and, starting about a week ago, the flows will no longer recognize attachments that are retrieved from a shared mailbox using the "when a new email arrives in a shared mailbox (v2) once the flow reaches the stage where the attachments are stored in a SP library with Get Attachments (v2).    

This flow worked flawlessly and same code, same service account (which, by the way, is running 22 other flows - ones which store attachments WITH the email file on a daily basis).  The bug is with Get Attachments (v2) - and there should be no Graph usage or other solutions or code to be added... this fully functional flow should just work.   I've tested all of the components and the error is all over these forums...

Why is there no fix??? 

[jonathanford]

@Anonymous - welcome to the frustration of the rest of us in this thread. Either login as the shared mailbox as a workaround or use Graph API; that's your options. MS has not said this is a bug which leads one to believe it's working as intended. They have told several they do not support actions on Shared Mailboxes unless the action says "Shared Mailbox" in the name, and to use Graph API as the supported method. 

We all commiserate with you, and also suggest using the workaround or supported solution. 

[Anonymous]

Thanks for your reply... but I stand by my statement that it is not working properly and MS is just testing their crappy code on the public as they've been doing for decades.   I'm not sure how large the companies are that y'all work for, but I'll tell you... providing a functional solution only to have it blow up a couple of days later is the king of thing that gets people laid off (especially during a pandemic).  

I appreciate the recommendations, however, Graph API  is not something I have access to utilize and "logging in as the shared mailbox" is a phrase that makes no sense to me.   

Makes me kick myself for dedicating my entire career to MS products.   It should have never worked if it was never intended to work and last week it worked as I expected it to... There was a change made that broke the flows we all had working and the developers don't care who loses their jobs, etc.   

This is no time for this garbage to be happening. 

[jonathanford]

Cool; guess you didn't read the thread then. 

We all feel the frustration. In times like this though, are you going to yell at a brick wall or listen to those who have gone before you and built the bridge you could use if you weren't staring at the wall yelling at it hoping it will listen. 

[Anonymous]

Yeah, I know i'm yelling at a wall - and I know I'm expressing frustration... but NO ONE needs people like  you to just exacerbate the problem by providing answers and trolling for anger in the forums. 

I knew this was a waste of time.   

[jonathanford]

No trolling here man. There are fixes in this thread you didn't take the time to try. You immediately went to yelling when there are solutions. NO ONE has time for that when people have been helping one another for a week in this thread. 

[timothydickson]

I found a solution posted by a Microsoft employee in the User Group surrounding a similar issue.  It was simple and it worked for my problem which was specific to the trigger [when a new email arrives at a Shared Outlook Inbox].  I was moving attachments into their respective SharePoint folders by name.  I had added the [Get Attachments] action to this trigger to start the process and (like everybody else here has reported) it worked flawlessly until recently. 

Essentially, they explained that this trigger has all of the Attachment IDs in the array when it is called - IF - you have the "Include Attachments" option ticked in the trigger, which I did.  So, you don't need additional actions to get the attachment IDs, the Names, Content, etc.   Once I deleted the [Get Attachments] step and rebuilt the subsequent steps, the flow worked.

Hope this helps!
Tim

[Anonymous]

Hello, @timothydickson,

Could you please share your Flow?

Thank you!

[Anonymous]

@timothydickson , Thanks for these details. Looks like my issue is fixed after removing "Get-attachment" as attachments are already there when we use initial trigger called "When  a new email arrived in Shared Mailbox V2". 

I am using Apply to each loop and inside that I am using "create file" in SharePoint based up on initial trigger. I believe it will create file for each and every attachment that was sent to this Shared-mailbox right? 

[teqs]

@jonathanford/ @Anonymous

Yes, good we have a solution. But I think that's not a reason why we should not complain about the situation. We use PowerAutomate for business processes, most customer will do that. And MS customer also have customer by their-self, which are affected when flows start making errors.

So, in my opinion MS should simply not change "things" so long-running customer flows run on error for days until find a solution.

Or affected customer have to be informed about that change before.

When searching in the templates, there are also some I tried today, which have the the same problem because Connectors in these templates run on "shared mailbox" which will not work anymore. Like this one:

Save attachments to OneDrive (Business) on new email in shared mailbox

https://emea.flow.microsoft.com/en-us/galleries/public/templates/91ed73104ee311e78ced3beedb3cacd3/save-attachments-to-onedrive-business-on-new-email-in-shared-mailbox/

This makes a "mark as read" on a mail in a shared mailbox, which is producing the "Item Id doesn't belong to the current mailbox" error. Or do I miss something and this template is still working?

At the moment it seems MS has changed more, because it already fails at the start of the flow when using "user connection" and "shared mailbox". This at least would be consistent. 🙂
So, it seems, it is at least clear for user now, who want to use this template for new flows, because it let you know from the start, that you cant't use it with your user-connection.

But I only get this error on beginning, when using the template. I do not get the error when using "When a new email arrives in a shared mailbox (V2)" trigger in a new flow manually and using my "user connection" to connect to a shared mailbox. Perhaps I miss something here. 😞

[jonathanford]

It sucks for sure, but that's joys of "the cloud" and SaaS. You're on someone else's infrastructure and at their mercy. Can you imagine what Change Control would look like if they asked all their customers before they changed something? We don't know this wasn't a security vulnerability. 

[timothydickson]

Indeed.  Yes, that is correct.