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

@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
Helper II
Helper II

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

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
Not applicable

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

 

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

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. 

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.

________________________________________________________

Welcome to my web site.

Anonymous
Not applicable

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??? 

@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
Not applicable

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. 

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
Not applicable

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.   

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
Frequent Visitor

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
Not applicable

Hello, @timothydickson,

Could you please share your Flow?


Thank you!

Anonymous
Not applicable

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

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

 

 

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. 

Indeed.  Yes, that is correct.

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!   Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪 🌠  

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!  Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Users online (5,252)