Gathering Prerequisites for Dynamics 365 in Azure
This section reviews what you will want to have prepared before you begin with the integration steps in the next section.
.NET Framework
The InRule for Microsoft Dynamics 365 integration framework is built against Microsoft .NET v8.0. For on-prem installations, ensure you have this .NET version installed.
Rule Authoring Environment
A Rule Authoring Environment is used to upload a Rule Application to your catalog app service. A Rule Authoring Environment is a machine or virtual machine where irAuthor has been installed with the irX for Microsoft Dynamics 365 extension. If you followed the instructions outlined in irX for Microsoft Dynamics 365 Help Documentation then you should already have a rule-authoring environment available to you.
Administrative Accounts
The purpose and setup of Dynamics service accounts is described in detail in Dataverse Connectivity and Authorization.
Dynamics 365 Organization Service URI: You will want to have the root URL of the organization web service exposed by your Dynamics 365 instance. The server URL is usually in the format of https://organization-name.crm.dynamics.com
InRule Azure License File
You will need an InRuleLicense.xml file used for licensing InRule in an Azure cloud environment. This should have been provided with your InRule Welcome package. Refer to License Management for more information. You can contact support@InRule.com if you have additional questions.
Deciding Resource Names
The following worksheet can be used to decide what to name Azure resources as you go through this Guide.
Many of these resources must have names that are unique in the world; they are hosted on Microsoft Azure and are given domain names that match. We recommend creating a "Base" name comprised of the following: app or organization name, "inrule" (to denote all inrule resources), and environment (dev, test, prod). For Example:
{AppOrOrgAbbreviation}-{inrule}-{EnvironmentAbbreviation}
myapp-inrule-dev
You can choose to follow this convention or invent your own.
| Resource and Description | Example Name |
|---|---|
| Base Name | myapp-inrule-dev |
| Azure Resource Group Name | myapp-inrule-dev-rg |
| App Service Plan Name | myapp-inrule-dev-sp |
| Azure SQL Server Name must be lower case | myapp-inrule-dev-sql |
| Catalog Database Name | myapp-inrule-dev-sqldb |
| Catalog App Service Name | myapp-inrule-dev-catalog |
| Decision Service App Service Name | myapp-inrule-dev-decision |
| Dynamics Execution App Service Name | myapp-inrule-dev-dynamics |
Optional Resource Files
The following file can be downloaded from the InRule support website's downloads section:
InRule for Microsoft Dynamics 365 Integration Framework.zip
This zip file contains several resources that can be used in advanced deployments. A typical installation does not require the use of these resources, as all of the required deployment assets are available online. However, certain deployment scenarios do require the assets contained in this zip file, such as: InRule Solution for Dynamics 365.
After you have downloaded this file, but before extracting, make sure that you go to the file properties for the zip and select Unblock. If the zip file is not unblocked before extracting, the deployment scripts will not be able to execute successfully.
After unblocking the zip file, extract the contents to a working folder.
Deploying and Configuring Components
There are two primary paths for deploying the required InRule components:
-
Microsoft App Stores: Azure Marketplace and Microsoft AppSource - (Recommended) Provides a straightforward, UI-driven process that simplifies deployment and eliminates the need to individually deploy both the Catalog App Service and the Rule Execution App Service. Both the Azure Marketplace (for InRule App Services) and the Microsoft AppSource (for the InRule Dynamics Solution) must be utilized to deploy their respective InRule Apps (see matrix below).
-
Manual Deployment using ARM Templates and Scripts: Manually deploy InRule Azure Resource Management (ARM) Templates through either the Azure Portal, PowerShell, or Azure CLI; then deploy the InRule Solution via PowerShell to your Dynamics 365 instance.
InRule components by deployment path:
| InRule Component | Microsoft App Stores | Manual Deployment |
|---|---|---|
| Catalog App Service | Azure Marketplace | ARM Template |
| Rule Execution App Service for Dynamics 365 | Azure Marketplace | ARM Template |
| InRule Solution for Dynamics 365 | Microsoft AppSource | PowerShell Script |
While deploying from Azure Marketplace and AppSource is generally recommended for initial environments; in advanced scenarios the manual deployment resources can be leveraged for multi-environment DevOps automation. Also note, choosing either path does not require you to stay on the same path across all components; as the deployment options can be mixed and matched as situations warrant.
In either deployment path, if you wish to leverage a server-to-server (S2S) connection between the rule execution service and your Dynamics environment, you'll need to first register an Azure Active Directory Application. A walkthrough of this can be found in Dataverse Connectivity and Authorization.
While the following sections are primarily focused on the manual deployment path, there are still relevant config and testing steps which apply to both paths. For Marketplace and AppSource deployments, you may skip the manual deployment steps and go directly to the relevant sub-sections for license management, configuration, and setup verification.