Ravindra BagaleCourses & study guides Track your progress

Chapter 42

42.1 Subscriptions, Alerts, Teams, Excel and Embedding

By Ravindra Bagale · Power BI deep series

Chala mitrano — managers will not live in the Service all day. Push the 07:05 IST PDF, alert when stock dips, pin Teams, pivot in Excel — without Publish to web.

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
  • Schedule an email subscription after refresh.
  • Set a data-driven alert on a dashboard tile.
  • Add a Power BI tab in Teams without bypassing RLS.
  • Use Analyze in Excel on the live model.
  • Refuse Publish to web for confidential data.
  • Explain push vs pull delivery in an interview.

Start with a problem (fictional). Aarav Shah (Mumbai cold-store lead, fictional) never opened the App before 09:00 IST standup. Stock ₹ value dipped overnight and nobody knew. Mei Lin in Singapore (partner ops) wanted pivots in Excel. Cyber rejected Publish to web. Priya wires subscriptions, alerts, Teams, and Excel — securely.

Sample layout — fictional data: report to subscription Teams Excel embed
Sample layout — fictional data (not a real Service screenshot)

1. Email subscriptions that arrive before standup

Why: If the PDF lands after the 09:00 IST meeting, nobody reads it.

What: A subscription emails a report page, dashboard, or scorecard on a schedule (licence limits apply).

How — set a useful subscription:

Vertical steps (one under another)

  1. Open the report → Subscribe.
  2. Pick page, frequency (daily), time 07:05 IST, and recipients (yourself first).
  3. Choose PDF or image where offered; save.
  4. Confirm refresh finished before the subscription time.
  5. Add the city-manager security group only after a test mail looks right.

Tiny example: Pune plant head (fictional) gets Ops page PDF every weekday 07:05 IST — after 06:45 refresh.

Ravindra Bagale's Tip

Friends, subscription time must be after scheduled refresh — else yesterday’s numbers.

2. Data-driven alerts on dashboard cards

Why: You need a ping when refrigerated stock ₹ value drops under a floor — not another inbox PDF.

What: Alerts watch a dashboard tile (often a card) and email when above/below a threshold.

How — wire one alert:

Vertical steps (one under another)

  1. Pin the KPI card to a dashboard.
  2. On the tile … → Manage alerts.
  3. Set condition (below 500000), frequency, and recipients.
  4. Save; trigger a test if available.
  5. Document who owns the alert when people change roles.

Tiny example: Cold-store alert (fictional): InventoryValue card below ₹5,00,000 → mail to night supervisor Aarav.

Ravindra Bagale's Tip

Friends, alerts need a refreshed Import tile — a stuck refresh means a silent night.

3. Teams tab — report where chat already is

Why: Asking staff to leave Teams for another URL slows adoption.

What: You can add a Power BI tab to a Teams channel pointing at a report or App content.

How — add the tab:

Vertical steps (one under another)

  1. In the channel, + → Power BI.
  2. Pick workspace and report (or App).
  3. Name the tab “MH Ops — Today”.
  4. Confirm members have Power BI permission (RLS still applies).
  5. Pin the tab for the channel.

Tiny example: Nagpur ops channel (fictional) pins the App page — Raja still only sees Nagpur via RLS.

Ravindra Bagale's Tip

Friends, Teams does not bypass RLS or workspace roles — permissions still matter.

4. Analyze in Excel

Why: Finance still lives in pivots — fight less, connect more.

What: Analyze in Excel gives a live connection to the semantic model (with permission).

How — open a live pivot:

Vertical steps (one under another)

  1. In Service, on the semantic model or report → Analyze in Excel.
  2. Open the workbook; sign in if asked.
  3. Build pivots on the model fields — do not paste static values as source of truth.
  4. Refresh to get latest Service data after model refresh.
  5. Remind users RLS still filters their pivots.

Tiny example: Controller Sofia Müller (fictional) pivots Margin by City on the shared model — same RLS as the App.

Ravindra Bagale's Tip

Friends, exporting a CSV snapshot is not the same as Analyze in Excel — snapshots go stale and skip RLS updates.

5. Embedding basics — stay inside the wall

Why: Publish to web is public. Most company data must never use it.

What: Secure options include embed for your organisation, SharePoint embed, and authenticated patterns — not anonymous public links.

How — choose a safe path:

Vertical steps (one under another)

  1. Prefer SharePoint / Teams / secure embed over Publish to web.
  2. Never Publish to web salary, patient, or customer phone data.
  3. For internal portals, embed with Azure AD user identity so RLS applies.
  4. Document which URL is external-facing — review with Cyber.
  5. When unsure, share App link with authentication instead.

Tiny example: Cyber (fictional) rejects public embed for dairy customer phones — App + groups wins.

Ravindra Bagale's Tip

Friends, if Cyber says no to public embed, that is the answer — use App + groups.

6. Interview: push vs pull

Why: They ask how stakeholders get numbers without living in the Service.

What: Push: subscriptions and alerts. Pull: Teams tab, App, Analyze in Excel. Never public web for private data.

How — practise the answer:

Vertical steps (one under another)

  1. Give one subscription example with time after refresh.
  2. Give one alert threshold example in ₹.
  3. Mention Teams tab + RLS.
  4. Say Analyze in Excel keeps one model.
  5. Reject Publish to web for confidential data.

Tiny example: Good line: “We push at 07:05 after refresh; we never Publish to web private stock.”

Ravindra Bagale's Tip

Friends, say push vs pull in one breath — interviewers love clear structure.

Quiz (5 questions)

1. Subscriptions should run:

2. Data-driven alerts need:

3. Teams Power BI tab:

4. Analyze in Excel is best when:

5. Publish to web is:

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

  1. Task. Write a subscription plan: page, time IST, recipients.
    Hint: section 1.
  2. Task. Why test the mail before adding the whole group?
    Hint: bad PDF blast.
  3. Task. Design an alert for stock below ₹5,00,000.
    Hint: section 2.
  4. Task. List Teams tab steps for MH Ops channel.
    Hint: section 3.
  5. Task. Interview: does Teams bypass RLS? Answer clearly.
    Hint: no.
  6. Task. When is Analyze in Excel better than exporting CSV?
    Hint: live + RLS.
  7. Task. Name two safe embed homes vs Publish to web.
    Hint: section 5.
  8. Task. Draft a Cyber one-liner rejecting public embed.
    Hint: confidential.
  9. Task. Order: refresh 06:45, subscription 07:05, standup 09:00 — why?
    Hint: order.
  10. Task. Who should own an alert when the creator leaves?
    Hint: document owner.
  11. Task. Compare push (subscription) vs pull (App open).
    Hint: section 6.
  12. Task. Excel pivot still wrong city — what do you check?
    Hint: RLS / permissions.

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: How do people get numbers without living in the Service?
Download interview-card PNG
Comparison Card: Subscription vs data-driven alert
Download comparison-card PNG
Revision Card: Delivery checklist before you share
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.