1 of 40

San Antonio Fabric and Power BI User Group

2 of 40

San Antonio Fabric and Power BI User Group

3 of 40

Welcome Everyone!!

4 of 40

Agenda

  • SA PUG Leaders
  • SA PUG Involvement
  • Fabric Updates
  • Power BI Updates
  • Sharing Smarter: Power BI Service Best Practices for Report Builders and End Use
  • Questions?
  • Closing Comments

5 of 40

PUG Leaders

  • Chris Aleman
  • Antonio Ramsey
  • Lawrence Coffee
  • Rayan Yassminh
  • Jason Roelofs

6 of 40

Join us!

SA PUG is growing, and we want you to be join us in our journey! Below are the different platforms we are apart of.

7 of 40

About Us & Save the Date

Whether you're part of a team or flying solo, this session is for you!

Join us for a collaborative, guided deep dive into Power BI, Microsoft Fabric, and related technologies.�We learn from each other to grow faster-together.

📅 Meetings: Last Wednesday of every month at 12 PM CST

  • Click here for Meetup info

8 of 40

Community Impact

SA PUG communities' topics of interest:

    • Power BI
    • ✅ DAX
    • ✅ Data Viz
    • ✅ Fabric
    • ✅ Dashboard Design
    • Event Streams & Real Time Analytics
    • ✅ Data Modeling & Transformation
    • Data Factory – Flows & Pipelines
    • ✅ Case Studies or Demos
    • ☀️Administration & Governance

We are looking for future speakers to present!

Click here for the Volunteer Speaker Request Form

9 of 40

Fabric Updates

Monthly Updates for Fabric

  • Click here for the video Summary by Microsoft

General

    • Desktop start-up performance improvements
    • Upgrade Power BI Desktop

Copilot and AI

    • Get a Copilot summary directly from your Teams message with a single click
    • Copilot in Power BI to write DAX queries in DAX query view updates
    • Improved language understanding for data questions
    • Ad hoc calculation support for data questions

Modeling

  • Use notebooks with your semantic model (Preview)
  • Access the Azure Analysis Services migration tool from your workspace

10 of 40

Power BI Updates

Monthly Updates for PBI

  • Click here for the video Summary by Microsoft
  • Security labels for PBI desktop files
  • More visual Calculation updates
  • Sparklines are GA now
  • Org Apps are now available in Mobile
  • Network graph visual by Powerviz on App store
  • Chat with your data and Copilot in Embedded reports for portals and websites
    • Click here

11 of 40

Sharing Smarter: Power BI Service Best Practices for Report Builders and End Use

12 of 40

Sharing Smarter: Power BI Service

Session Takeaways:

    • Understand the differences between viewer, member, and contributor roles- and when to use each.
    • Learn best practices for organizing and publishing reports via apps, shared links, and workspaces.
    • Explore how to reduce confusion and improve user adoption by tailoring access and visibility.

13 of 40

What are Workspaces?

Workspaces are places to collaborate with colleagues to create collections of dashboards, reports, semantic models, and paginated reports.

14 of 40

What are Workspaces?

15 of 40

What are Workspaces?

Workspaces features

  • Use granular workspace roles
  • Contact list
  • Create template apps
  • Share semantic models

16 of 40

Roles in Workspaces

  • Roles let you manage who can do what in a workspace, so teams can collaborate.

  • Workspaces allow you to assign roles to individuals, and also to user groups such as security groups, Microsoft 365 groups, and distribution lists.

17 of 40

Roles in Workspaces

18 of 40

Roles in Workspaces

19 of 40

Sharing Content in Power BI

Ways to share:

  • Links, Apps, Teams, Direct Access
  • Internal or external
  • Embed, print, subscriptions, .pbix file, PowerPoint

20 of 40

Real World Scenario

From Sharing to Struggling: Lessons Learned

    • Initially shared reports via workspaces and direct links
    • Assumed users would easily navigate and access content
      • Frequent feedback:
      • "I can't find the report“
      • "Where do I go?“
      • "Is this the right version?“

Key Realization:

  • Just publishing content isn’t enough-structure, clarity, and user-focused design are essential

21 of 40

Our End Users Struggled

Guiding question:

    • How do we provide easy access while maintaining governance?
    • Challenges

Too steep of a learning curve for our end users

    • Too difficult to find reports
    • Navigating PBI service was challenging for non computer literate folks
    • Low adoption rate

22 of 40

Avoiding Early Pitfalls

Key mistakes made during initial rollout:

    • Didn’t follow Microsoft documentation
    • Gave coop access to workspaces
    • Didn’t use apps
    • Permission groups not fully dynamic
    • Relied on consultants to guide us- they were learning too!

23 of 40

Avoiding Early Pitfalls

24 of 40

Used Workspaces incorrectly

Collaborative dev environment for:

    • Dashboards, reports, semantic models
    • Not for end-user consumption-developers only

25 of 40

Designing for Clarity

Our Mistakes

    • Coop had direct access to workspaces
    • Too much noise, hard to navigate
    • Confusion during Tableau to PBI transition

26 of 40

Designing for Clarity

27 of 40

Designing for Clarity

Solution

    • Created apps for report consumers
    • Cleaner interface, easier navigation
    • Had to rebuild bookmarks/subscriptions

Apps offer:

    • Customization
    • Separation between dev and end-user layers
    • Workspace access limited strictly to report devs via Entra ID groups

28 of 40

Designing for Clarity

29 of 40

Designing for Clarity

30 of 40

Designing for Clarity

31 of 40

Permissioning for Security and Usability

Our Mistake

    • Security groups too broadand not dynamic
    • Created manual viewer groups (e.g., individual accountants)
    • Result: messy, cluttered group structure

32 of 40

Permissioning for Security and Usability

Our Solution

    • Rebuilt groups from scratch using job roles
    • Now fully dynamic groups with:
      • Less overhead
      • Easier updates when job roles change
      • Inherited access for new hires

33 of 40

Designing for Clarity

34 of 40

Designing for Clarity

35 of 40

Grouping and Role Based Strategy

  • One overall viewer group buckets all dynamic groups
  • Additional smaller dynamic groups:
    • Executive leadership
    • Admin roles
  • Ongoing addition of dynamic groups as coop usage grows

36 of 40

Designing for Clarity

37 of 40

Final Thoughts

Power BI success requires:

    • Governance clarity
    • Role-based access
    • End-user centric design

Our lessons = smoother experience for developers and business users alike

38 of 40

Additional Resources

39 of 40

Questions?

40 of 40

Thank you and we’ll see you next month!