Episode Details

Let’s be real—Power BI alerts are like Clippy: “It looks like you’re trying to stay informed… but let me waste your time first!” Who decided restricting alerts to dashboards was a smart move anyway? Probably the same squad that thought Cortana was going to beat Siri. Follow the M365.Show LinkedIn page for livestreams with MVPs—because you’ll want the real fixes, not the marketing slides. Now, Microsoft says alerts keep you in the loop. In practice, they keep you building dashboards you never wanted. Data Activator promises a different approach—and we’re about to walk through what that looks like. Stick around, we’ll show the fix. So with that said—why does setting up an alert feel like you’re building a shrine instead of just checking data?The Dashboard PrisonThat brings us to what I call the Dashboard Prison—the place where most Power BI alerts get locked up by design. Instead of being quick and flexible, alerts are tied down with rules that turn a basic need into an administrative headache. Here’s the core frustration. Many admins find that Power BI alerts require pinned visuals on dashboards. You can’t just hop into a report, set a threshold, and get notified. No—first you’ve got to pin something to a dashboard you never planned on creating. (If you want the formal definition, Microsoft’s docs spell it out, but the lived reality is obvious the first time you try it.) It’s the classic Microsoft trade: a simple feature, but wrapped inside something bigger that you didn’t actually ask for. And let’s be clear—no admin wakes up thinking, “Please give me more dashboards laying around my tenant.” But that’s the tax you pay. A single alert equals another pinned card somewhere, which equals another dashboard object cluttering up workspaces. Very quickly, you’re managing an entire graveyard of dashboards that exist for no purpose other than propping up one lonely alert. Here’s a relatable example. Say you’re an IT admin who needs a daily heads-up if revenue passes $1,000. Sounds simple. In practice, you’ve now built a dedicated visual, pinned it onto a brand new dashboard, and made yourself responsible for explaining what the dashboard is for—because in six months, you probably won’t remember. That’s not lightweight alerting. That’s unnecessary upkeep. Now multiply that setup across dozens of metrics and you’re essentially drowning in dashboards that exist purely as storage containers, not working tools. And even once you’ve made peace with the clutter, there’s another catch. Admins repeatedly point out that alerts are tied only to card visuals. In other words, if you want to track something meaningful like a trend line, a KPI over time, or any chart with context—you’re out of luck. If you double-check Microsoft’s documentation, you’ll see the guidance: alerts trigger only on card-type visuals pinned to dashboards. If you don’t feel like digging into the docs, just trust the admins who set up dummy cards every day just to work around that rule. That restriction is where the system really shows its age. Businesses don’t care about flat one-number tiles. They care about changes, patterns, outliers. But Power BI alerts don’t give you that. Management doesn’t ask, “Did you build me enough dashboards?” They ask, “Why didn’t anyone flag the problem last night?” And our answer is usually something like, “Because Microsoft made us wrap the alert inside a dashboard, on a card, and nothing else counts.” That’s not a system serving you. That’s you serving the system. And beyond annoyance, it adds to governance sprawl. Every pinned card is an object your tenant has to carry. That means permissions, names, lifecycle, the whole bit. Admin teams already deal with clutter in Teams, SharePoint, and OneDrive. Do we really need alerts manufacturing more dead objects? It’s the equivalent of not letting you install a smoke detector without building a shed to house it first. By the time the flames show up, you’re still explaining why twenty half-dead dash