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.

2 ACCEPTED SOLUTIONS

Accepted Solutions
Anonymous
Not applicable

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:

 

0.png

 

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:

 

1.png

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:

 

2.png

 

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.

View solution in original post

Anonymous
Not applicable

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.

screenshot.png

View solution in original post

146 REPLIES 146
rsaikrishna
Community Champion
Community Champion

@EGreen ,

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. 

Anonymous
Not applicable

Has this issue got resolved? As i am also facing the same issue from yesterday.

I haven't found a solution yet.

 

@Anonymous Out of curiosity, is your issue also relating to a shared mailbox?

Anonymous
Not applicable

@EGreen Yes it is related to Shared mailbox

sobenson
Resolver I
Resolver I

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."

Anonymous
Not applicable

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

Just now I wrote ticket on MS support with this issue, so we will see...

Stewartjohn100
Advocate II
Advocate II

Same issue - multiple failures on flow that monitors emails arriving into a Shared Mailbox.

@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:

 

 
  "status"404,
  "message""Item Id doesn't belong to the current mailbox.\r\nclientRequestId: (AGUID)\r\nserviceRequestId: (AGUID)",
 
    "message""Item Id doesn't belong to the current mailbox.",
    "code""ErrorInvalidMailboxItemId",
    "originalMessage""Item Id doesn't belong to the current mailbox."
 
  "source""office365-eus2.azconn-eus2-01.p.azurewebsites.net"

Hi @EGreen 

 

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."

 

Thanks.

Error details:

 

{
  "error": {
    "code""ErrorInvalidMailboxItemId",
    "message""Item Id doesn't belong to the current mailbox.",
    "innerError": {
      "request-id""87da33ff-fa43-4cdf-8258-aa8cc6e23643",
      "date""2020-04-22T10:17:53"
    }
  }
}

UPDATE

 

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.

timothydickson
Frequent Visitor

Indeed.  Same here.  Although my issue is intermittent.  It doesn't fail consistently... which is even more maddening.

Anonymous
Not applicable

I'm having the same issue. The Delete Email (V2) doesn't delete the email. The message id is being used.

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. 

jhargrov
Frequent Visitor

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. 

 

{
  "status"404,
  "message""Item Id doesn't belong to the current mailbox.\r\nclientRequestId: 6c40f5e1-81f3-4383-b667-c65ce0bbd6a7\r\nserviceRequestId: f940f2ba-16bd-45c0-bdc7-64fa427f3667",
  "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-eus2.azconn-eus2-01.p.azurewebsites.net"
}

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,492)