I'm working on a logic app that's meant specifically for sending emails from Synapse. However, I've noticed that using the Outlook connector sends the email through my personal email account. Is there a way to send it from a different email, like one that's tied to a service principal? I've looked into Azure Communication Services, but it seems like a bit of an overkill for my needs. What would be the best approach here? Do I really need to stick with logic apps, and can they interface directly with the final email delivery service? Sorry if this sounds a bit clueless; I'm just getting familiar with Azure and it's a bit overwhelming!
5 Answers
Using Azure Communication Services is an option. You can just configure an allowed mail sender and call the API as needed. It's pretty straightforward once you get it set up.
How many emails are you planning to send? If it's just a few, using Azure Communication Services is typically the way to go. It's not too complicated to set up, and it keeps you compliant with licensing and regulations. Depending on your service, you might have to either set up a custom domain or just use the default one the service creates for you.
A straightforward solution might be to use the 'Send Email' action through Microsoft Graph with the HTTP connector. You'll need to set up service principal permissions for a user who has an Exchange mailbox. There are some helpful guides on Stack Overflow that can walk you through the steps you need to take to get this sorted out.
Last I checked, managed identities aren't supported for this scenario yet. If you want to go a different route, your best bet might just be to create a new email account specifically for sending these emails.
Unfortunately, you can't just bypass it. Either you can create a new Office 365 account just for sending the emails, use Azure Communication Services, or go the Microsoft Graph API route.
Related Questions
How To Get Your Domain Unblocked From Facebook
How To Find A String In a Directory of Files Using Linux