Why Simplicity Wins in Microsoft 365 with Evi van der Velden [MVP]

Microsoft Cowork IQ Implementation: Architecting Scalable Knowledge Graphs for Modern Hybrid Workforces

Most organizations believe they have an AI problem when the real issue is their knowledge architecture. Microsoft Copilot deployments are exposing a deeper enterprise challenge: organizations cannot reliably structure, govern, connect, or retrieve the knowledge they already own. Employees still spend enormous amounts of time searching across SharePoint, Teams, OneDrive, emails, project workspaces, and disconnected business systems trying to find information that technically already exists somewhere inside the tenant.In this episode, Mirko Peters explains why successful enterprise AI deployments in 2026 depend less on the language model itself and far more on the semantic architecture underneath it. This deep technical conversation explores how organizations can design scalable Microsoft CoWork IQ and knowledge graph architectures that transform Copilot from a basic search experience into a trusted enterprise intelligence layer capable of reasoning across organizational knowledge. THE ENTERPRISE KNOWLEDGE PROBLEM Hybrid work dramatically increased knowledge fragmentation inside organizations. Institutional knowledge that once moved naturally through conversations, office interactions, and proximity is now scattered across disconnected systems, duplicated documents, forgotten Teams channels, and poorly governed SharePoint environments.This episode explores why modern organizations struggle with discoverability, semantic consistency, and AI readiness even after years of digital transformation investments. Mirko explains why enterprise AI systems fail when organizational context is weak and why generative AI has fundamentally changed what employees expect from enterprise knowledge systems. UNDERSTANDING MICROSOFT GRAPH & THE SEMANTIC INDEX Most organizations misunderstand what Microsoft Graph actually is. This episode explains how Microsoft Graph functions as a relationship and context engine connecting people, documents, meetings, identities, permissions, and collaboration signals across Microsoft 365.The conversation breaks down the three architectural layers powering modern Copilot experiences:The Microsoft Graph relationship layer, the Semantic Index for Copilot, and Fabric semantic models.Mirko explains how these systems work together to create meaning-aware retrieval experiences that allow AI systems to reason across organizational relationships rather than simply searching files by keyword. WHY COPILOT DEPLOYMENTS UNDERDELIVER Many organizations experience the same deployment pattern after rolling out Copilot. Early demos create excitement, but production usage slowly exposes retrieval problems, governance gaps, outdated citations, overshared content, and weak answer quality.This episode explains why these failures are usually not model problems. They are architecture problems caused by weak metadata structures, inconsistent governance, poor permissions hygiene, and disconnected content estates.The conversation explores how retrieval quality directly shapes AI reliability and why organizations that skip foundational information architecture work consistently struggle with trust and adoption. KNOWLEDGE GRAPHS IN MICROSOFT 365 Mirko breaks down what a knowledge graph actually means in a Microsoft 365 environment. The episode explores how entities, relationships, metadata, and organizational context combine to create AI-ready semantic architectures capable of supporting enterprise reasoning.Rather than functioning as a traditional search platform, a knowledge graph allows AI systems to traverse relationships between projects, people, systems, policies, documents, customers, and business processes in real time.The discussion explains how Microsoft 365 services including SharePoint, Teams, Entra ID, Purview, and Fabric semantic models contribute to building this organizational intelligence layer. METADATA AS AN AI CONTROL SYSTEM Metadata is no longer administrative overhead. In enterprise AI environments, metadata becomes a retrieval control system, a governance mechanism, and an AI trust layer.This episode explores how metadata quality directly affects:AI grounding, retrieval accuracy, semantic ranking, hallucination reduction, governance enforcement, and citation quality.Mirko explains the importance of provenance metadata, freshness metadata, authority signals, sensitivity classifications, and retrieval metadata in shaping the quality of enterprise AI responses.Without structured metadata, Copilot cannot reliably distinguish between current policies, outdated drafts, approved guidance, or sensitive content. GOVERNANCE FOR AI-FIRST ORGANIZATIONS Traditional governance models were designed for compliance reporting. AI systems require governance models built for semantic retrieval and continuous organizational change.This section explains the three governance disciplines modern organizations need:Readiness, Relevance, and Resiliency.The episode explores why permissions cleanup, lifecycle management, oversharing remediation, content recertification, and governance automation must happen before AI systems are deployed at scale.Mirko explains why governance is no longer separate from architecture. Governance now defines what AI systems can safely reason over. HARDENING THE SEMANTIC LAYER The Semantic Index is not just a productivity layer. It is a security boundary.This episode explores how organizations can harden semantic retrieval systems using:Sensitivity labels, Purview controls, item-level classification, Conditional Access, access recertification, and semantic exposure testing.Mirko explains why organizations must validate their retrieval surface before enabling Copilot broadly and why Microsoft Search can function as a visibility testing mechanism for semantic exposure risk. HALLUCINATIONS ARE A RETRIEVAL FAILURE One of the most important themes in this episode is that enterprise hallucinations are usually retrieval failures, not model failures.The conversation explores two major hallucination patterns:Retrieval-induced hallucinations and gap-filling hallucinations.Mirko explains how metadata-first RAG architectures improve retrieval quality through filtering, semantic reranking, provenance tracking, and retrieval routing strategies that prioritize trusted organizational sources over generic semantic similarity. BUILDING SCALABLE INGESTION PIPELINES Enterprise-scale knowledge graphs require ingestion pipelines capable of handling massive amounts of organizational content while preserving semantic quality.This section explores Bronze-Silver-Gold ingestion models, semantic chunking strategies, delta queries, webhook synchronization, Syntex taxonomy tagging, and Graph API optimization patterns.The episode explains why ingestion architecture directly influences semantic retrieval quality and long-term AI scalability. ENTERPRISE ONTOLOGY DESIGN Ontology design determines whether AI systems can reason across enterprise relationships effectively.Mirko explains the difference between taxonomy and ontology while exploring how organizations should model:Customers, projects, products, policies, processes, people, systems, and business relationships.The episode also explores the dangers of overengineering ontology structures and explains why organizations should begin with a minimal viable ontology tied to a specific business use case rather than attempting to model the entire enterprise upfront. ENTITY RESOLUTION & GRAPH QUALITY Modern enterprises store fragmented representations of the same organizational entities across multiple systems.This episode explores how entity resolution improves graph quality by identifying and consolidating duplicate organizational concepts, projects, customer references, and knowledge fragments into unified semantic entities.Mirko explains how clean entity resolution improves answer quality, semantic traversal, and retrieval accuracy across enterprise AI systems. SECURITY ARCHITECTURE FOR HYBRID WORK Enterprise AI security depends heavily on identity architecture.This section explores how Entra ID, Conditional Access, dynamic groups, Privileged Identity Management, and least privilege design shape the security boundaries of enterprise knowledge graphs.The episode also explores data residency, sovereignty requirements, global workforce governance, and agent security boundaries for distributed organizations operating across multiple regions. CONTINUOUS GOVERNANCE OPERATIONS Governance is not a one-time project. It becomes an ongoing operational discipline once AI systems are connected to enterprise content.This section explores governance automation, SharePoint Data Access Governance reports, Power Automate governance workflows, access reviews, taxonomy maintenance, semantic monitoring, and drift detection strategies.Mirko explains why governance drift is one of the biggest long-term risks facing enterprise AI deployments. FROM SEARCH TO PREDICTIVE INTELLIGENCE Once a knowledge graph matures, organizations move beyond reactive search and toward predictive organizational intelligence.This episode explores how graph-powered Copilot experiences enable:Context-aware retrieval, expert discovery, semantic collaboration, organizational memory systems, and proactive knowledge surfacing.Mirko explains why this shift is especially important for modern hybrid workforces that no longer benefit from the informal knowledge transfer patterns common in traditional office environments. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

