I have taught and mastered many desktop tools, including Power BI, for the purpose of prototyping designs for business intelligence and data warehousing. Currently, I am teaching data analytics at graduate level and Power BI is on my schedule.
We teach tools like Power BI by going through common scenarios in a business intelligence environment, which most often deal with the factual numerics that get designed into a sales force reporting dashboard or similar solution, showing details like order placement, orders shipped and paid for, etc. The templates for these typically use a style of diagramming called star schema, which is a common dimension modeling technique.
I can't say whether it's the most frequent real-world use case that a real customer would focus on, but for the level of our tutorials, a sales scenario might involve a description of customers, products, locations, maybe geography, and the timing of sales for trends analysis.
Other than Power BI, I also teach AWS and Azure, where I help guide students to plan and come up with architecture for deploying to the cloud. It's not actually very hands-on, as it's more to help with architecture diagramming for the intentions that students have when using them. And at our institution, all of our courses last only four weeks, so it's very fast tracked, which sometimes means that we don't really go too in-depth.
AWS has a lot of samples and diagrams, including many graphics that are fairly artistically detailed. The level at which I've helped students reference those kinds of diagrams is mainly for their team projects, to illustrate their intention, for example, to deploy a database into AWS. If it's an SQL Server database, we usually choose Azure. But it's not to actually do it. It's rather to have the intention to, for illustration purposes.