『M365 Show with Mirko Peters - Microsoft 365 Digital Workplace Daily』のカバーアート

M365 Show with Mirko Peters - Microsoft 365 Digital Workplace Daily

M365 Show with Mirko Peters - Microsoft 365 Digital Workplace Daily

著者： Mirko Peters - Microsoft 365 Expert Podcast
無料で聴く

このコンテンツについて

 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 政治・政府
エピソード
  • How to Set Up Data Loss Prevention (DLP) in Microsoft 365

    How to Set Up Data Loss Prevention (DLP) in Microsoft 365
    2025/08/21
    Are you actually protecting your company’s data, or just ticking a compliance box? Most admins set up a few blanket DLP rules and assume they’re covered. But if sensitive files are still slipping through Teams chats or emails, that’s a massive blind spot. In this podcast, I’ll show you how to build a layered DLP strategy inside Microsoft 365—step by step, like assembling a real security system. By the end, you’ll know if your setup is just policy paperwork, or an actual fortress. Let’s find out which one you’ve got.The Hidden Map of Your Sensitive DataEvery company thinks they have a clear handle on where their files live. Ask three different admins and you’ll almost always hear three different answers. Some swear everything important is locked down in SharePoint. Others claim OneDrive is where the bulk of corporate files sit. Then there’s always someone who insists Teams has become the new filing system. The truth is, they’re all correct—and that mix is exactly where the challenge begins. Data in Microsoft 365 is everywhere, and once you start poking around, you realize just how scattered it really is. That scattering, or “data sprawl,” sneaks in quietly. A finance manager stores quarterly forecasts in OneDrive to finish at home. HR officers send performance reviews as attachments inside Teams chats. Sales reps drop entire customer lists into email threads so they can ask quick questions. None of this feels risky at the time—it’s just how people get their work done. But from an admin’s perspective, it’s chaos. Sensitive data ends up scattered across services that weren’t designed as the final resting place for long‑term confidential files. Here’s where the headache begins. You’ve been told to build DLP policies, but you sit down, look at the console, and realize you don’t even know which workloads hold the dangerous stuff. If you target too broadly, you risk endless false positives and frustrated users. If you target too narrowly, you blind yourself to leaks happening in less obvious places. That’s the tension—how do you lock down what you can’t even find? Picture this: one of your project managers, excited to share progress, posts a confidential report into a Teams channel with external guests. The file syncs to people’s laptops before you even wake up in the morning. No one involved meant harm. They just didn’t realize an internal-only file was suddenly accessible to outsiders. That tiny slip could turn into regulatory fines or even a reputational hit if the wrong set of eyes lands on the document. And the worst part? Without visibility tools in place, you might not even know it happened. SharePoint brings its own subtle traps. You might believe a library is safely restricted to “internal only,” but the second sync client is enabled, those files flow down to end‑user laptops. Suddenly you have copies of sensitive material sitting unencrypted in places you can’t directly monitor. A misplaced laptop or a personal backup tool picking up synced data means confidential material leaks outside your intended perimeter. None of that shows up if you’re only staring at basic access controls. This is why discovery matters. Microsoft includes tools like Content Explorer and Activity Explorer for exactly this reason. With Content Explorer, you can drill into where certain sensitive information types—like financial IDs or personal identifiers—are actually stored. It’s not guesswork; you can see raw numbers and counts, broken down across SharePoint, OneDrive, Teams, and Exchange. Activity Explorer builds on that by highlighting how those sensitive items are being used—whether they’re shared internally, uploaded, or sent to external contacts. When you first open these dashboards, it can be sobering. Files you thought were locked away neatly often show up in chat threads, temp folders, or forgotten OneDrive accounts. By building this map, you trade uncertainty for clarity. Instead of saying “we think payroll data might be in SharePoint somewhere,” you know exactly which sites and which accounts hold payroll files, and you can watch how they’re accessed day to day. That understanding transforms how you design protection strategies. Without it, your rules are guesses—sometimes lucky ones, sometimes costly misses. With it, you’re working from evidence. What discovery really does is shift invisible risks into visible assets. Once something is visible, you can measure it, plan around it, and ultimately protect it. That’s a huge change in approach for admins. You stop standing in reaction mode—responding only after a problem surfaces—and start proactively shaping your defensive posture based on actual data flows. So before we talk about setting any rules or policies, the first foundation stone is this discovery step. Think of it like surveying the land before building anything. If you don’t know what sits beneath the soil—rocks,...
    続きを読む 一部表示
    21 分
  • How to Monitor Compliance in Microsoft Defender for Cloud

    How to Monitor Compliance in Microsoft Defender for Cloud
    2025/08/20
    Compliance isn’t just about checking boxes—it’s about proving to your stakeholders that you can prevent issues before they ever hit production. But here’s the catch: most teams rely on manual reviews that are blind to what’s actually happening across workloads. What if Microsoft Defender for Cloud could give you continuous, system-wide assurance without you chasing down every policy? Today, we’re looking at how to set up compliance monitoring that actually sticks—where reports, automation, and remediation all connect into one real-time compliance story.Why Compliance Isn’t Just a CheckboxWhy do so many companies still stumble during audits even when every single box on the checklist is marked complete? On paper, the requirements look satisfied. Policies are documented, evidence folders are neatly organized, and auditors can flip through binders that seem airtight. Yet the reality is that compliance isn’t a paperwork exercise, it’s an operational one. The disconnect shows up the moment those binders meet the real environment, where workloads are changing daily and controls don’t always hold up under pressure. Compliance in the cloud is less about what’s written down and more about how systems behave in real time. A Word document can say encryption is enforced, but if a storage account spins up without it, the policy is only true in theory. That’s where teams get into trouble—treating compliance as paper snapshots rather than an ongoing system challenge. Modern workloads shift too quickly for manual reviews or quarterly audits to catch everything, which is why so many organizations pass one review only to discover a major gap weeks later. Picture this: a cloud engineering team coasts through an audit in March. All the evidence lines up: access controls are documented, storage encryption policies are filed, and network rules checked out. Yet halfway into a project in May, someone realizes that a critical storage account was left exposed without encryption. Suddenly, the same company that had “proven compliance” a few weeks earlier is staring at a misconfiguration that undermines the credibility of the entire program. The paperwork looked fine, but the system itself was out of step with the promise. Frameworks like ISO 27001, NIST, or PCI DSS make this distinction clear if you look closely. They’re not just asking for policy statements; they’re requiring organizations to demonstrate active enforcement. Saying “all traffic must be encrypted in transit” isn’t enough. At some point you need evidence that every workload is actually following that rule, right now, not just in the past quarter. That’s where the weight of compliance really sits—proving that operational controls hold up under continuous change. And here’s where the emotional side matters. When compliance is handled reactively, it slowly eats away at trust. Executives stop believing that passing an audit equals being secure. Customers begin wondering if claims of compliance mean anything when breaches still make headlines. Even internal teams lose confidence, because they know their daily work doesn’t always align with the official documents. Once that trust starts to erode, even the strongest spreadsheet of completed tasks can’t restore it. Nobody wants to find out during a board meeting that what was claimed last quarter no longer matches current reality. This is the gap that tools like Microsoft Defender for Cloud try to close. Instead of just handing you another portal to upload reports, Defender acts as a visibility layer over your workloads. It doesn’t stop at “do you have a policy?” It asks, “are those policies enforced right now, on these resources?” Imagine pulling up a single dashboard that shows which controls actually stick across every subscription, resource group, or machine, without flipping through audit notes. That’s the difference between guessing compliance and seeing it. The key here isn’t just spotting gaps faster; it’s about creating an ongoing narrative of compliance. A static report gives you the past tense. Continuous visibility gives you the present tense. That’s what shifts compliance from reactive documentation into active posture management. You stop being surprised by findings because you already know the current status and where issues are creeping in. Defender gives you that persistent lens, turning compliance from a stack of static files into a live system benchmark. And yes, this is where frameworks and dashboards start to play together. You can take something complex like NIST or ISO, map it into Defender, and immediately see how your workloads stack against each requirement. But more importantly, you don’t have to wait until the next annual review to know. It’s right there, as it happens. That blend of framework mapping and real-time visibility is where the weight starts to lift off security and compliance teams. So when we talk about ...
    続きを読む 一部表示
    23 分
  • Step-by-Step Guide to Organizing Projects in Teams

    Step-by-Step Guide to Organizing Projects in Teams
    2025/08/20
    What’s the difference between a project that feels effortless and one that leaves everyone chasing files and status updates? It’s not the tool—it’s the system behind it. And most teams don’t realize they’re missing a few simple building blocks.Today, I’ll show you how to create an interconnected project structure in Microsoft Teams using SharePoint and Power Automate that makes project visibility automatic instead of manual—and why setting this up the right way from the start changes everything.Why Most Project Systems Collapse Within 90 DaysWhy do so many teams start strong but quickly slide back into chaos? The excitement at the beginning is real—you launch a fresh workspace, everyone agrees it’s going to be “the” organized project this time, and channels start filling with conversations. Tasks get dropped into planner boards, files make it into the right folder, and people actually post updates in threads instead of sending emails. For a short while, it feels like the team finally solved the coordination problem, like the right tool unlocked a better way of working. But that sense of order rarely lasts. Within a couple of months, the bright start fades, and suddenly you’re asking yourself why things look exactly like the last system that failed. The most common slide usually starts small. Maybe a single document that someone couldn’t find, so they dropped it into chat instead of uploading it. Or a new person joins the project and is confused about which channel or tab is current, so they create their own folder structure. Within weeks, the clean setup starts to sprout duplicates. The document library has ten different “final” versions, each hiding in different corners. Chat threads drift into mini project logs, while the supposed central tracker stops reflecting what the team is actually doing. Everyone has good intentions, but the snowball effect is real: unclear updates lead to side conversations, which lead to contradictory data, which eventually leads back to the exact confusion you thought you solved at the start. Sound familiar? Teams channels that were supposed to be focused workstreams turn into sprawling chatrooms that bury critical information. SharePoint libraries that were set up with neat categories end up buried under personal subfolders and one-off uploads. You go looking for a key file, and you’re faced with “copy of presentation (final 3).pptx” in multiple places, none of which you can be sure is the right one. The structure is still there in theory, but the day-to-day use of it doesn’t reflect that design anymore. Now, here’s the reality most teams don’t want to admit: the collapse isn’t because you didn’t pick the right app. It’s not that Teams is missing a magic feature or that SharePoint isn’t intuitive enough. Research into project management failures consistently shows the bigger issue is system design, not tool choice. Tools only enforce behavior if there’s a system that guides how they will be used as a whole. Without it, every project becomes another round of learning the same lessons through trial, error, and frustration. There’s a difference between short-term habits and long-term structure. Starting strong often relies on habits—people remember to upload files, they check the planner board, they reply in the right channel. But habits fade under pressure. Once deadlines heat up or the team scales past the original group, people fall back into the fastest way of working—even if that means clutter, duplication, and confusion. Short-term habits keep you disciplined only as long as energy is high. Structure, however, doesn’t depend on people remembering. A well-designed structure makes the right action easier than the shortcut, so discipline doesn’t have to be a daily choice. And what’s the hidden cost when there isn’t structure? Hours vanish into searching for documents that should’ve been centralized. Tasks are logged twice in separate trackers, which means work gets repeated or handoffs are missed. Updates come late, or worse, they contradict each other, so leaders make decisions based on outdated information. Over time, the cost adds up not only in wasted effort but in slower progress, higher stress, and lower trust across the team. Everyone feels like they’re working hard—because they are—but the actual system multiplies inefficiency instead of eliminating it. So why do some teams manage to keep their systems running smoothly while most collapse in under three months? The answer is that they don’t treat the tool itself as the fix. They don’t assume “new channel equals new workflow.” They design principles first. Principles give a framework that shapes how the team uses the tool, rather than leaving it as a blank canvas that slowly falls apart. Without principles, the tool is just a series of folders, chat windows, and dashboards waiting to be misused. With them, even if tools evolve or ...
    続きを読む 一部表示
    20 分
まだレビューはありません