ERP Modernization Without the Chaos with Alicia King [MVP]

Enterprise Resource Planning (ERP) modernization is no longer just a technology initiative — it is a business transformation journey that directly impacts people, processes, culture, and long-term growth. In this episode of the M365 FM Podcast, Mirko Peters sits down with Alicia King, Microsoft MVP, Pre-Sales Engineering Director at RSM US LLP, speaker, and ERP transformation expert, to explore what truly makes ERP projects successful. Drawing from more than 100 ERP transitions across 40+ countries, Alicia shares practical insights on Dynamics 365 Finance & Supply Chain, executive alignment, AI adoption, change management, data quality, and why leadership plays the biggest role in modernization success. WHY ERP MODERNIZATION IS REALLY ABOUT PEOPLE Alicia explains that ERP projects are often treated as technology deployments when they are actually people transformation programs. Organizations frequently focus too much on software capabilities while underestimating the importance of trust, communication, and cultural alignment. According to Alicia, successful ERP modernization starts with understanding where the company wants to go and aligning leadership, teams, and implementation partners around a shared vision. She emphasizes that businesses are not buying ERP systems simply to install software — they are investing in a better way to serve customers, improve visibility, and create scalable operations for future growth.  DYNAMICS 365 FINANCE & SUPPLY CHAIN EVOLUTION The conversation dives deep into how Microsoft Dynamics 365 Finance & Supply Chain has evolved over the years. Alicia discusses the transition from AX 2009 to AX 2012 and ultimately to Dynamics 365, highlighting how Microsoft transformed the platform into a more connected and holistic ERP ecosystem. Instead of relying heavily on disconnected third-party applications, organizations can now manage finance, manufacturing, warehouse management, asset management, project operations, and supply chain workflows inside one integrated platform. She also explains how Microsoft’s acquisition strategy helped consolidate critical ERP functionality directly into the Dynamics 365 core application, reducing complexity while improving visibility and operational efficiency.  THE BIGGEST ERP IMPLEMENTATION MISTAKES One of the strongest themes throughout the episode is the importance of executive alignment and realistic expectations. Alicia explains that many ERP projects fail because organizations underestimate the operational impact of transformation and overload employees who already manage full-time responsibilities. She stresses that ERP success requires strong project managers, transparent communication, proactive risk management, and leadership teams that actively support the change initiative. Without clear alignment between CIOs, CFOs, CEOs, and business leaders, ERP implementations can quickly become fragmented and lose direction. Key ERP implementation lessons from Alicia King include: * ERP projects fail when organizations ignore change management. * Clean and accurate data is essential for successful go-live execution. * Leadership must create psychological safety for employees during transformation. * ERP modernization should start with business objectives, not software features. CHANGE MANAGEMENT AND USER ADOPTION Alicia shares why user adoption remains one of the biggest challenges in ERP modernization projects. Even the most technically successful implementation can fail if employees resist using the system. She explains that many workers fear new ERP systems because they disrupt familiar processes and introduce uncertainty into day-to-day operations. Leaders must actively communicate why the transformation matters, reassure employees that they are supported, and personalize experiences inside Dynamics 365 to simplify adoption. The discussion highlights how personalization, workflow simplification, and training can dramatically improve ERP adoption rates across finance and supply chain teams.  DATA QUALITY, PROCESS DESIGN, AND ERP SUCCESS The episode also explores why poor data quality creates serious risks during ERP transformations. Alicia warns that organizations often underestimate the importance of costing, master data governance, and process redesign. Dirty data can create inaccurate reporting, incorrect profit margins, inventory issues, and customer service failures after go-live. She explains why organizations must design processes with the “end in mind,” focusing on how leadership wants to measure performance, profitability, and operational success before configuring the ERP platform itself.  GLOBAL ERP TRANSFORMATIONS AND LOCALIZATION Having worked across more than 14 countries, Alicia shares valuable perspectives on international ERP implementations, cultural differences, and localization challenges. She discusses how finance processes vary across regions, including IFRS versus GAAP reporting, VAT handling, statutory chart of accounts requirements, and country-specific compliance regulations. The conversation highlights why global ERP success requires flexibility, cultural awareness, and strong collaboration between international business units and leadership teams.  AI, COPILOT, AND THE FUTURE OF ERP Artificial Intelligence and Microsoft Copilot are rapidly changing the ERP landscape. Alicia explains how AI-powered supplier agents, predictive insights, and natural language interactions are helping organizations automate repetitive tasks and surface critical business information faster. Rather than replacing employees entirely, AI is shifting human work toward higher-value decision-making and strategic analysis. The discussion also covers governance, role-based security, Microsoft’s connected ecosystem strategy, and how organizations can responsibly adopt AI inside Dynamics 365 environments.  RAPID FIRE INSIGHTS FROM ALICIA KING Toward the end of the episode, Alicia shares several memorable leadership and career insights that resonate far beyond ERP modernization: * ERP systems are tools — they do not magically fix broken business cultures. * Future consultants must stay flexible and continuously learn AI technologies. * Companies should think about where they want their business to be in five years. * Growth happens when people learn to become comfortable being uncomfortable. FINAL THOUGHTS This episode delivers a powerful perspective on ERP modernization, leadership alignment, Microsoft Dynamics 365, AI-driven transformation, and the human side of enterprise technology projects. Alicia King combines real-world implementation experience with strategic leadership advice, making this conversation especially valuable for CFOs, CIOs, ERP consultants, Microsoft professionals, and digital transformation leaders navigating complex modernization initiatives. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

