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.
Solved! Go to Solution.
You have to create conection using my instruction. Because I also could not add sharedmail box using connection editor on the right. You have to you use those 3 dots (take a look at my screenshot). First fix conection then everything should work. If something we can make teamviewer sesion 😉 Because I understand how frustrating it is...
Looks like the solution for Get-Attachment is to use "Invoke http request" which is an premium License requirement. My company doesn't have that license. Is there any way to get this working?
I have used "get-attachment V2" and still same error as everyone is getting. As per the below documentation this "Action should work". Not sure why it is not working yet.
This is frustrating and we need to stop our production roll-out because of this issue. Meanwhile I will also open ticket with Microsoft.
My ORG also starting looking for third party solution instead of PowerAutomate as the changes are not consistent.
@jonathanford , are you saying to change the password of Shared Mailbox account itself or the user account that has permissions to the shared mailbox should be changed with new password? I believe we need to set Shared Mailbox password itself right?
Redirect all your incoming emails from shared mailbox (set a rule in Outlook) to your personal mailbox and then change mailbox address in Flow Trigger "When a new email arrived".
I explained all the steps above. If you need other explanations, don't hesitate to contact me.
For me - it worked and it seems much easier than other solutions.
bad solution. Create a rule just to fix a bug?
If I were a MS boss, I'd return the "Invoke an HTTP request" action back to non-premium.
@jeneaMD , Thanks for your suggestion. This solution can be a temporary purpose. Because daily we (shared mailbox) receive more than 600 reports/attachments. I don't want my mailbox to flood with these emails and different to load them due to high quantity.
I am trying password reset today and if that doesn't work then I will set the rule as per your suggestion until Microsoft fix this. We will be also opening ticket with Microsoft and I will keep posted on this. This is frustrating for sure.
@jeneaMD is your solution sustainable? What happens when you get hit by the lottery bus, leave the company and the delete your account? All your flows stop working? I know it wouldn't be your issue, but usually we don't want to screw over then next guy.
@sobenson, thank you for being ironic, but as @kumarraj88 said earlier: when you have hundreds of emails/attachments that should be saved somewhere in the cloud on a daily basis and you don't have other solution until Microsoft will solve it or will propose alternatives --> then, yes, is sustainable.
Other solutions proposed are not applicable for me.
And yes, in my organization, each employee has a back-up, don't worry about my financial health. 🙂
Looks like if you have the trigger "When a new email arrives in a shared mailbox" attachment content is in there and appears to work without issue, for those who are trying to get attachments from a shared mailbox, might have to "enable" via the advanced options in the trigger
Agree with @srduval , the "When a new email arrives in a shared mailbox" trigger is still working. The issue was sending a command to do something to the message after that. Using the SharePoint action "Create file" to a SharePoint site is still working.
We were all exploiting a bug that was patched. MS has done their jobs and fix a flaw. Would it be great if they released Shared Mailbox actions, yes. I am sure there are User Voice posts asking for this.
@Mindaugas Thank you for sharing!! This worked for me also.
Anybody still facing this problem should definitely try the solution posted by Mindaugas.
Be advised that if you do not sign-in to Shared Mailboxes typically (I do not either), then you will need to set a password manually in Office Admin center.
Hey Guys got this problem from Wednesday too. I have a flow witch reads mail in sharedmailbox, saves attachmetns to sharepoint and marks email as read.
1. First you have to know password of sharedmailbox IF Not go admin center -> active user -> find shared mailbox and get password.
2. Go to your MS flow that keeps failing. Then Edit.
3. Find action that is failing in my case it was "Mark as read or unread V2"
4. Then push 3 dots. And there is +Add new connection select it.
5. Enter sharedmailbox adress and password.
6. Checked if it appeared among other conections. As in step 4 if not try again. ( Few times needed for me.)
Wordked for me.
Check out new user group experience and if you are a leader please create your group
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Many congratulations to the Season 1 2021 Flownaut Crew!
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.