❌

Normal view

How Microsoft connects your data across the enterprise

14 September 2026 at 19:55

For CIOs and CDOs heading into Microsoft Fabric and SQL Community Conference Europe, the main question is not which data technology sits at the center. It is whether the data platform improves revenue, productivity, and decision speed while creating a trusted foundation for AI at scale. That should drive the data strategy.

Enterprise AI is forcing companies to tackle a familiar problem, with data spread across ERP, CRM, operational systems, databases, applications, warehouses, and analytics platforms built over years. That was manageable for reporting and point-to-point integration. Copilots and agents raise the stakes because they need to reason across customers, orders, inventory, financial implications, operating constraints, permissions, and business rules at the same time.

That moves the discussion from architecture into CIO and CDO strategy. What outcomes are we trying to improve? What data and context are required? What needs to move versus connect? Where do Microsoft Fabric, Azure Databases, and other platforms fit? How will governance and authority follow the data? Where should the data be stored and what sovereignty or regulatory restrictions apply? And how will we measure results?

Microsoft is positioning its broader data platform around AI business value. That framing is useful when it translates into an operating strategy. As I wrote in Forbes about Microsoft Build in June, the next phase of AI depends less on the model and more on data readiness, governance, interoperability, and operational execution. The conference should give customers a closer view of how those pieces come together. The question for CIOs and CDOs is how that direction fits their existing data estate.

The AI problem is usually a data problem

Many AI initiatives stall on data readiness rather than the model itself. The issue is not one statistic. It is the combination of fragmented data, inconsistent definitions, and the effort needed to prepare and govern information before AI can use it reliably.

Copilots and agents need trusted context around customers, financials, inventory, operations, permissions, and business rules. AI exposes existing weaknesses. Duplicate customers, poor product data, and inaccurate inventory become more consequential when AI is recommending or taking action. AI does not create the data quality problem; it makes the operating cost harder to ignore.

The goal is to make more of the existing data estate useful for AI without turning modernization into a wholesale rebuild.

Microsoft Fabric and Azure Databases play different roles

For customers, the question is how Microsoft’s broad portfolio translates into architectural choices, including what should move, what should connect, and what can stay in place without limiting the result the business is trying to achieve.

Azure Databases support transactional and operational workloads, each with distinct performance and application requirements. Fabric provides a unified SaaS experience across data integration, engineering, analytics, real-time intelligence, data science, and business intelligence. Fabric IQ adds a semantic intelligence layer that provides shared business context for Copilot and agents. Some workloads may belong in Fabric, others in Azure Databases, and some on third-party platforms; moving them adds cost without creating enough business value.

The architecture should follow workload, data maturity, economics, and business value, not a single destination.

Connected data has to improve the decision

Microsoft’s broader data platform can connect systems of record and operational applications with analytics and AI. Azure Databases, Fabric, OneLake, Power BI, and governance can play different roles. What matters is whether those connections shorten the path from operational data to a decision, not how neatly the products line up.

A customer record may live in CRM, orders in ERP, inventory in operational databases, and demand models in an analytical environment. Fabric Real-Time Intelligence can add live events to that picture. A manufacturer can stream equipment events or production events, detect a developing issue, and alert teams while there is still time to change the outcome. The value comes from reasoning across that context so the business can understand what is happening, why it matters, and what action makes sense next.

Trusted context turns data into AI business value

I recently wrote in InfoWorld that trusted context is becoming the currency for enterprise AI. That is especially relevant here because once copilots and agents rely on enterprise data, then quality, permissions, lineage, and security become operating requirements, not background data issues.

Knowing inventory is 8,000 units is data. Knowing whether those units are available, committed elsewhere, in the wrong distribution center, or on quality hold is business context. As AI moves from answering questions to taking action, that context determines whether the result can be trusted.

