Couverture de M365.FM - Modern work, security, and productivity with Microsoft 365

M365.FM - Modern work, security, and productivity with Microsoft 365

M365.FM - Modern work, security, and productivity with Microsoft 365

De : Mirko Peters - Founder of m365.fm m365.show and m365con.net
Écouter gratuitement

Welcome to the M365.FM — your essential podcast for everything Microsoft 365, Azure, and beyond. Join us as we explore the latest developments across Power BI, Power Platform, Microsoft Teams, Viva, Fabric, Purview, Security, and the entire Microsoft ecosystem. Each episode delivers expert insights, real-world use cases, best practices, and interviews with industry leaders to help you stay ahead in the fast-moving world of cloud, collaboration, and data innovation. Whether you're an IT professional, business leader, developer, or data enthusiast, the M365.FM brings the knowledge, trends, and strategies you need to thrive in the modern digital workplace. Tune in, level up, and make the most of everything Microsoft has to offer. M365.FM is part of the M365-Show Network.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.Copyright Mirko Peters / m365.fm - Part of the m365.show Network - News, tips, and best practices for Microsoft 365 admins Politique et gouvernement
Épisodes
  • The End of EWS: Migrating to Microsoft Graph with Glen Scales [MVP]

    The End of EWS: Migrating to Microsoft Graph with Glen Scales [MVP]
    May 20 2026
    The retirement of Exchange Web Services (EWS) marks one of the biggest transitions in Microsoft messaging development in nearly two decades. For organizations still relying on legacy Exchange integrations, migration is no longer optional — it is urgent. In this episode of the m365.fm podcast, Mirko Peters sits down with longtime Exchange developer, Microsoft MVP, blogger, open-source contributor, and messaging expert Glen Scales to discuss the end of EWS, the future of Microsoft Graph, and what developers and organizations need to do right now before Microsoft permanently disables EWS in Exchange Online. With more than twenty years of experience building against Exchange APIs, Glen has lived through nearly every generation of Microsoft messaging development — from CDO and WebDAV to EWS, OAuth, and Microsoft Graph. His blog posts, GitHub repositories, Stack Overflow answers, and Substack articles have helped thousands of developers solve real-world Exchange and Microsoft 365 challenges. This conversation dives deep into API evolution, migration strategies, Graph limitations, mail architecture, authentication, throttling, notifications, synchronization, PowerShell automation, and the changing future of enterprise messaging development.WHY THE END OF EWS MATTERS Microsoft will retire Exchange Web Services in Exchange Online beginning in October 2026, with full removal completed in April 2027. That means:Applications using EWS against Microsoft 365 will stop workingOrganizations must identify legacy dependencies nowVendors and internal development teams need migration plans immediatelyOld synchronization models may need redesignsSecurity and permission models must be modernizedGlen explains that many organizations still do not realize how deeply EWS is embedded inside older enterprise applications, migration tools, CRM systems, provisioning systems, custom workflows, and legacy automation scripts. Some organizations may even discover unknown EWS dependencies years after original developers left the company.HOW EXCHANGE DEVELOPMENT EVOLVED One of the most fascinating parts of the episode is Glen’s perspective on the evolution of Exchange development itself. He describes how messaging development once represented some of the most advanced enterprise programming work available. Back in the early Exchange days, APIs like MAPI and EWS offered developers extremely deep access to mailbox data, calendar structures, public folders, and messaging workflows. Over time, Microsoft shifted toward:Cloud-first architectureREST APIsJSON payloadsOAuth authenticationGranular permissionsSecurity-first developmentWebhook-based integrationsMicrosoft Graph standardizationThis transition fundamentally changed how developers build integrations and applications around Microsoft 365 workloads.WHY MICROSOFT GRAPH IS THE FUTURE According to Glen, Microsoft Graph represents a major architectural shift compared to EWS. While EWS relied heavily on SOAP and XML, Microsoft Graph uses modern REST APIs and JSON payloads, making development easier, faster, and far more compatible with modern frameworks and open-source tooling. Microsoft Graph also introduces:Better OAuth authenticationGranular permissionsImproved security boundariesModern SDK supportCross-platform developmentWebhook supportDelta synchronizationModern integration patternsGlen explains that the biggest security issue with EWS is impersonation. In many EWS scenarios, applications receive extremely broad mailbox access, creating significant security risks in modern enterprise environments. Graph changes this by allowing applications to request only the minimum permissions required.THE BIGGEST CHALLENGE: MIGRATION The core challenge organizations now face is migration. Glen explains that simple email workloads are relatively easy to migrate from EWS to Graph because feature parity is already strong for common CRUD operations and mail handling. However, more complex workloads become significantly harder:Calendar synchronizationTasks and To-Do integrationsPublic folder accessCustom MAPI property usageLegacy formsNotification architecturesSynchronization enginesEnterprise migration toolingMany older applications were designed around EWS assumptions that no longer exist in Graph.STREAMING NOTIFICATIONS VS WEBHOOKS One of the most technical and insightful parts of the discussion focuses on notifications and synchronization. EWS supported:Pull notificationsPush notificationsStreaming notificationsGraph primarily relies on webhooks. This introduces major architectural changes because organizations now need:Public endpointsCloud-accessible infrastructureModern event processingQueue-based architecturesNotification deduplicationBetter retry logicGlen explains that older EWS streaming notification systems often struggled in cloud environments because mailbox moves could silently break persistent connections. Modern Graph webhooks behave far better in cloud-native architectures.DELTA ...
    Afficher plus Afficher moins
    48 min
  • From DAX to Community: The Power BI Journey with Bernat Agulló Roselló (MVP)

    From DAX to Community: The Power BI Journey with Bernat Agulló Roselló (MVP)
    May 20 2026
    Behind every great Power BI solution is more than just dashboards and data models. There is logic, automation, storytelling, optimization, architecture, and most importantly — community. In this episode of the m365.fm podcast, Mirko Peters sits down with Bernat Agulló Roselló, Microsoft MVP, Senior BI Developer Partner at Sabrina, Tabular Editor contributor, organizer of the Power BI & Fabric Barcelona User Group, and one of the most passionate voices in the Power BI community today. From DAX optimization and semantic model automation to community building and multilingual collaboration, this conversation explores the technical depth and human side of modern Business Intelligence. Bernat shares his journey from Excel macros and reporting automation to becoming a recognized expert in DAX, Tabular Editor scripting, semantic modeling, and enterprise Power BI development. But this episode is not just about technology. It is also about curiosity, learning, international experiences, and the incredible role that community plays in shaping careers, opportunities, and innovation across the Microsoft Data Platform ecosystem.THE JOURNEY FROM EXCEL TO POWER BI Bernat’s BI journey started long before he officially realized he was working in Business Intelligence. While working with Excel macros inside manufacturing environments like Nissan, he was already building reporting automation, aggregating data from multiple sources, and solving business reporting challenges long before terms like “semantic modeling” or “data warehousing” became part of his vocabulary. Eventually, after reading Kimball’s Data Warehouse Toolkit and diving deeper into BI concepts, Bernat recognized that he had already been practicing many foundational Business Intelligence principles for years. This realization sparked a deeper passion for analytics, Power BI, DAX, automation, and semantic modeling that continues today. WHY DAX CHANGES EVERYTHING One of the strongest technical themes throughout the episode is DAX — Data Analysis Expressions — the language behind Power BI calculations and advanced analytics. According to Bernat, one of the biggest misconceptions people have about DAX is assuming it behaves like Excel formulas. In reality:DAX depends heavily on semantic modelsRelationships are criticalFilter context changes everythingMeasures and calculated columns behave fundamentally differentlyUnderstanding context transition is essentialBernat explains how learning the foundations of DAX and semantic modeling completely changes how developers approach Power BI solutions. He strongly recommends that anyone serious about Power BI eventually studies “The Definitive Guide to DAX” by Marco Russo and Alberto Ferrari — a book that fundamentally shaped his own understanding of the platform.THE POWER OF TABULAR EDITOR Another major focus of the discussion is Tabular Editor and why it has become one of the most important tools for advanced Power BI and semantic model development. Bernat explains how Power BI Desktop works well for getting started, but as enterprise semantic models become larger and more complex, development workflows quickly become difficult to manage. Tabular Editor enables developers to:Manage large semantic models efficientlyEdit measures fasterAccess advanced model propertiesWork with calculation groupsBuild reusable automation scriptsImprove semantic model governanceOptimize development workflowsAutomate repetitive tasksFor advanced BI developers, Tabular Editor becomes a critical productivity multiplier.AUTOMATION IS THE FUTURE OF POWER BI DEVELOPMENT One of the most exciting parts of the episode focuses on automation using C# scripting, Tabular Editor, and semantic model tooling. Bernat shares how his background in Excel macros naturally evolved into Power BI automation and eventually into advanced Tabular Editor scripting. Through automation, developers can:Generate calculation groups automaticallyBuild reusable semantic model patternsCreate dynamic measuresStandardize formattingReduce manual development workImprove consistencyEliminate repetitive tasksScale semantic model developmentAccording to Bernat, automation does not just save time — it dramatically improves developer experience and mental health by removing repetitive, error-prone tasks. He estimates that automation can realistically save BI teams up to 40% of their development time.WHY REPETITIVE TASKS SHOULD DISAPPEAR One of the most practical insights from the conversation is Bernat’s philosophy around repetitive work. He strongly believes developers should spend less time copying logic, recreating measures, and manually repeating patterns — and more time solving meaningful business problems. This includes:Dynamic measure generationDAX UDF automationCalculation group templatingSemantic model standardizationMetadata-driven developmentDependency analysisMeasure reuse across reportsBy reducing repetitive tasks, teams become faster, ...
    Afficher plus Afficher moins
    50 min
  • From Deployment to Impact: Copilot Adoption That Works with Edyta Gorzoń (MVP)

    From Deployment to Impact: Copilot Adoption That Works with Edyta Gorzoń (MVP)
    May 19 2026
    Deploying Microsoft Copilot is easy. Driving real adoption, measurable impact, and long-term behavioral change across an organization? That is the real challenge. In this episode of the m365.fm podcast, Mirko Peters sits down with Microsoft MVP, Copilot Architect, adoption expert, and Copilot Team Lead at Billennium, Edyta Gorzoń, for a deep and highly practical conversation about what truly makes Copilot adoption successful inside modern organizations. While many companies focus heavily on licensing, governance, and technical rollout, Edyta explains why successful AI transformation is ultimately about people, communication, culture, and change management. Throughout the episode, she shares real-world lessons from customer projects, common mistakes organizations continue to make, and practical strategies that help companies move from simply deploying AI to genuinely transforming the way employees work. With more than a decade of experience in Microsoft technologies and a strong business background, Edyta brings a unique perspective to the AI conversation. Her focus is not just on technology itself, but on understanding users, organizational behavior, productivity patterns, communication strategies, and how businesses can create sustainable adoption models that actually deliver ROI.WHY COPILOT ADOPTION IS MORE THAN JUST TRAININGOne of the strongest themes throughout the episode is that Copilot adoption cannot be solved through generic feature-based training sessions alone. According to Edyta, many organizations mistakenly believe that purchasing Copilot licenses and scheduling a few training sessions automatically guarantees success. In reality, adoption requires a much broader strategy that includes governance, communication, behavioral change, scenario-based enablement, leadership involvement, and continuous support. She explains that organizations often experience temporary spikes in Copilot usage immediately after training sessions, only to see activity quickly decline again afterward. This happens because users never fully integrate AI into their daily workflows and routines. Building sustainable habits becomes far more important than simply delivering technical knowledge. CHANGE MANAGEMENT IS THE REAL DIFFERENTIATOR Edyta believes change management has become one of the most critical success factors for AI transformation projects. In previous Microsoft 365 adoption waves, organizations focused heavily on enabling tools like Teams, SharePoint, and OneDrive. But AI introduces entirely new emotional and cultural challenges:Fear of job replacementConcerns around data privacyDistrust in AI-generated contentResistance to changing workflowsUncertainty around productivity expectationsSome employees even feel that using AI is somehow “cheating” or replacing their own expertise. Because of this, Edyta emphasizes the importance of understanding user sentiment early in every Copilot project. Organizations need to understand how employees actually feel about AI before they can create effective communication and adoption strategies.COMMUNICATION IS EVERYTHING One of the most powerful insights from the episode is the importance of communication. According to Edyta, poor communication remains one of the biggest reasons why digital transformation projects fail. Organizations frequently launch AI initiatives using technical jargon, generic messaging, or overly abstract business language that employees simply do not connect with. Instead, communication must be:Tailored to different user groupsPractical and scenario-focusedEasy to understandBusiness relevantContinuous and visibleSupported by leadershipEdyta explains that IT professionals often unintentionally speak in highly technical language that business users do not understand. Terms like “tenant,” “connectors,” “governance,” or “grounding” may confuse non-technical employees immediately and create unnecessary resistance from the very beginning.WHY GOVERNANCE MATTERS BEFORE COPILOT Another major topic throughout the discussion is governance and technical readiness. Edyta strongly warns organizations against rushing into Copilot deployments without first reviewing their existing Microsoft 365 environments. Oversharing, poorly managed SharePoint permissions, inconsistent governance, and outdated collaboration structures can create major security and compliance risks once AI systems gain access to organizational data. She explains that:Copilot respects existing permissionsAI surfaces information dramatically fasterLegacy governance problems become visible instantlyPoorly structured data creates AI chaosDocumentation and governance become essentialOne particularly important recommendation is creating clear governance documentation that both technical and business stakeholders can understand. As AI teams increasingly combine IT, security, business, and compliance roles, organizations need a shared “single source of truth” around policies, ...
    Afficher plus Afficher moins
    56 min
adbl_web_anon_alc_button_suppression_c
Aucun commentaire pour le moment