M365 Show with Mirko Peters - Microsoft 365 Digital Workplace Daily Titelbild

M365 Show with Mirko Peters - Microsoft 365 Digital Workplace Daily

M365 Show with Mirko Peters - Microsoft 365 Digital Workplace Daily

Von: Mirko Peters - Microsoft 365 Expert Podcast
Jetzt kostenlos hören, ohne Abo

Über diesen Titel

 The M365 Show – Microsoft 365, Azure, Power Platform & Cloud Innovation Stay ahead in the world of Microsoft 365, Azure, and the Microsoft Cloud. The M365 Show brings you expert insights, real-world use cases, and the latest updates across Power BI, Power Platform, Microsoft Teams, Viva, Fabric, Purview, Security, AI, and more. Hosted by industry experts, each episode features actionable tips, best practices, and interviews with Microsoft MVPs, product leaders, and technology innovators. Whether you’re an IT pro, business leader, developer, or data enthusiast, you’ll discover the strategies, trends, and tools you need to boost productivity, secure your environment, and drive digital transformation. Your go-to Microsoft 365 podcast for cloud collaboration, data analytics, and workplace innovation. Tune in, level up, and make the most of everything Microsoft has to offer. Visit M365.show.

m365.showMirko Peters Politik & Regierungen
Folgen
  • Ditch Passwords—How Real Azure Apps Secure Everything

    Ditch Passwords—How Real Azure Apps Secure Everything
    Oct 7 2025
    Here’s a fun fact: embedding credentials in your Azure apps is basically handing out house keys at a bus stop. Entra ID and managed identities let you lock every door without juggling keyrings or hoping nobody notices the Post-It note under your keyboard. The good news—you don’t need to be a cryptography wizard to do this. I’ll show you step by step how to swap secrets for tokens and sleep better at night.The Doormat Key ProblemWhy do so many Azure apps still stash passwords in config files like we’re all still writing VBScript in 2003? Seriously, it’s 2024. We have cloud-native security systems that mint tokens on demand, yet someone somewhere is still committing a literal `sa` password to their repo like it’s a badge of honor. And the excuse is always the same: “We hard‑code it just to save time.” Save time today, and then spend weeks cleaning up the mess when it leaks. That's not a shortcut. That’s procrastination with extra steps. The problem is bigger than laziness. Developers think dropping usernames and passwords into a web.config file or appsettings.json is harmless because it stays internal. Except nothing ever stays internal. That config gets copied to dev, test, staging, three different QA branches, backups, and a laptop someone left on a plane. That’s not a secret; that’s a distributed broadcast. Add in Git, where “oops, wrong push” has put more production passwords public than I care to count, and you’ve got an incident queue that writes itself. Here’s the part nobody likes to admit: these “quick fixes” don’t just risk exposure—they guarantee it over time. Secrets are slippery. They creep into log files because you forgot to sanitize an exception. They hide in screenshots shared over Teams. They get zipped into backups sitting unencrypted in blob storage because no one paid for the vault tier. All it takes is one bored attacker scanning public repos for obvious strings—`Password123!` is still a goldmine—and suddenly your entire app is wide open. One of my favorites? Remember when thousands of credentials showed up in public GitHub a few years back because devs used personal repos for “just testing”? Attackers didn’t even have to try. They ran keyword scans, found connection strings, and walked straight into production resources. No zero‑day. No Hollywood hacking montage. Just copy, paste, profit. That’s what hard‑coding secrets buys you—a house where the burglar doesn’t even need to pick a lock. The key’s under the mat, and you spray‑painted “KEY IS UNDER REACT APP SETTINGS” on the front porch. You wouldn’t leave your front door unlocked with the garage code written on a sticky note, but that’s exactly how connection strings behave when they include credentials. Sure, it works. Until a neighbor—by which I mean some anonymous botnet—figures out where you hid them. Microsoft has been very clear these days: hard‑coded credentials are being pushed into the same bucket as Internet Explorer and Clippy. Deprecated. You can limp along with them, but expect disappointment, breakage, and an audit log screaming at you. Add to that the sprawl problem. Each environment needs its own settings, so now you’ve got a password per dev box, an admin string in staging, another one production, and nobody knows if they’re rotated. Different teams hoard slightly out‑of‑date copies. Someone comments out an old connection string instead of deleting it. Congratulations: your app is a digital junk drawer of skeleton keys. Attackers love it because it’s a buffet. And let’s not even mention what happens when contractors get read‑access to your repos. You think they only take the code? The takeaway here is simple: the real danger isn’t just a password leaking. It’s the way secrets breed. Once you let them into configs, they replicate across environments, backups, scripts, and documentation. You cannot manage that sprawl. You cannot contain it with “clever” obfuscation tricks. It’s not a problem you patch; it’s a problem you eliminate. Stop thinking about where to hide the key. Instead, stop using keys at all. That’s why tokens exist. They don’t behave like passwords. They aren’t long‑lived, they aren’t static, and they don’t sit in files for years daring the wrong person to find them. The cure for password sprawl isn’t to hide the passwords better—it’s to replace them with something that self‑destructs when it’s misused. Tokens let you do exactly that, and Entra ID is the system handing them out. Okay, so if we throw the doormat keys away, how do tokens avoid turning into even messier problems for us admins? Let’s talk about why they actually make life easier instead of harder.Why Tokens Beat Passwords Every TimeIf passwords are car keys, tokens are valet tickets—you use them for a single ride, and they’re worthless once the trip’s done. Nobody makes a sneaky copy of a valet ticket, and...
    Mehr anzeigen Weniger anzeigen
    20 Min.
  • I Replaced 500 Measures Instantly—Here’s How

    I Replaced 500 Measures Instantly—Here’s How
    Oct 6 2025
    Ever stared at a Power BI model with 500 measures, all named like a toddler smashing a keyboard? That endless scroll of “what-does-this-even-mean” is a special kind of pain. If you want fewer helpdesk tickets about broken reports, hit subscribe now—future you will thank you when it’s cleanup time. The good news? Power BI now has project- and text-first formats that let you treat models more like code. That means bulk edits, source-control-style safety nets, and actual readability. I’ll walk through a real cleanup: bulk renaming, color find-and-replace, and measure documentation in minutes. And it all starts with seeing how bad those 500 messy names really are.When 500 Measures Look Like Goblin ScriptIt feels less like data modeling and more like trying to raid a dungeon where every potion is labeled “Item1,” “Item2,” “Item3.” You know one of them heals, but odds are you’ll end up drinking poison. That’s exactly how scrolling through a field list packed with five hundred cryptic measures plays out—you’re navigating blind, wasting time just figuring out what’s safe to click. Now swap yourself with a business analyst trying to build a report. They open the model expecting clarity but see line after line of nonsense labels: “M1,” “Total1,” “NewCalc2.” It’s not impossible to work with—just painfully slow. Every choice means drilling back, cross-referencing, or second-guessing what the calculation actually does. Seconds turn into minutes, minutes add up to days, and the simple act of finding the right measure becomes the real job. With a handful of measures, sloppy names are irritating but tolerable. Scale that up, and the cracks widen fast. What used to be small friction balloons into a major drag on the entire team’s productivity. Confusion spreads, collaboration stalls, and duplicated effort sneaks in as people re-create calculations instead of trusting what’s already there. Poor naming doesn’t just clutter the field list—it reshapes how people work with the model. It’s a bit like Active Directory where half your OUs are just called “test.” You can still hunt down users if you’re patient, but you’d never onboard a new hire into that mess. The same goes here. New analysts try to ramp up, hit the wall of cryptic names, and end up burning time deciphering the basics instead of delivering insights. Complexity rises, learning curves get steeper, and the whole workflow slows to a crawl. You feel the tax most clearly in real-world reporting. Take something as simple as revenue. Instead of one clean measure, you’ve got “rev_calc1,” “revenueTest2,” and “TotalRev_Final.” Which one is the source of truth? Everyone pauses to double-check, then re-check again. That delay ripples outward—updates arrive late, dashboards need extra reviews, and trust in the reports slides downhill. So people try to fix it the hard way: renaming by hand. But manual cleanup is the natural 1 of measure management. Each rename takes clicks, dialog boxes, and round-trips. It’s slow, boring, and guaranteed to fall behind before you’ve even finished. By the time you clean up twenty labels, two more requests land on your desk. It’s spoon-versus-dragon energy, and the dragon always wins. The point isn’t that renaming is technically difficult—it’s that you’re locked into brittle tools that force one painful click at a time. What you really want is a spell that sweeps through the entire inventory in one pass: rename, refactor, document, done. That curiosity is the opening to a more scalable approach. Because this isn’t just about sloppily named measures. It’s about the container itself. Right now, most models feel like sealed vaults—you tap around the outside but never see inside. And that’s why the next move matters. When we look at how Power BI stores its models, you’ll see just how much the container format shapes everything, from version control to bulk edits. Ever try to diff a PBIX in Git? That’s like comparing two JPEGs—you don’t see the meaning, just the noise.Binary Black Box vs. Human-Readable PBIPThat’s where the real fork in the road shows up—binary PBIX files versus the newer project-style PBIP format. PBIX has always been the default, but it’s really just a closed container. Everything—reports, models, measures—is packed into one binary file that’s not designed for human eyes. You can work with it fine in Power BI Desktop, but the moment you want to peek under the hood or compare changes over time, the file isn’t built for that. PBIX files aren’t friendly to textual diffs, which makes them hard to manage with modern developer workflows. Quick note: if you’re documenting or teaching this, confirm the exact constraints in Microsoft’s official docs before stating it absolutely. Now picture trying to adjust a set of measures spread across dozens of reports. With PBIX, you’re clicking dialogs, hunting ...
    Mehr anzeigen Weniger anzeigen
    17 Min.
  • Dynamics 365 Sales Isn’t Just CRM—It’s Your Sales HQ

    Dynamics 365 Sales Isn’t Just CRM—It’s Your Sales HQ
    Oct 6 2025
    Think your CRM is just a fancy address book? The truth is, many teams still wrestle with manual logging and repetitive admin work instead of actually selling. Before we roll initiative, hit Subscribe so these ecosystem hacks auto-deploy to your feed—no patch window required. Now imagine this instead: your CRM whispering the next best move, drafting client-ready emails, and dropping call summaries straight onto your desk. That’s Copilot in Dynamics 365 Sales. Pair that with Outlook, Teams, and Power Platform plugged directly into your workflow, and you’ve got a real command hub—far more than a Rolodex in the cloud. So let’s talk about why this system isn’t just another CRM.Why This Isn’t Just Another CRMA lot of folks still picture CRM as a clunky filing cabinet with a search bar attached. That mindset leaves reps treating the tool like cold storage for names and notes instead of a command post for selling. The difference matters, because the moment your system stops being passive and starts acting like mission control, you gain actual leverage. Traditional CRMs keep track of calls, emails, and meetings, and they’re decent at showing a list of past actions. But notice the pattern—everything is retrospective. You type, you log, you file, and in exchange you get a static report once the quarter ends. It’s busywork wearing a business suit. In gaming terms, that’s like scribbling your character stats on loose paper while the battle rages on. You might capture history, but you have no live HUD showing where to swing next. Dynamics 365 Sales flips that script. Instead of a flat notebook, it’s more like a dashboard in a game showing health bars on accounts, XP levels on opportunities, and status alerts on what matters now. That one analogy gets the point across: real-time guidance over static notes. The “HQ” framing isn’t just a cute tagline either. It signals a shift from storage to orchestration. Headquarters are where signals arrive, orders are shaped, and teammates coordinate before moving. Microsoft backs this with more than branding—the platform actively invests in AI guidance with Sales Copilot, embedded agents, and extensibility in the current and upcoming release plan. It’s not just holding records; it’s wired to handle the flow of selling itself. Here’s where the HQ idea shows up in action. Instead of staring at blank fields and trying to guess what comes next, D365 can surface a playbook tied to your process. Playbooks, guided sequences, and next-best-action prompts create a worklist so you execute rather than chase scattered tasks. If a buyer opens your proposal, the system doesn’t just log the view—it nudges you to follow up with the right context. That replaces the haunting question of “what now?” with a clear sequence you can trust. And because everything connects, the HQ pulls signals from deals, calls, emails, and customer interactions into one view. You’re not juggling seven different apps to puzzle together the situation. Instead, insights and scoring surface in one console. That matters, because it cuts out manual overhead. Instead of slogging through updates like a secretary with a stack of forms, you scroll through a prioritized task list and act. The grunt work is offloaded, the decision-making stays with you. It’s worth spelling out the contrast. A record-keeper CRM tells you what already happened. A Sales HQ tells you what deserves your attention right now and with which tactic. Guided selling sequences, AI scoring, and task lists turn it into the tactical console, so every action counts. Once you run a few turns from that playbook, going back to static spreadsheets feels like a natural 1. That’s what earns it the “mission control” label. It transforms the feel of selling—less keyboard logging, more strategic steering. The HQ becomes the place you check for situational awareness, confident that all your comms, data points, and nudges are consolidated. With fewer clicks and cleaner signals, reps stop drowning in inputs and start executing with pace. But of course, even the best headquarters can feel distant if you have to travel back and forth just to use it. Which leads to the next real challenge: your daily workflow is already split between Outlook, Teams, and whatever else is screaming for your attention. So what happens when the HQ doesn’t sit apart at all, but pipes directly into the tools already fighting for space on your screen?No More Tab-Hopping: Outlook and Teams Built InHow many windows do you juggle before lunch? A draft email half-written, CRM data hiding in another tab, Teams chat pinging like a party member spamming emotes. It’s not multitasking—it’s a tab zoo, and every extra switch pulls you out of rhythm. That friction adds up. Type a client email, realize you need account notes, bounce to CRM, copy details, hop back to Outlook—and by then Teams has already thrown you another “quick” question. It ...
    Mehr anzeigen Weniger anzeigen
    18 Min.
Noch keine Rezensionen vorhanden