rss.livelink.threads-in-node

Fabric ML Model Endpoint returns 401 from application but works in Postman with the same token

vkeda29 — Thu, 29 Oct 2026 16:05:27 GMT

Hi,

I'm currently integrating the Fabric ML Model endpoint with a .NET application and encountering a 401 Unauthorized error when calling the scoring API.

The endpoint is activated and working as expected when tested directly through Postman. However, when the application calls the same Fabric scoring API, it returns HTTP 401.

As far as we've verified, the same Bearer token and authentication details are being used.

Endpoint pattern:

POST /v1/workspaces/{workspaceId}/mlmodels/{modelId}/endpoint/score

Error response:

{ "errorCode": "RequestFailed", "message": "Unable to process the request", "isRetriable": false }

Additional details from the application logs:

HTTP status: 401 Unauthorized
Authorization header present on final request: True
WWW-Authenticate header: Empty
Postman request: Successful
Application request: Fails with 401

The error response doesn't provide any additional information to identify the exact cause.

I'm trying to understand whether there are any specific authentication, authorization, endpoint configuration, or HTTP client requirements when calling Fabric ML Model endpoints from an external application.

Has anyone encountered a similar issue where the same token works in Postman but fails when used in the application?

Are there any additional headers, permissions, redirect behaviors, or diagnostic steps that we should check to identify the cause? Any suggestions?

Thanks!

Power BI to set up a request access instructions

3508026 — Thu, 29 Oct 2026 16:02:45 GMT

Hello,
'd like to configure a custom "Request Access" message for users who open a Power BI report link but do not have access. The goal is to display instructions informing users that dashboard access is managed centrally and that they must follow specific guidelines (for example, request access through the our tool) rather than contacting the report owner directly.

Could you please advise where this setting can be configured, or whether it requires specific permissions or an app-level configuration?

Thank you in advance for your help.

Introducing the data engineering agent for Fabric (Project Osmos)

nareshvenkat — Thu, 29 Oct 2026 15:55:24 GMT

AI coding assistants are excellent at turning natural-language transformation instructions into code. For data engineers, the harder question is whether that code produces results they can trust.

You can describe transformation logic in natural language, and an AI coding assistant will happily generate hundreds of lines of Spark code. Impressive.

But a Spark job can execute successfully and still produce completely wrong results. The logic may work for a subset of the data but fail when run against the full dataset. The pipeline's logic and validation checks may not account for future changes to the data or schema. Incremental loads can cause duplicates. Revenue numbers might look perfectly reasonable until someone reconciles them against the source.

Anyone who's spent time working with real-world enterprise data knows that automating data engineering with AI comes with a unique set of challenges.

Data engineering involves more than code: it requires working with large datasets and retaining context about their schemas, relationships, and business rules over time.

Quality & governance matter a lot. The cost of errors or data loss is very high.

Data engineering work typically spans team-based, collaborative, long-running, milestone-driven projects; not a single conversation between one person and a coding agent.

What if specialized, data-aware agents could help teams investigate these problems, implement solutions, and validate the results—not just generate code?

Following Microsoft's acquisition of Osmos in January 2026, we've been working on bringing autonomous data engineering capabilities as a native experience in Microsoft Fabric.

The idea behind Project Osmos is simple: instead of asking AI to help you write data engineering code, you define a complete problem and the outcome you expect. It has the autonomy to use the tools and an orchestration framework to build, validate, troubleshoot, and refine its implementation, making decisions within the boundaries you set and working towards a high quality output.

The task's code execution and data operations run within your selected Fabric lakehouse.

Real-world data engineering is rarely straightforward

Let's take an insurance use case to illustrate the complexity.

Imagine an insurance company consolidating policy and claims data from enterprise systems such as SAP, Guidewire, and Oracle, a common challenge in an industry that grows through acquisitions. The project also needs to ingest external datasets and user-generated data.

The objective is to build a consolidated view of a claim, including its policy, coverage, and financial history.

