Microsoft Power Platform and Dynamics 365 CE PowerApps
We try out AI, we hear about AI, we layer on AI tools, but what needs to be considered is how the whole infrastructure aligns with the business application feature sets such as the features in Microsoft Dynamics 365 Customer Engagement (Configured for your industry) layered on top of common features such as Sales, Customer Service, Contact Center, Field Service and more..
For the last few years Microsoft has been quietly (or perhaps not so quietly) adding Copilots to every feature within every business application and within the development tools that feed those applications. The last I counted there were at least 150 different Copilots and they add the steroids to the features (sometimes more, sometimes less). Sure, we could search on activity history, but now we have a Copilot that summarizes that history for us and that is just one example of many.
It is not getting people to “Add Data” into their CRM system, it is providing the ability for people to get data out when they need it and from where they need it from.
The Visual Reporting (Power BI) and the Dynamics Views that tie easily to Excel (for people who just do not want to give up Excel), the Dashboards that pull from the Dataverse and sometimes from many other sources of data and the power of predictive data.
For those living on the bleeding edge, Copilots are just part of their every day productivity and now they are embracing all of the new Agents and Agents that talk to other Agents. The Sales Research Agent in Microsoft Dynamics 365 is just “there” and part of your Spring menu. As a development team, we don’t have to work magic to get multiple vendor offerings aligned to provide you with Agent power and clients don’t have to juggle multiple vendor pricing and as a +1 Copilot Studio allows us to quickly configure agents based on your needs.
Sales Research running in Microsoft Dynamics 365 Sales with the Microsoft Teams Embedded open.
The Sales Research Agent Menu Item in Microsoft Dynamics 365 Sales
As much as we all love to hate Microsoft when any gap is stepped into. They are pushing the envelope hard with all of their development and product teams. The key is to work with teams who know the FIT/GAPs and although GAPS disappear as fast as the technology changes knowing and listening to the key variables is a critical way to avoid frustrations.
In this day of Big Data Centers and incredible compute power, we often forget to think hard about what might impact performance.
Performance is not about the speed of the processor or the speed of your computer. Performance is all about managing the bottlenecks.
If you have the fastest car in the world and you are on a highway where the toll bridge is raised, you are not going to go very fast. The cars in front of you are stopped and the road is unavailable.
There are two areas in Microsoft Dynamics 365 Customer Engagement architecture that people need to be aware of when configuring the system.
The first is often ignored. “Sharing” If you allow your users to “Share” various components you are basically asking for an exception. This exception needs to bypass all Role Based Entitlement architecture and internal user access and give exception to the person an individual is sharing too. As a best practice we try to limit sharing and prefer to architect with good requirements and needs in mind.
The second is Role Based Entitlement security roles. If you have 100s of role based entitlements and you layer these extensively, your performance will be impacted. Minimal layering of security roles is encouraged, heavily redundant layering of the same permissions in every role or excessive layering (more than 10) causes the system to do some pretty heavy lifting. We architect with these key concepts in mind.
Tips:
Know your bottlenecks for any application and infrastructure footprint.
Know if your vendor has created an application bottleneck. Microsoft Dynamics 365 Customer Engagement modules do not have application bottlenecks, but extensions (custom code) and some customizations can create some.
Know all about the API calls, by design many vendors will restrict total number of API calls per day (throttle) given that millions of API calls can create performance bottlenecks for other users.
Use the free Microsoft Dynamics 365 tools to check for SDK role breakers such as solution checker.
As we slowly begin to adapt to the warmer temperatures and as the flowers emerge my thoughts turn to all of the work that has been happening behind the scenes when it comes to the Spring 2026 Major upgrade and release for Microsoft Dynamics 365 Customer Engagement.
As many know, Microsoft has been obsessed with creating Agents, Agent Template libraries and all of the associated derivatives. Agents that call other Agents and that totally change the way we work.
If you want to dip your toes into the new features, you can start here.
A Reference Architecture for Financial Services Institutions
Delivering Trusted, Compliant, and Intelligent Client Experiences
In financial services, customer experience is inseparable from trust. Whether the interaction occurs in a branch, through a relationship manager, or via a digital channel, institutions must balance personalization with regulatory rigor, data privacy, and operational resilience.
Microsoft Dynamics 365 Customer Engagement (CE), built on the Power Platform with Microsoft Dataverse and integrated with Microsoft 365, and optionally Microsoft Fabric, provides financial institutions with a modern reference architecture that does exactly that, connecting client engagement, compliance, and intelligence on a single, governed platform.
This architecture enables banks, insurers, and capital markets firms to move from fragmented client data and disconnected processes to a unified, auditable, and insight‑driven operating model.
Dynamics 365 Customer Engagement supports core client‑facing functions across the financial services lifecycle:
Sales and Relationship Management for commercial, and wealth clients
Client Service and Case Management aligned to SLAs and regulatory obligations
Client Onboarding, and Lifecycle Events
Targeted Marketing and Client Communications
What differentiates Dynamics 365 CE in financial services is not just functionality, it is the underlying platform architecture that ensures controls, organization, reduced complexity, transparency, and scale.
The Common Data Universe, “Dataverse” = The Trusted Client Data Backbone
At the heart of the architecture is Microsoft Dataverse, serving as the operational system of record for client engagement data.
For financial institutions, Dataverse provides:
A canonical client data model across accounts, account hierarchies, households, contacts, relationships, products, and interactions
Granular security controls, including row‑level and field‑level access to protect PII information
Full auditability, supporting regulatory and internal compliance requirements
Policy‑driven business logic, ensuring consistent execution of onboarding, servicing, and escalation processes
Dataverse becomes the “single version of the truth” for client engagement—controlled, governed, and resilient.
Integration with Microsoft 365: Secure Productivity for Front Office Teams
Relationship managers, advisors, and service agents like to live in Outlook or Teams or Excel or all three. Dynamics 365 CE integrates client data directly into these tools while maintaining compliance boundaries.
Examples include:
Outlook and Teams integration for secure client communications and internal collaboration linked to client records
Excel integration for controlled analysis and data updates, without exporting sensitive data unmanaged
Document management with retention and compliance policies enforced
This integration improves productivity while ensuring that interactions remain traceable and compliant.
Azure Data Lake: Analytical Scale Without Risk
Operational systems like Dataverse are designed for transaction integrity, not massive analytical workloads. To meet regulatory reporting, risk analysis, historical point in time analysis, and other advanced analytics needs, data is replicated to Azure Data Lake using Dataverse Synapse Link.
This enables:
Near‑real‑time replication of client engagement data
Secure, read‑only analytical copies of operational data
No performance impact on client‑facing systems
For financial services, this separation is critical. It ensures that reporting, risk modeling, and analytics never compromise operational stability or data integrity.
Microsoft Fabric: Intelligence, Risk Insight, and Regulatory Reporting
Microsoft Fabric provides a unified analytics and AI platform built directly on Azure Data Lake. In Dynamics 365 architecture, Fabric powers even more enterprise intelligence.
Key financial services use cases include:
Client profitability and relationship analytics
Conduct risk and service quality monitoring
Regulatory reporting and supervisory analytics
Advanced AI and predictive modeling, responsibly governed
Fabric enables institutions to move beyond static reporting toward continuous insight—all while maintaining lineage, governance, and security.
Power Platform: Controlled Agility
Across this architecture, the Power Platform enables innovation without sacrificing control and it supports the constant change of technology so Enterprise Accounts don’t fall behind. We also get
Power BI which delivers trusted dashboards to executives and regulators
Power Automate which orchestrates exception handling, business process automation and cross‑system workflows
Power Apps which can extend customer engagement processes, subset features into department specific needs and safely and efficiently deliver results
This allows financial institutions to adapt quickly to regulatory change and evolving client expectations.
High Level Architecture
The diagram below illustrates how these capabilities come together in a financial services context where you might have people outside of the enterprise accessing and offering a subset of data through Power Page Portals and where inside the Enterprise people are using Single Sign on authentication and leveraging off of Microsoft 365 Office with Microsoft Dynamics 365 Customer Engagement Apps.
Flow Overview:
Client interactions occur across branches, contact centers, and digital channels
Dynamics 365 CE orchestrates engagement and process execution
Dataverse serves as the secure, auditable system of record
Microsoft 365 enables compliant productivity and collaboration
Azure Data Lake and/or Microsoft Fabric deliver analytics, AI, and regulatory insight
Why This Architecture Matters for Financial Leaders
From an executive perspective, this architecture enables:
Client‑centric growth without compromising compliance
Regulatory confidence through auditable, governed data flows
Operational resilience via clear separation of transactional and analytical workloads
AI readiness grounded in trusted, secure data
In an era where regulators, clients, and markets demand both transparency and intelligence, this is not just a technology architecture—it is a strategic advantage.
Final Thought
Financial institutions that modernize client engagement on Dynamics 365, Dataverse, Microsoft 365, Azure Data Lake, and Fabric are not simply upgrading CRM systems. They are establishing a platform for trusted growth—where every client interaction is compliant, contextual, and informed by real‑time insight.
If you’d like, I can:
Adapt this article for banking vs. insurance vs. wealth management
Add Copilot and AI scenarios specific to financial services
Create a board‑ready version focused on risk, ROI, and transformation outcomes
One of the most critical concepts to understand when thinking about Microsoft Dynamics 365 Customer Engagement is the centralized experience of the Common Data Universe (Dataverse). When working with Dynamics 365 Customer Engagement modules (or call them Microsoft Developed Power Apps), they are all sharing a common source. We can take this common source and extend it out into Microsoft Azure Data Factory or Microsoft Fabric, but it is not required.
“Predicting rainfall is an example of regression machine learning, as it will predict a numeric value for future rainfall by using historical time-series rainfall data based on factors, such as seasons.
Clustering is a machine learning type that analyzes unlabeled data to find similarities in the data.
Featurization is not a machine learning type, but a collection of techniques, such as feature engineering, data-scaling, and normalization.
Classification is used to predict categories of data.”
Should you use OpenAI directly or go through Microsoft Azure OpenAI? While both offer access to powerful models like GPT-4 and DALL·E, the differences in deployment, governance, and enterprise readiness are substantial.
Azure OpenAI is a collaborative service between Microsoft and OpenAI, designed for enterprise use. It provides access to the same models as OpenAI directly (GPT-4, GPT-4 Turbo, DALL·E, Whisper and more) but within the Azure cloud ecosystem.
What value does Azure Cloud bring?
Data residency and isolation: Ensures data stays within your Azure subscription
Enterprise-grade security: Role-based access control, encryption at rest, and compliance with Microsoft standards which have passed a large number of global certifications. More details can be found on the Microsoft Trust website. You don’t have to trust Microsoft, you can trust the industry regulation requirements that have been cross verified.
Integration with Microsoft stack: Seamless use across Microsoft 365, Power Platform, Dynamics 365 PowerApps, and Azure DevOps.
So in general consider Azure Open AI that extra layer of control and compliance. It also provides fine-tuning, embeddings, and custom deployment opportunities with an extra set of tools.
If you want more specific use cases this table might be helpful:
Azure AI Foundry supports Observability using some of the following evaluators:
Groundedness: measures how consistent the response is with respect to the retrieved context.
Relevance: measures how relevant the response is with respect to the query.
Fluency: measures natural language quality and readability.
Coherence: measures logical consistency and flow of responses.
Content safety: comprehensive assessment of various safety concerns.
So my word of the day is Groundedness, mostly because the “word” just jumped out at me as one of those new definitions for my brain, and in general vocabulary has other meanings for the growing generations.
In the Merriam-webster dictionary we find -> “Emotional and Psychological Context It can also describe a person who is mentally and emotionally stable, realistic, and unpretentious. Someone with groundedness is often seen as calm, mindful, and not easily swayed by external chaos. [merriam-webster.com]”
and in Psychology Today we get “Spiritual and Mindfulness Context Psychology Today defines groundedness as a sense of being fully embodied, whole, centered, and balanced in oneself and relationships. It’s associated with clarity, harmony, and a deep connection to the authentic self. [psychologytoday.com] “
So using the term as an evaluator trends towards a new sense of logic as we observe and evaluate AI results.
While both offer tools for publishing content online, they differ significantly in terms of flexibility, user experience, and ecosystem. So what are the key differences.
1. Ownership and Ecosystem
WordPress comes in two flavors: WordPress.com (hosted) and WordPress.org (self-hosted). The latter gives users full control over their site, including custom themes, plugins, and server access.
Typepad is a hosted platform owned by Endurance International Group. It offers a more controlled environment, which can be appealing to users who prefer simplicity over customization.
2. Ease of Use
Typepad is known for its straightforward interface and minimal learning curve.
WordPress, especially the self-hosted version, has a steeper learning curve but offers far more flexibility. The block editor (Gutenberg) has improved usability, but beginners may still find it overwhelming.
3. Customization and Extensibility
WordPress shines in this area. With thousands of themes and plugins, users can tailor their site to virtually any need—from e-commerce to membership portals.
Typepad offers limited customization. While users can tweak templates and use some widgets, it doesn’t support the extensive plugin ecosystem that WordPress does.
4. Community and Support
WordPress benefits from a massive global community. Whether you need help with a plugin or want to hire a developer, resources are abundant.
Typepad has a smaller user base and community. Support is available via email and forums, but it’s not as robust or active as WordPress’s.
5. SEO and Performance
WordPress offers powerful SEO plugins like Yoast and Rank Math, giving users granular control over metadata, sitemaps, and more.
Typepad includes basic SEO features, but lacks the depth and flexibility that WordPress provides.
6. Cost
Typepad is subscription-based, with pricing tiers depending on features and bandwidth.
WordPress.org is free, but users must pay for hosting, domain registration, and any premium themes or plugins. WordPress.com offers free and paid plans.