Microsoft frames AI business value around growth, insight, and scale. Each needs an operating definition. Growth can mean new revenue, better customer responsiveness, or growing without adding cost at the same rate. Insight means combining context across Microsoft 365, Fabric, and operational systems to make better decisions faster. Scale means expanding AI without rebuilding governance for every use case.

A reusable data foundation can also reduce pipeline and management effort while improving decisions around pricing, inventory, customers, supply chain, and finance. Microsoft cites coverage of more than 100 standards. The practical question is whether AI can scale without risk and complexity growing at the same pace. For multinational or regulated organizations, that also includes where data is stored and processed and which sovereignty requirements apply.

Agentic workloads raise the bar. Organizations need to know what information informed a decision, who or what had authority to act, which policies applied, and how a wrong action can be reviewed or reversed.

That is where the data platform becomes part of what I describe as decision architecture. Context explains what is happening. Decision logic determines what should happen next. Authority defines what a person or agent can do. Orchestration coordinates systems and people. Execution completes the action and provides a path to review or reverse it. Trusted data feeds that architecture. Without trusted data, automation will be difficult to trust at scale.

Microsoft’s breadth is most useful when it reduces complexity

Microsoft’s advantage may be its enterprise footprint. Azure Databases, Fabric, OneLake, Power BI, Microsoft 365, business applications, developer tools, identity, security, and partners touch many of the places where information is created and work gets done.

Most customers will keep data across multiple systems. Microsoft’s opportunity is to use that breadth to create a simpler path from data to workflow to business outcome without requiring everything to live in one place.

Customer proof points matter because data strategies can get abstract. The KPMG Australia example is useful because KymChat moved beyond an internal productivity tool into a client-facing offering, creating a path from internal AI investment to new business. Microsoft also reports that improvements to the data foundation increased KymChat search quality from 50% to 91%, with results delivered in under a second.

BMW Group provides a more recognizable operating example. Microsoft says Azure helped BMW make vehicle data delivery and analysis 10 times faster, cutting the lead time for engineering insights from days to hours or minutes. Audi adds an AI deployment example. It used Azure AI Foundry, Azure App Service, and Azure Cosmos DB to launch a secure HR assistant in two weeks and is extending the same framework to eight additional agents across the enterprise. Levi Strauss & Co. offers another angle. It consolidated nine ERP systems on Azure, reported a twofold improvement in latency and a 60% improvement in IOPS and now uses Fabric IQ for companywide cost reporting. These are the kinds of proof points that connect platform architecture to time, cost, productivity, and decision quality.

Interoperability matters across the enterprise estate

Microsoft sits in a market with Snowflake, AWS, Google Cloud, Oracle, and others, each with different strengths across infrastructure, databases, analytics, openness, and AI. Databricks also plays an important role, but the connection is different because Azure Databricks is provided as a first-party service directly on Azure. Most large enterprises will remain heterogeneous, making interoperability, cross-platform governance, and incremental modernization central to strategy.

The opportunity is to make Microsoft’s data platform useful across the mix of systems that customers already run. Most enterprises are not starting from a blank sheet, so the value is in helping them connect, govern, and modernize over time without forcing everything into one place.

CIO and CDO strategy should start with the business outcome

This is where the conversation becomes most useful at the Microsoft Fabric and SQL Community Conference Europe. For CIOs and CDOs, an architecture diagram matters more when it is backed by a decision model. A useful data and AI strategy should work backward from the business outcome through five decisions.

  1. Start with the business outcome. Define what needs to improve, including revenue, margin, productivity, customer experience, decision speed, working capital, or time to value. Let the technology choice follow the objective.
  2. Map the data and context required. Identify the operational, transactional, and analytical information, semantics, and business rules that influence the outcome.
  3. Decide what moves and what connects. Determine where Fabric, Azure Databases, and non-Microsoft platforms fit. Let workload, economics, and value drive modernization rather than a single destination.
  4. Design governance, authority, and economics together. Define how security, permissions, lineage, and controls span operational, analytical, and AI workloads, and identify opportunities to simplify pipeline, integration, and management efforts.
  5. Measure the operating result. Set KPIs before scaling. Technology adoption is not the outcome. CIOs and CDOs should know which business measures should change, by how much, and over what period.

