Outlook Delete Email (including V2) deprecated?

[AFWS]

For months my flows have been working correctly and now they all fail on Delete Email - "This action does not support shared mailboxes". Why have they started failing? This occurs using original and V2.

The failures began on 28th April, so I think Microsoft have broken it. That was after a weekend so would have been an update.

It seems it's not possible to report actual bugs to Microsoft, they don't want to know about it.

[v-bacao-msft]

Hi @AFWS ,

This is a known limitation, we could not use Delete Email action to delete the message from the shared mailbox currently.

Please check this link:

https://docs.microsoft.com/en-gb/connectors/office365/#shared-mailbox-support

Maybe you could use Invoke an HTTP request to achieve this requirement. More discussion about this, please check the following thread:

https://powerusers.microsoft.com/t5/Connecting-To-Data/Item-Id-doesn-t-belong-to-the-current-mailbox...

Best Regards,

[AFWS]

Thanks,

Except that it WAS working, until last week.... so it's not a 'known limitation' it's something that's changed in the last round of updates.

My understanding is that HTTP version only works with power apps, not power automate?

[v-bacao-msft]

Hi @AFWS ,

Some users have provided Invoked an HTTP request sample, please check it:

https://powerusers.microsoft.com/t5/Connecting-To-Data/Item-Id-doesn-t-belong-to-the-current-mailbox...

But we need to have a standalone license(flow per user plan) to use this premium action.

Best Regards,

[AFWS]

So a week ago Microsoft broke this function and now you suggest I pay to fix it?

If that fix works, then why don't the brilliant engineers at Microsoft use that method for the Power Automate function?

[v-bacao-msft · Accepted solution]

Hi @AFWS ,

I am afraid that this limitation has really troubled you, I just explained that if we need to use "invoke-an-http-request" to achieve this requirement, we need to have a license to create a premium connection.

The good news is that PG has already reacted to this restriction, they have added an optional parameter to operations allowing users to specify a shared mailbox to access and will be officially supporting this functionality in the connector. Users should not see this issue after fix is deployed. Hope this fix can solve your problem.

Best Regards,

[AFWS]

Thanks for the information. When is the fix likely to be deployed? BTW Who are 'PG'?

[v-bacao-msft]

we expect to see this fix deployed to all regions by the end of this week. Product Group.

[AFWS]

That's good, fingers crossed it works!

[joachimvb]

As of May 6, several Outlook 365 parameters have supposedly had Shared Mailbox functionality added through the "Mailbox Address" parameter.

We have a rule set on a a shared mailbox that automatically redirects most undeliverable e-mail ("bounce") responses into a folder.  We have 30,000+ bounced e-mails in that folder.  I'm trying to harvest all the non-functioning e-mail addresses.

Mailbox Address is working okay in "Get Emails V3."  It won't see the folders, but you can type the folder name in yourself.

Unfortunately, Get Emails only fetches up to 25 emails at once.  I thought that would be okay if I could mark those emails as read, delete them, flag them, etc. so that I could iterate and go through the next 25.

However, those other actions (which supposedly support Shared Mailboxes now) are not working correctly.  I'm passing the Message ID through, but it says "Resource could not be discovered" when the Flow fails.

I've tried the same actions on my personal mailbox and it worked just fine.