Sounds reasonable, until you start looking at the data.

The same person, vehicle, or incident could have different IDs across systems. The same ID could also refer to completely different incidents across systems. Reconciling payments and ledger entries needs to be done with extreme caution. Discrepancies could result in overpayments and wrong forecasts.

You need to investigate the data, understand its relationships, establish the business rules, and validate that the resulting view is consistent with those rules. Getting it wrong can have serious downstream implications.

Quality and accuracy matter more than speed.

In this example, a team would ask the Project Osmos to investigate relationships across the datasets, implement the agreed business rules, and validate the consolidated claims view. The agent would autonomously work through the problem and regularly report updates to the user. Users can review the evidence and validate results before accepting the output.

A purpose-built orchestrator

Under the hood, Project Osmos uses a purpose-built orchestrator that coordinates multiple specialized agents to tackle the problem. Each agent has a well-defined role from code generation to validation to evaluation.

The agents interpret instructions, analyze the data, evaluate implementation approaches, generate code in isolated sandboxes, and verify the outputs. They use execution results to guide further iterations, with the aim of meeting your validation and quality requirements. Your team reviews the evidence to determine whether the results are acceptable.

Should the agent need additional information or get blocked, or if the agent determines that the task cannot be accomplished within the constraints, the user will be elicited for input and guidance, and task will pause waiting user input.

Project Osmos isn't merely simulating what the code might do. It submits PySpark code through the Fabric Livy API for execution in Fabric Spark sessions, so it can test the implementation and validate actual results. Whether changes use copies, staging tables, or in-place updates depends on the write pattern you select.

The goal isn't to remove humans from the process. It's to let the agents take on the investigation and implementation work, while allowing people to guide the outcome, resolve ambiguities, and review the evidence.

Figure: Project Osmos coordinates knowledge, Spark worker, and validation agents in Fabric.

Autonomy, with the right guardrails

Of course, giving an AI agent the autonomy to execute code and modify data raises the most important question: How do you make sure it doesn't do something it shouldn't? Before a task starts, you review the operating guardrails recommended by Project Osmos to define the scope and impact of its work. You specify which resources it can use, where outputs should go, whether changes should be staged, how reruns should behave, and whether schema changes are permitted.

Project Osmos also recommends a reasoning effort setting, which users can adjust. More extensive reasoning can be useful for complicated problems, but it also comes at the cost of additional time and compute.

These instructions guide the agent's work, but they aren't a substitute for proper access controls. Agents operate within the user's permissions, and Fabric and OneLake permissions continue to enforce what the agent is authorized to access.

And while Osmos can carry out extensive validation, your team ultimately determines whether the results meet the business requirements.

A persistent task that lives in Fabric

Real-world data engineering problems rarely get completed in a single sitting. Requirements change. New data arrives. Business rules get clarified. Often implementations that worked perfectly the previous month need to be revisited.

With Project Osmos, work is organized into persistent tasks hosted in Microsoft Fabric. Each task represents an ongoing data engineering project, rather than a single chat exchange.

Once created, a task runs independently in Fabric, consuming Fabric capacity units (CUs). You can start it from GitHub Copilot CLI, Claude Code, or Codex using the Skills for Fabric plug-in, then disconnect without stopping the work. You don't need to keep your terminal open, maintain an active chat session, or even keep your laptop running.

The task maintains its state, context, execution history, and outputs. You can monitor its progress in your Fabric Lakehouse, inspect what the agents are doing, review errors, and examine the outputs.

The task is reusable and can evolve with additional instructions. You can interrupt it to provide additional context, clarify a requirement, or pause and resume the work through your local coding agent.

Say you've built a data pipeline, and a new data drop arrives the following week. You don't have to start another task and explain the entire project all over again. You can reference the existing task and ask Project Osmos to process the new data.

It has the context of the previous work and can decide whether to reuse the existing implementation or update it to account for the new data.

Figure: Animated GIF of a persistent Project Osmos task and its activity history in Fabric.

