AlfaPeople | 2 simple tools to integrate your Dynamics 365 cloud data with on-premise infrastructure
Faced with the need to move data between Dynamics 365 for Finance and Operations and on-premises LOB (Line of Business) applications, many end users of Dynamics 365 for Finance and Operations who operate on Microsoft’s Azure cloud often find themselves wanting a simple way to integrate or interface with other systems.
In this blog post, we’ll look at two methods to achieve Azure integration: Recurring Integration Scheduler (RIS) and the Azure File share approach.
1. Recurring Integration Scheduler (RIS)
RIS is a solution developed in C#/.net. It runs as a Windows service on the server. Internally it uses Dynamics 365 for Finance and Operations methods to export data and import data in specific file formats. Once configured on the server (on premise server of the end user/Cloud VM), the RIS service reads and writes files to and from configured folders. It also monitors the status of Dynamics 365 for Finance and Operations processes, moving input files between “status” folders based on the status.
Recurring Integration Scheduler (RIS) – Source: https://github.com/Microsoft/Recurring-Integrations-Scheduler/wiki
| Pros | Cons |
|---|---|
| Windows service, easy to install on any on premise windows server | Limited enterprise level features, detailed exception handling, disaster recovery, audit logs etc. |
| No additional license cost/Azure cost | Maintenance and support post go-live by the end user/customer, level of expertise in .net |
| All files written on premise infrastructure | Not auto scalable |
| Allows the use of the same instance of the RIS to connect to different Dynamics 365 environments | Releases and maintenance done by git hub community |
2. Azure Cloud File share approach
This Azure integration service is fully cloud based when it comes to the components involved. It is a Dynamics 365 for Finance and Operations custom module based on a batch framework as the recurring processing component, Azure file share, Azure MS flow, in order to read and write files to and from the end user’s file share to Azure file.
As a cloud data integration service, it supports end users needing to have numerous file-based data exchanges between Dynamics 365 for Finance and Operations. The end user previously had limitation on changing the old legacy system. This custom module in Dynamics 365 for Finance and Operations helps to read and write files according to the specifications provided by the end user.
| Pros | Cons |
|---|---|
| All custom code within Dynamics 365 for Finance and Operations can leverage all solution features | Error handling during failure scenarios needs to be customized, high level of monitoring logic needs to be developed |
| The solution is in the cloud and the execution can be monitored from Dynamics 365 for Finance and Operations | Azure flow has some license fees, and must be handled by the end user |
| Dynamics 365 for Finance and Operations Batch Engine is a bottleneck if the proper sizing has not been addressed when deploying the environment |
Conclusions
When it comes to Azure cloud integration between on-premise and cloud-based data, the underlying factor is budgetary:
- RIS is ideal for clients who don’t have the budget for enterprise level implementations like biz talk, logic apps, and have infrastructure limitations.
- Azure cloud-based approach is ideal for clients with a budget for Azure licensing cost.
Contact us for advice
For the 10th consecutive row, AlfaPeople has been recognized among the top 1% of Microsoft’s vast Partner Network as a leading consultancy firm for Microsoft Business Applications. With a number of premiere Azure integration services, including migration, our consultants are on hand to discuss your specific operational needs. Contact us today!
