The document discusses governance strategies for Power BI, including tools for enforcing policies, managing access and content, and auditing usage. It provides examples of organizational practices to avoid, such as overloading reports, not creating mobile views, and exposing cached data. Links are included for resources on Power BI administration, governance best practices, and YouTube videos on the topics.
12. Who can Edit?
How and who access Data Source?
Templates and custom visuals to use
On
Prem
DB
Direct Query?
Cash/import data?
Who can consume?
Similar across devices?
Special authentication?
Design
Data Integrity
Scheduled
connections
13.
14.
15. Let’s start with the most celebrated topic…
(Credits: @geek_king)
26. Link
Free Pro License Premium License Report Server
(SQL 2017 or
PowerBI
Reporting)
Azure on
demand
27.
28.
29. APPS Content Packs Governance
Maintain Grouping and
Identity
loses its grouped identity: it's just a
list of dashboards and reports
Apps – Identity and data access
1:1 Workspace to App (to
group…)
Multiple content packs from
workspace
CP – Different content vs. continue
based on group
Allows selective publishing Allows selective publishing Both
Push notification when created
to users, link the app
Send the content pack, link report
or dashboard
Apps – linkable, single source of
truth
The way to publish your
content
Will be deprecated Why didn’t I just start here???
30. Dataset
Reports
Dashboards PowerBI App
Workspace -
Dev
Workspace Test
Dataset
Reports
Dashboards
Prod – Entire
organization
Group Workspace
Prod
Dataset
Reports
Dashboards
Site
SharePoint/ Web
PowerApp
Selective Publishing
Can Directly connect through API
36. (Release link
Sep)
Theme
Colors
Fonts
Text Size
Data Labels control (not for the custom
visuals)
Report Theme Generator for the UI
Designers LINK
Theme creation for the color match
challenged LINK
(Thank you Charles Sterling!!!)
37. How do we use them?
Can be added as a file
Can be added from the store
Can be created
My Company store – Amanda Cofsky
February release
38. specify which visuals are approved to use in your organization consider
customizing according to themes
Decide if it is important and follow through/ customize with R
Visuals review after every release or some of them by your PowerBI admin
Data integrity for coordinates (I have manually changed in 134 buildings…)
SDL in every PowerBI implementation
Guidance specific to your organization on Dashboard and Reports UI
39.
40. Which Enforcing tools have
we got?
Templates and Visual Guides – can be overridden
Publishing methods are restricted (Premium vs
Pro)
Monitor the views and reports – log
view/Embeded
Create alerts and policies for suspicious activity –
Using other tools – Embedded
Applications across devices – Where the
application can be viewed – more control
41. Enabling the
Governance
• Export and Sharing
• Can people publish to the
web?
• Can data be exported?
• PowerPoint is still in
Preview, should we use that
and risk complains?
• Print settings (Dave still got
print screen )
43. The full list of all your
embed reports
Who published them and
where can they be found
Usage and other metrics
in premium or the
PowerBI Imbedded on
Azure
52. Organizational Practice Result
To save on licensing cost, the reports
are simply shared via SharePoint and
emails using the Share to Web
Cashing and importing all the data
instead of using direct query
Not creating the mobile view
Creating a group for each report
Overloading custom queries and
heavy visualization
The cashed data is completely exposed
The data synchronization is done to multiple
sources resulting data caps reached
The data quote of 10G per group is running out, the data
sets cannot be updated anymore
Data Integrity in case of no Sync or communication lost
for live DB
Frustrated mobile users – adoption is affected
Too much mobile data used
Presentation is not fir for screen
Shared data cannot be viewed, report versions are
becoming common, leads to lack of single source of truth in
visualization
Slow performing reports, error messages when some data
access might be wrong