Support Engineering Weekly

About Support Engineering Weekly

Support Engineering Weekly is the podcast from the Support Engineering Blog, featuring technical conversations about Microsoft technologies, support engineering, troubleshooting, administration, architecture, operations, and modernization. Each week, we explore practical engineering challenges, technical decisions, and the deeper considerations behind keeping enterprise technology working. Visit Support Engineering Blog at https://blog.sadhan.ch/ (https://blog.sadhan.ch/)

Publisher

Support Engineering Blog

Category

education · technology

Language

en

Explicit

No

First episode

29 Aug 2026

Latest episode

8 Nov 2026

Latest episodes

21 episodes in the feed.

1. 

   8 Nov 2026

   Planner Premium Isn't Project Online — So What Is the Gap?

   Microsoft Project Online is approaching retirement - or, in this case, its retirement date has already passed. But replacing a project management platform is not as simple as moving tasks from one product to another. In this episode of Support Engineering Weekly, Alex and Maya examine the architectural differences between Project Online and Planner Premium, and why treating Planner Premium as a one-to-one replacement can put important business processes at risk. We begin by separating project execution from enterprise project and portfolio management. Planner Premium is well suited to structured collaborative execution, including task dependencies, milestones, timelines, and critical paths. But enterprise workloads may also depend on resource capacity planning, complex timesheets, financial forecasting, and cross-project management capabilities that require a different approach. The discussion explores Planner Premium’s technical boundaries, including task, resource, custom field, successor link, and project duration limits. We then examine the illusion of equivalence: why workload visibility is not the same as enterprise resource management, and why portfolio views do not automatically unify every project management system. From there, we look at the hidden dependencies that make migrations difficult: Power Automate flows, custom Power Apps, APIs, reporting, financial systems, governance, and the need to establish an authoritative plan of record. Alex and Maya then walk through a fit-gap assessment approach, from identifying the business capabilities teams actually use to classifying requirements, validating dependencies, selecting the right destination, and testing complex workloads in a pilot. Finally, we explore how different workloads may need different destinations—including Planner Basic, Planner Premium, Project Server, Dynamics 365 Project Operations, Project desktop, or archival for inactive projects. The central lesson: Don't replace the product. Replace the capability. Disclaimer: This episode discusses the Microsoft Project Online retirement date of September 30, 2026, which has already passed. The episode is being published after that date because an earlier publication slot was not available. The discussion reflects the retirement timeline referenced during the original recording. Chapters 00:00 — The Retirement Deadline and the Assumption 02:01 — Project Execution vs. Enterprise PPM 04:35 — Planner Premium's Technical Boundaries 07:44 — Visibility vs. Resource Management 11:29 — Dependencies, Governance, and Migration Risk 17:12 — Routing Workloads to the Right Platform 20:01 — Archive What No Longer Needs a Home Learn more: The full technical article, references, and supporting resources are available through the Support Engineering Blog at https://blog.sadhan.ch/.

2. 

   6 Nov 2026

   Microsoft Weekly — November 2–6, 2026

   Microsoft 365’s latest updates are reshaping how users communicate and collaborate—but beneath the cleaner interfaces, this week’s incidents reveal just how fragile cloud routing and data pipelines can be. Alex and Maya examine changes across Microsoft Teams, Teams Rooms, and Viva Engage, including minimized meeting controls, new chat sections, private event chat, and dynamic audiences. Then, they connect the user-facing symptoms to the infrastructure behind them: Exchange Online quarantine failures caused by a missing tenant identifier, duplicate emails triggered by abnormal SMTP headers, Copilot chat histories that appeared to vanish because of regional synchronization issues, and Copilot Cowork traffic throttled by an internal API loop. They also explore delayed usage reports, stale Copilot health data, and Microsoft Purview audit-log backlogs—and why reporting delays do not necessarily mean data loss. The episode closes with three practical lessons for support engineers: communicate UI changes before users are surprised by them, understand the fragility of backend routing and automated defenses, and distinguish telemetry pipeline problems from service or data loss. As Microsoft 365 services become more interconnected, dependency mapping and blast-radius analysis will matter more than ever. This episode is based on the Microsoft Message Center and Service Health updates covered for November 2–6, 2026. Chapters 00:00 Introduction: When Cloud Services Break 02:38 Microsoft 365 Collaboration Changes 08:18 Exchange Quarantine and Secure Failure 10:10 SMTP Forwarding and Duplicate Emails 12:05 Copilot Routing and API Loops 16:30 Telemetry Pipelines and Admin Visibility 20:30 Three Lessons for Support Engineers Learn more: Visit the Support Engineering Blog at https://blog.sadhan.ch/ (https://blog.sadhan.ch/) for the full articles, technical references, and additional support-engineering resources behind the discussion.

3. 

   1 Nov 2026

   Planner Premium: When Task Management Becomes Project Management

   When does a simple task list stop being enough to manage a project? A team can coordinate everyday work perfectly well with a basic task board. But when activities become interconnected, dependencies start affecting delivery dates, and leadership needs visibility into project risks, tracking individual tasks is no longer enough. In this episode of Support Engineering Weekly, Alex and Maya explore how Microsoft Planner Premium moves work management beyond basic task coordination into structured project delivery. The discussion begins with the four-stage Work Management Journey, from individual tasks and team coordination to structured projects and enterprise portfolio management. We examine the differences between Planner Basic and Planner Premium and explain why project complexity is driven by relationships between tasks rather than simply the number of items on a board. From there, we explore dependencies, milestones, timeline views, and critical path analysis. We look at how these capabilities help project managers understand cascading delays, identify delivery bottlenecks, and manage the actual constraints of a project rather than simply tracking incomplete tasks. The conversation then turns to licensing. Using a practical implementation example, Alex and Maya explain why organizations should assign licenses according to individual responsibilities rather than automatically licensing every project participant for premium capabilities. The discussion also examines how separating task execution from strategic schedule management can support better project governance. We then address the retirement of Project Online and what it means for organizations planning their next work management platform. Planner Premium is not an automatic replacement for every Project Online workload. We explore the enterprise decision framework and the different paths involving Planner Premium, Project Server Subscription Edition, and Dynamics 365 Project Operations. The episode also examines the four-stage adoption approach: assess, pilot, govern, and scale. We discuss why successful adoption requires measurable behavioral evidence, why the organization must provide the project management method, and how administrators can evaluate whether teams are genuinely using structured planning capabilities. Finally, Alex and Maya explore the evolving AI experiences in Planner, distinguishing Planner Agent from Copilot in Planner. We examine how AI can accelerate project creation and reporting while also introducing the risk of generating poorly governed plans at greater speed. The central lesson is simple: Planner provides the mechanics, but the organization must provide the method. Technology can make structured project delivery possible, but human governance, accountability, and sound project practices remain essential. Chapters 00:00 — When Task Lists Stop Being Enough 02:15 — From Tasks to Structured Projects 05:53 — Dependencies and Critical Path 09:11 — Premium Licensing by Role 13:00 — Project Online Retirement and Migration Paths 18:00 — Adoption, Governance, and AI in Planner 22:26 — Choosing the Right Work Management Model Learn more The full technical article, references, and supporting resources are available through the Support Engineering Blog (https://blog.sadhan.ch/).

Reach and audience

Public platform figures. Ratings count people who left a rating, not total listeners.

Spotify

5.0 / 5

1 ratings

Contact Support Engineering Weekly

Guest appearances

Does not typically book guests

Based on episode analysis; this does not confirm that the show is currently accepting guests.