rss.livelink.threads-in-node

Add Automated Pre-Upgrade Compatibility Assessment for Fabric Spark Runtimes

mourakshit — Sat, 19 Sep 2026 21:49:22 GMT

Microsoft Fabric should provide an automated compatibility assessment before a workspace, Environment, notebook, or Spark Job Definition is upgraded to a newer Fabric Runtime.

Spark runtime upgrades can introduce significant platform changes, including new versions of Apache Spark, Python, Java, Scala, Delta Lake, operating-system components, built-in libraries, and execution behavior.

Today, teams can test a new runtime manually, but enterprise customers need a faster way to understand which workloads are likely to break before changing the runtime.

Fabric should provide a "Run Compatibility Assessment" capability that analyzes the workloads attached to an Environment or workspace before an upgrade.

The assessment should identify:

Python libraries that are incompatible with the target runtime

Custom wheel, JAR, or R package compatibility issues

Scala and Java version incompatibilities

Deprecated Spark APIs used by notebooks or Spark Job Definitions

Removed or changed configuration properties

Delta Lake protocol or feature compatibility risks

Native Execution Engine compatibility issues

Python version breaking changes

UDF compatibility issues

Structured Streaming compatibility concerns

Notebook or job dependencies that require remediation

Environments that must be republished after the runtime change

Workloads that passed compatibility validation

Fabric should generate a report that classifies each workload as:

Compatible

Compatible with warnings

Requires remediation

Unable to assess

For every detected issue, the report should identify the affected notebook, Spark Job Definition, Environment, library, or configuration and explain the remediation required.

For example, before moving an enterprise workload from Runtime 1.3 to Runtime 2.0, an administrator should be able to scan all notebooks and jobs attached to the Environment and determine whether changes in Python, Scala, Java, Spark, Delta Lake, or installed libraries are likely to cause failures.

The assessment should also be available through REST APIs and CI/CD so organizations can automatically validate runtime compatibility before promoting changes into production.

This would significantly reduce runtime-upgrade risk and make Spark platform lifecycle management safer for large Fabric environments.

Support Creator-Independent Managed Identity and Ownership Transfer for Fabric Operations Agents

mourakshit — Sat, 19 Sep 2026 21:47:51 GMT

Microsoft Fabric Operations Agents should support an enterprise identity and ownership model that is independent of the individual user who originally created the agent.

Today, an Operations Agent receives its own Microsoft Entra Agent ID, but the agent operates using the delegated identity and permissions of its creator.

This creates an operational dependency on an individual employee account.

For production environments, an Operations Agent may run continuously for months or years. The agent should not stop working or unexpectedly lose access because the original creator changes roles, loses access to a workspace, leaves the organization, or has permissions modified.

Fabric should support:

Creator-independent agent identity

Managed identity or service-principal-style execution

Explicit permissions assigned directly to the agent

Transfer of agent ownership to another user or team

Multiple agent owners or administrators

Separation between agent owner, operator, approver, and notification recipient

Ability to rotate or replace the execution identity without recreating the agent

Clear visibility into which identity is used for every query and action

Permission validation before an agent is started

Alerts when the agent's required permissions are removed

Audit history for identity and ownership changes

Support for deployment across development, test, and production using environment-specific identities

For example, a manufacturing Operations Agent may continuously monitor equipment telemetry and invoke a Fabric notebook or Power Automate workflow when abnormal conditions are detected.

If the employee who originally created that agent leaves the project, the production agent should continue operating using an enterprise-managed identity rather than depending on the former employee's delegated permissions.

Administrators should also be able to transfer ownership without recreating the agent, regenerating its playbook, or breaking its rules and downstream actions.

This capability would make Operations Agents significantly safer for long-running enterprise automation and would align agent lifecycle management with established enterprise security, least-privilege, and service-identity practices.

Add Centralized Health, Freshness Monitoring, and Alerts for OneLake Shortcuts

mourakshit — Sat, 19 Sep 2026 21:45:04 GMT

