Generated on: November 08, 2025 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 3 items
Published: November 07, 2025 19:00:43 UTC Link: Public Preview: openCypher support for KQL graph semantics
Update ID: 522866 Data source: Azure Updates API
Categories: In preview, Analytics, Azure Data Explorer
Summary:
What was updated
Azure Data Explorer and Fabric Eventhouse now support openCypher queries alongside Kusto Query Language (KQL) graph semantics in public preview.
Key changes or new features
This update introduces the ability to run openCypher, a popular open-source graph query language, directly on graph data within Azure Data Explorer and Fabric Eventhouse. Developers and data professionals can leverage openCypher’s expressive syntax to query and analyze graph structures without switching tools or languages. This enhances interoperability and simplifies graph analytics workflows by combining KQL’s performance with openCypher’s familiarity and flexibility.
Target audience affected
Developers, data engineers, and IT professionals working with graph data in Azure Data Explorer or Fabric Eventhouse who want to use openCypher for graph querying and analytics.
Important notes if any
The feature is currently in public preview, so users should evaluate it in non-production environments and provide feedback. Integration with existing KQL graph semantics allows seamless use of both query languages on the same datasets. Users should review documentation for syntax differences and best practices when mixing KQL and openCypher queries.
Details:
The recent Azure update introduces public preview support for openCypher within Kusto Query Language (KQL) graph semantics, enabling users to execute openCypher queries directly on graph data stored in Azure Data Explorer (ADX) and Fabric Eventhouse. This integration bridges the gap between the widely adopted open-source graph query language, openCypher, and Microsoft’s native graph querying capabilities, enhancing flexibility and interoperability for graph analytics workloads.
Background and Purpose
Azure Data Explorer has long supported graph data modeling and querying through KQL’s native graph semantics, which provide powerful pattern matching and traversal capabilities. However, KQL’s graph syntax differs from other popular graph query languages, limiting ease of adoption for users familiar with openCypher—a declarative graph query language originally developed by Neo4j and now an open standard widely used in the graph database ecosystem. The purpose of this update is to lower the learning curve and increase accessibility by allowing users to leverage openCypher syntax natively within Azure’s graph analytics environment, thereby facilitating migration, integration, and cross-platform graph analytics.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation
The implementation involves a query parser and translator layer that interprets openCypher syntax and maps it to equivalent KQL graph operators and functions. This translation is optimized to leverage ADX’s columnar storage and indexing for efficient graph pattern matching. The integration ensures that query execution plans generated by ADX’s engine maintain high performance and scalability. Additionally, the system supports schema inference to map openCypher node and relationship types to ADX tables and columns, enabling flexible schema-on-read scenarios.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
Published: November 07, 2025 19:00:43 UTC Link: Generally Available: labels() function in KQL graph semantics
Update ID: 522772 Data source: Azure Updates API
Categories: Launched, Analytics, Azure Data Explorer
Summary:
What was updated
The labels() function in Kusto Query Language (KQL) graph semantics has reached general availability.
Key changes or new features
The labels() function allows developers and IT professionals to retrieve, filter, and project label information associated with nodes and edges in graph queries. This enhancement simplifies handling categorized graph data by enabling more precise and readable queries on graph structures within Azure Data Explorer.
Target audience affected
Developers and IT professionals working with graph data in Azure Data Explorer, especially those leveraging KQL for complex graph queries and analytics.
Important notes if any
With general availability, the labels() function is fully supported for production workloads. Users can now confidently integrate label-based filtering and projection in their graph queries to improve data exploration and insights. For detailed usage and examples, refer to the official Azure documentation.
Details:
The recent general availability of the labels() function in Kusto Query Language (KQL) graph semantics marks a significant enhancement for IT professionals working with graph data in Azure Data Explorer and related services. This update addresses the need for more granular and efficient querying of graph-structured data by enabling direct access to label metadata on nodes and edges within graph queries.
Background and Purpose of the Update
Graph semantics in KQL allow users to model and query complex relationships between entities using nodes (vertices) and edges. Prior to this update, extracting label information—categorical metadata assigned to nodes and edges—required cumbersome workarounds or was limited in scope. Labels often represent types, categories, or classifications essential for understanding graph topology and semantics. The labels() function was introduced to simplify and standardize the retrieval and manipulation of these labels, enhancing expressiveness and productivity in graph queries.
Specific Features and Detailed Changes
The labels() function is now fully supported and generally available, allowing users to:
This function integrates seamlessly into existing graph query constructs, such as graph_match and graph_path, enabling more concise and readable queries.
Technical Mechanisms and Implementation Methods
Under the hood, the labels() function queries the internal metadata store where label information is maintained as part of the graph schema. When invoked on a node or edge, it returns a dynamic array of strings representing all labels assigned to that entity. This leverages KQL’s dynamic data type and array manipulation capabilities, allowing further filtering or transformation using native KQL operators (e.g., mv-expand, has_any, array_length). The function supports use in both inline queries and stored functions, facilitating reusable graph query components.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
This update primarily benefits Azure Data Explorer users leveraging graph semantics for complex relationship analysis. It complements Azure Sentinel’s advanced security analytics by enabling more precise graph-based threat hunting queries. Additionally, it can be integrated into Azure Synapse Analytics pipelines where KQL is used for data exploration. The labels() function enhances interoperability with visualization tools like Azure Monitor Workbooks by enabling richer, label-aware graph visualizations.
In summary, the general availability of the labels() function in KQL graph semantics provides IT professionals with a powerful, native method to access and manipulate label metadata on graph entities, streamlining graph queries and enabling more sophisticated data analysis scenarios across Azure’s data and security platforms.
Published: November 07, 2025 18:45:02 UTC Link: Generally Available: Azure Database for PostgreSQL – Flexible Server availability zones expansion in Japan West
Update ID: 508408 Data source: Azure Updates API
Categories: Launched, Databases, Hybrid + multicloud, Azure Database for PostgreSQL, Features
Summary:
What was updated
Azure Database for PostgreSQL – Flexible Server now supports deployment across all three availability zones in the Japan West region.
Key changes or new features
The expansion enables high availability and improved resilience by allowing flexible servers to be provisioned in any of the three distinct availability zones within Japan West. This enhances fault tolerance and disaster recovery capabilities for PostgreSQL workloads.
Target audience affected
Developers and IT professionals managing PostgreSQL databases on Azure in the Japan West region who require high availability, zone-redundant deployments, and improved uptime SLAs.
Important notes if any
Users can now architect their PostgreSQL flexible server deployments for zone redundancy in Japan West, aligning with best practices for disaster recovery and minimizing downtime risks. This update supports workload continuity in case of zone-level failures. For detailed configuration and pricing, refer to the official Azure documentation.
Details:
The recent update announces the general availability of Azure Database for PostgreSQL – Flexible Server deployment across all three availability zones (AZs) in the Japan West region, enhancing high availability and resilience for PostgreSQL workloads in this geography.
Background and Purpose:
Azure Database for PostgreSQL – Flexible Server is a managed database service designed to provide greater control and flexibility over PostgreSQL deployments, including custom maintenance windows, zone-redundant high availability, and burstable compute options. Prior to this update, Flexible Server deployments in Japan West were limited in availability zone options, restricting customers’ ability to architect highly available, zone-redundant database solutions within this region. The expansion to support all three AZs addresses regional redundancy requirements and disaster recovery strategies, aligning with enterprise demands for improved uptime and data durability.
Specific Features and Detailed Changes:
This update enables customers to deploy Flexible Server instances in any of the three distinct AZs in Japan West, or configure zone-redundant high availability that spans all three zones. This means that primary and standby nodes can be placed in separate AZs to protect against zone-level failures. The update also supports zone-aware maintenance and failover, minimizing downtime during planned or unplanned events. This capability complements existing Flexible Server features such as automated backups, point-in-time restore, and scaling options.
Technical Mechanisms and Implementation Methods:
Under the hood, Azure leverages its physical datacenter infrastructure in Japan West, which consists of three isolated AZs, each with independent power, networking, and cooling. Flexible Server’s high availability architecture uses synchronous replication between primary and standby nodes deployed in separate AZs. The service automatically manages failover to the standby node in case of primary node or zone failure. Deployment through the Azure portal, CLI, or ARM templates now includes the option to select the specific AZ or enable zone-redundant HA. The platform also integrates with Azure’s underlying network fabric to ensure low-latency replication and consistent performance across zones.
Use Cases and Application Scenarios:
This enhancement is particularly valuable for mission-critical applications requiring stringent SLAs for availability and disaster recovery within the Japan West region. Examples include financial services, e-commerce platforms, and SaaS applications that must maintain continuous database availability despite datacenter-level disruptions. Developers and DBAs can architect multi-AZ deployments to meet compliance and business continuity requirements without resorting to complex manual replication or third-party clustering solutions.
Important Considerations and Limitations:
While zone-redundant deployments improve resilience, customers should be aware of potential latency impacts due to cross-zone synchronous replication, which may affect transaction throughput. Pricing may also vary based on zone redundancy and selected compute tiers. It is important to validate application compatibility with failover scenarios and to test backup and restore procedures in a multi-AZ context. Additionally, this update applies specifically to the Japan West region; customers requiring similar capabilities in other regions should verify availability accordingly.
Integration with Related Azure Services:
Flexible Server’s multi-AZ capability integrates seamlessly with Azure Monitor for health and performance monitoring, Azure Backup for data protection, and Azure Private Link for secure network connectivity. It also complements Azure Virtual Network configurations to isolate database traffic and enforce security policies. When combined with Azure App Service or Azure Kubernetes Service (AKS) deployed in the same region and AZs, customers can build highly available, scalable application architectures with end-to-end zone redundancy.
In summary, the general availability of Azure Database for PostgreSQL – Flexible Server across all three availability zones in Japan West significantly enhances the region’s capability to support resilient, zone-redundant PostgreSQL deployments, enabling IT professionals to design robust, highly available database solutions aligned with enterprise-grade availability and disaster recovery standards.
This report was automatically generated - 2025-11-08 03:02:07 UTC