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

@timothydickson this solution worked for me! Thank you so much.

EGreen
Advocate I
Advocate I

It looks like Microsoft has updated the error for this issue in Flow. The new error is "This action does not support shared mailboxes" and they include a link to the documentation that recommends the Graph solution.

 

So no new information really for those of us who have been working through this issue, but I wanted to include that error text so a search could at least retrieve this thread.

Anonymous
Not applicable

the solution from @timothydickson  worked for me. remove the "get attachments" action and create the file just using the "when item arrives in shared mailbox" trigger

@timothydickson !!! Thank you very much for posting the detailed description of your fix.   This was what I needed to get my Flow running again, as well.  I really appreciate you taking the time to share the information.   

 

Cheers!

@MindaugasMy admin says that my sharebox doesn't have password. Can I use your solution without password? When I try to enter my sharebox in the connections, I got error message that the Email address is wrong. Any advice?

 

Thanks,

Your admin is lazy admin. You can change any password of mailbox. He has to find it with all rest of active users in admin center

My admin is also mentioned that there is no password to this shared mailbox. I'm not completely clear, but he said this account is provided same E3 license or something of that sort, so these are not the same as other accounts.

My admin create a @grassavoye365.onmicrosoft.com account for this shared mailbox

Just do not forget that you can also ask MS per support ticket for help. It's also a good idea to show them the amount of problems they produce with changes like this.

 

And I am wondering why I still find official MS flow templates, which use "mark as read" on "shared mail box" items. Which in my opinion can't work after the last changes:


"Save attachments to OneDrive (Business) on new email in shared mailbox"

Link: https://emea.flow.microsoft.com/en-us/galleries/public/templates/91ed73104ee311e78ced3beedb3cacd3/sa...

Perhaps someone can correct me, that this template should still work as it is?

gjeh
Responsive Resident
Responsive Resident

I'm having a similar issue, when ever i try to run a flow that starts with the trigger 'when a new email arrives in a shared mailbox (V2)' it fails like this:errortje13.PNG

 

Odd thing is that if I try to use it on my test tenant it works perfectly fine. (how typical; works where it doesn't matter - doesn't work where it matters).

 

run on unimportant, pointless tenant:

succes.PNG

 

the only actual difference are the language settings between tenants.

@timothydickson , What is simple solution. This works perfectly for me thank you. I was  using the trigger to save attachments in the shares email to a OneDrive folder. So a little bit different than the original issue reported but one that was discussed with in the thread. The files were retrieved but corrupted.

Anonymous
Not applicable

Hi,

We had same issue with the Shared Mailbox , where we marked the mail as read, flagged it Complete and moved it into another folder in the Shared Mailbox.

Now we have changed to a Service User account's mailbox , and proceding the same process , but since we can login as Service user account and with password , our connections are now using the Service User connection and everything works just as it did with the Shared Mailbox before.

Hello, my problem was with getting attachements from shared mailbox in Logic App.

 

I have opened ticket to MS , after few calls solved it by these steps :

- Invoke HTTP witn Azure AD - Invoke an HTTP request (need connect to https://graph.microsoft.com/  in both parameters), URL parameter:


https://graph.microsoft.com/beta/users/"Your shared mailbox adress"/messages/MessageId/attachments

- Parse JSON - Contet: Body from HTTP call

- For Each JSON.Vakue set variable XY to base64ToBinary(ContentBytes)

schema:

{
"properties": {
"@@odata.context": {
"type": "string"
},
"value": {
"items": {
"properties": {
"@@odata.mediaContentType": {
"type": "string"
},
"@@odata.type": {
"type": "string"
},
"contentBytes": {
"type": "string"
},
"contentId": {},
"contentLocation": {},
"contentType": {
"type": "string"
},
"id": {
"type": "string"
},
"isInline": {
"type": "boolean"
},
"lastModifiedDateTime": {
"type": "string"
},
"name": {
"type": "string"
},
"size": {
"type": "integer"
}
},
"required": [
"@@odata.type",
"@@odata.mediaContentType",
"id",
"lastModifiedDateTime",
"name",
"contentType",
"size",
"isInline",
"contentId",
"contentLocation",
"contentBytes"
],
"type": "object"
},
"type": "array"
}
},
"type": "object"
}

- write attachemnt/file to Sharepoint Libary: name from JSON, content from  variable XY

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

@Anonymous Wow, great update. I just added in the shared mailbox to my existing Flows and they're all working again.

The world thanks you @Anonymous. 

Hello @Anonymous ,

 

nice to see the change. I see this new "mailbox" field on connectors like "get attachments" and "get mail" but not on actions like "Mark as read". So, I guess, your solution is not able to "Mark as read" for a email in a shared folder?

Or do it solve this also and I miss something?

 

thanks and best regards

Anonymous
Not applicable

I'm not sure how many actions they are adding it to.  They just said "updating the Email actions".  Maybe it will get an update today also.  If not, I can pass the info on but may also need another support ticket or uservoice submission.

@teqs I can see the Mailbox Address field on the Mark as read or unread (V2) step.


@Anonymous wrote:

 

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.

 


what is the mailbox adres?  identity@domain.com  or ? (im very noob, legit question)

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,016)