Trick for sending mail from a shared or group mailbox using Power Automate!

Подписаться 7 тыс.

Просмотров 8 тыс.

50% 1

Sending emails from a shared mailbox adds polish to your Power Automate workflows! Here's how to configure the permissions and action settings to send email from the shared mailbox.
The permission change addresses the error "status: 403, You are not authorized to send mail on behalf of the specified sending account."
I have a version of this tutorial on my blog as well: christine-payton.com/send-pow...

Наука

Опубликовано:

8 авг 2023

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 8

@andrewadams8601 3 месяца назад

This was super helpful. I was using the send from a shared mailbox action instead and it was using the "Send on behalf of" instead of "Send as" permission even though my account had both. There was no way to change it in that action that I found, so I switched to this action, used the "From (Send as)" field just like you showed, and it worked perfectly. Thanks!

@bi-ome 3 месяца назад

Yeah, I did the EXACT same thing the first time around, that's why I made this video!

@gunapalani5580 3 месяца назад

Thanks for this useful video

@nadafathi8221 4 месяца назад

Hi Christine If Administrator is not displayed in the Power Automate menu, is there any other way to achieve this?

@bi-ome 4 месяца назад

Hello! The link that it goes to is here, you do need to have an Exchange administrator to do this - if you don't have an Exchange administrator role, you might contact your IT Department: admin.microsoft.com/

@Kingbob2 7 месяцев назад

how about sending an Approval from a shared mailbox or similar so my name and email aren't plastered all over our department approval processes?

@bi-ome 7 месяцев назад

The best way I’ve found to do this is to have a designated Power Automate service account to run the flow, you can name it Power Automate or whatever you like that’s generic. It’s best practice to run flows from a service account anyways, because if you’re running them from your account and leave your org, they all start failing. Using a service account, they will all continue to work. This way, approvals also look like they’re coming from a non-person account. It just costs an extra license per month, so not prohibitively expensive.

@Kingbob2 7 месяцев назад

@@bi-omethanks! I suspected a dedicated account was the only solution here.