The Grounded Copilot: Building a Trusted Foundation for Enterprise AI

Microsoft Copilot gives answers that sound confident, polished, and intelligent. But in many enterprise environments, those answers are still incomplete, generic, or entirely wrong. The problem usually is not the model itself. The problem is grounding.In this episode, Mirko Peters breaks down the hidden architecture problem behind enterprise AI deployments and explains why most organizations are building Copilot on the wrong foundation from the start. If Copilot cannot access the systems where your company’s real knowledge lives, it cannot reason over the information your teams actually depend on every day. WHY COPILOT DOESN’T KNOW WHAT YOUR BUSINESS KNOWS Large language models are trained on public information. Your organization’s real intelligence lives somewhere else entirely.Critical operational knowledge is spread across systems like ServiceNow, Salesforce, Jira, Confluence, GitHub, SharePoint, internal databases, and legacy applications that Copilot cannot automatically access out of the box.That creates what Mirko calls the “Grounding Gap” — the distance between what Copilot can see and what your organization actually knows.Without grounding, Copilot defaults to generic responses. And generic AI responses quickly become a trust problem inside enterprise environments. THE REAL REASON USERS STOP TRUSTING COPILOT Most AI adoption problems are not caused by poor prompting. They are caused by poor architecture.When users repeatedly receive answers that feel vague, incomplete, or disconnected from operational reality, confidence disappears fast. Once teams stop trusting the AI, adoption quietly dies.This episode explains why grounding quality matters more than prompt engineering and why enterprise AI success depends on feeding the model the right organizational context before a response is ever generated. GRAPH CONNECTORS VS PLUGINS One of the biggest architectural decisions organizations face is choosing between Graph Connectors and Plugins.Mirko explains why these two models solve completely different problems: * Plugins are designed for actions and real-time transactions * Graph Connectors are designed for organizational knowledge retrieval * Plugins call live APIs at runtime * Connectors extend the Microsoft 365 Semantic Index * Plugins create operational workflows * Connectors create grounded AI reasoning Most organizations instinctively start with Plugins because they appear faster and simpler to deploy. But for enterprise knowledge retrieval, Connectors are almost always the better long-term architecture. INSIDE THE MICROSOFT 365 SEMANTIC INDEX This episode goes deep into how the Microsoft 365 Semantic Index actually works.Rather than functioning like a traditional search engine, the Semantic Index creates a pre-computed semantic map of organizational knowledge using embeddings, contextual relationships, and LLM-powered indexing.Mirko explains: * Why semantic retrieval changes Copilot quality * How embeddings are created at indexing time * Why retrieval speed matters for adoption * How organizational context improves reasoning * Why Graph Connectors become part of the same semantic knowledge layer as SharePoint, Teams, and Exchange This is one of the most important architectural concepts behind modern enterprise AI. THE HIDDEN COST OF CUSTOM RAG Custom RAG middleware often looks attractive to technical teams because it offers flexibility and full-stack control.But in real enterprise deployments, custom retrieval pipelines introduce: * Latency bottlenecks * Security complexity * ACL synchronization challenges * Governance overhead * Operational maintenance debt * Compliance exposure * Scaling problems Mirko explains why many organizations underestimate the long-term operational burden of running their own vector databases, orchestration layers, embedding pipelines, and retrieval infrastructure. SECURITY, GOVERNANCE, AND COMPLIANCE Security is not a policy problem. It is an architectural problem.This episode explains how Microsoft Graph Connectors inherit Microsoft 365 governance controls, including: * Entra ID access enforcement * DLP policies * Sensitivity labels * eDiscovery support * Retention policies * Compliance boundaries * Audit capabilities Mirko also explains why oversharing becomes dramatically more dangerous once AI systems make organizational content searchable through natural language prompts. SCHEMA DESIGN MISTAKES THAT HURT COPILOT One of the most overlooked parts of enterprise AI architecture is schema design.Poor property naming conventions and weak metadata structures silently degrade Copilot quality even when the connector itself is technically functioning correctly.This episode explores: * Why field naming matters to LLMs * How metadata influences reasoning quality * Why business-friendly schema design improves grounding * The importance of retrievable, searchable, and refinable properties * Common schema mistakes organizations make during connector deployments THE ACCESS CONTROL CHALLENGE ACL mapping is one of the hardest parts of connector deployment.Mirko explains how organizations must translate permissions from systems like ServiceNow, Salesforce, file shares, and legacy applications into Entra ID-based access controls that Microsoft Graph can enforce safely.Topics include: * Permission drift * ACL synchronization * External group mapping * Overexposure risks * Staged rollout strategies * Identity translation challenges THE GRAPH SECURITY CONNECTOR DEPRECATION This episode also covers the Microsoft Graph Security Connector deprecation currently affecting production environments.Mirko walks through: * What broke * Why existing Power Automate workflows are failing * The shift toward direct Microsoft Graph Security API integration * The move from alert-centric to incident-centric architecture * Migration planning considerations * Security automation modernization strategies This section is especially important for organizations using legacy security automation workflows. REAL-WORLD ENTERPRISE DEPLOYMENT PATTERNS The episode explores practical deployment scenarios across multiple industries and operational teams.Examples include: * IT helpdesk knowledge retrieval * ServiceNow incident grounding * Salesforce account intelligence * Engineering onboarding with GitHub and Confluence * Compliance policy retrieval * AI-assisted sales preparation * Enterprise search modernization These examples show how organizations are transforming Copilot into a domain-specific enterprise knowledge system rather than a generic AI assistant. WHY LATENCY DETERMINES ADOPTION AI performance is not just a technical metric. It directly changes user behavior.Mirko explains why response times above a few seconds dramatically reduce AI engagement and why retrieval architecture determines whether Copilot feels interactive or frustrating.Topics include: * Semantic Index retrieval speed * GPT-5.5 Instant latency improvements * Custom middleware performance tradeoffs * Caching limitations * Enterprise-scale retrieval patterns * User psychology and AI adoption THE ENTERPRISE AI IMPLEMENTATION CHECKLIST This episode finishes with a practical roadmap organizations can act on immediately.Key implementation steps include: * Auditing where organizational knowledge actually lives * Identifying the highest-value connector candidates * Cleaning permissions before indexing * Designing schemas specifically for Copilot grounding * Piloting deployments with limited user groups * Testing ACL enforcement carefully * Building governance processes before scaling KEY ENTERPRISE AI TOPICS COVERED * Microsoft 365 Copilot * Microsoft Graph Connectors * Enterprise AI architecture * AI governance * Semantic Indexing * Retrieval-Augmented Generation (RAG) * Enterprise search * AI grounding strategies * Security and compliance * Copilot Studio * Plugins vs Connectors * AI latency and performance * Organizational knowledge retrieval * AI adoption strategy * Enterprise AI governance Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

