In today’s blog post, I will showcase how you can leverage Catalog in Power Platform to share solutions and reuse components across your organization. This is especially relevant if your organization is trying to leverage the replication operating model, where you have a template of solutions that you try to reuse across multiple implementations. 1. Catalog in Power Platform The Catalog in Power Platform is a set of solutions and packages that you can pick up off the shelf and install in any environment.

In this post, I will try to explain the inner workings of Copilot and how we can preprocess prompts with additional data to generate better responses from the underlying Large Language Models. I will finish it off with an example of how this theory could be manifested and used in practice. 1. Background 1.1 Dynamics Customer Service Copilot Surly you have heard about Dynamics Customer Service Copilot by now. The product comes in the way of a chat side pane integrated within Dynamics and lets you generate email replies, summarize cases, and generate responses based on knowledge articles.

Recently I had the opportunity to click around in a Legacy System. This got me thinking about the evolution of IT systems and how legacy systems still are in use even though there is newer technology out there. Changing IT systems truly is a painful thing, and it is even worse for a business-critical system. This article aims to first compare Dataverse to legacy systems and then advise on how you can improve your legacy system by making some architectural changes.