That is how the data platform becomes enterprise strategy, tying architecture, governance, AI, and economics to operating outcomes and bringing business leaders into the discussion before the architecture is set.

What customers will still want to understand

Microsoft has many of the pieces required to connect enterprise data, analytics, and AI. Customers will keep looking for guidance on the roles of Azure Databases, Fabric, and the broader data platform, along with cost, licensing, migration, and governance across heterogeneous environments. They will also want more proof points from KPMG, BMW Group, Audi, and Levi Strauss & Co. that start with a business result.

That is where Microsoft’s positioning around a data platform for AI business value comes together. The value is in helping customers connect platform choices to better decisions, faster action, and measurable operating results.

After three decades in enterprise technology, I keep coming back to the same point. The technology is only part of the answer. For CIOs and CDOs, the harder part is deciding how the data platform fits into the way the business operates, how decisions get made, and where AI can improve the outcome. That is really the question behind how Microsoft connects your data across the enterprise. The conference should give customers a useful view of how Microsoft is bringing those pieces together and where that can create better business outcomes.

Rapid Wildfire Structure Risk Assessment Helps Fire-Adapted Communities

9 September 2026 at 17:27

Wildfire scientists have unveiled a new rapid risk-assessment tool that shows substantial wildfire danger to homes and buildings in three major Arctic communities, revealing that between 14% and 26% of structures in Anchorage, Fairbanks, and Whitehorse face high or very high risk from approaching flames. The study, led by Jennifer I. Schmidt of the University of Alaska Anchorage together with Robert H. Ziel, Monika P. Calef, Anna Varvak, and Julio C. Postigo, was published in the International Journal of Disaster Risk Science. Rather than relying on complex fire-behavior simulations that demand specialist analysts and expensive software, the approach combines datasets that most local governments already possess: building footprints, zoning maps, and readily available vegetation layers. The result is an updatable, affordable portrait of which buildings face the greatest threat and where mitigation dollars can do the most good.

The urgency behind the work is hard to overstate. Wildfire costs and damages in the United States alone are now estimated at between USD 394 billion and 893 billion annually, and the 2019 to 2020 Australian fire disasters cost nearly USD 100 billion. The Arctic, often imagined as too cold and wet to burn, is not immune: since 1980, wildfires have cost Alaska between USD 2 billion and 5 billion, with projections suggesting costs could rise 68% by the end of the century. Canadian suppression expenses are expected to climb by 60 to 110% relative to the 1980 to 2009 baseline. Meanwhile, structure loss from wildfire has doubled over the past two decades in the western United States, and western Canada has suffered major structure-loss events in four of the last eight fire seasons. Nearly half the global population now lives within the wildland-urban interface, the zone where people and forests meet or intermingle, making tools that translate fire science into actionable local maps increasingly vital.

The researchers’ central premise is conceptually simple but technically consequential: for a structure to be at high risk, a flammable hazard must exist nearby, within roughly 500 meters, and the surrounding landscape must exhibit high wildfire exposure. The method begins with a flammability hazard layer at 30-meter resolution, built from a modified version of NASA’s ABoVE Landcover dataset in which generic evergreen classes were refined to reflect locally flammable species such as black spruce, white spruce, lodgepole pine, and subalpine fir, each assigned hazard ratings from 0 to 100. Critically, the team treated structures themselves as fuel. Each building contributes three fuel units to the surrounding flammability score, a value chosen after systematic testing of one through ten fuel units; three proved optimal, nudging densely built environments up a hazard category without causing wholesale reclassification. Structure density was computed at 90-meter resolution, multiplied by three, and added to the vegetation-based hazard to produce an enhanced flammability hazard layer.

