Skip to content
Module 11 of 1245 min readMixed

Power BI Service — workspaces, apps, deployment pipelines

Dev → test → prod via deployment pipelines, scheduled refresh, gateways for on-prem data sources, Power BI apps as the consumer surface.

92%

Listen along

Read “Power BI Service — workspaces, apps, deployment pipelines” aloud

Plays in your browser using on-device text-to-speech — nothing leaves the page.

Learning objectives

By the end of this module, you should be able to:

  • 01Publish to a Power BI workspace and set up scheduled refresh
  • 02Use deployment pipelines for dev → test → production
  • 03Configure gateways for on-premises data sources

Publishing a .pbix is straightforward. Doing it at enterprise scale — with proper environments, refresh schedules, and governance — is where Power BI Service becomes more than a publishing target. The infrastructure side of Power BI is what separates working with the tool from running it for an organisation.

Workspaces and Apps

  • Workspace: a collaboration space. Authors and reviewers live here. Has its own permissions and content (datasets, reports, dashboards, dataflows).
  • Apps: packaged consumer-facing views of a workspace. Authors publish an App from the workspace; consumers see the App tile in their Power BI home.
  • Recommended pattern: separate Dev and Prod workspaces. Authors work in Dev; the App is published from Prod. Promotion between them via deployment pipelines.

Scheduled refresh

Datasets in the Service refresh on a schedule. Settings → Scheduled Refresh → set frequency (up to 8x/day on Pro, 48x/day on Premium). Refresh requires credentials to the source — set them once on the dataset. Refresh failures send email to the dataset owner; set up a Power Automate flow for team-wide alerting.

Deployment pipelines

A deployment pipeline has three stages — Dev, Test, Prod — each a workspace. Click 'Deploy to next stage' and the content promotes with rule-based parameter swaps (e.g., dev server → test server → prod server). Available on Premium. The right pattern for any team shipping more than a handful of reports.

Gateways

Power BI Service runs in Microsoft's cloud. To reach on-premises data (SQL Server in your office, Excel files on a network drive), you install the On-Premises Data Gateway — a small Windows service that brokers connections. Required for most enterprise refresh scenarios. Two modes: Personal (single user, single dataset) and Standard (shared across the organisation, the production choice). Install on a server, not a laptop.

Subscriptions

Users can subscribe to a report or dashboard and receive a scheduled email with a PDF or snapshot. The Service lets users self-serve subscriptions; admins can also create subscriptions on behalf of others (Premium). The most-loved Power BI feature among non-analyst stakeholders.

Exercise

If you have Power BI Pro access: publish a report to a workspace. Set scheduled refresh. Subscribe yourself to a daily PDF. Now share the report with a colleague via the workspace permissions. Are they able to view, edit, or only see the App? Confirm via the workspace 'Access' panel.

Key takeaways

  • Workspaces hold reports and datasets; Apps package them for end users.
  • Deployment pipelines automate dev → test → prod with rule-based parameter swaps.
  • Gateways are the bridge to on-prem data — required for most enterprise scenarios.
Loading progress…
LeadAfrikPublic Economics Hub