Microsoft Fabric should provide a centralized health-monitoring experience for OneLake Shortcuts across workspaces and data sources.

As organizations adopt OneLake Shortcuts at enterprise scale, hundreds or thousands of shortcuts may connect Lakehouses, Eventhouses, external storage, mirrored databases, and other Fabric data sources.

Today, a shortcut can become unavailable, stale, misconfigured, or disconnected from its source without providing administrators with a simple tenant-wide view of its health.

Fabric should provide a Shortcut Health dashboard showing the operational status of every shortcut.

The capability should include:

- Current shortcut health status

- Source connectivity status

- Last successful source access

- Last successful metadata synchronization

- Data freshness or synchronization lag

- Schema synchronization status

- Authentication or authorization failures

- Broken or missing target paths

- Source deletion, rename, or movement detection

- Query failures associated with the shortcut

- Shortcut cache status

- Historical health and availability metrics

- Configurable freshness thresholds

- Alerts when a shortcut becomes unavailable or exceeds its freshness SLA

- Notifications through Fabric, email, Teams, or Activator

- REST API access to health information for automation and monitoring

- Tenant, domain, workspace, Lakehouse, and individual-shortcut views

For example, if an Eventhouse table is receiving current telemetry but a downstream OneLake shortcut has not exposed new data for 45 minutes, Fabric should identify the synchronization lag and proactively alert the responsible data owner.

Similarly, if an external storage credential expires or a source table is renamed, Fabric should clearly identify the affected shortcut, root cause, and downstream consumers.

Administrators should also be able to define health expectations such as:

This shortcut should not be more than 10 minutes behind its source.

Fabric could then monitor the shortcut continuously and alert when that expectation is violated.

This would make OneLake Shortcuts significantly easier to operate at enterprise scale and reduce the risk of downstream reports, notebooks, semantic models, and AI agents silently consuming stale or unavailable data.

Add Schema Compatibility Policies and Breaking-Change Detection to Fabric Event Schema Registry

mourakshit — Sat, 19 Sep 2026 21:42:29 GMT

Fabric Event Schema Registry should support configurable schema compatibility policies so teams can safely evolve event contracts without breaking downstream Eventstreams, Eventhouse ingestion, applications, or other consumers.

Today, schemas can be versioned, but compatibility enforcement is not yet available. This means producers can introduce changes that may unexpectedly break existing event-processing flows.

Fabric should allow teams to define compatibility rules at the schema-set or individual-schema level.

Requested capabilities should include:

Backward compatibility

Forward compatibility

Full compatibility

No-compatibility mode for intentionally breaking changes

Automatic validation before a new schema version is published

Clear identification of incompatible field additions, removals, type changes, and structural changes

Breaking-change warnings

Dependency and impact analysis showing which Eventstreams, Eventhouse tables, destinations, and applications use the affected schema

Side-by-side schema diff between versions

CI/CD validation API so compatibility checks can run before deployment

Approval workflow for intentionally breaking changes

Ability to mark older schema versions as deprecated with an effective retirement date

For example, if a producer changes a field from integer to string, removes a required property, or changes a nested structure, Fabric should immediately show whether the new version is compatible with existing consumers before the schema is activated.

The experience should also show exactly which downstream artifacts may be affected by the change.

This would turn Event Schema Registry into a true enterprise contract-management capability rather than simply a centralized place to store schema versions.

It would significantly reduce production failures caused by unexpected schema evolution and make Fabric Eventstream safer for large-scale real-time and event-driven architectures.

Add Dry-Run Simulation and Historical Event Replay for Fabric Activator Rules

mourakshit — Sat, 19 Sep 2026 21:40:35 GMT

Fabric Activator should provide a dry-run simulation mode that allows developers to test rules against historical or sample event data without executing real downstream actions.

Activator rules can trigger operational actions such as notifications, pipelines, workflows, and other automated processes. Before deploying or modifying these rules in production, teams need a safe way to understand exactly how the rule would have behaved against real data.

Activator should allow users to select a historical time range, Eventstream data, or sample event set and replay those events through a rule in simulation mode.

During simulation, Fabric should evaluate the complete rule logic but suppress external actions.

The simulation experience should show:

Which events would have matched the rule

Which events would not have matched

Why each condition evaluated to true or false

The exact time each activation would have occurred

Which downstream action would have been invoked

The parameters that would have been passed to the action

Duplicate or repeated activations

Suppression, cooldown, and timing behavior

Errors or missing fields encountered during evaluation

Total simulated activations for the selected period

Users should also be able to compare the behavior of the current rule with a modified version before publishing the change.

For example, an operations team may change an equipment-temperature rule from 90 degrees to 85 degrees. Before deploying the change, they should be able to replay the previous seven days of telemetry and see how many additional alerts and actions the new rule would have generated.

This would make it possible to regression-test Activator rules before production deployment and reduce the risk of alert storms, incorrect pipeline execution, excessive notifications, and unintended automation.

A reusable simulation API would also allow teams to include Activator rule validation in automated CI/CD testing.

Preserve Power BI Semantic Model Measures and Business Metadata When Generating Fabric IQ Ontologies

mourakshit — Sat, 19 Sep 2026 21:34:16 GMT

When Fabric IQ generates an ontology from an existing Power BI semantic model, it should preserve more of the business semantics that organizations have already invested in defining.

Today, a semantic model may contain years of curated business logic and metadata. Generating an ontology should reuse that semantic investment instead of requiring teams to recreate important context manually.

Fabric IQ should preserve or map, where applicable:

Measures and measure descriptions

Business-friendly display names

Column and table descriptions

Hierarchies

Formatting and units

Date and time semantics

Hidden versus visible fields

Source lineage

Business metadata associated with model objects

Other semantic annotations that can improve ontology and agent understanding

Fabric should also provide a mapping report showing:

Which semantic-model objects were successfully mapped into the ontology

Which metadata could not be mapped

Any transformation or interpretation applied

Warnings where business semantics may be lost

For example, if a semantic model already defines measures such as Revenue, Gross Margin, Active Customers, or On-Time Delivery with descriptions, formatting, and business context, that information should help enrich the generated ontology rather than being discarded.

This request is intentionally separate from reusing semantic-model relationships, which is already covered by another Fabric Idea. The focus here is preserving measures and rich business metadata when generating Fabric IQ ontologies.

This would reduce duplicate modeling effort, improve consistency between Power BI and Fabric IQ, and give Data Agents richer governed business context from the beginning.

Enforce OneLake Row and Column Security End-to-End in Fabric IQ Ontology

mourakshit — Sat, 19 Sep 2026 21:32:23 GMT

Fabric IQ Ontology should natively preserve and enforce OneLake Security when users access ontology entities, relationships, graphs, and downstream AI experiences.

Enterprises may define row-level and column-level security directly in OneLake so that security policies are consistently enforced across Fabric workloads. Fabric IQ should participate in that same centralized security model rather than requiring separate security configuration or exposing broader access through ontology bindings.

When an ontology entity is backed by a secured Lakehouse or other supported OneLake source, queries through the ontology should execute using the requesting user's identity and enforce the applicable OneLake permissions.

The capability should include:

Row-level security enforcement

Column-level security enforcement

User identity passthrough

Security inheritance from the underlying OneLake source

Support for ontology relationships without bypassing source security

Security-aware Graph and Data Agent queries

Clear diagnostics showing why a user cannot access an entity, property, or relationship

Administrative visibility into which identity and security policy were applied

Consistent enforcement when ontology entities are used by downstream AI agents and applications

For example, if a Sales ontology contains Customer, Account, Opportunity, and Territory entities, a regional sales user should only receive the rows and properties permitted by the underlying OneLake security policies, even when asking questions through a Data Agent or traversing relationships through Fabric IQ.

Organizations should be able to define security once in OneLake and rely on Fabric IQ to honor those policies consistently.