Collaborative by design

Complex data engineering projects are rarely a one-person job.

They involve a team of data engineers, data architects, business analysts, data stewards, and domain experts. And each of these people brings something different to the table.

Getting the details right often requires conversations between people who understand different aspects of the problem.

Project Osmos allows authorized teammates to work with the same task, inspect what's been done, and provide additional guidance.

So instead of passing notebooks back and forth or having different people initiate separate AI conversations with slightly different assumptions, the team can collaborate on the same ongoing work.

The task retains the context as requirements evolve, making it possible for someone joining later to understand what has already been attempted and contribute to the next steps.

Figure: Teammates collaborate on a shared Project Osmos task.

What about the data engineering work you've already done?

So far, we've talked mostly about building new data engineering projects. But a significant amount of engineering effort also goes into maintaining and improving what's already there.

This is also work you can delegate to Project Osmos.

For instance, you could ask Project Osmos to convert an existing pipeline to an incremental load and validate its rerun behavior. You could also ask it to optimize Spark code in existing notebooks, improve the performance of Delta tables in your lakehouse, or assist with migrating data engineering workloads from another platform to Fabric while preserving business rules and validating the results.

Give Project Osmos a try!

Getting started with Project Osmos is straightforward.

Install the Skills for Fabric plugin in GitHub Copilot CLI, Claude Code, or Codex, sign in to Azure, and ask your coding agent to create a Project Osmos task.

Point it to your Fabric workspace and Lakehouse, describe the outcome you want, and specify how you'd like the results to be validated.

You'll need Contributor or higher workspace permissions, the required tenant settings, and an eligible Fabric capacity. Trial capacities are not supported. Review the quickstart for prerequisites and preview limitations before you begin.

We've put together a few resources to help you get started:

Project Osmos Quickstart: A step-by-step walkthrough, including a sample medallion architecture project you can run in an empty Lakehouse.
Project Osmos Overview: A deeper look at how tasks work and what the agent can do.
Best Practices: Guidance for defining project outcomes, setting boundaries, and specifying validation requirements.

Have a messy dataset, a pipeline that needs fixing, or a migration you've been putting off? Give Project Osmos a try and see what it can do!

Combining Two Power BI Dashboards into One Report

b-kopik — Thu, 29 Oct 2026 15:54:21 GMT

Hello,

I currently have two separate Power BI dashboards/reports, each connected to its own data source. I don't need to merge or combine the underlying data sources.

What I'm trying to achieve is having copy the pages with my visualizations so users can access everything in one place.

Is there a way to bring the pages/visuals from one report into another without having to rebuild them manually or merge the datasets? Ideally, I'd like to keep the existing data connections and simply consolidate the reporting experience.

Has anyone done this before, and what would be the recommended approach?

Thanks!

Can't login to Microsoft tenant

Zilvak — Thu, 29 Oct 2026 15:19:05 GMT

Hello,
Usually I joined to Fabric community calls using Microsoft tenant. Last time I did that maybe one month ago. But today I tried and I couldn't do that. At the beginning it was simply error (don't remember what exactly error was). Now I get "Your account has been locked. Contact your support person to unlock it, then try again."

I joined today's call using our company tenant.

Can you help me to restore ability to use microsoft tenant?

Zilvinas

Power BI Matrix Heatmap – How to Display Blank Instead of Zero While Keeping All 24 Hours Visible?

manoj_0911 — Thu, 29 Oct 2026 14:46:49 GMT

Power BI Matrix Heatmap – How to Display Blank Instead of Zero While Keeping All 24 Hours Visible?

Hi everyone,

I am developing a Japanese CXI dashboard in Power BI using a Matrix visual as a heatmap.

My requirements are:

Display all 24 hours (00–23) and all seven weekdays, even when there is no data for certain hours.
Display a blank cell instead of 0 when the selected metric value is zero or blank.
Preserve the heatmap's conditional background formatting.
Continue to support dynamic metric selection through a slicer.

