cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
EGreen
Advocate I
Advocate I

Item Id doesn't belong to the current mailbox

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.

145 REPLIES 145
PeteFromDenver
Advocate I
Advocate I

I too am having the same issue.  For me it started on April 17th. The flow has a trigger to watch new messages in a shared mailbox.  It manages to get the message and the contents.  If I used the Get Email (deprecated) or Get Email (v2) and use the Message ID, it fails with the same error as everyone else.  

 

This was working for almost 2 years.

CStPierre
Regular Visitor

I got the same issue using the graph sdk (c#) to access an email in a group mailbox.

 

 

graphClient.Users[userName].Messages[post.Id].Request().GetAsync()

 

 

https://graph.microsoft.com/v1.0/users/{user}/messages/{id}

 

 

I tested with Graph Explorer and got the same response.

 

This call used to work for more than a year.

We have this exact same issue, but from a Logic App connecting to a O365 Shared MailBox (trying to get an existing message).

Anonymous
Not applicable

Have to give this a bump. We are having the same issue in a Logic App that has been working for a few months and no changes have been made to it or outlook.

 

Also just to clarify: the Get Email (V2) action is reading a shared mailbox through a personal email connector if it has any significance to this. "Doesn't belong tocurrent mailbox" would suggest it having something to do with it.

jeneaMD
Helper III
Helper III

Same here.

@ALL, please update this post when found the solution or the ticket is solved.


Thank you!

ThijsSoepenberg
Frequent Visitor

Same issue here! In combination with 'Get Attachment (V2)' action and a shared mailbox.

Django
Kudo Kingpin
Kudo Kingpin

Big bump: for Production Flows this is a killing bug 😥

Please keep us updated on the Microsoft Ticket 🙏

Anonymous
Not applicable

UPDATE:

 

Based on a reply from MS support, the Get Email V2 action isn't officially supposed to support accessing shared mailboxes, but the API has worked until now for some reason. The email can still be accessed through Export Email (V2) but that will get the raw email content with headers etc. so it would need to be parsed somehow and I can't see any easy way to do this.

 

The API can also be called directly with HTTP with Azure AD but that seems to have the same limitations as well. Outlook API documentation: https://docs.microsoft.com/en-us/graph/api/resources/mail-api-overview?view=graph-rest-1.0

GET /users/{id | userPrincipalName}/messages/{id}              <- Get Email
GET /users/{id | userPrincipalName}/messages/{id}/$value       <- Export Email

This is a poor response from Microsoft TBH (If it's the official line)

 

This has been working for a long time and has just stopped working - officially supported or not (and it appears that the only action officially supported with shared mailboxes is "Send an email from a shared mailbox (V2)" )

 

Come on Microsoft - this needs fixing.

Folks - I can confirm that "Export Email (V2)" does still work with a shared mailbox (you can access the components of the email in  a similar way to Get email (v2) in subsequent actions)

 

I know this doesn't help those of you that are not trying to extract attachments from shared mailboxes, but for those that are it may be a way forward. (Although this also may stop working as it's not officially supported) 🙄

 

Regards Jon

 

Still testing...……………………….. Will update when I have a full answer

The same here! Please provide some solution

aurelijusm
Frequent Visitor

Experiencing the same issue both in MS Flow and PowerApps!

update:

I just copied the flow under new name and activated... for me it works again! 🙂

Anonymous
Not applicable

Can confirm this also works for me now. If copying the action to another flow/logic app is not an option, as in our case, changing the connector email seems to trigger a change also.

 

Otherwise maybe try renaming it or something, if possible. This just means you have to rewrite all actions depending on Get Email (V2)'s output. Changing the connector doesn't require that so it's the better alternative.

I opened a ticket with MS and after some searching on their part this is their reply:

"using actions like “Get Email” and “Delete Email” in Shared Mailboxes is currently not supported, per the documentation for this connector: https://docs.microsoft.com/en-us/connectors/office365/#shared-mailbox-support.  Only triggers and actions with Shared Mailbox in the name are supported.

 

This has been documented for some time but was working.  It seems last week a change was finally made [with Outlook] that broke this functionality.  As mentioned in that documentation, the suggested workaround is to use the “HTTP with Azure AD” connector and the Graph API to work with items in Shared Mailboxes."

 

I've not had the opportunity to look into any of this yet, but I wanted to give the update that MS gave to me.

The same issue is also on Logic Apps - receive mails from Shared mailbox, and Get attahcments action failed to the same error as in Flows. "Clone" Logic Apps also did not help.

Copying the flow did not fix it for me. My flow is triggered by mail arriving into a shared mailbox. I mark the email as read and parse the attachment. Yesterday I removed the mark as read action as it comes before the parse, but then Get Attachment fails. 

 

I am trying to escalate through our MS rep. I'll keep everyone posted. I already had a ticket open in the Power Platform admin center. 

 

Update: 

I did finally get a reply (and it went to Quarantine, from MS - don't you love it?) but I'm not putting myself through the torture of MS support when the easy fix in this thread downstream worked so well. 

eduardotgjr
Regular Visitor

Same issue here, it started today and now all flows that worked for at least a year now don't anymore.

 

@MIS please help.

 

Regards

Eduardo

We are in the same boat.   Logic app worked perfectly for years, now bust.   This is a big deal here.   I've opened a Sev A ticket and notified my Account Rep.

PeteFromDenver
Advocate I
Advocate I

If you look at their updated documentation it now says If the action does not include "Shared Mailbox" in the title, then the action no longer supports accessing Shared Mailboxes. 

 

Per my Microsoft support response yesterday:

Unfortunately this has been documented for a while as not being a supported scenario. It appears that Outlook team has finally closed gaps in the APIs and had to make changes, despite the fact that it was working before.

 

Can you please check the below link-

https://docs.microsoft.com/en-us/connectors/office365/#shared-mailbox-support

Helpful resources

Announcements
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Welcome Super Users.jpg

Super User Season 2

Congratulations, the new Super User Season 2 for 2021 has started!

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Microsoft Ignite 768x460.png

Find your focus

Explore the latest tools,training sessions,technical expertise, networking and more.

Users online (2,495)