This is particularly important for financial, healthcare, HR, government, and other regulated enterprise scenarios where semantic and AI layers must never become a path around the underlying data-security model.

Support Schema Evolution for Fabric Graph Without Rebuilding the Graph Model

mourakshit — Sat, 19 Sep 2026 21:30:27 GMT

Fabric Graph should support controlled schema evolution as enterprise business models change over time.

Graph models are rarely static. Organizations need to add new node types, properties, relationships, keys, and source mappings as new business requirements emerge. These changes should be manageable without forcing teams to recreate the graph model and reconnect downstream dependencies.

Fabric Graph should support compatible schema changes directly on an existing graph model while preserving the graph identity, security configuration, queries, lineage, and downstream references.

Requested capabilities include:

Add or modify node properties

Add new node and relationship types

Add or update source mappings

Safely modify keys and relationship definitions

Schema version history

Compare and diff between graph schema versions

Breaking-change detection

Dependency and impact analysis before deployment

Migration preview

Rollback to a previous schema version

CI/CD support for promoting graph schema changes across development, test, and production environments

For potentially breaking changes, Fabric should identify the affected queries, Digital Twin models, Fabric IQ ontologies, dashboards, Data Agents, and other downstream consumers before the change is applied.

For example, an organization may initially model Asset, Site, and Work Order entities and later introduce Manufacturer, Sensor, Maintenance Contract, and additional relationships. These changes should be evolutionary rather than requiring a graph redesign or recreation.

Enterprise graph models will continuously evolve. Fabric should provide a governed schema-evolution experience that allows organizations to extend those models safely while protecting existing applications and dependencies.

Make Fabric IQ Ontology Entities First-Class Assets in OneLake Catalog

mourakshit — Sat, 19 Sep 2026 21:28:03 GMT

Fabric IQ ontology entities and business concepts should be discoverable as first-class governed assets in OneLake Catalog.

Today, users often need to know the underlying Fabric item, table, semantic model, or workspace before they can find the data they need. With Fabric IQ, organizations are defining business concepts such as Customer, Asset, Work Order, Supplier, Contract, Shipment, Device, and Product. These semantic entities should be directly searchable and discoverable in OneLake Catalog.

For each Fabric IQ entity, OneLake Catalog should display:

Business name and definition

Entity type

Properties and key attributes

Related entities and relationships

Underlying Lakehouse, Warehouse, Eventhouse, semantic model, or other bound data sources

Data owner and steward

Endorsement or certification status

Sensitivity and governance metadata

Lineage

Associated Data Agents, reports, dashboards, Graph models, or applications using the entity

Users should be able to search the catalog using business terminology such as "Customer", "Asset", or "Work Order" and discover the governed Fabric IQ entity even if they do not know the physical table or Fabric item name.

This would connect technical data discovery with semantic discovery and make OneLake Catalog much more useful for business users, data stewards, architects, analytics developers, and AI agent developers.

This request is different from general full-text search in OneLake Catalog. The goal is to make Fabric IQ entities and relationships themselves governed, searchable catalog assets, not simply to improve text search across existing Fabric items.

Add Incremental and Event-Driven Refresh for Fabric IQ Ontology

mourakshit — Sat, 19 Sep 2026 21:26:14 GMT

Fabric IQ Ontology should support incremental and event-driven updates when the underlying source data changes.

For operational and real-time scenarios, ontology entities and relationships may be backed by Lakehouse, Eventhouse, semantic models, or other Fabric data sources that change frequently. Fabric should not require users to manually refresh or rebuild large portions of the ontology simply to make changed source data available.

Fabric IQ should automatically identify which entities, properties, and relationships are affected by source-data changes and update only the impacted portions of the ontology.

The capability should include change-aware incremental refresh, Eventstream-triggered refresh, pipeline-triggered refresh, configurable freshness targets, entity-level refresh status, last-successful-update timestamps, failed-record diagnostics, dependency-aware refresh ordering, and monitoring of refresh processing and capacity consumption.

