You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Fabric/Power BI admin, I want an automated process that manages all Fabric/Power BI artifacts in my organization's tenant according to a set of rules that I specify.
Current obstacles & hardships
Many artifacts already in production
Some artifacts updated frequently
Complex lineage/dependency trees
New artifacts being added all the time
Manually managing all of the above
Time-consuming
Error-prone
Monotonous
Proposed solution
An Azure Function (or other cloud-based unattended app) which:
Has one or more state files
Has one or more configuration files
Utilizes
Power BI Scanner API
Power BI Admin API
Power Automate API
Others (?)
Keeps track of all existing Power BI artifacts and their lineage/dependency trees in state file(s)
Monitors configuration file(s) for changes and updates Power BI artifacts accordingly
Monitors Power BI tenant for artifact changes and updates state file(s) accordingly
Adds/removes/modifies Power Automate flows to reflect the latest configuration & state
Uses the configuration file(s) to determine what to do, and how to do it
Necessary components
Config file(s) - most likely YAML
State file(s)
Probably JSON (at least at first)
May need to upgrade to a cloud data storage solution with concurrent reads & writes for performance if necessary
Power BI Scanner API script(s)
Power BI Admin API script(s)
Power Automate API script(s)
The text was updated successfully, but these errors were encountered:
User Story
As a Fabric/Power BI admin, I want an automated process that manages all Fabric/Power BI artifacts in my organization's tenant according to a set of rules that I specify.
Current obstacles & hardships
Proposed solution
An Azure Function (or other cloud-based unattended app) which:
Necessary components
The text was updated successfully, but these errors were encountered: