Dynamics 365 Deployment Options
This guide is oriented towards deploying InRule as a cloud-based solution in Microsoft Azure to interoperate with Microsoft Dynamics 365 Online. Alternatively, Dynamics 365 on-premises version 9.0 and up is still supported via local installation of the InRule services.
The following sections describe which deployment scenario will be the most applicable depending on your needs:
- Microsoft Dynamics 365 (Online) – InRule SaaS-hosted Rule Execution Service
- Microsoft Dynamics 365 (Online) – Self-hosted Rule Execution Service in Microsoft Azure
- Microsoft Dynamics 365 (On Premises) – Local IIS or Azure IaaS Rule Execution Service
- Other Integration Scenarios
The primary consideration for InRule SaaS vs self-hosted Azure generally depends on if your organization is already setup to manage an Azure subscription and services.
- If your organization does not have an Azure subscription, this can be compelling rationale to go with InRule SaaS and forgo the overhead of Azure management and deployment.
- If your organization has an Azure subscription, it does not exclude you from going with InRule SaaS, but it may indicate that your IT department has requirements or preferences for self-managed Azure solutions.
Either way, this guide will provide you with the information to help determine which InRule configuration will best suit your needs, including Government Cloud and other considerations.
Microsoft Dynamics 365 (Online) – InRule SaaS
InRule for Dynamics 365 is now available via InRule SaaS, in which case many of the deployment steps in this document are not applicable and will be managed for you. This is the most stream-lined deployment available to both qualified Trial users and licensed customers.
If you are new to InRule and do not have an InRule SaaS subscription, you can request a free trial here and specify that you would like to integrate it with your Dynamics 365 instance.
With InRule SaaS, the deployment steps are significantly reduced by eliminating the need to install the InRule App Services in Azure. This narrows the deployment focus down to irAuthor with irX for Dynamics 365 and the InRule Dynamics Solution from the Microsoft AppSource. The main deployment steps in this scenario are summarized as follows:
| Deployment Step | Installation Type |
|---|---|
| 1. irAuthor with irX for Dynamics 365 | InRule installer via the InRule Support Site |
| 2. Rule Execution Services for Dynamics 365 | *managed by InRule SaaS Support |
| 3. InRule Solution for Dynamics 365 | Microsoft AppSource (or script-based) |
All information to set up the connectivity between Rule Execution Services hosted by InRule SaaS and your organization's Dynamics instance can be managed through the InRule SaaS Portal. The following configuration will be managed through the Portal. More information can be found in Dataverse Connectivity and Authorization.
Entered by users in the SaaS Portal – configuration information for the Rule Execution App Services
- The Organization URL for Dynamics.
- Service account credentials for Dynamics – used to allow the InRule SaaS-hosted Rule Execution Service to connect to Dynamics. Alternatively using S2S authentication, InRule can be granted consent as a Trusted App to your Azure AD.
Provided to users in the SaaS Portal – configuration information for the InRule Dynamics Solution:
- Primary and Secondary API Keys
The net effect of an InRule SaaS deployment is that after the above pre-requisites are met, you get to skip ahead to Configuring the InRule Solution for Dynamics 365. Beyond this initial setup the remainder of the guide will be beneficial for detailing advanced rule execution methods and troubleshooting.
Microsoft Dynamics 365 (Online) – Self-hosted in Microsoft Azure
If you are using Microsoft Dynamics 365 (Online), you will be hosting InRule using a Platform-As-A-Service (PaaS) model on Microsoft Azure. When setting up the InRule App Services, ensure that all Azure components and the Dynamics installation are in the same geographical location to reduce timeout exceptions due to network latency. The Azure resources can be deployed using either the ARM Template shipped in the integration zip or via the Azure Marketplace. You can find more info about these options in Deploying and Configuring Components.
This document discusses deploying the following three components:
- Catalog App Service and Azure SQL Database
- Rule Execution App Service for Dynamics 365
- InRule Solution for Dynamics 365
Performing the Installation: In Azure provides a complete walkthrough.
Microsoft Dynamics 365 (On Premises) – Local IIS or Azure IaaS
If you are using Microsoft Dynamics 365 (On premises) or plan to deploy to the cloud using an Infrastructure-As-A-Service (IaaS) model, you will be hosting our integration framework via Internet Information Services (IIS) on a Window Server OS. This document discusses the following 3 components:
- Catalog Web Service and Database
- Rule Execution Web Service for Dynamics 365 On-Premises
- InRule Solution for Dynamics 365 On-Premises
Performing the Installation: On-Premises provides a complete walkthrough.
Other Integration Scenarios
You are welcome to look at alternate integration options. The following are some possible integration scenarios that you may pursue, which may require either deployment or solution customization. Please take the opportunity to verify the rationale for customization with InRule to ensure plausibility.
RuleHelper integration with the InRule (non-Dynamics) Decision Service
- This execution model uses the RuleHelper to query Dynamics data in rule applications running under Decision Services (as compared to the Dynamics execution service). This approach can be useful for targeted scenarios that do not require the full Integration Framework.
- For self-hosted or InRule SaaS implementations, there are manual steps required to set up this integration:
- Self-hosted - the dlls must be manually deployed to the EndpointAssemblies folder per instructions in the Decision Services API Guide - Considerations for Self-hosting article
- InRule SaaS - the setup must be requested via InRule Support
- Moving forward in a future release of InRule Decision Services, the deployment process will be automated to no longer require manual setup
While there are other possible routes, they generally will not work with the Integration Framework we provide off the shelf. As such, we strongly encourage that you follow the model outlined in this guide to start with, until you've acquired a more advanced understanding of how all of the pieces of the InRule for Microsoft Dynamics 365 Integration Framework work together to provide a solution.