How Graph API Discovery Rewrites the Rules of Enterprise Semantic Search Performance

Enterprise search is broken — and most organizations still don’t realize why. The problem is no longer storage. It’s no longer indexing. And it’s definitely no longer about adding more servers to your search infrastructure. The real issue is latency between reality and discoverability. In this episode of the M365FM Podcast, we explore why traditional enterprise search models are collapsing under the pressure of modern AI workflows and how Microsoft Graph API discovery is fundamentally rewriting the rules of semantic search performance. Most enterprise environments still rely on scheduled crawlers and periodic indexing jobs that scan SharePoint, Teams, Exchange, and file repositories on fixed intervals. But modern work doesn’t happen on schedules anymore. It happens continuously — through Teams chats, Loop components, collaborative Excel sessions, live meetings, Copilot interactions, and high-velocity organizational signals. By the time legacy crawlers finish scanning enterprise data, the organization has already changed again. This creates what we call the “staleness gap” — the dangerous period where employees, executives, and AI systems are making decisions using outdated context. And once semantic search systems start serving stale information into AI pipelines, retrieval becomes a liability instead of an advantage. In this episode, we break down the architectural shift from pull-based discovery to event-driven discovery powered by the Microsoft Graph API. Instead of forcing search engines to continuously crawl massive repositories looking for changes, Graph discovery allows systems to subscribe to organizational events in real time. The result is sub-second freshness, massively reduced infrastructure overhead, and AI systems that actually understand what is happening right now — not what happened six hours ago. We also explore why this transformation goes far beyond search performance. Modern enterprise AI now depends on live context, security-aware retrieval, GraphRAG architectures, delta query synchronization, semantic lineage tracking, and compliance-aware ingestion pipelines. This episode dives deep into the future of enterprise intelligence systems and explains why Graph-based discovery is becoming the foundational layer for next-generation semantic infrastructure. IN THIS EPISODE * Why traditional enterprise search architectures are failing * The hidden cost of stale semantic indexes * How Graph API delta queries eliminate full crawls * The shift from “Pull” discovery to “Subscribe” discovery * Why semantic search performance is now measured in milliseconds * How GraphRAG changes retrieval reasoning across enterprise data * The security risks of vector stores and semantic leakage * Why security trimming becomes critical in AI retrieval systems * How live meeting intelligence transforms organizational decision-making * The future of real-time enterprise knowledge systems * Why compliance and data lineage are becoming mandatory by 2026 * How organizations can build sub-second AI retrieval pipelines * The infrastructure strategies behind modern Graph discovery engines * Why Graph API architecture creates a strategic competitive moat KEY TOPICS WE EXPLORE THE LATENCY CHASM Why enterprise search feels broken even when the infrastructure appears healthy — and how stale retrieval destroys trust in AI systems. EVENT-DRIVEN DISCOVERY How Microsoft Graph transforms discovery from a scheduled crawl into a real-time organizational nervous system.  DELTA QUERY ARCHITECTURE Understanding the breakthrough behind odata delta links, token state management, and scalable synchronization.  GRAPHRAG AND RELATIONAL REASONING Why flat vector retrieval is no longer enough for enterprise intelligence workflows. REAL-TIME GOVERNANCE How compliance, lineage tracking, and auditability are becoming performance requirements instead of optional controls.  SUB-SECOND RETRIEVAL The 250ms latency benchmark every enterprise AI system will need to hit to remain usable. SECURITY TRIMMING IN AI Why vectors alone cannot enforce permissions and how semantic leakage creates hidden enterprise risk.  WHO THIS EPISODE IS FOR This episode is designed for: * Microsoft 365 architects * Enterprise AI strategists * CIOs and IT leadership * SharePoint and Teams administrators * Graph API developers * Semantic search engineers * Security and compliance professionals * Copilot implementation teams * Knowledge management leaders * Enterprise platform architects If your organization is building AI retrieval systems, deploying Microsoft 365 Copilot, designing semantic search infrastructure, or modernizing enterprise discovery pipelines, this episode will completely change how you think about search performance and organizational intelligence. FINAL THOUGHT The future of enterprise search is not about finding documents faster. It’s about creating systems that stay synchronized with organizational reality in real time. The companies that master Graph discovery, event-driven retrieval, and live semantic infrastructure will move faster, make better decisions, and operate with a level of organizational awareness their competitors simply cannot match. This is the shift from navigation to context. And it changes everything. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].

