Episodes

Microsoft Designer and Fabric Dataflows Gen2 are killing the busywork in marketing and analytics. Designer auto-applies your brand kit (fonts, colors, logos) to create on-brand assets in seconds—inside Microsoft 365 with real-time collaboration across SharePoint, OneDrive, and Teams. Dataflows Gen2 brings AI-assisted Power Query to unify messy campaign data fast and reliably. The result: fewer revisions, faster throughput, and more time for strategy and creative judgment—while humans still guard tone and brand integrity. If you’re ready to trust AI with the repetitive grind, this is how your marketing ops (and reporting) get faster, cleaner, and smarter.

Dev Tunnels in Visual Studio let you expose your local Teams, SharePoint, or Power Platform services to the internet in minutes—no Azure deploys required. Configure a named, persistent tunnel and use Private (authenticated) access tied to Microsoft Entra ID to keep tests secure and your OAuth redirect URIs stable. With real-time feedback in Microsoft 365, you’ll cut iteration loops, avoid “Final_v2” chaos, and standardize setup with the Dev Tunnels CLI. The biggest risk? Leaving a tunnel Public/anonymous—one missed setting can expose your entire dev box. Lock it down, log it, and shut it off when done.

Stop exporting Dynamics 365 data to Excel. Connect Dataverse to Microsoft Fabric, build an analytics model once, and embed Power BI directly inside Dynamics 365 (CRM/ERP) screens. With live, role-aware metrics (RLS), sales and ops teams act on fresh data without tab-switching, stale snapshots, or version drift. Use Fabric Data Factory/Dataflows Gen2 to shape data, enforce security with Entra ID and sensitivity labels, and place context-specific visuals in forms and dashboards. Result: faster decisions, fewer reconciliations, and a proactive, in-app analytics loop.

Auditing user activity in Microsoft 365 is no longer optional — it’s essential for security, compliance, and governance. Microsoft Purview provides powerful audit capabilities, but many organizations don’t use them correctly or fail to leverage advanced logging features. In this guide, we walk through how to enable auditing in Microsoft Purview, how to search and analyze audit logs effectively, and how to use audit data for threat detection, compliance investigations, and risk mitigation. Whether you're investigating suspicious behavior, preparing for a compliance review, or strengthening your security posture, this step-by-step breakdown shows you how to turn audit data into actionable insight.

Stop guessing where your data went. In Microsoft Fabric, automatic lineage, workspace-based permissions, and Purview’s enterprise catalog turn opaque pipelines into auditable, end-to-end flows—from ingestion to transformation to the report. Fabric captures every hop (Data Factory, Lakehouse, notebooks/SQL/Dataflows, semantic models, Power BI), enforces access consistently via workspace inheritance, and records who changed what and when. With Purview cataloging and classifications on top, you can search sensitive fields across workspaces, prove compliance with unified audit logs, and fix broken KPIs fast—without chasing email threads or exporting mystery CSVs.

Copilot can overreach if Graph permissions are too broad. One mis-scoped app permission lets AI surface files, spreadsheets, and confidential client data users couldn’t normally access. Fix it by treating Copilot like any high-privilege app: lock Graph scopes to least privilege, segment access with Entra ID role groups, and extend DLP and sensitivity labels to AI-generated content in Exchange, SharePoint, OneDrive, and Teams. Use Purview Audit to trace who asked Copilot for what, from where, and when—and pipe signals to Sentinel for proactive alerts. Governed right, Copilot stays fast and useful without leaking sensitive data.

MFA isn’t Zero Trust. If Microsoft 365 and Dynamics 365 don’t enforce the same identity, device, and session checks, attackers walk through the side door. “Zero Trust by Design” treats M365 + D365 as one system: align Conditional Access and risk signals, apply just-in-time roles, segment identities by job, and continuously re-verify sessions across clouds. Tie it together with adaptive policies that cut MFA fatigue. Result: coordinated defenses, fewer blind spots, and strong security that doesn’t slow work.

Stop waiting on dashboards. Fabric Data Activator turns live signals into instant actions—pausing bad pipelines, placing purchase orders, opening D365 work orders, or triggering API calls the moment thresholds hit. Because it’s native to Microsoft Fabric, it listens to streams and models from Power BI, Synapse, and the Lakehouse, then executes pre-approved playbooks with minimal latency. Start small with high-value triggers, design for capacity and downstream SLAs, and wire in guardrails so you get signal—not alert spam. That’s how you move from data-driven to data-activated.

