Nice article, but let’s be candid: the “unified portal” currently feels more like a frontend consolidation than true backend integration.
This is especially visible in Advanced Hunting, which remains unreliable after the Sentinel + Defender XDR integration. The underlying Log Analytics backends are still separate, so the exact same query may run against Advanced Hunting Log Analytics or Sentinel Log Analytics depending on the selected time range. That creates inconsistent behavior and results.
There are also schema mismatches between the two environments. For example, the AdditionalFields column in the DeviceInfo table is a string in XDR, but dynamic in Sentinel. Issues like this create constant friction for daily investigations, threat hunting, and detection engineering.
From a customer perspective, this is directly affecting operational efficiency. Unfortunately, despite multiple support cases and escalations, product team is not interested in providing improvements in those matters.
It is also worth noting that Sentinel Data Lake is still unavailable in many Azure regions, including major ones such as West Europe.