Building Custom Portal for Microsoft Dynamics 365 Customer Engagement

So, what if you want to create a Portal for your customers and you already use Dynamics 365 Customer Engagement? What technology should you choose? What will work best in what scenario? Do you want to build an up-to-date modern user experience for your customer?

I’m a Dynamics 365 technical architect with 12 years of experience with this product working from the very first versions. We build a lot of fully custom portals as well as do a lot of customizations based on the standard Microsoft Dynamics Portal.

Microsoft Dynamics Portal provided out-of-the-box now works always as the best option for any case. We examined it in the previous article.

  • However, what if you want to go far beyond the functionality Microsoft Dynamics Portal provides?
  • What if you have very specific UI requirements, or what if you have a lot of integrations required?

So let me share our experience on building complicated high-load solutions on different technologies for Dynamics 365 Customer Engagement

Therefore, in this particular article, we are talking about building a Portal solution from scratch.

You can also check my video on this topic:



Let’s review are key advantages of this approach, what are concerns, and what questions should you challenge to understand if the custom portal works for you.

Key Advantages and Concerns


  • High flexibility
  • High performance
  • Modern technologies and approaches
  • More integration options
  • More control over the solution roadmap and maintenance


  • Maintenance and implementations costs
  • Complexity of maintenance
  • Feature delivery timeline

When to Go with Custom Portal?

If you answer these questions positively, this might be your choice:

  • Do you have many users?
  • Do you want a modern solution on the latest technologies and UX?
  • Do you have enough budget to maintain development team costs?
  • Do you have multiple software you need to integrate with?
  • Do you have strict UI/UX or other requirements?


  • CMS based
  • Backend (.Net Core, PHP, Python, Go…)
  • Frontend (React, Angular, Vue, …)

Frameworks selection is out of the current scope discussion. But in case you want more details on this – please contact us.

Final Thoughts

So, if you have enough budget, big plans, and fancy UI requirements – building a custom portal for Microsoft 365 Customer Engagement might be your choice. In the end, you will receive something that will match exactly what you want (in the case of a professional implementation team of course), but be prepared to wait a little longer and spend a little more.

In the next article, we will discuss the integration of your existing Portal with Dynamics 365.