If you, however, want the 100% custom experience for whatever reason, you can use the Microsoft Graph APIs to build your e-mail solution. With SMTP relay services (such as the SendGrid above), you get much room for customizations, including templates. I will demonstrate a super-basic way to craft your custom e-mail templates in HTML and use that for sending somewhat good-looking e-mails to the recipients. Simply put, it's your code, so you set the rules. For me, this creates a seamless experience. This setup helps a lot with conversations that have sparked from your automated e-mails. Using the Microsoft Graph APIs to send e-mails as a user, you can decide whether to keep the sent e-mails in your "Sent" folder. Sometimes, however, you may like to send an e-mail and keep the history of the entire conversation at your fingertips - in your Microsoft 365 mailbox. Sometimes you want to send an e-mail, and you don't need to think twice about it. Sending e-mails one-off or by automation is a great way to fulfill many of our requirements, both for the business and our technical solutions. While there are a lot more use cases and requirements we could spend time talking about, here's a few of the recurring themes I'm seeing.
Always make informed decisions for your situation. These use cases do not replace SendGrid or any other third-party service, but it adds to the story of when you may want to consider one or the other. Let's take a quick look at a few business cases where sending e-mails using the Microsoft Graph APIs could be an interesting fit. It's about sending e-mails using Microsoft Graph, an excellent fit for several business requirements. Sending e-mails using the SendGrid NuGet packages is easy.īut, this post isn't about sending e-mails with SendGrid. If you want to send e-mails, I recommend that you look at whether SendGrid fits your requirements. Recommended method of sending e-mail in Azure (Microsoft Docs) Using these email delivery services isn't restricted in Azure, regardless of the subscription type. You might also have an authenticated SMTP relay service on your on-premises servers. SendGrid is one such SMTP relay service, but there are others. (These relay services typically connect through TCP port 587, but they support other ports.) These services are used to maintain IP and domain reputation to minimize the possibility that external domains reject your messages or put them to the SPAM folder. Quote from the docs about sending e-mails in Azure: We recommend you use authenticated SMTP relay services to send email from Azure VMs or from Azure App Service. Plain and simple, and this works in a wide array of use cases. To send e-mails in Azure, Microsoft recommends a service like SendGrid. Ensuring the account is licensed to send e-mails.Create an Azure AD app with Microsoft Graph permissions.
#GTD APPLICATIONS MICROSOFT FULL#
#GTD APPLICATIONS MICROSOFT CODE#
In this post, we'll check out an easy way to set up the basic configuration and code for allowing our applications to send e-mails using the Microsoft Graph. Let's talk about that a bit further down. Sometimes that's the way forward, and sometimes it's not.
Microsoft even recommends a third-party, SendGrid, for sending e-mails in Azure. Sending e-mails from custom applications and integrations in the cloud is relatively easy, whether you're building a fully customized app, low-code apps, or integrations using existing plug-and-play solutions.
0 kommentar(er)
