Ravindra BagaleCourses & study guides Track your progress

Chapter 43

43.1 Licensing, Capacity, Fabric and Admin Basics

Chala mitrano — wrong licence plans block sharing on Monday. Separate authors from viewers, know capacity vs Pro, skim Fabric, and escalate tenant switches.

Fictional sample data for learning. All company names and brands belong to their owners. We use the names only so students can understand. Numbers on this page are made up.
After this lesson you can
  • Contrast Free, Pro, and PPU at a practical level.
  • Explain when capacity helps many viewers.
  • Give a one-page Fabric overview without buzzword panic.
  • Name tenant admin concerns like Publish to web.
  • Prepare a licence conversation with finance and Cloud.
  • Deliver a clear interview licence ladder.

Start with a problem (fictional). Finance lead Ananya Iyer asks why 200 city managers each need Pro. Cloud says capacity might help viewers. A blog comments “just use Fabric” and confuses the team. Priya separates authors vs viewers, checks current docs, and books a 30-minute Cloud call — no purchase from a rumour.

Sample layout — fictional data: Free Pro PPU capacity Fabric ladder
Sample layout — fictional data (not a real Service screenshot)

1. Free, Pro, PPU — what changes for sharing

Why: A Free user cannot freely share into the collaboration pattern most teams expect.

What: Pro is the common per-user licence to publish and share with other Pro users. PPU unlocks some premium features per user. Always re-check Microsoft’s current matrix — it evolves.

How — think before you promise:

Vertical steps (one under another)

  1. List who authors vs who only views.
  2. If everyone authors/shares peer-to-peer, plan Pro (or higher) for those people.
  3. If hundreds only view Apps, ask whether capacity makes sense.
  4. Never promise “Free can do everything” — test with a real guest account.
  5. Re-read Microsoft’s current licence matrix before buying.

Tiny example: 12 authors + 200 viewers (fictional MH Ops) is a different bill than 212 Pro seats.

Ravindra Bagale's Tip

Friends, this chapter teaches thinking, not a price list — verify current Microsoft docs.

2. Capacity mindset (overview)

Why: Leadership asks why viewers still need Pro on every report.

What: Content on a capacity can be viewed under capacity rules; admins assign workspaces to a capacity (SKU names change — learn the idea).

How — ask the right questions:

Vertical steps (one under another)

  1. Know which workspaces are on shared capacity vs Pro-only.
  2. Move the Prod App workspace to capacity only with Cloud/admin approval.
  3. Watch refresh concurrency and model size limits for your SKU.
  4. Keep Dev on a smaller footprint when possible.
  5. Document who pays and who owns the capacity.

Tiny example: MH Prod App on capacity (fictional) so 200 city viewers read without individual Pro — authors still licensed to publish.

Ravindra Bagale's Tip

Friends, capacity does not delete RLS — security still matters.

3. Fabric overview in one page

Why: Buzzwords scare beginners; you need a calm map.

What: Microsoft Fabric brings analytical items (Lakehouse, Warehouse, Dataflow Gen2, notebooks, …) beside Power BI. Power BI remains how many people consume.

How — keep the map small:

Vertical steps (one under another)

  1. Remember: Power BI reports can sit on Fabric capacities.
  2. Dataflow Gen2 / Lakehouse may replace some classic patterns — learn when your tenant has them.
  3. Do not rewrite every model on day one of Fabric.
  4. Keep RLS, Apps, and refresh discipline — they still matter.
  5. Ask Training which Fabric items your company enables.

Tiny example: Training note (fictional): “We enable Dataflow Gen2 this quarter; lakehouse next — don’t migrate blindly.”

Ravindra Bagale's Tip

Friends, Fabric is a platform map — not a reason to throw away working Apps overnight.

4. Admin basics you will hear in meetings

Why: Someone must turn on features and block Publish to web.

What: Power BI / Fabric admin portal settings control tenant switches, export, embed, and trial behaviour.

How — know your lane:

Vertical steps (one under another)

  1. Know who your tenant admin is (often Cloud/IT).
  2. Request: disable Publish to web if policy says so.
  3. Request: allow service principals only where needed.
  4. Understand that workspace creation may be limited.
  5. Never change tenant settings without change control.

Tiny example: Priya is workspace admin — she escalates Publish to web disable to Cloud with a ticket.

Ravindra Bagale's Tip

Friends, you are usually a workspace admin, not the tenant admin — escalate.

5. Worked example — licence conversation with finance

Why: Finance wants costs; Ops wants city managers viewing Apps.

What: Separate author licences from viewer strategy; write assumptions.

How — run the meeting:

Vertical steps (one under another)

  1. Count authors who publish (need Pro/PPU as applicable).
  2. Count viewers of Prod App.
  3. Option A: all Pro. Option B: capacity + fewer author licences.
  4. List risks (SKU limits, admin overhead).
  5. Schedule a 30-minute call with Cloud before purchase.

Tiny example: Slide (fictional): 12 authors Pro, 200 viewers via capacity — pending Cloud SKU check.

Ravindra Bagale's Tip

Friends, never buy from a WhatsApp forward — Cloud + current docs only.

6. Interview lines

Why: They ask Free vs Pro vs Premium/capacity in one minute.

What: Free: limited sharing. Pro: peer share. Capacity: scale viewing. Fabric: platform extras. Always check current docs.

How — practise sixty seconds:

Vertical steps (one under another)

  1. Say you verify docs — licences evolve.
  2. Separate authors and viewers.
  3. Mention tenant admin for Publish to web.
  4. Admit when you escalate to Cloud.
  5. Tie answer to a real App audience size.

Tiny example: Good close: “I’d confirm today’s SKU names with Microsoft docs and our Cloud team.”

Ravindra Bagale's Tip

Friends, humility about changing SKUs sounds more senior than fake certainty.

Quiz (5 questions)

1. Pro licence mainly helps with:

2. Capacity is often discussed when:

3. Fabric overview lesson:

4. Tenant admin settings include things like:

5. Before buying licences you should:

Practice tasks (12) — hints only, no full answers

  1. Task. Table: Free / Pro / capacity — one line each.
    Hint: sections 1-2.
  2. Task. Count authors vs viewers for a fictional 12/200 org.
    Hint: section 5.
  3. Task. Why verify Microsoft docs each year?
    Hint: licences change.
  4. Task. List two tenant switches Cyber may care about.
    Hint: Publish to web.
  5. Task. Fabric: name two item types besides Power BI reports.
    Hint: section 3.
  6. Task. Interview 60-second Free vs Pro vs capacity.
    Hint: section 6.
  7. Task. When do you escalate vs change a tenant switch yourself?
    Hint: section 4.
  8. Task. Risk of moving Prod to capacity without approval?
    Hint: Cloud change control.
  9. Task. Why Dev might stay off the biggest capacity.
    Hint: cost / blast radius.
  10. Task. Draft three questions for a licence meeting.
    Hint: authors viewers SKU.
  11. Task. Does capacity remove the need for RLS?
    Hint: no.
  12. Task. What is PPU in one sentence?
    Hint: premium features per user.

Ravi Sir's cards (Excel card style)

Standalone cards — no tip or photo sections. QR points to this lesson. Download PNG to revise offline.

Interview Q&A: Explain Free, Pro, capacity and Fabric in one minute
Download interview-card PNG
Comparison Card: All Pro licences vs capacity for viewers
Download comparison-card PNG
Revision Card: Admin guardrails to remember
Download revision-card PNG

Think like a professional

In a real tenant, rights and sharing are controlled by Fabric / Power BI admins. Always follow your company policy. This lesson uses fictional people and numbers so you can practise the ideas safely.