I am using the following DAX measure:

SelectedMetricValue heatmap = COALESCE( SWITCH( SELECTEDVALUE('TOP 10 QUEUES BY'[MetricName]), "OFFERED", 'Measure Table'[TOTAL OFFERED], "応答済み", 'Measure Table'[TOTAL ANSWERED], "放棄された", 'Measure Table'[ABANDONED], "フローアウト", 'Measure Table'[FLOW-OUT], "ハンドル", 'Measure Table'[HANDLE], "移行", 'Measure Table'[TRANSFER], "短時間放棄", 'Measure Table'[SHORT ABANDONED], "サービスレベル合意達成", 'Measure Table'[MET SLA], "ASA", [ASA (S)], "サービスレベル（%）", 'Measure Table'[SERVICE LEVEL], BLANK() ), 0 )

My hour and weekday calculated columns are:

HEATMAP Hour = FORMAT([TXN_DATE], "HH")HEATMAP Weekday = SWITCH( WEEKDAY([TXN_DATE], 2), 1, "月", 2, "火", 3, "水", 4, "木", 5, "金", 6, "土", 7, "日" )

I understand that COALESCE(..., 0) returns zero when the measure is blank, which is why zero values currently appear in the matrix.

My questions:

What is the recommended DAX approach to display blank instead of zero in the Matrix cells?
Can I remove COALESCE() or use a conditional expression to return BLANK() when the selected metric is zero?
How can I keep all 24 hour columns and all seven weekday rows visible when some or all values are blank?
Will returning BLANK() affect conditional background formatting or the ability to show items with no data?
Since my measure supports counts, ASA duration, and service-level percentages, is there a recommended approach that handles all these metric types correctly?

I have attached a screenshot of my current heatmap for reference.

Thank you for your suggestions!

How to Display Count and Percentage in Different Colors in Power BI Decomposition Tree Data Labels?

manoj_0911 — Thu, 29 Oct 2026 14:40:48 GMT

How to Display Count and Percentage in Different Colors in Power BI Decomposition Tree Data Labels?

Hi everyone,

I am developing a Power BI dashboard and need to display the interaction count and percentage of total at the end of each horizontal bar, using different font colors.

My requirement:

Count: Orange — #E66C37
Percentage: Grey — #666666
Both values should appear next to each other at the end of each bar.
Example: 1,091 (26.0%)

Currently, I am using a dynamic format string for my Call Volume measure:

VAR _total = CALCULATE( [Call Volume], REMOVEFILTERS('DETAILS_V'[DIRECTION]), REMOVEFILTERS('DETAILS_V'[MEDIA_TYPE]), REMOVEFILTERS('DETAILS_V'[IVA_OUTCOME]), REMOVEFILTERS('DETAILS_V'[DIVISION]) ) VAR _pct = DIVIDE([Call Volume], _total) RETURN "#,##0 ""(" & FORMAT(_pct, "0.0%") & ")"""

This displays the count and percentage together, but I cannot apply separate font colors to the count and percentage within the same label using the standard formatting options.

My questions:

Is there a way to apply different font colors to individual parts of a data label in a native Power BI horizontal bar chart?
Can this be achieved using separate numeric measures and the native chart's Data labels or Detail settings?
Is there another native Power BI workaround that preserves the horizontal bar chart layout and places both values at the end of each bar?
If native formatting does not support this, is Deneb the recommended solution for displaying the count in #E66C37 and percentage in #666666?

I would prefer to retain the existing bar chart design and ensure that the labels respond correctly to report filters and slicers.

I have attached a screenshot of the current visual for reference.

Thanks in advance for your suggestions!

Securing the Agentic Enterprise with Microsoft Security Copilot, Defender & Sentinel

Riya99 — Thu, 29 Oct 2026 14:19:17 GMT

Traditional security approaches need to evolve to address emerging risks associated with AI-driven operations.