Out-of-the-box Copilot in Dynamics 365 is a smart generalist. To make it an expert in your business, feed it your domain data—securely—via Dataverse, curated connectors, and Azure data pipelines. Map fields to clear schemas, apply role-based access and conditional access, and label sensitive columns so Copilot only sees what it should. With well-structured, compliant datasets (and ongoing monitoring), Copilot starts speaking your language—driving forecasts, recommendations, and workflows that match your reality, not an average model.

Stop torturing your laptop. Train models where the data lives. With Microsoft Fabric notebooks running on Spark next to your Lakehouse, you skip CSV exports, move terabytes at query speed, and iterate in Python or R without memory crashes. Push transforms to the data, engineer features at scale, monitor long runs in real time, checkpoint models, and evaluate across massive test sets—cutting days of wrangling into hours of results.

Turn “Where are we on Project Apollo?” into one accurate answer. Build a Copilot plugin that unifies Planner tasks, SharePoint milestones, and Teams context via Microsoft Graph + SharePoint REST, described by a clean manifest and secured with least-privilege Entra ID (Azure AD) OAuth. Result: one question in, one policy-compliant status out—no spreadsheets, no tab-hopping.

Dataverse “slowness” is often schema, not size. Fix table bloat, simplify relationships, and add the right indexes to turn crawling forms and timing-out flows into crisp responses. Design for performance from day one—balance normalization, limit cascades, and index what you filter on.

Viva Topics can surface gold—or noise. Turn AI guesses into trusted answers by triaging topics in week one, curating only what matters, merging duplicates without losing links, and designing rich, action-first topic cards. With the right governance, SMEs, and analytics, people stop “searching” and start finding.

Manual SharePoint reviews don’t scale. Use PnP PowerShell + Microsoft Graph + Azure Automation to enumerate every site, expand nested/group/inherited permissions, and deliver a clean, daily report. App-only auth, throttling-safe queries, and diff alerts turn a weeks-long audit into an automated, trustworthy pipeline.

Teams meetings can be a live work hub—not just video. Combine custom apps, in-meeting side panels, and Microsoft Graph meeting lifecycle events to surface live business data, run workflows, and trigger automation from the meeting itself. Wire the three together so the meeting behaves like an app: context-aware, real-time, and automated.

Viva Connections can be more than a pretty SharePoint homepage. Pair a solid foundation (navigation, targeting, permissions, mobile) with SPFx web parts and Adaptive Card Extensions (ACEs) to surface live business data and actions inside Teams. Build tiles that do work—approve, submit, track—then drive adoption with role-based personalization, performance discipline, and a measured change plan.

Stop context-switching. Embed Dynamics 365 Sales directly into Microsoft Teams so reps update opportunities, trigger approvals, and log notes where they already work. Layer Power Automate and Adaptive Cards to turn chats into actions (create/update/approve) and keep CRM as the single source of truth. Result: faster deal cycles, cleaner data, fewer misses.

Ever spent hours carefully building a SharePoint site, only to realize the next one looks and behaves completely differently? That frustration comes from manual setup—and it’s almost guaranteed to drift over time. This episode breaks down why hand-built SharePoint sites never stay consistent and how Site Scripts help you take control again. By defining branding, lists, and structure in a single JSON file, you can ensure every new site launches with the same look, layout, and core components, without relying on memory or checklists. But Site Scripts aren’t the whole story. When automation needs go deeper—like setting unique permissions, deploying custom web parts, or handling scenarios Microsoft doesn’t support natively—that’s where PnP PowerShell fills the gaps. Used together, Site Scripts handle predictable structure, while PnP PowerShell enforces the advanced configurations that keep sites secure and usable at scale. The episode also covers the real-world pitfalls of automatio…

