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.

[RHCC]

@Anonymous

Yes - two options for you.

1. Ask your Office 365 Administrator or your organization's Helpdesk if they are able to reset the password for the account. They may look at you a bit strange - you should reference this article. This sort of thing is certainly outside the norm.

2.  If you cannot get help internally, escalate a ticket to Microsoft Support if you have not already, explain the issue and ask them to reset the password and provide the credentials to you.

-RHCC

[Anonymous]

Thanks for the suggestion

[RHCC]

You're welcome! 

[pmontra]

I am getting the same error message as well starting just last week on Flows that should flag an email at the end of the tasks in a Shared Box. Everything runs OK except the last piece for Flagging the Email which gets the error.

[pmontra]

I am receiving the same error as well. All task run successfully on an email in a Shared Email box and the last piece for Flagging the Email receives the same error.

[sandeepk1999]

@pmontra : my flow is also failing at the end when I want to mark it as "Read". But if i forward the email it automatically marks it as read, so I forwarded the mail to my personal mailbox and I have rule in my mailbox to delete this email.

[GoneWithTheFlow]

Thank you @Mindaugas ,

you are my hero

[Anonymous]

@Mindaugas @jonathanford , My shared mailbox is in disabled mode as we don't use for any interaction. For this testing purpose we have enabled, reset the password and then added the connection which started working.  But can not keep that Shared Mailbox account in disabled mode and use this? Not sure why Microsoft keep's on changing and breaking existing functionality. Not your fault. 

But for Temporary purpose this is working. I need to looks for permanent solution. 

[jonathanford]

Permanent solution is to use the "HTTP with Azure AD" connector or the "HTTP" connector with the Graph API but those connectors are Premium. I have the Premium license but haven't wanted to jump off into that yet. 

[Violat0r]

Really @microsoft,

Everybody pays you lots of money every month and you guys cannot inform us what have you messed up?

Do you really want us to escape to solutions like Nintex or K2?

Please treat your client with respect. This action is commonly used in a lots of organizations around the globe. Please give us some update.

[Anonymous]

This occurs when you run actions which do not pertain to a shared mailbox.

e.g. Delete email refers to deleting email in your personal mailbox. If you use dynamic content (Message Id) from your shared mailbox, it won't work.

Microsoft should provide more actions for a shared mailbox. Must be some update Microsoft has run to identify this (which is the right thing to do). Most of their updates seem like an afterthought. Having said that, there aren't many better low code products right now. Also, I won't risk running enterprise dependent solutions on power automate.

[Anonymous]

@Mindaugas my shared mailbox does not have a password. is there a way to connect to it?

[Anonymous]

@Anonymous glad this worked for you. My shared mailbox does not have a password but users are granted access to it with their specific credentials. How would this solution work in my case? 

Any feedback is highly appreciated.

[RHCC]

Yes - two options for you.

1. Ask your Office 365 Administrator or your organization's Helpdesk if they are able to reset the password for the account. They may look at you a bit strange - you should reference this article. This sort of thing is certainly outside the norm.

2.  If you cannot get help internally, escalate a ticket to Microsoft Support if you have not already, explain the issue and ask them to reset the password and provide the credentials to you.

-RHCC

[RHCC]

If you have access to Office Admin, just go to the Users section and find the shared mailbox. Reset the password manually.

-RHCC

[Stewartjohn100]

thanks @Anonymous  -- this worked for me!

[jonathanford]

I was able to get the support method working today using the Graph API. I figured this is how they want you to interface with things going forward so might as well get it going. 

[Anonymous]

@jonathanford glad you got it working. Could you please share how you did it. I am still having issues.

[Anonymous]

Does anyone tried using Premium connector? We were given premium license and not allowed to enabled Shared Mailbox for direct conenction.

So the only option left is to go with Premium connector. Not sure exactly about which connector and Steps to achieve this. 

My flow. 

1. when a new email arrived in Sharedmailbox

2. Get-Attachment V2

3. Copy file to SharePoint Library

Can anyone comment instead of Get-Attachment, which premium connector I have to use to retrieve the attachment? 

[frano72]

Hi, I am trying to use the graph api workaround seeing as the approach we've been using has now stopped.

https://graph.microsoft.com/v1.0/me/messages

Anyone know what the "me" should be replaced with for a shared mailbox ?

I've tried the email address(es) of the shared mailbox and none seem to work.

Thanks !