The current process of updating gateway software is not effective or efficient for large enterprise with multiple gateway servers.
The process works like this.
- Schedule installer via SCCM or PowerShell to update gateway software.
- Log into each server and sign in to gateway software to make newer version show up in Power BI service
The above process can be fully automated by adding post install step to allow PowerShell script to run as either service principal or service account to sign into gateway software. This will streamline patching process and give better user experience.
3 Comments
- Kevin_JozwiakowNew Member
Suman, i thumbed up voted this.
- Olga_UlisNew Member
Upvoted
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Separate Download and Publish Permissions for Power BI Workspaces
Idea / Feature Request Introduce more granular permissions in Power BI to independently control report download and report publishing permissions at the workspace level. Business Scenario We have ...ewarstdhyjugkhi11 minutes agoMicrosoft EmployeeNew10Views4likes0CommentsSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull221 hour agoAdvocate INew29Views1like1CommentPaste values in slicers for hierarchy data
Hierarchical slicers are widely used in enterprise reports (for example Product RCN > SKU Key, Region > Country > City, or GPP > Division > RCN > SKU). Users often need to bulk-filter by pasting valu...eddieisking20003 hours agoFrequent VisitorNew0Views0likes0Comments