Forum Discussion
Send As Service Account in Hybrid Setup
Hi,
Here's my scenario:
Service account in SQL is generating emails, and those emails need to come from a shared mailbox based in Exchange Online.
Service account isn't mail enabled, and could be - but that'd use a license.
I can't add the service account to give it send as permissions on an Exchange Online.
I can't log on with the shared mailbox to send the email as that's a disabled account as per shared mailbox requirements.
I don't want to use Exchange On-prem as the SMTP server and send the emails anonymously, as the groups the emails go to are set to only accept authenticated senders so we don't get spammed from the outside.
How do I do a send as without using another license, or is that not possible?
- Hi Adam,
AFAIK, don't think that's possible, I think in this scenario (where you need to use that specific mailbox, using authenticated SMTP via smtp.office365.com 587 and groups which only accept from authenticated senders) its an authenticated mailbox. For that, a Kiosk mailbox which is much cheaper than standard EO mailboxes should suffice so it would simply mean converting the shared mailbox into a kiosk mailbox.
If there wasn't the authentication requirement, you could have done it by using direct send with an inbound connector (fixed to your firewall IP) and then direct the sending application at the 365 MX
https://docs.microsoft.com/en-gb/Exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3?redirectSourcePath=%252fen-ie%252farticle%252fHow-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4
Best, Chris
- Hi Adam,
AFAIK, don't think that's possible, I think in this scenario (where you need to use that specific mailbox, using authenticated SMTP via smtp.office365.com 587 and groups which only accept from authenticated senders) its an authenticated mailbox. For that, a Kiosk mailbox which is much cheaper than standard EO mailboxes should suffice so it would simply mean converting the shared mailbox into a kiosk mailbox.
If there wasn't the authentication requirement, you could have done it by using direct send with an inbound connector (fixed to your firewall IP) and then direct the sending application at the 365 MX
https://docs.microsoft.com/en-gb/Exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3?redirectSourcePath=%252fen-ie%252farticle%252fHow-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4
Best, ChrisHi Chris,
Thanks for the response. I think the best outcome I can get then, is a single service account that uses a license, and is added as 'send as' rights for any mailbox it's impersonating. That can then be used across multiple systems.
You're right, as long as I don't need EWS, a Kiosk license will do the job.
- Glad I helped Adam, look forward to working together again soon.
Best, Chris
