How to showcase Power BI dashboards on a portfolio website

Quick answer

Start with screenshots and a written case study. Add a short video to demonstrate filters and explain your decisions. Use an interactive Power BI embed only when it improves the demonstration and you understand its access, cost and privacy implications.

For a public portfolio, Microsoft’s Publish to web makes the report publicly available on the internet. It is not a confidential sharing method. Use public or synthetic data, not employer or client information. [1]

Compare screenshots, videos and interactive embeds

Choose the format around what a reviewer needs to understand—not around the most technically impressive implementation.

Microsoft documents secure embedding separately from public publishing [5]. Its Embedded documentation explains customer embedding and row-level security [2], while Azure describes capacity purchasing and usage billing [3].

What should an analyst in India budget?

Power BI Desktop is available as a free download. The supplied Microsoft India pricing page lists Power BI Pro at ₹1,165 per user/month, paid yearly, with GST extra as applicable; it lists Power BI Embedded as variable. Verify the current offer before buying. These are Power BI costs, not your complete website budget. [14]

My recommendation: start with static project pages. Pay for interactive infrastructure only when you need to demonstrate something screenshots and video cannot communicate adequately. Buying Pro should not be treated as a shortcut to an anonymous, secure portfolio embed.

Why Publish to web is unsuitable for confidential data

Publish to web creates content that internet users can view through a public URL or an embedded page and share onwards. Microsoft explicitly excludes secure confidential or proprietary information from this feature and lists reports using row-level security as unsupported. [1]

A password on your portfolio page does not turn the underlying public report into a private report. Neither should filters, obscure URLs or hidden navigation be treated as security controls.

Before publishing any format:

• Confirm that you have permission to publish the data, screenshots and business context.
• Remove personal identifiers, account details, internal targets and commercially sensitive information.
• Review combinations of details that could identify a person or organisation even after names are removed.
• Inspect tooltips, drill-through pages and every view shown in a recording.
• If permission or anonymity is uncertain, rebuild the example using synthetic data and label it clearly.

For example, recreate an employer’s collections-reporting problem with fictional invoices rather than publishing debtor names or outstanding balances. A synthetic demonstration can show your modelling and DAX skills without exposing the original business.

Create your portfolio assets step by step

1. Prepare screenshots that explain the report

1. Choose a useful default state: a meaningful reporting period, clear filters and readable KPI labels.
2. Capture one overview and separate close-ups of important visuals.
3. Crop unused application chrome, but retain context such as units and active filters.
4. Add descriptive alternative text and a caption explaining the business takeaway.
5. Check the images on a phone. If labels become tiny, use focused crops rather than one dense dashboard image.

For an India-focused retail project, label currency consistently as INR or ₹ and explain whether values use rupees, lakhs or crores. Write the reporting dates explicitly rather than leaving “FY” undefined.

2. Record a short walkthrough

Aim for roughly two minutes as an editing target, not a requirement. Use this sequence:

1. Question: explain the decision the report supports.
2. Navigation: demonstrate one useful filter or drill-through interaction.
3. Evidence: explain one insight and how you checked it.
4. Action: recommend a next step and acknowledge a limitation.

For a fictional Bengaluru and Pune retail comparison, explain how channel mix affects interpretation rather than merely clicking through city filters. Close unrelated windows, disable notifications and review the complete recording before uploading it. Keep a text summary alongside the video so the project remains understandable without sound.

3. Add a public interactive report only if appropriate

1. Prepare a separate, portfolio-safe version with approved public or synthetic data.
2. Check Microsoft’s Publish to web limitations. Reports using row-level security or DirectQuery are among the unsupported configurations. [1]
3. In the Power BI service, use Publish to web for the eligible report and read the warning before confirming publication.
4. Preview the result and select the size and default page where offered. [5]
5. Add the generated embed through your website’s supported HTML or embed component, or provide the public report link.
6. Test from a signed-out browser and a phone. Keep screenshots and the case study available if the embed fails.

Microsoft notes that Publish to web data is cached for one hour after retrieval, so changes may not appear immediately. Stage and review your report before sharing the portfolio link. [1] Its publishing guidance also covers preview settings and staging. [5]

4. Separate restricted demonstrations from your public portfolio

If the work must remain restricted, publish a permitted summary or synthetic recreation instead. Offer a private demonstration only with the data owner’s approval and appropriate access controls.

For a client-facing application, evaluate Power BI Embedded with a developer. Microsoft distinguishes model and embed-token-based row-level security from JavaScript filtering; a visual filter is not a substitute for an authorisation design. [2]

A mobile-friendly dashboard project page structure