Microsoft Security Copilot, Microsoft Defender, and Microsoft Sentinel bring AI-assisted investigations, threat intelligence, and security analytics together to help security teams identify risks faster and respond more effectively.

📅 Tuesday, December 15, 2026
🕒 12:00 PM EST
🔗 CLICK HERE TO REGISTER: https://cutt.ly/MyYXvNCy

WHY ATTEND?

As AI agents become more capable, securing identities, managing access, and responding to threats across connected environments are increasingly important. Security teams need practical strategies to maintain visibility, manage emerging risks, and improve incident response.

WHAT YOU’LL LEARN

Understand AI Agent Security Risks: Explore emerging security challenges associated with AI agents and enterprise workflows.
Operationalize Microsoft Security Copilot: Discover how AI-assisted capabilities can support security investigations and daily SecOps activities.
Investigate Threats with Defender and Sentinel: Learn how to use security signals and analytics to investigate incidents and strengthen response workflows.
Govern Security Copilot: Understand approaches to managing workspaces, access, and plugins.
Manage Security Agent Lifecycles: Explore considerations for managing Microsoft and partner-built security agents.
Strengthen AI-Driven SecOps: Discover strategies for integrating AI capabilities into enterprise security operations.
Join the Live Q&A: Get your questions answered by a Microsoft Certified Trainer.

WHO SHOULD ATTEND?

CISOs and security leaders
SOC managers and security analysts
Security architects and engineers
Cloud, AI, and identity security professionals
IT directors and security operations decision-makers

Benefits of Learning with NetCom Learning

NetCom 365 Portal: Access a digital learning platform with reporting capabilities and complimentary additional learning resources.
Microsoft Certified Trainer : Learn from an expert instructor at NetCom Learning, the 2023 Microsoft US Learning Partner of the Year.

See you in the masterclass! 😊

Enable "Include My Changes" when sharing reports from Power BI Apps

jakka_pranesh — Thu, 29 Oct 2026 14:16:47 GMT

Business Need: Business users consume reports through Power BI Apps and need the ability to share their current filtered report view with other authorized users.

Current Limitation: The "Include my changes" option is available when reports are accessed from workspaces but is unavailable when the same reports are accessed through Power BI Apps. Personal bookmarks also cannot be shared with others. [community....rosoft.com], [learn.microsoft.com]

Expected Behavior: Provide an option in Power BI Apps to:

Share report with current filters and slicers applied.
Generate a shareable URL containing the current report state.
Optionally create and share personal bookmarks with users who already have report access.

Business Benefits:

Improves collaboration among business users.
Reduces dependency on report developers.
Increases Power BI App adoption.
Provides consistent sharing capabilities across Workspace and App experiences.

Power BI Subscriptions: Allow Multiple Users to Manage a Subscription

annstruchen — Thu, 29 Oct 2026 13:44:19 GMT

Currently, a Power BI subscription is managed by the individual who created it. For subscriptions used to distribute business reports to groups of users, this creates unnecessary dependency on a single person.

Please provide the ability to assign multiple owners or managers to a Power BI subscription so authorized users can maintain the same subscription without having to recreate it.

Additional subscription managers should be able to:

View and edit the subscription configuration
Add or remove recipients
Update the schedule and delivery options
Enable, disable, or run the subscription
Maintain the subscription when the original creator is unavailable or leaves the organization

For business-critical reporting, subscription management is often a team responsibility rather than an individual responsibility. Allowing multiple designated managers would improve continuity, reduce key-person dependency, and make administration of shared Power BI reports more sustainable.

Ideally, the subscription creator could designate one or more additional managers, or management rights could be granted based on an appropriate Power BI workspace role.

Power BI Dataflow Refresh Fails Despite Queries Loading Successfully in Power Query

Crystal_Dsouza — Thu, 29 Oct 2026 13:32:56 GMT

Hi everyone,

I'm facing an issue with a Power BI Dataflow and would appreciate some guidance.

I have three queries pulling data from different sources, which I've appended into one final query using Table.Combine.