Breaking the Scale Barrier: Building Multi-Tenant SaaS on Power Pages

Building multi-tenant SaaS on Power Pages changes the way architects think about Dataverse scalability. Most developers traditionally viewed Power Pages as a portal platform intended for forms, authentication, and moderate business applications. Enterprise-scale SaaS workloads were assumed to require fully custom Azure infrastructure and external databases. Elastic Tables challenge that assumption by introducing Cosmos DB-backed storage directly inside Dataverse, allowing Power Pages to support large-scale operational workloads while preserving the familiar Dataverse developer experience. WHY STANDARD DATAVERSE TABLES HIT LIMITS Standard Dataverse tables are optimized for relational transactional workloads such as CRM systems, account management, and business processes. They perform extremely well for structured business entities but begin struggling under workloads dominated by telemetry ingestion, event logging, audit history, and append-heavy operational data. As tenant counts grow, noisy-neighbor effects appear because all tenants compete for the same relational backend resources. The architecture problems become especially visible when SaaS platforms start accumulating massive volumes of operational records. Bulk write operations slow down, storage costs increase rapidly, and query performance degrades under high-ingestion scenarios. These are not flaws in Dataverse itself but rather signs that the workload no longer aligns with the strengths of Azure SQL-backed storage. * Azure SQL excels at relational workloads * Operational SaaS data behaves differently * Multi-tenant contention creates performance issues * Storage costs rise quickly at scale ELASTIC TABLES AND COSMOS DB Elastic Tables replace the underlying SQL engine with Azure Cosmos DB while preserving the same Dataverse APIs, security model, and Power Pages integration patterns developers already know. From the outside, the experience still feels like standard Dataverse development. Underneath, however, the storage model becomes horizontally scalable and partition-aware. Cosmos DB distributes records across logical partitions using PartitionId values. This enables Elastic Tables to scale write throughput horizontally rather than relying on a single database instance. Microsoft specifically designed Elastic Tables for telemetry, event streams, operational logging, and large append-heavy workloads that traditionally break relational systems at scale. * Horizontal partitioning improves scalability * Bulk ingestion becomes dramatically faster * TTL support enables automatic data expiration * Dataverse APIs remain unchanged for developers PERFORMANCE DIFFERENCES THAT MATTER Elastic Tables dramatically outperform standard tables during batch operations such as CreateMultiple and UpdateMultiple requests. Community benchmarks showed improvements ranging between two and ten times faster for bulk ingestion scenarios. This advantage exists because Cosmos DB distributes writes across partitions simultaneously rather than funneling all operations through a single relational engine. At the same time, Elastic Tables are not universally superior. Standard relational queries and traditional CRUD operations may still perform better on SQL-backed Dataverse tables. Successful SaaS architectures therefore separate operational workloads from relational business entities rather than attempting to move everything into Elastic storage. * Elastic Tables dominate high-volume writes * Standard tables remain stronger for relational queries * Batch ingestion benefits most from Cosmos DB * Hybrid architectures deliver the best results PARTITION STRATEGY DEFINES SUCCESS Partition design is the single most important Elastic Table decision because the partition key cannot be changed after deployment without migration. For multi-tenant SaaS platforms, tenantId naturally becomes the foundation of the partition model because nearly every query is scoped to a tenant context. Large enterprise customers introduce additional complexity. A single “elephant tenant” can overwhelm a partition if all records share the same partition key. Hierarchical Partition Keys solve this by introducing multiple partition levels such as tenantId, userId, and sessionId. This spreads traffic and storage evenly while preserving efficient query routing. The resulting architecture supports both small tenants and extremely large enterprise customers without requiring different application logic or separate development patterns.  SECURITY AND TENANT ISOLATION Security in multi-tenant SaaS depends on structural isolation rather than trusting developers to consistently apply tenant filters. The architecture combines Dataverse business units, web roles, table permissions, and partition-aware query routing to create layered tenant isolation across both the platform and storage layers. Business units define tenant boundaries inside Dataverse, while tenantId-based partition routing ensures Cosmos DB queries physically access only the relevant tenant partitions. This layered approach strengthens compliance readiness for SOC 2, ISO 27001, GDPR, and enterprise procurement reviews. * Business units isolate tenants at the platform layer * Partition routing isolates tenants at the storage layer * Web roles enforce frontend access permissions * Defense-in-depth improves compliance readiness POWER PAGES AS THE FRONTEND EXPERIENCE Power Pages functions best as the authenticated frontend experience layer rather than the ingestion engine itself. User-facing reads and writes operate through the Web API, while backend services such as Azure Functions or Power Automate handle high-throughput ingestion using CreateMultiple operations. This separation keeps portals responsive while allowing ingestion pipelines to scale independently. Query shaping, pagination, caching, and asynchronous loading patterns become essential for maintaining fast user experiences within Power Pages request limits.  JSON COLUMNS AND FLEXIBLE DATA MODELS Elastic Tables support JSON-based schema flexibility by allowing semi-structured metadata inside string columns. This enables tenant-specific customizations without requiring constant Dataverse schema changes. Entire activity feeds or operational datasets can be stored as compact JSON payloads instead of thousands of relational rows. The flexibility comes with governance responsibilities. Field-level security does not apply inside JSON structures, meaning sensitive information should always remain in strongly typed Dataverse columns where security policies can be enforced properly.  Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support [https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support?utm_source=rss&utm_medium=rss&utm_campaign=rss].