Skip to main content

msdyn365bc - Enhanced Email Capabilities - Part 1.

Hi Readers,

With Business central 2020 Wave 2 Microsoft have added an optional feature regarding Enhanced Email Capabilities.  

In this series of articles we will talk about setting up the enhanced email capabilities. But as I said earlier before turning a feature on in Feature Management make sure to Test in in Sandbox / docker environment. 

You might be using extension which are still relying on old SMTP Method and will be broken if you enable Enhanced Email Capabilities.   

Open Feature Management,  and Enable Feature Update: Enhanced Email capabilities for all users as Shown below.

After you login to your tenant again the new email feature is enabled and old SMTP is disabled. If you search for Email you will see new options in your tenant. 


To Start with open Set Up Email, which will help us to setup an email account.

This will invoke a wizard, to setup email account. Click Next.


There are multiple options to add a email account. If you plan to use Microsoft 365 & Current user you need to setup Azure Active Directory, as shown below.


You can also use SMTP (old way) which I will use for this demo. Select SMTP and click Next to Enter your SMTP Account Information as shown below.


You can setup a default account before you finish the Email setup. You can also sent Test Email if required.

You can check all Email Account by Navigating Email Accounts using Tell Me Feature.


Email Account page list all the email accounts that you have added and also provides you option to -

  • Add New Email Account.
  • Assign Scenarios To Email Account.
What is E-mail Scenarios?

E-mail Scenarios, are set of  areas in Business Central where email capabilities are added by Microsoft , ISV Extension  or Per Tenant Extensions.

You can define default Sender email Id for scenarios. You can attach multiple scenarios to an email account. 

In Email account window, Select Email account and then 
  1. Click on Email Scenarios.
  2. Then Choose Apply Scenarios. 
  3. Choose scenarios that you would like to attach.

Once you have setup email scenarios based on your requirement you will end up with a setup like below. For those email scenarios, the default email address will be used as shown below.


In next article, we will discuss how we utilize email feature with Business Central 2020 release Wave 2 and higher. 



Let me know your views as comment to this article.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

Dynamics 365 Business Central 2021 release wave 2 (BC19) Released.

Hi Readers, As we all were expecting Microsoft have Released Business Central 2021 Release Wave 2 Today a.k.a BC19. In this article we will see what all is announced with the General Availability.  Starting Today Customers & Partners can start using Business Central 19. #msdyn365bc #bc19

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.