Generated on: August 20, 2026 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 6 items
Published: August 19, 2026 21:04:18 UTC Link: Generally Available: Azure Databricks Lakebase in four additional regions
Update ID: 569684 Data source: Azure Updates API
Categories: Launched, AI + machine learning, Analytics, Azure Databricks, Feature
Summary:
What was updated
Azure Databricks Lakebase is now generally available in four additional Azure regions: North Central US, France Central, Germany West Central, and East Asia.
Key changes or new features
This update expands the regional availability of Azure Databricks Lakebase, enabling customers to deploy and operate Lakebase in these new regions. It offers greater flexibility for data residency, compliance, and disaster recovery strategies.
Target audience affected
Developers, data engineers, and IT professionals using or planning to use Azure Databricks Lakebase for analytics, data engineering, and AI workloads, especially those with regional requirements.
Important notes if any
Customers can now select these additional regions when provisioning Lakebase resources, supporting scenarios that require local data processing or compliance with regional regulations. This expansion may also help reduce latency for users and applications located in or near the new regions. No changes to API or service functionality were announced; this update is focused on regional availability.
Details:
Azure Update Technical Report
Title: Generally Available: Azure Databricks Lakebase in four additional regions
Link: Azure Update
Background and Purpose of the Update
Azure Databricks Lakebase is a unified analytics platform designed to simplify and accelerate data engineering, data science, and analytics workloads. The purpose of this update is to expand the general availability of Lakebase to four additional Azure regions: North Central US, France Central, Germany West Central, and East Asia. This regional expansion aims to provide customers with increased flexibility in deployment, improved data residency options, and enhanced performance by reducing latency for workloads hosted closer to their user base.
Specific Features and Detailed Changes
The core change in this update is the general availability (GA) of Lakebase in the newly listed regions. Customers can now provision Lakebase resources in North Central US, France Central, Germany West Central, and East Asia, in addition to previously supported regions. This enables organizations to leverage Lakebase’s capabilities for scalable data processing, analytics, and machine learning in these geographies. No new features or functional changes to Lakebase are announced; the update strictly pertains to expanded regional support.
Technical Mechanisms and Implementation Methods
From a technical perspective, the regional expansion involves the provisioning of Lakebase infrastructure within the Azure datacenters located in North Central US, France Central, Germany West Central, and East Asia. This is achieved by deploying Lakebase’s managed services and compute clusters in these regions, ensuring compliance with Azure’s regional architecture and operational standards. Customers can select the desired region during resource creation in the Azure portal or via ARM templates, allowing for seamless integration with existing Azure resource management workflows.
Use Cases and Application Scenarios
The regional availability of Lakebase is particularly beneficial for organizations with data residency requirements or those seeking to optimize performance for users in the newly supported regions. Typical use cases include:
Important Considerations and Limitations
IT professionals should consider the following when utilizing Lakebase in these regions:
Integration with Related Azure Services
Lakebase integrates seamlessly with other Azure services such as Azure Data Lake Storage, Azure Synapse Analytics, and Azure Machine Learning. The regional expansion ensures that these integrations can be leveraged locally, enabling end-to-end data pipelines and analytics solutions within the supported regions. IT professionals can architect solutions that combine Lakebase with Azure-native storage, compute, and security services for comprehensive data management and analytics.
Summary Sentence:
Azure Databricks Lakebase is now generally available in North Central US, France Central, Germany West Central, and East Asia, providing customers with expanded regional deployment options and enhanced flexibility for data analytics workloads.
Published: August 19, 2026 21:01:47 UTC Link: Generally Available: Azure SQL updates for mid-August 2026
Update ID: 569145 Data source: Azure Updates API
Categories: Launched, Databases, Hybrid + multicloud, Azure SQL Database, Feature
Summary:
What was updated
Azure SQL received updates in mid-August 2026, focusing on enhanced integration with Visual Studio Code.
Key changes or new features
Developers can now customize keyboard shortcuts for Quick Queries, the Results Grid, and the Query Editor directly within Visual Studio Code. This allows users to tailor their workflow and increase productivity without leaving the editor. Shortcut conflicts can be resolved within the same interface, ensuring a smoother experience.
Target audience affected
These updates primarily impact developers and IT professionals who use Azure SQL within Visual Studio Code, especially those who rely on keyboard shortcuts for efficient database development and management.
Important notes if any
The new customization options are available natively in Visual Studio Code, requiring no external tools or extensions. Users should review and adjust their shortcut settings to avoid conflicts and optimize their workflow. For more details, refer to the official Azure Update documentation.
Details:
Azure SQL Update Report – Mid-August 2026
Background and Purpose of the Update
The mid-August 2026 Azure SQL update focuses on enhancing developer productivity and customization within the Visual Studio Code (VS Code) environment. The primary goal is to streamline SQL development workflows by allowing users to tailor keyboard shortcuts for key Azure SQL features, thereby improving efficiency and accessibility for technical professionals working with Azure SQL databases.
Specific Features and Detailed Changes
The update introduces the ability to customize keyboard shortcuts for the following Azure SQL functionalities within VS Code:
These enhancements are accessible directly within the VS Code editor, eliminating the need to exit the development environment or use external configuration tools. The customization interface is integrated into VS Code’s settings, allowing for seamless adjustment of shortcuts according to individual or team preferences.
Technical Mechanisms and Implementation Methods
The update leverages VS Code’s extensibility and keyboard shortcut management system. Azure SQL’s VS Code extension now exposes additional command bindings for Quick Queries, Results Grid, and Query Editor actions. Users can configure these shortcuts via VS Code’s built-in “Keyboard Shortcuts” panel (Ctrl+K Ctrl+S), where Azure SQL-specific commands are listed and can be assigned to preferred key combinations.
The implementation ensures that shortcut changes are persisted within the user’s VS Code settings, supporting both local and cloud-synced environments. This mechanism relies on VS Code’s JSON-based settings files, which can be versioned and shared across development teams.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
This update is tightly integrated with the Azure SQL extension for VS Code, which connects to Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure Virtual Machines. It complements Azure DevOps workflows by facilitating faster query execution and script editing, and it can be used alongside other Azure services accessed via VS Code, such as Azure Resource Manager or Azure Storage extensions.
Summary Sentence
The mid-August 2026 Azure SQL update enables direct customization of keyboard shortcuts for Quick Queries, Results Grid, and Query Editor within Visual Studio Code, enhancing developer productivity and workflow efficiency without leaving the editor environment.
Published: August 19, 2026 21:00:19 UTC Link: Public Preview: SQL Formatter in MSSQL extension
Update ID: 569155 Data source: Azure Updates API
Categories: In preview, Databases, Hybrid + multicloud, Azure SQL Database, Feature
Summary:
What was updated
The MSSQL extension for Visual Studio Code now includes a SQL Formatter feature, available in public preview.
Key changes or new features
Developers can now format SQL scripts directly within the editor, improving code readability and consistency. The SQL Formatter offers enhanced customization options, allowing users to tailor formatting rules to their preferred coding style. This streamlines development workflows and helps maintain code quality across teams.
Target audience affected
This update is relevant to developers, database administrators, and IT professionals who use the MSSQL extension in Visual Studio Code for SQL Server development and management.
Important notes if any
As this feature is in public preview, users may encounter minor bugs or incomplete functionality. Feedback is encouraged to help improve the formatter before general availability. Users should review the extension’s documentation for configuration details and best practices.
For more information, visit the official update page.
Details:
Azure Update Technical Report: Public Preview – SQL Formatter in MSSQL Extension
Background and Purpose of the Update
The introduction of the SQL Formatter in the MSSQL extension addresses the need for improved code readability and maintainability within SQL development workflows. Traditionally, SQL scripts can become inconsistent in style due to manual formatting, which complicates collaboration and code review processes. The purpose of this update is to provide developers with an integrated tool to automatically format SQL scripts directly within their editor, promoting cleaner and more consistent codebases.
Specific Features and Detailed Changes
The SQL Formatter, now available in public preview, offers the following enhancements within the MSSQL extension:
Technical Mechanisms and Implementation Methods
The SQL Formatter is integrated into the MSSQL extension, which is typically used with Visual Studio Code or similar editors. The formatting engine processes SQL scripts in real-time, applying user-defined or default formatting rules. Customization is achieved through configuration files or editor settings, enabling granular control over formatting behavior. The extension leverages editor APIs to trigger formatting actions, either manually (via command palette or keyboard shortcuts) or automatically (on file save).
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
The MSSQL extension, and by extension the SQL Formatter, is designed to work with Azure SQL Database and SQL Server instances. This integration streamlines development and management of Azure-based SQL resources by providing a consistent, formatted scripting experience. While the formatter itself does not directly interact with Azure services, its use within the MSSQL extension supports Azure SQL workflows, improving script quality and maintainability for cloud-based database solutions.
Summary Sentence
The public preview of SQL Formatter in the MSSQL extension enables IT professionals to format SQL scripts directly within their editor, offering customizable options for cleaner, more consistent, and readable code to streamline SQL development and collaboration.
Published: August 19, 2026 20:59:19 UTC Link: Generally Available: Azure SQL Database provisioning in MSSQL extension
Update ID: 569160 Data source: Azure Updates API
Categories: Launched, Databases, Hybrid + multicloud, Azure SQL Database, Feature
Summary:
What was updated
Azure SQL Database provisioning is now generally available in the MSSQL extension.
Key changes or new features
Developers and IT professionals can now create and connect to fully managed Azure SQL Databases directly from their code editor (such as Visual Studio Code) using the MSSQL extension. This feature is free to use and streamlines the database provisioning process without leaving the development environment. The update also provides ready-to-use templates for Azure Resource Manager (ARM), Bicep, and Terraform, enabling Infrastructure as Code (IaC) workflows for automated and repeatable deployments.
Target audience affected
Developers, DevOps engineers, and IT professionals who use Azure SQL Database and Infrastructure as Code tools (ARM, Bicep, Terraform), especially those working within code editors.
Important notes if any
This feature simplifies database provisioning and integration with IaC pipelines, reducing setup time and potential errors. It is suitable for development, testing, and learning scenarios at no cost, but production workloads should still consider Azure’s standard pricing and resource limits. Ensure you have the latest MSSQL extension version to access these capabilities.
Data source: Using API data
Azure Update Link
Details:
Azure Update Report: Generally Available – Azure SQL Database Provisioning in MSSQL Extension
Background and Purpose of the Update
This update announces the general availability of Azure SQL Database provisioning directly within the MSSQL extension. The primary purpose is to streamline the process for developers and IT professionals to create and connect to fully managed Azure SQL Databases from their code editor environment, eliminating the need to switch between multiple tools or portals. This enhancement is aimed at improving developer productivity and simplifying cloud database adoption during development and testing phases, especially as the provisioning is offered at no cost.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation Methods
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
Summary Sentence
The general availability of Azure SQL Database provisioning in the MSSQL extension enables IT professionals to create and connect to fully managed cloud databases directly from their editor at no cost, with integrated support for ARM, Bicep, and Terraform templates to streamline development, automation, and DevOps workflows.
Published: August 19, 2026 17:20:42 UTC Link: Generally Available: vCore Customization: Disable Multithreading and Configurable Constrained Cores
Update ID: 569051 Data source: Azure Updates API
Categories: Launched, Compute, Virtual Machines, Feature
Summary:
What was updated
Azure Virtual Machines now offer General Availability of vCore Customization, specifically the ability to disable Simultaneous Multi-Threading/Hyper-Threading (SMT/HT) and configure constrained cores.
Details:
Azure Update Technical Report
Title: Generally Available: vCore Customization: Disable Multithreading and Configurable Constrained Cores
Link: Azure Update
The General Availability of VM vCore Customization for Azure Virtual Machines addresses the need for greater control over CPU resource allocation and performance characteristics in cloud environments. Traditionally, Azure VMs have offered fixed vCPU configurations, often with Simultaneous Multi-Threading (SMT) or Hyper-Threading (HT) enabled by default. However, certain workloads—such as high-performance computing (HPC), latency-sensitive applications, and software licensing scenarios—require more granular control over CPU threading and core allocation. This update provides IT professionals with enhanced flexibility to optimize VM performance and compliance.
SMT/HT Disabling:
When provisioning a VM, administrators can select an option to disable SMT/HT. Azure orchestrates the VM deployment to ensure that only physical cores are presented to the guest OS, effectively preventing the operating system from seeing or utilizing logical (hyper-threaded) cores.
Configurable Constrained Cores:
During VM creation or resizing, users can define the desired number of vCores. Azure’s resource manager enforces this constraint, allocating only the specified number of cores to the VM, regardless of the underlying hardware’s total core count.
Both features are accessible via Azure Portal, CLI, ARM templates, and API, ensuring seamless integration into existing deployment workflows.
Published: August 19, 2026 16:36:30 UTC Link: Generally Available: BYON (Bring Your Own NIC) in Azure Site Recovery
Update ID: 569515 Data source: Azure Updates API
Categories: Launched, Management and governance, Migration, Azure Site Recovery, Feature
Summary:
What was updated
Azure Site Recovery now supports Bring Your Own NIC (BYON) for Azure-to-Azure disaster recovery scenarios.
Key changes or new features
You can now attach an existing, pre-provisioned Network Interface Card (NIC) in the target region during test-failover and failover operations. This allows you to retain custom networking configurations, such as static IP addresses, network security groups, and other settings associated with the NIC. Previously, Azure Site Recovery would create a new NIC during failover, requiring manual reconfiguration.
Target audience affected
This update is relevant for IT professionals managing disaster recovery, network administrators, and developers responsible for Azure infrastructure automation and configuration. It is especially useful for organizations with strict networking requirements or those leveraging Infrastructure as Code (IaC) for environment consistency.
Important notes if any
To use BYON, you must pre-provision the NIC in the target region before initiating failover or test-failover. Ensure that the NIC is not attached to any other VM and is configured with the necessary network settings. This feature enhances automation, reduces manual intervention, and helps maintain compliance with organizational networking policies.
For more details, see the official update: https://azure.microsoft.com/updates?id=569515
Details:
Azure Update Report: Generally Available – BYON (Bring Your Own NIC) in Azure Site Recovery
Background and Purpose of the Update:
Azure Site Recovery (ASR) is a disaster recovery solution that enables replication, failover, and recovery of workloads across Azure regions. Previously, during failover or test-failover in Azure-to-Azure scenarios, ASR automatically created and attached a new Network Interface Card (NIC) to the recovered VM. This often resulted in loss of custom networking configurations, IP reservations, and security settings, requiring additional post-failover configuration. The purpose of this update is to provide greater control and flexibility by allowing users to bring and attach a pre-provisioned NIC in the target region, thereby preserving networking configurations and reducing recovery time.
Specific Features and Detailed Changes:
The update introduces the ability to use an existing, pre-provisioned NIC for both test-failover and actual failover operations in Azure-to-Azure disaster recovery scenarios. Users can now select a NIC that has been configured in advance with desired settings such as IP address, subnet, network security group (NSG), and other network properties. This feature is generally available and can be leveraged during the recovery process to ensure that the VM retains its network identity and configuration.
Technical Mechanisms and Implementation Methods:
The implementation allows users to specify a pre-provisioned NIC in the target Azure region when configuring recovery settings for a protected VM in ASR. During failover or test-failover, ASR will attach the specified NIC to the recovered VM instead of creating a new NIC. This preserves all custom configurations associated with the NIC, including static IP assignments, NSG rules, and any other network-related settings. The process is managed through the Azure portal or via automation using Azure Resource Manager templates and APIs.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
BYON NIC in ASR integrates seamlessly with Azure Virtual Network, Network Security Groups, and Azure Resource Manager. It enhances disaster recovery workflows by enabling tighter integration with network management and security services, and supports automation through ARM templates and Azure APIs. This update complements existing ASR features, providing a more robust and customizable recovery solution.
Summary Sentence:
Azure Site Recovery now supports attaching pre-provisioned NICs during failover and test-failover in Azure-to-Azure scenarios, enabling preservation of custom network configurations and reducing post-recovery setup time.
This report was automatically generated - 2026-08-20 03:05:29 UTC