Wildfire exposure, the second pillar of the assessment, captures the potential for hazard to travel. It is calculated as the average flammability hazard within a 100-meter or 500-meter radius, representing the likelihood that fire can reach and burn a given location even if the local fuels themselves are sparse. Exposure values, also ranging from 0 to 100, are classified into five tiers from very low to extreme, and concentrated pockets of flammable vegetation drive scores upward. The third ingredient is structure vulnerability, produced by multiplying the enhanced flammability hazard by a structure importance factor derived from zoning data: residential buildings and critical infrastructure such as hospitals, schools, and nursing homes receive the highest weight, followed by commercial and other structures. Where zoning was unavailable, as on military installations like Joint Base Elmendorf-Richardson in Anchorage and Fort Wainwright and Eielson Air Force Base in Fairbanks, the team collaborated with base personnel or interpreted aerial imagery to classify neighborhoods. The final risk score synthesizes hazard, exposure, and vulnerability into six categories, from extremely low to very high.

The results paint a nuanced picture of Arctic fire danger. Fairbanks showed the greatest proportion of structures in the top two risk categories at 26%, followed by Whitehorse at 22% and Anchorage at 14%. Anchorage, paradoxically, had the highest share of buildings in the top vulnerability tiers, 42%, yet the lowest risk, a consequence of its large urban footprint where dense housing raises vulnerability but fragmented, less-flammable vegetation and abundant developed ground suppress exposure. Fairbanks and Whitehorse, with structures woven into spruce- and pine-dominated boreal landscapes, showed closer alignment between vulnerability and risk. Anchorage was also the only study area where more than 1% of cells jumped two or more flammability categories when buildings were counted as fuel, at 7%, reflecting its 27% share of structure area containing seven or more buildings per cell. The analysis also confirmed the primacy of exposure: when a structure’s wildfire exposure was extreme, at least 87% of such buildings landed in the highest risk category across all three communities.

A key innovation lies in how the team redrew the wildland-urban interface itself. Traditional WUI maps distinguish urban, interface, and intermix zones; the researchers added a fourth category, the transmission zone, marking areas roughly 2.4 kilometers beyond the WUI boundary where fire could move into a community and where fuel breaks might be sited. Within the 500-meter buffer around structures, urban areas were defined by exposure values of 20 or less, interface zones by 21 to 60, and intermix by values above 60, cross-referenced with Alaska and Yukon wildfire management designations that prioritize suppression from critical down to unplanned or wilderness levels. Fairbanks claimed the largest overall WUI footprint, and the transmission zone proved the largest category in every study area, spanning 23,347 square kilometers around Anchorage, 6,180 square kilometers around Fairbanks, and 665 square kilometers around Whitehorse. Across all sites, most structures fell within interface zones, 52 to 61%, followed by intermix at 20 to 35%. Thousands of buildings sit in the high-risk interface and intermix zones where mitigation should concentrate: 15,537 structures in Anchorage, 16,212 in Fairbanks, and 3,734 in Whitehorse.

The method faced its most demanding test against a real disaster. On 17 August 2019, during southcentral Alaska’s hottest and driest summer on record, the likely human-caused McKinley wildfire was driven by high winds across 13.3 square kilometers in three days, destroying 52 residential structures, 84 outbuildings, and three commercial buildings, affecting 1,028 properties and forcing roughly 350 to 400 people to evacuate. By comparing pre-fire aerial imagery from 2017 with post-fire imagery from 2020 at 0.3-meter resolution and linking vanished buildings to the Matanuska-Susitna Borough structure database, the team identified exactly which structures burned. The verdict was statistically compelling: burned structures had significantly higher wildfire exposure than those that survived, and the proportion of burned structures with exposure values above 60 was significantly larger than among unburned ones. Structure risk scores above 60 were also significantly associated with burning. Notably, the test held even under conditions so extreme that normally resistant, low-flammability fuels were igniting.

