Skip to main content

Navigating Microsoft Dynamics 365 Customization: Plugins vs. Azure Functions

Embarking on the Microsoft Dynamics 365 customization journey offers numerous opportunities to enhance your business processes. However, deciding between the available options, such as Plugins and Azure Functions, can be challenging. This engaging post will serve as your trusty guide, helping you choose the best option for your Dynamics 365 customization needs!

The Two Customization Pathfinders: Plugin and Azure Function

The Agile Plugin 🏃‍♂️

Reference: Microsoft Docs - Write a plug-in

Plugins are like the swift trail runners of the Dynamics 365 customization world. They're the go-to choice for quick, real-time (synchronous), or background (asynchronous) operations that occur within the platform. They can intercept events and modify data before it's saved or displayed to the user.

Choose Plugins when:

  • You need real-time processing (synchronous) or background processing (asynchronous).
  • You want to ensure data integrity.
  • You need tight integration with Dynamics 365.

Plugins might not be the best choice for long-running processes, as they could slow down the overall performance of your system if synchronous or consume system resources if asynchronous.

The Powerful Azure Function 🚀

Reference: Microsoft Docs - Azure Functions Documentation

Azure Functions, like the high-powered rocket ships of the customization world, bring power and scalability to your Dynamics 365 customizations. They're perfect for more complex or compute-intensive tasks that require the full power of the Azure platform. Azure Functions can be triggered by various events and can interact with other Azure services, opening up a world of possibilities.

Choose Azure Functions when:

  • You need advanced processing capabilities or complex logic.
  • You require integration with other Azure services.
  • You want to leverage the power and scalability of Azure.

Azure Functions could be overkill for simple, real-time operations, so consider Plugins if your customization needs are more straightforward.

To integrate Azure Functions with Dynamics 365, you can create a custom connector in Power Apps, which can also be applied to Dynamics 365. This approach allows you to call your Azure Function from within your Dynamics 365 solution.


To recap, choose Plugins for real-time (synchronous) or background (asynchronous) operations with tight integration to Dynamics 365, and Azure Functions for advanced processing capabilities and integration with other Azure services. With this guide, you're now equipped to navigate the Dynamics 365 customization landscape and select the perfect customization pathfinder for your needs! 🌄


Popular posts from this blog

Validating User Input In CRM Portals With JavaScript

When we are setting up CRM Portals to allow customers to update their information, open cases, fill out an applications, etc. We want to make sure that we are validating their input before it is committed to CRM.  This way we ensure that our data is clean and meaningful to us and the customer. CRM Portals already has a lot validation checks built into it. But, on occasion we need to add our own.  To do this we will use JavaScript to run the validation and also to output a message to the user to tell them there is an issue they need to fix. Before we can do any JavaScript, we need to check and see if we are using JavaScript on an Entity Form or Web Page.  This is because the JavaScript, while similar, will be different.  First, we will go over the JavaScript for Entity Forms.  Then, we will go over the JavaScript for Web Pages.  Finally, we will look at the notification JavaScript. Entity Form: if (window.jQuery) { (function ($) { if (typeof (entityFormClientVali

Dynamics Set IFrame URL - D365 v8 vs. D365 v9

While doing client work, I came across a problem with setting an IFrame URL dynamically.  The underlying issue was that the sandbox instance is on v8 of Dynamics 365 and production is on v9 of Dynamics 365.  The reason for this was because this client was setup around the time that Microsoft rolled out v9.  Anyways, JavaScript that I wrote to dynamically set the URL of the IFrame wasn't working in the v9 instance.  This was because of changes that Microsoft made to how IFrames are loaded on the form and also changes to JavaScript. Here is my v8 setup: JavaScript runs OnLoad of contact form.  This works because of how IFrames are loaded in v8.  You can also run it on either a tab change (hide / show) or OnReadyStateComplete event of the IFrame.  Depending on your setup you will need to choose which is best for you.  For me in this case it was the OnLoad event. Here is the JavaScript: function OnLoad() { //Get memberid var value =

Report Authoring Extension Updated To Support Visual Studio 2019

 FINALLY, Microsoft has pushed an update to the Report Authoring Extension for Dynamics 365 to allow for use of Visual Studio 2019.  This update went live on 12/18/2020 and can be found here .  Installing won't be straight forward into Visual Studio 2019, even if you install everything when you first installed it.  This is because SSDT (SQL Server Data Tools) is installed but, SSAS, SSIS and SSRS are all separate modules for SSDT that you have to install separately.  While you should be fine with just installing SSRS to make this work, I would recommend just installing all 3 parts.   All of these can be found in Microsoft documentation .  In the "Install SSDT with Visual Studio 2019" section, you will see a link to the marketplace where you can download the extensions and install them.  Once that is done, download the Report Authoring Extension and run the installer.  That is it, you can now work on SSRS within Visual Studio 2019 for Microsoft Dynamics.