Use this order so someone can understand your work without waiting for an interactive report:

1. Project title and business question: “Retail margin analysis: where should the sales team investigate discounting?”
2. Context strip: your role, tools, dataset type and reporting period. Identify self-initiated or synthetic projects.
3. One-sentence takeaway: state what the analysis revealed, without claiming unverified business results.
4. Readable overview image: include alternative text and an explanatory caption.
5. Viewing choices: “Watch walkthrough” and, when suitable, “Explore interactive report.”
6. Case study: business question, cleaning, model, DAX, insights and recommendations.
7. Supporting evidence: selected measure definitions, methodology and a reviewed repository link.
8. Contact action: invite a recruiter to discuss your approach or a prospect to discuss a similar reporting problem.

Ask your website builder or developer for a single-column phone layout, responsive image sizing and a report container that fits the available width. Avoid fixed desktop-width embeds. Test the report itself too: resizing its container does not automatically make dense charts readable.

Place the interactive section below the summary and screenshot. Offer a clearly labelled separate report link where appropriate, and never make the embed the only way to understand the project.

Copy this Power BI case-study template

Replace the bracketed prompts with your actual work. The retail example below is illustrative, not a claim about a real client or outcome.

Business question and scope

Template: “The intended user is [role]. They need to decide [decision]. This report examines [scope and period] using [public, synthetic or approved data]. Success would mean [decision or process improvement].”

Example question: “Which combinations of city, product category and sales channel need investigation for weak margins?” State your contribution and distinguish it from collaborators’ work.

Data cleaning and model

Template: “The source contained [issues]. I applied [transformations] because [reason], validated them using [checks], and documented [remaining limitations].”

• Explain how you handled duplicates, missing values, returns and inconsistent category labels.
• Specify date and currency conventions; identify assumptions rather than silently filling gaps.
• Describe the fact-table grain and relationships to date, product and location tables.
• Show how row counts and totals reconciled before and after cleaning.

Describe actual choices. “Removed duplicates” is less useful than explaining which fields defined a duplicate and why legitimate repeated transactions were retained.

DAX measures and validation

Include a few important measures and explain their business meaning. For an illustrative model with a Sales table, these could be:

• Revenue = SUM(Sales[NetSales])
• Gross Profit = SUM(Sales[NetSales]) - SUM(Sales[Cost])
• Gross Margin % = DIVIDE([Gross Profit], [Revenue])

Adapt the fields and definitions to your dataset. Define whether net sales includes returns or taxes, and format the margin as a percentage. Explain why the margin uses total profit divided by total revenue rather than an unweighted average of row-level percentages. Record checks for zero revenue, returns and filtered totals.

Insights and recommendations

Insight template: “Within [period and filters], [observed pattern] appears in [visual or measure]. I checked [alternative explanation]. The evidence does not establish [limitation].”

Recommendation template: “Ask [decision owner] to investigate or test [action], monitor [metric], and review after [defined period].”

Separate observation from causation. A low-margin channel might justify reviewing discounts and product mix; it does not, by itself, prove that discounts caused the result.

Outcome and reflection

State whether recommendations were implemented. For a portfolio exercise, write “proposed next steps” or “expected decision benefit,” not invented revenue gains or time savings. Finish with what you would improve with better data or more time.

Add projects to a template-based or custom website

Template-based portfolio

Choose a template with project detail pages, readable text sections, image galleries and video support. Before committing, verify that its editor accepts the Power BI embed method you intend to use. If it does not, use screenshots and a clearly labelled external report link.

Repeat the same case-study structure across projects. A repository can hold reviewed documentation and measure examples; link directly to the project page from your CV and LinkedIn. Portfolio guidance also recommends short write-ups, organised repositories and LinkedIn’s Featured section. [7]

Custom portfolio

Choose a custom build when you need more control over project navigation, mobile presentation or interactive behaviour. Specify screenshot fallbacks, accessible controls and clear error states. A custom website changes presentation; it does not override Power BI permissions.

PaidPortfolio builds portfolio websites for Indian professionals. Explore its templates for a consistent project layout or a custom portfolio for a tailored presentation.

Final checks before applying or pitching

• Open every project link while signed out.
• Check the page, images and viewing controls on a phone.
• Verify publication permission and review every visible data detail.
• Make dataset provenance, your contribution and limitations explicit.
• Check that DAX definitions match the displayed metrics.
• Keep the business question and recommendation understandable without interaction.
• Send the most relevant project link, not just your homepage.

The goal is not merely to display a dashboard. It is to show that you can frame a business problem, prepare trustworthy data and explain a defensible recommendation.