Message extensions are the most overlooked productivity feature in Microsoft Teams. Instead of bouncing between apps to paste data, use the right extension for the job: Search extensions surface existing records on demand; Action extensions collect input, trigger back-end workflows, and return results via adaptive cards; Link unfurling turns pasted URLs into rich previews with instant context. The episode walks through building an action-based extension using the Teams SDK and Bot Framework to query external systems (like CRM or ticketing) and post structured, interactive results directly in chat—no context switching. You’ll also learn rollout gotchas: OAuth/SSO, permissions, privacy scope, manifest versioning, tenant-by-tenant deployment, and adoption tips. Pick the extension type that fits the workflow and Teams becomes a decision hub, not a copy-paste log.

Most Power BI environments start fast and stall under copy-paste sprawl: duplicated PBIX files, conflicting measures, and “spreadmart” dashboards that nobody fully trusts. The fix isn’t another naming convention—it’s a model-first architecture. Microsoft Fabric elevates the semantic model to an enterprise asset: one definitional layer reused across reports, workspaces, and teams. Pair that with calculation groups to eliminate endless YTD/QTD/TTM variants and keep time intelligence, KPIs, and business rules centralized and auditable. Add row-level security in the model to deliver true governed self-service—users explore freely while access is enforced automatically by role and region. The result: fewer datasets, consistent metrics, faster updates, and a BI stack that scales without chaos. If you’re tired of DAX drift and number debates, Fabric’s semantic models + calc groups + RLS turn scattered reports into a trustworthy analytics backbone.

Microsoft Fabric Lakehouse environments enable unified analytics across structured and unstructured data — but performance optimization is critical to ensure scalability, cost control, and reliable reporting. In this guide, we break down how to optimize Lakehouse performance in Microsoft Fabric, including data modeling strategies, partitioning best practices, query tuning, workload management, and storage optimization. Whether you're working with large datasets, real-time analytics, or enterprise reporting, these practical recommendations help you prevent bottlenecks and improve overall system efficiency. If your Fabric Lakehouse feels slow, unpredictable, or expensive — this is where to start.

Copilot is powerful—but out of the box it sees only Microsoft 365 content, missing the bulk of your organization’s knowledge in legacy wikis, CRMs, ticketing tools, and file shares. The fastest path to business-specific answers is Microsoft Graph Connectors. Unlike narrow plugins or brittle custom integrations, Graph Connectors bring external sources into the Microsoft Graph index with security trimming intact, so Copilot respects existing permissions while surfacing precise, contextual answers. Use connectors to index internal documentation portals, older SharePoint or MediaWiki sites, SQL/line-of-business systems, and platforms like Salesforce or ServiceNow—without risky migrations. The result: fewer “I can’t find it” moments, faster onboarding, and decision-making grounded in institutional memory. This guide explains when to choose connectors vs. plugins/APIs, how connectors work, a step-by-step rollout, and the ROI metrics to track so Copilot finally acts like it knows your busine…

“Add a connector” isn’t an AI strategy. Real deployments pair Power Apps or Dynamics 365 with Power Automate orchestration, Azure OpenAI for intelligence, and Azure API Management for security, throttling, and observability. This episode details the end-to-end pattern: clean and enrich payloads in flows, pick the right model and prompts per use case (classification vs. summarization vs. generation), cap tokens and rate-limit requests, and log everything. We cover scaling pitfalls (latency, runaway costs, hallucinations), security must-haves (key protection, IP restrictions, per-user quotas), and governance essentials (cost tags, budgets/alerts, the Power Platform CoE Starter Kit, audits). You’ll leave with a step-by-step build plan, KPIs to track, and guardrails to keep performance predictable and compliant—so your AI features move from demo to durable.

Most Graph-powered apps fail at rollout not because of code, but consent. Dev tenants allow broad testing; production enforces tight policies that block risky scopes. The fix is understanding Graph’s two models—delegated (user-in-context) vs. application (app-only, org-wide)—and requesting the minimum viable scopes that match how your app actually runs. Keep user data to delegated where possible; reserve app-only for unattended or cross-tenant jobs and plan for admin approval. Map tenant consent policies early, stage permissions (pilot → broaden), and document why each scope is required. Use least-privilege alternatives (e.g., Calendars.Read vs. Calendars.ReadWrite, Team.ReadBasic.All vs. full directory). Wrap with governance: pre-approval workflow, quarterly reviews, tagging, and audit logs. Result: fewer “admin consent required” popups, faster security sign-off, and a rollout that survives contact with real users.