All three queries load correctly in Power Query, and the appended query also previews the combined data without any errors.

I've disabled Enable Load for the three source queries and kept it enabled only for the final appended query.

However, whenever I refresh the dataflow, the refresh fails, and the error only shows a Request ID and Activity ID without any specific details.

I've also tried simplifying the final query to just the basic append operation, but the refresh still fails.

Has anyone experienced something similar? Could this be related to query dependencies, combining different data sources, or dataflow settings? Any suggestions on how to troubleshoot or resolve this would be greatly appreciated.

Thank you!

Power BI Subscriptions: Allow a Generic Power BI Sender Instead of the Subscription Owner

annstruchen — Thu, 29 Oct 2026 13:27:13 GMT

With the recent changes to Power BI subscription emails, subscription notifications can appear to recipients as though they were sent directly by the person who created or owns the subscription.

For automated report subscriptions, this can be confusing to recipients. The individual who configured the subscription may not be the report owner, business contact, or appropriate person to receive questions about the report. It can also make an automated system-generated notification appear to be a personally sent email.

Please provide an option for Power BI subscription emails to be sent from a generic Power BI or organizational sender address, rather than the individual subscription owner.

Ideally, organizations or subscription owners could choose from options such as:

A generic Microsoft Power BI sender
An organization-defined or shared mailbox
The subscription owner, when that behavior is desired

This would make it clearer that the email is an automated Power BI subscription while allowing organizations to select the sender identity that best fits their reporting and support model.

Power BI Subscriptions: Restore the Ability to Open or Enlarge the Individual Report Page Preview

annstruchen — Thu, 29 Oct 2026 13:24:56 GMT

With the recent changes to Power BI subscription emails, the subscribed report page is displayed as a small preview within the email, and recipients no longer have the ability to open the individual page image in a larger view.

For reports that are distributed through subscriptions, the report page itself is often the primary content users need to review. The current preview can be too small to easily read detailed tables, charts, or other information. Attaching the full report is not an appropriate alternative when recipients only need the single subscribed page.

Please provide an option to either:

Open or download the individual subscribed report page as an image or attachment, similar to the previous experience, or
Configure the inline report page preview to display at a larger size.

This would allow users to view the subscribed page clearly without requiring them to open the full Power BI report or receive an attachment containing pages they do not need.

Composite model Refresh issue

Flypigeon0929 — Thu, 29 Oct 2026 10:27:32 GMT

Hi guys,
I wanted to consolidate 3 power bi reports into one, following it i used the live connection semantic model top get data, after that adding another report, it converted the live connection to direct query storage mode, i was able to create the consolidated report after publishing it on the service the refresh took 1 second finding out that the report isnt refreshing its showing the older data,
any solution for this, I used the power bi Workspace apps to show the report as i needed only one page from each report(Summary Page) but the business denied it bevcause they want to see the 3 reports in scrolling

Can I start a new Fabric trial capacity after the 60-day trial expires?

Lucassabetta5 — Thu, 29 Oct 2026 10:01:13 GMT

Hi everyone,

Once a Fabric trial capacity reaches its 60 days and expires, can I start a new trial capacity in the same tenant? The documentation says that eligibility for another trial isn’t guaranteed and that Microsoft might restrict repeated trials, but it doesn’t explain the exact rules.

Specifically:

Can the same user, or another user in the same tenant, start a new trial after the first one expires?
Does an expired trial still count toward the tenant’s trial capacity limit?

How to Display Both Total Call Volume and Percentage of Total in a Power BI Decomposition Tree?

manoj_0911 — Thu, 29 Oct 2026 09:59:25 GMT

How to Display Both Total Call Volume and Percentage of Total in a Power BI Decomposition Tree?

Hi everyone,

I am building a Contact Center Summary Dashboard in Power BI using the native Decomposition Tree visual.

My current configuration is:

Analyze: Total Call Volume
Explain by: Direction → Media Type → IVA Outcome → Division

