Power BI Mobile and Embedded — Data That Travels and Data That Lives Inside Your App

"Reports shouldn't just be powerful — they should be where people are." — your future, slightly smug BI champion

You're already familiar with Power BI Desktop (where you build magic) and the Power BI Service (where you publish, share, and schedule refreshes). Now let's take that magic out of the lab and either put it into people's pockets or stitch it into the apps they already use all day. Welcome to Power BI Mobile and Power BI Embedded — the dynamic duo that turns static dashboards into living, breathing experiences.

Quick framing: Why this matters

Mobile gets your insights in front of decision-makers who are not chained to a laptop — field sales, executives, on-call engineers. If a KPI spikes at 2AM, a push notification beats an email.
Embedded lets you give reports to your customers or put analytics inside your product. You don't force users to hop between apps — analytics become a native part of the workflow.

Imagine a sales rep closing deals from a car with a single tap, or a SaaS product showing personalized usage analytics inside its dashboard. That’s what we mean by frictionless BI.

Power BI Mobile — the short version (but useful)

What it is: Native apps for iOS and Android that let users view dashboards and reports, receive alerts, annotate screenshots, and use Q&A (natural language queries).

How it connects to Desktop & Service: Design and publish your report in Power BI Desktop. In the Power BI Service you control sharing, workspaces, and refresh — and then users open those same reports in the Mobile app. Pro tip: use the mobile layout in Desktop to optimize the experience.

Key features

Mobile-optimized layout: rearrange visuals specifically for small screens in Power BI Desktop (we covered report editing in Desktop — remember?).
Push notifications & data alerts: set threshold-based alerts in the Service and receive mobile push messages.
Annotations & sharing: screenshot a report, mark it up, and send it to colleagues.
Offline caching: limited — some tiles and snapshots are cached for quick access.

Best practices for Mobile design

Simplify visuals — small screen = less ink. Use big fonts and single-metric cards.
Prioritize content — put the top KPI first; use bookmarks to surface relevant states.
Touch targets — make buttons and slicers easy to tap.
Test on devices — never trust the emulator alone.

Power BI Embedded — the long, delightful nerdy cousin

What it is: A set of services and APIs that enable you to embed Power BI reports, dashboards, and visuals into your own web or mobile applications.

There are two main embedding scenarios you should know:

Embed for your organization ("User owns data") — embedding reports for users within your tenant. Users must authenticate with Azure AD and have Power BI licenses; you honor their permissions.
Embed for your customers ("App owns data") — your app handles authentication, and the app presents reports to external customers. This commonly uses service principals or master accounts and requires dedicated capacity (A SKU or Premium/EM) depending on scale.

Technical building blocks

Azure AD for authentication (users or service principals)
Power BI REST APIs to generate embed tokens, manage content, and do programmatic operations
powerbi-client (JavaScript) or SDKs (.NET) for rendering reports inside your app
Capacity (A, EM, or Premium SKUs) to guarantee performance and licensing for external embedding

Here's a minimal JavaScript example that shows the embed configuration (conceptual):

const embedConfig = {
  type: 'report',
  id: '<REPORT_ID>',
  embedUrl: '<EMBED_URL>',
  accessToken: '<EMBED_TOKEN>',
  tokenType: models.TokenType.Embed,
  settings: { panes: { filters: { visible: false } } }
};

const report = powerbi.embed(document.getElementById('reportContainer'), embedConfig);

(Yes, you still need to generate that embed token server-side using a secure flow.)

Licensing & capacity (TL;DR)

Internal users: often covered by Power BI Pro or Premium per user. No dedicated capacity required for small orgs.
External customers / wide public apps: you must use Power BI Embedded (A SKUs) or Power BI Premium (EM/P SKUs) to avoid requiring every user to have Power BI licenses.

Side-by-side: Mobile vs Embedded

Aspect	Power BI Mobile	Power BI Embedded
Primary audience	Internal users on phones	Customers or app users (internal/external)
Setup	Install app, sign-in	Integrate SDK & REST APIs into app
Auth model	User signs in with AAD	User-auth or app-auth (embed token)
Licensing	Pro / PPU / Premium for sharing	A/EM/P capacities for customer-facing
Best for	Alerts, quick decisions, on-the-go	Seamless analytics inside apps

Best practices for Embedded deployments

Use RLS (Row-Level Security) to ensure users only see what they should — even in app-owned scenarios.
Use service principals over master accounts for security and manageability.
Cache smartly — pre-generate tokens and warm report visuals to reduce first-load latency.
Monitor capacity with metrics to scale A/EM/P as load grows.
Isolate tenants (multi-tenant apps) by designing workspace structures or using separate reports per tenant.

Security & governance — the boring but crucial stuff

Never embed master credentials in client code.
Ensure embed tokens are short-lived and minted server-side.
Use least privilege for service principals and rotate secrets.
Track usage and refresh failures in the Power BI Service and Azure Monitor.

Closing rally: how to practice this without breaking production (or your nerves)

In Power BI Desktop, create a mobile layout for one of your reports (remember that trick from Desktop Overview?).
Publish to a development workspace in the Service and open it on your phone. Tweak.
Spin up a simple web app (or use a sample) and follow the "Embed for your organization" path to render a report using powerbi-client.
Experiment with tokens, RLS, and capacity monitoring — start small, measure, then scale.

Final thought: Mobility makes analytics immediate. Embedding makes analytics invisible. Both turn ideas into action. If your insights aren’t where people are working, they might as well be sitting in a dusty PDF.

Key takeaways

Mobile = optimized, on-the-go consumption; use mobile layouts and alerts.
Embedded = analytics inside apps; two embedding modes (user owns data vs app owns data) with different auth and capacity needs.
Security & capacity are the levers that determine whether your solution is scalable and safe.

Go on — make your data less shy. Put it in pockets and in products. Your reports deserve a stage.

Introduction to Power BI

Content