With the increasing demand for new technology and the growing needs of businesses, most organizations cannot avoid some kind of integration with a 3rd party application. For our Dynamics 365 clients, we’ve built numerous integrations for organizations. These integrations have ranged from data based to functional based. However, integrating with a 3rd party always comes with its challenges. The main challenge I want to focus on in this topic is how to ensure integrations with 3rd parties run smoothly, even as the 3rd party application continues to evolve.
Tip 1: Understanding authentication expiration dates
In order to integrate between 2 applications, there are usually going to be credentials required. Whether these are application based credentials, user based credentials or token based, they likely have some kind of expiration date tied to them. It’s important to understand what that expiration is and for your team to have a plan in place to reset those credentials before they expire. Depending on the type of authentication needed and the policies in place, you could automate this. One way that you could do this is using Microsoft Flow, which allows power users to build workflows that integrate a diverse set of apps and services.
Tip 2: Knowing when updates to the 3rd party application will impact your integration
Many vendors have distribution lists that your team can request to be added to when changes are coming that could impact your solution. For example, as a Microsoft partner, we (and our clients) have received email notifications when authentication changes are being made to Dynamics 365 or when components are being deprecated. This gives our team sufficient time to plan ahead and prepare for any updates necessary to integrations that may be tied to those components. Reach out to the 3rd party and request…