The decomposition tree correctly displays the total call volume at each level. However, I would also like to display the percentage of total call volume alongside the call count for each node.

For example, my total call volume is 4,202:

Category	Call Volume	% of Total
Inbound	2,161	51.4%
Outbound	2,041	48.6%
Voice	1,767	42.1%
Message	346	8.2%

The percentage should be calculated against the overall total of 4,202 while respecting report filters and slicers, such as date, organization, and other selected filters.

My questions:

Does the native Power BI Decomposition Tree support displaying both the call count and percentage of total directly on each node?
Can a DAX measure be added to the Tooltips field to show the percentage when hovering over a node?
Is there a supported workaround to display the count and percentage together, such as 2,161 (51.4%), on each node?
If the native visual does not support this, would a custom visual or another approach be recommended?

I would prefer to retain the native Decomposition Tree because its drill-down functionality is useful for analyzing call volume by Direction, Media Type, IVA Outcome, and Division.

I have attached a screenshot of my current visual for reference.

Thanks in advance for your help!

How to Display Different Colors for Count and Percentage in Power BI Bar Chart Data Labels?

manoj_0911 — Thu, 29 Oct 2026 09:56:49 GMT

How to Display Different Colors for Count and Percentage in Power BI Bar Chart Data Labels?

Hi everyone,

I’m developing a Power BI dashboard and would like to display data labels on a horizontal bar chart with two different colors.

My requirement:

Interaction count should appear in orange (#FF7043).
Percentage should appear in grey (#808080).
Both values should appear together at the end of each bar.

For example:

33 (0.8%)
1,091 (26.0%)
562 (13.4%)
1,310 (31.2%)

Currently, I am using the following DAX measure to combine the count and percentage into a single text label:

Duration Volume Summary = VAR CallVolume = [INTERACTION DURATION VOLUME] VAR Percentage = DIVIDE( CallVolume, CALCULATE( [TOTAL INTERACTIONS], REMOVEFILTERS('Duration Buckets') ), 0 ) RETURN FORMAT(CallVolume, "#,0") & " (" & FORMAT(Percentage, "0.0%") & ")"

Since both values are returned as a single text string, I cannot apply separate font colors to the count and percentage using the standard data-label formatting options.

My questions:

Is it possible to display different colors for individual parts of a data label in a native Power BI bar chart?
If this is not supported natively, is there a workaround that allows the count to remain orange and the percentage to appear grey?
Would Deneb, another custom visual, or a combination of visuals be the best approach to achieve this while keeping the labels aligned at the end of each bar?

I would prefer a solution that preserves the existing horizontal bar chart layout and responds correctly to report filters and slicers.

I have attached a screenshot of the current visual for reference.

Thanks in advance for your suggestions!

Cost of Living Tracker: Power BI report that breaks US inflation into categories (free to download)

AnalyticPulse — Thu, 29 Oct 2026 09:56:27 GMT

Hi everyone,

Headline inflation hides the real story: rent can climb while gasoline falls, and the average matches nobody’s budget. I built a Power BI report that breaks the consumer price index into the categories that make up a household budget.

What’s on the page

Six KPI cards for all items, food, rent, energy, medical care and transportation, each with a change since last month and a trend line
A key-insight sentence and a “purchasing power of $100” card, both written with DAX and driven by a period selector (1Y to Max)
A ranked bar chart of inflation by category and a price chart with three views: change vs year ago, price index and monthly change
A month-by-month heatmap colored by a measure
Housing, energy and food deep dives (rent vs owners’ equivalent rent, gasoline vs electricity, food at home vs away)
A personal inflation view with Renter, Homeowner, Student and Retiree profiles, using illustrative spending weights

How it’s built

Data comes from 14 BLS price series through the FRED API, loaded in one Power Query that loops over the series list, so a bad ID only blanks that series.
A category dimension table drives colors and groupings, and a disconnected table drives the period selector and the three views.
The heatmap and line colors come from measures using “format by field value”.
Personal inflation is a weighted sum over a profiles table.
The project was built as a PBIP, so the model and report are plain text.

Free to download

The PBIX is free. Email contact@docynx.com and I’ll send it. The file includes a working FRED API key, or you can replace it with your own free key inside the Cpi query.

More on my site

I wrote a longer walkthrough of each visual, the series codes and how to read the numbers. You’ll also find the full report there, plus my other dashboards:

👉 https://www.docynx.com/dashboard/cost-of-living-tracker-dashboard

I’d like feedback on the heatmap and the personal inflation idea. Would you prefer sliders, or presets like these?

Thanks for looking!

Explore Dashboard Gallery

Will Invoke Pipeline (Legacy) be deprecated?

benitovbreugel — Thu, 29 Oct 2026 09:30:45 GMT

Is there currently any plan or timeline to deprecate Invoke Pipeline (Legacy) in Microsoft Fabric?

For same-workspace pipeline orchestration, the Legacy activity is still very convenient. The new Invoke Pipeline activity provides additional capabilities, such as cross-workspace invocation and child-pipeline monitoring, but it also requires a Connection object.

Given the performance concerns that have been reported by multiple users, I’m wondering what the recommended approach is:

Is it safe to continue using Invoke Pipeline (Legacy) for now?
Does Microsoft recommend migrating existing pipelines to the new Invoke Pipeline activity?
Is there any indication that the Legacy activity will eventually be deprecated or removed?
Should we already start rebuilding existing pipeline orchestration using the new activity and Connections?

It would be great to understand the intended direction, especially before investing time in rebuilding existing pipeline implementations.

Thanks!

Change Community Login Email

adityavighne — Thu, 29 Oct 2026 09:18:49 GMT

Hello Team,

I would like to know how I can change community login email.

Do let me know the process.

Thank you!

Aditya Vighne

rss.livelink.threads-in-node

Fabric ML Model Endpoint returns 401 from application but works in Postman with the same token

Power BI to set up a request access instructions

Introducing the data engineering agent for Fabric (Project Osmos)

Real-world data engineering is rarely straightforward

A purpose-built orchestrator

Autonomy, with the right guardrails

A persistent task that lives in Fabric

Collaborative by design

What about the data engineering work you've already done?

Give Project Osmos a try!

Combining Two Power BI Dashboards into One Report

Can't login to Microsoft tenant

Power BI Matrix Heatmap – How to Display Blank Instead of Zero While Keeping All 24 Hours Visible?

How to Display Count and Percentage in Different Colors in Power BI Decomposition Tree Data Labels?

Securing the Agentic Enterprise with Microsoft Security Copilot, Defender & Sentinel

WHY ATTEND?

WHAT YOU’LL LEARN

WHO SHOULD ATTEND?

Enable "Include My Changes" when sharing reports from Power BI Apps

Power BI Subscriptions: Allow Multiple Users to Manage a Subscription

Power BI Dataflow Refresh Fails Despite Queries Loading Successfully in Power Query

Power BI Subscriptions: Allow a Generic Power BI Sender Instead of the Subscription Owner

Power BI Subscriptions: Restore the Ability to Open or Enlarge the Individual Report Page Preview

Composite model Refresh issue

Can I start a new Fabric trial capacity after the 60-day trial expires?

How to Display Both Total Call Volume and Percentage of Total in a Power BI Decomposition Tree?

How to Display Different Colors for Count and Percentage in Power BI Bar Chart Data Labels?

Cost of Living Tracker: Power BI report that breaks US inflation into categories (free to download)

Hi everyone,

Headline inflation hides the real story: rent can climb while gasoline falls, and the average matches nobody’s budget. I built a Power BI report that breaks the consumer price index into the categories that make up a household budget.

What’s on the page

How it’s built

Free to download

More on my site

Other links:

Explore Dashboard Gallery

Will Invoke Pipeline (Legacy) be deprecated?

Change Community Login Email