The study’s design was shaped by sustained community engagement. Through workshops in 2019, 2021, and 2023, along with 15 to 20 meetings organized by Anchorage community councils and landowner associations and public events ranging from wildfire awareness days to Arbor Day, residents and agency staff reshaped everything from color schemes to model parameters. One consequential example: Anchorage residents and fire managers insisted that the maps reflect the spruce beetle outbreak first detected in 2016 and peaking around 2020, which killed and removed many spruce trees. The team responded with rules derived from aerial detection surveys, reclassifying white spruce cells in areas of beetle intensity of 11% or greater to mixed forest, and shifting mixed forest cells to open shrub, while a succession model updated vegetation on areas burned within the last 30 years. This iterative dialogue ensured outputs that both wildfire practitioners and the general public can interpret, a prerequisite the authors see as central to building fire-adapted communities.

The practical implications for planning are direct. Because mitigation funding is often tied to officially designated WUI areas, the ability to rapidly recalculate boundaries from updated building layers expands funding opportunities and keeps pace with community growth. The framework also points to different interventions in different zones: structures in intermix areas, surrounded by vegetation, benefit most from fuel treatments, while those in interface zones, where flammable vegetation is scarcer, are better served by home hardening measures such as fire-resistant roofs, siding, decks, screens, and unburnable buffers. Given that wildfire activity tends to occur where exposure exceeds 60, the authors recommend concentrating resources on the top two risk categories. Where national products like wildfirerisk.org rely on generalized fuel layers that can overestimate unburnable area in WUI zones and are updated too slowly for annually burning landscapes, this approach trades complexity for transparency, using local data that governments already collect. The underlying wildfire exposure toolbox is publicly available on GitHub, and the team argues that empowered residents, equipped with accurate, current, neighborhood-scale information, are crucial to reducing wildfire risk, particularly where communities may prefer action without government intervention.

Subject of Research: Rapid assessment of wildfire risk to structures and wildland-urban interface delineation in Arctic communities using local vegetation, building footprint, and zoning data.

Article Title: Fueling Fire-Adapted Communities Through a Rapid Wildfire Structure Risk Assessment

Article References: Schmidt, J. I., Ziel, R. H., Calef, M. P., Varvak, A., & Postigo, J. C. (2026). Fueling Fire-Adapted Communities Through a Rapid Wildfire Structure Risk Assessment. International Journal of Disaster Risk Science, 17(2), 351-362. https://doi.org/10.1007/s13753-026-00716-y

Image Credits: AI Generated

DOI: 10.1007/s13753-026-00716-y

Keywords: Arctic, Wildfire, Risk assessment, Wildland-urban interface, WUI, Mitigation planning, Structures, Fire-adapted communities, Wildfire exposure, Flammability hazard, Alaska, Yukon

SnapLogic introduces agentic assistant for data integration

5 August 2026 at 00:47

SnapLogic has introduced its new SnapGPT, an agentic assistant that helps enterprise teams plan, build, understand, and operate integrations through natural language.

Unveiled July 28 and described as the company’s most-significant advancement in SnapGPT since 2023, the new SnapGPT evolves from an AI-powered integration copilot into an agentic assistant for the integration life cycle, combining platform intelligence, integration-specific reasoning, and operational guidance to help teams move from business intent to production faster, according to SnapLogic. SnapGPT combines agentic planning, integration-specific reasoning, pipeline execution validation, and more than 15 years of enterprise integration expertise built into the SnapLogic Agentic Integration Platform, including platform intelligence, operational context, and proven integration patterns, the company said.

SnapGPT now helps teams across the entire integration life cycle:

  • Plan – Plan Mode helps teams validate requirements, explore implementation approaches, refine workflows, and identify potential issues before development begins.
  • Build – Generate high-quality, production-ready integrations through integration-specific reasoning and pipeline execution validation, while accelerating development with multi-pipeline generation, intelligent pipeline refactoring, reusable expression libraries, and natural-language generation of SnapLogic MCP Servers.
  • Understand – Analyze existing integration assets, explain pipeline logic, and surface contextual insights to help teams better understand and improve complex integrations.
  • Operate – SnapGPT Activity Log provides administrators with visibility into AI-assisted development activity, while SnapGPT Monitor Insights extends AI assistance into production operations with diagnostic intelligence and AI-powered troubleshooting.

