The Clearly Podcast

Andy: How's everyone doing?

Tom: I'm good, still cold here, though.

Andy: Yeah, I see lots of fleeces. Today, we'll talk about Power BI as part of the Power Platform, which includes Power BI, Power Apps, Power Automate, and Power Virtual Agents.

Shailan: It's Power Virtual Agents (PVA). None of us have worked with it much.

Andy: Right, we'll focus on Power BI, Power Apps, and Power Automate.

Shailan: I feel a vote coming on. Which one do you think is more important, Power Apps or Power BI?

Andy: Power Automate is also crucial as it runs in the background, integrating data between systems.

Shailan: Let's decide our favorite component in the Power Platform at the end.

Andy: Sure. Let's start with how Power BI fits into the Power Platform. All four components can work independently and with other solutions, making the Power Platform versatile. For example, Power Automate can integrate Salesforce with Power BI seamlessly.

Shailan: We recently did a strategic piece of work for Microsoft Consulting Services. The client used Power Apps extensively, which has canvas, model-driven, and portal components.

Andy: Can you discuss how these components work as standalone solutions before we talk about their integration?

Shailan: Sure. Power Apps is more than just a form capture tool; it includes complex workflows and data entry. Power BI, which we use weekly, visualizes data. Power Automate handles information flow and triggers events. Power Virtual Agents can assist with tasks, learning over time.

Andy: We've seen integrations between these tools, like using Power Automate to refresh Power BI, which then updates within a Power App.

Tom: Dataverse is crucial as the database backing the Power Platform, enabling structured data storage and integration.

Shailan: Power Apps can embed Power BI for near real-time reporting, creating a seamless user experience. Power Automate can trigger updates and integrate with other data sources via connectors.

Andy: The term "citizen developer" suggests anyone can use these tools, but a certain level of technical skill is still required.

Tom: Yes, while the Power Platform lowers the barrier to entry, creating effective solutions still needs some technical knowledge.

Andy: For example, setting up security roles in Power Apps is not intuitive and requires understanding user access considerations.

Tom: Also, users must understand the broader policy and compliance context, not just the technology.

Andy: Licensing also plays a role, making it easier to adopt the Power Platform without significant additional costs.

Shailan: Clients often want a managed app service, simplifying their experience while ensuring data governance and compliance.

Andy: Alright, let's vote. Tom, what's your favorite part of the Power Platform?

Tom: Power BI, for its broad applicability across businesses.

Andy: I'll go with Power Apps for its ability to replace complex Excel spreadsheets with structured, secure data capture.

Shailan: I'll likely pick Power Apps too, due to its low code/no code capabilities and cost efficiency.

Andy: Let's see what the audience thinks. What kind of music should we play out with today?

Tom: A power ballad, fitting for the Power Platform discussion.

Andy: Perfect, a power ballad it is.