For example, if the status of an Asset, Work Order, Shipment, Customer, Device, or other operational entity changes, Fabric IQ should be able to update the relevant ontology state quickly without requiring a full ontology refresh.

This would make Fabric IQ significantly more practical for operational intelligence, Digital Twin scenarios, Real-Time Intelligence, and AI agents that depend on current business context.

Add Versioning, Git Integration and CI/CD for Fabric IQ Ontologies

mourakshit — Sat, 19 Sep 2026 21:24:38 GMT

Fabric IQ Ontology can become a shared enterprise definition of business entities, relationships, properties, and context. As ontologies become dependencies for Data Agents, Graph, applications, and other AI experiences, they need the same production lifecycle controls as other Fabric artifacts.

Fabric IQ Ontology should support version history, Git integration, export/import, compare and diff, pull-request review, deployment pipelines, environment-specific data bindings, rollback, and a complete audit history.

Fabric should also provide dependency and breaking-change analysis before an ontology change is deployed. For example, if the definition, key, or relationship for a Customer entity changes, Fabric should identify affected relationships, Graph models, Data Agents, applications, and other downstream consumers.

This would make Ontology practical for enterprise development teams that need controlled development, testing, approval, deployment, and rollback across development, test, and production environments.

Zoom Based Visibility for Location Labels in the Azure Maps Visual

AllianceDA — Sat, 19 Sep 2026 18:28:22 GMT

Location labels can be helpful for maps but also create a lot of clutter when zoomed out. It would be great if zoom based visibility controls could be enabled for this feature.

Question about exam voucher deadline (DP-800)

kishori_sowmya — Sat, 19 Sep 2026 14:51:48 GMT

I have a voucher for the DP-600/DP-700/DP-800 exam group, with a redemption deadline of August 25, 2026 and a requirement to take the exam by September 30, 2026. I wanted to check: if I'm unable to sit the exam by September 30, does the voucher expire completely, or is there any flexibility to reschedule to next month (october) within the voucher's terms?Could you please clarify what my options would be in that case?

iOS Shortcuts Support for Direct Access to Power BI Reports

Default8129 — Sat, 19 Sep 2026 12:11:20 GMT

We are looking to deploy several Power BI reports to support emergency response activities. The intended users are primarily non-technical staff who do not use Power BI currently, but who would benefit from quick access to critical information from their phones during an emergency.

We would like Power BI to support Apple Shortcuts, allowing users to create a Home Screen shortcut that opens a specific Power BI report or app directly in the Power BI mobile app.

For emergency-response scenarios, minimizing the number of steps required to reach information is especially important. Rather than asking users to open Power BI, navigate through workspaces or apps, and locate the appropriate report, we could configure their devices with a clearly labeled Home Screen icon that takes them directly to the resource they need.

This would reduce training requirements and make Power BI more accessible for occasional and non-technical users, particularly in situations where fast, simple access to information matters.

filter earlier posts based on keyword

powerbiexpert22 — Sat, 19 Sep 2026 11:02:08 GMT

i have more than 1000 posts created by me on this forum, i want to filter those posts based on certain topic or key word so that it should give me ony those posts where that keyword is used , let say for example if i search on "direct query" then it should give my posts where direct query word was used, how to do on this forum?

Fire! Leicestershire Fire and Rescue Service incident report

Coriel-11 — Sat, 19 Sep 2026 10:35:07 GMT

The aim with this Fire Service report was to create a fully interactive, all-on-one screen, dashboard that showcased the incidents dealt with by Leicestershire Fire and Rescue Service. I was able to do this because they make this data publicly available on their website.

Fire service data is good to play with because it's something that affects us all. All the visuals and filters all interact with each other, so you can break down the data and look at it by:

Local authority area within Leicestershire
Ward area (a subdivision of each LA)
Time range
Day of the week
Hour of the day
What caused the incident
The perceived motive