The new SnapGPT is available as part of the SnapLogic Agent Integration Platform. In June SnapLogic introduced the SnapLogic MCP Builder, a template-based tool that generates Model Context Protocol servers from existing integrations.

Bayesian framework integrates longitudinal EHR data with genetic discovery

16 July 2026 at 14:41

A new Bayesian system called ALADYNOULLI is designed to forecast how multiple diseases unfold over time from longitudinal electronic health record (EHR) histories. The work targets a central challenge in longitudinal modelling: evaluating prediction without “information leakage,” so that future diagnoses never influence training for past timepoints. By explicitly simulating real clinical follow-up, the researchers aim to make risk estimates more trustworthy for decision-making.

In the primary assessment, ALADYNOULLI produced dynamic 1-year forecasts at 10 fixed moments during follow-up, starting at enrollment and extending to years 1 through 9. At each timepoint, models were retrained using only data available up to that moment, then tested on 1-year outcomes. The key metric was the median area under the receiver operating characteristic curve (AUC) across these dynamic evaluations, summarizing how predictive accuracy changes as new diagnoses accumulate.

The study spans 28 diseases and reports robust discrimination for several clinically important endpoints. Performance was strong for atherosclerotic cardiovascular disease (ASCVD), breast cancer, atrial fibrillation, heart failure, and Parkinson’s disease, with AUC values of 0.879, 0.867, 0.801, 0.811, and 0.796, respectively. Importantly, the evaluation excluded people with prevalent disease at prediction time, aligning the comparisons with prospective risk.

ALADYNOULLI was also benchmarked against established clinical risk tools where feasible. At enrollment, static models trained only on baseline information were compared for both 1-year and 10-year horizons. While longer-term predictions naturally degraded, ALADYNOULLI retained meaningful power—for example, for ASCVD at 10 years—highlighting the advantage of learning from longitudinal EHR trajectories rather than relying solely on cross-sectional inputs.

Calibration analyses further supported reliability: predicted and observed event rates matched closely across millions of at-risk patient-time observations. The researchers report a mean squared error on calibration of 4.67 × 10⁻⁷, with mean predicted rates (5.55 × 10⁻⁴) closely tracking mean observed rates (5.45 × 10⁻⁴). This suggests not only ranking accuracy, but also quantitative risk realism.

To test whether results were driven by subtle temporal artifacts, the team ran sensitivity analyses that excluded events occurring shortly before prediction and varied washout windows. They also examined alternative horizons and a dynamic 10-year rolling interpolation strategy, which updates risk estimates as annual information becomes available. Together, these checks help confirm that temporal patterns are being learned in a causally aligned manner.

Overall, the findings position ALADYNOULLI as a clinically relevant framework for multi-disease risk forecasting, combining longitudinal EHR modelling with predictive discrimination and calibration. By rigorously preventing leakage and validating dynamic follow-up scenarios, the approach offers a pathway toward more actionable, time-aware risk prediction in real-world healthcare settings.

Subject of Research: Longitudinal EHR-based multi-disease risk prediction using Bayesian modelling and genetic/EHR integration
Article Title: A Bayesian framework for longitudinal EHR and genetic discovery.
Article References: Urbut, S.M., Ding, Y., Nakao, T. et al. A Bayesian framework for longitudinal EHR and genetic discovery. Nature (2026). https://doi.org/10.1038/s41586-026-10780-5
Image Credits: AI Generated
DOI: https://doi.org/10.1038/s41586-026-10780-5
Keywords: longitudinal EHR, Bayesian framework, disease risk prediction, dynamic forecasting, temporal validation, calibration, AUC, ASCVD

❌