Apr 10, 2018

Configure Generic Email (i.e. Info@ABC.com) for Dynamics 365

In most cases, we need to have an Email address for general inquiries apart from user mailboxes. Let us see how we can do this with Dynamics 365 using Exchange Online.

1) Connecting to Exchange Online

To know how Exchange Online connects to Dynamics 365, please refer this post first.

2) Create Shared Mailbox

Now go to Office 365 Admin center and create a Shared Mailbox.


Actually shared Mailbox can be shared among users. When someone sends mail to this address, all the members would get the mail to a separate Mailbox. Any member can obviously reply from that. Interestingly, received mail will see it as it has come from Info@ address.

Though this is pretty cool, our intention here is not to use this sharing scenario, but to receive all the mails of Info@ address to a separate queue, so that any queue member can take action. In fact, we don’t add any member to this shared mailbox.


Anyway, in a while after we configure the shared mailbox, we should see the relevant entry in Exchange Admin Center as below.


3) Configure Queue in Dynamics 365

Now browse D365 Settings > Business Administration > Queue and open the Queue we are interested in and set Incoming Email with our shared Email. Also note that Convert Incoming Emails to Activities field is also important.



4) Configure Queue Mailbox in Dynamics 365

Now browse to D365 Settings > Email Configuration > Mailboxes and Open the Shared Mailbox and configure the Incoming and Outgoing emails for Server side sync as below. (Alternatively click Apply Default Email Settings if you have set Default by now. Click this for more information)
Now click Approve Email, Test and Enable Mailbox.


5) Check behaviour

a) Send an Email to Info@ address from outside. Then you will see this email in the Queue as below;


b) Now any member of the Queue can open the mail for replying.

Note;
Anyway when open the reply mail, by default, From field is getting populated with login user, but you need to select the Info@ account if the reply too should go with generic email address.


c) Here, we get the Reply mail too from Generic Info@ email


Apr 5, 2018

Configure Emails for Dynamics 365 Trial version

Once you get a Trial Dynamics 365, one of the most needed features would be Emails. Let’s see how to get it working.

1) Get Office 365 Enterprise E5

Since Exchange Online comes with Office 365 Enterprise E5, you need to get a trial version of it as well. For that, from Office 365 Admin Centre, browse to Purchase Services and get the trial.


2) Check if Exchange Server Online is Ready

Once refresh, you may see link Exchange under the Admin Centre. Once click it, it will open another window with Exchange Admin Center where you can click Mailboxes.


Well, you will not see any Mailbox at this point.


3) Assign Licence to Users to get Mailboxes

Now go to Users section of the Office 365 Admin Center where you can see all the active users. Once you open a User you will see the message “This user doesn’t have an Exchange Online License” under Mail Settings.


Then you have to click the Edit button for Product Licence as circled above where you have to enable a Licence for Office 365 Enterprise E5.


As you do this, you will see massage under the Mail Settings will change to below one.


This may take a while, but once complete the process, you will see those Mailboxes appear in Exchange Server Online Admin.


4) Check Active Email Server profile

Browse D365 to Settings > Email Configuration > Email Server Profiles.

Here, Microsoft Exchange Online profile should be already visible since Exchange and D365 are in same tenant. Make sure its Active.


5) Configure default email processing and synchronisation

Now browse to Setting > Administration > System Settings in D365 and go to Email Tab. Your configuration should look like below;


6) Configure Mailboxes in D365

Browse D365 Settings > Email Configuration > Mailboxes

Open the Mailbox you need to configure and do below steps;


a. Click Apply Default Email Settings button – This sets the default settings in Step 5.

b. Click Approve Email – You needs to be a Global Administrator to do that, Otherwise click Send Email for Approval which will request Approval from Global Admin.

c. Click Test & Enable Mailbox – This will take few minutes to Test the mail and enable the Mailbox.

7) Check if the Mailbox is correctly done

After all, you can Browse to the Alert section of the Mailbox to see the test result as below. These details show that testing is successful.


Same way, if there are issues, you can see the descriptions.

Mar 25, 2018

Continuous Integration (CI) for Dynamics 365

DevOps being very popular among developing arena, Continuous Integration (CI) has become very important aspect. Though you will find many articles on theoretical approach on CI, guide on how to do it for a XRM is still rare. In fact, thought of sharing one approach tried recently.

Here I am explaining a working skeleton of my choice for D365 V9. I am not going in-depth in VSTS (Visual Studio Team Services) online Build and Release process, but explain D365 specific work, which is the focus.

CI for D365 needs utilising of collection of tools together. In this example, I am deploying a Package consist of a Solution as well as a Data file.

1) Package Deployer – to Create Package

Here I am using Package Deployer of D365 SDK.  Below Videos explain standard usage of Package Deployer;

a. Create Package: https://www.youtube.com/watch?v=KJKZPu4C-O4
b. Deploy Package: https://www.youtube.com/watch?v=lKt-bPdiBgM&t

Usually, Package is deployed through supplied wizard based steps, but we need to automate the deployment process. Still structure of the package and the way It’s being created remains same.

According to our scenario, we define Package with one Solution and a Data file resulting below Config file;


A couple of points;

• Solution component is required, though data file is optional.  Suppose our requirement is to push only the data file, still a dummy solution needs to be there.

• If the Solution is already deployed to D365 and we try to push it with same version, importing of the solution is skipped.

If you want to deep dive in to Package Deployer, please refer below article.
https://msdn.microsoft.com/en-us/library/dn688182.aspx

2) Configuration Migration Tool – to Create Data Files

Configuration Migration tool, supplied by SDK, is to be used to generate the Data file explained in step 1.

This explains how this tool should be used;
https://www.youtube.com/watch?v=_DrDbfRlJZI

3) Prepare VSTS Online

In our, scenario we use xRM CI Framework as an add-in.  Below simple steps illustrate how it can be added to VSTS;

a. Browse to Market Place of VSTS

b. Search for Xrm and click Get it free

c.You are done.


4) Build Process

Build definition is simple and consist of only one Task which is Publish Artefact task.


One point to keep in mind is, I have kept package in correct structure in BuildPath folder.


Once built, published artefacts are in the same correct structure in Artefacts Explorer as shown below;

5) Release Process

In Release definition, we use MSCRM Package Deployer task provided by xRM CI Framework. Within the relevant configuration, you will notice how I have pointed the Assembly of the package and Package directory to the build Artefacts we built in previous step.


Anyway, by the time this writting, this works only if Crm SDK Version is set to 8.2. If I find more about this issue or workaround, will publish in this blog in future.

Happy days!.. Releases are happening..


Now your package is pushed to Dynamics 365.