In this data visualization I tried to keep the colours in line with LRFS's branding, though I added darker colours on the heat map showing the times with most incidents. I also used colour to distinguish between the different LAs, keeping that consistent across the map, LA selector bar chart and the top ten wards graphics.

Technical details

The data is published as a downloadable Excel file from LFRS's website. I coded the location of this as a parameter in Power Query for easy switching when new data becomes available.

I used #PowerQuery to break the data down into a classic star schema, as well as bringing in some LA location data in PQ to make the maps work. The #Mcode was fairly basic for this one.

I used my own #DAX built calendar/date fact table combining the tables in Model View.

The reporting cards are my own custom-built #SVG images, powered by DAX.

This is the largest canvas size I have yet used, but the intention is that it means all the text/numbers are readable on a monitor screen, even if some zooming is required. But that is its intended user context, rather than in a presentation.

Please let me know what you think.

Power BI Financial DAX Functions Explained | ODDFPRICE, ODDFYIELD, ODDLPRICE & ODDLYIELD

suparnababu8 — Sat, 19 Sep 2026 04:06:48 GMT

In this video, you'll learn four advanced Financial DAX Functions with practical, real-time business examples.

✅ ODDFPRICE

✅ ODDFYIELD

✅ ODDLPRICE

✅ ODDLYIELD

If you find this video helpful, please Like, Share, and Subscribe to the NDAC Channel for more learning content.

Power BI - Slicer Control

RajiKarthik — Fri, 18 Sep 2026 23:12:49 GMT

I need a slicer selection to appear and disappear based on a parameter slicer selection:

I have 3 metrics in my parameter: Student Enrollment, Course Enrollment and Credit Hours

Whenever student enrollment is selected, the user should be provided with an additional slicer option, "Area of Study Category", and for other metrics, it should stay invisible.

I created control DAXs "Show Area of Study Slicer" and "Area of Study Slicer Header". Added the "Show Area of Study Slicer" to the visual level filter and set it to 1. Similarly added the "Area of Study Slicer Header" to the header control, so the header disappears too.

Issue - Header disappears, but if I make any selection in the "Area of Study Category" slicer and then change the metric to "Course Enrollment", then the slicer remains with only the selected value. Other values disappear, though. But I want the whole slicer to disappear when the metric parameter changes. Experts, please help! Thanks in advance!!

Parameter Definition:

Metric Selector =

DATATABLE(

"Metric Key", INTEGER,

"Metric Name", STRING,

"Sort Order", INTEGER,

"Department Map", STRING,

{

{ 1, "Student Enrollment", 1, "Student" },

{ 2, "Course Enrollment", 2, "Course" },

{ 3, "Credit Hours", 3, "Course" }

}

)

Control DAXs to use in the filter & Header:

Show Area of Study Slicer =

VAR MetricKey = SELECTEDVALUE('Metric Selector'[Metric Key], 1)

RETURN

IF(MetricKey = 1, 1, 0)

Area of Study Slicer Header =

VAR MetricKey = SELECTEDVALUE('Metric Selector'[Metric Key], 1)

RETURN

IF(MetricKey = 1, "Area of Study Category", "")

Monitor Power BI Report Performance

Lorenz33 — Fri, 18 Sep 2026 21:42:03 GMT

I am a Fabric administrator and with my permissions I can utilize the MS Fabric Capacity Metrics app. However, regular users do not have access to this data. I have a report developer who is requesting data on performance metrics for his report. Data such as how long did it take a report to load. How many CUs did an object use. Is there any way I can make this information available? I have a report I created that access the Power BI Activity log and shows audit data but it does not have the performance information he is requesting. He would like this for performance tuning and optimization. I checked out the reports in the Admin Monitoring workspace but they do not appear to have performance data.

semantic models no updated in admin monitoring workspace

bbtresoo — Fri, 18 Sep 2026 20:59:26 GMT

hello,

is there any reason admin monitoring reports such as Feature Usage and Adoption is not refreshed ???

Content sharing report hasn't been refreshed for 6 months.

what's the purpose of making available no updated monitoring artefacts?

Regards