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... @Anonymous 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.

146 REPLIES 146
Anonymous
Not applicable

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.

Anonymous
Not applicable

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
Impactful Individual
Impactful Individual

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.

Anonymous
Not applicable

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

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Top Kudoed Authors
Users online (4,230)