Generated on: July 01, 2026 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 2 items
Published: June 30, 2026 20:45:26 UTC Link: Generally Available: Client-side data integrity protections in Azure Blob Storage
Update ID: 566895 Data source: Azure Updates API
Categories: Launched, Storage, Azure Blob Storage, SDK and Tools
Summary:
What was updated
Client-side data integrity protections in Azure Blob Storage are now generally available, with enhanced support for CRC64-NVME integrated into the latest Azure Blob SDKs for .NET, C++, and JavaScript.
Details:
Comprehensive Technical Explanation: Azure Update – Client-side Data Integrity Protections in Azure Blob Storage
Background and Purpose of the Update:
Azure Blob Storage has historically provided mechanisms for data integrity validation, starting with MD5 hash support as part of the original HTTP standards. In 2019, Azure introduced CRC64-NVME support to further enhance integrity checks. The purpose of this update is to strengthen client-side data integrity protections by integrating CRC64-NVME directly into the latest Azure Blob SDKs for .NET, C++, and JavaScript, thereby enabling developers to perform robust integrity validation during data transfers.
Specific Features and Detailed Changes:
This update makes CRC64-NVME data integrity validation generally available within the Azure Blob Storage SDKs for .NET, C++, and JavaScript. With this integration, developers can now utilize CRC64-NVME checksums natively in their client applications when uploading or downloading blobs. This feature supplements the existing MD5-based validation, allowing for more flexible and reliable integrity verification options. The SDKs now expose methods and properties to generate and validate CRC64-NVME checksums as part of blob operations.
Technical Mechanisms and Implementation Methods:
CRC64-NVME is a cyclic redundancy check algorithm designed for high performance and reliability. When a client uploads or downloads a blob, the SDK calculates the CRC64-NVME checksum for the payload. This checksum is transmitted alongside the data, allowing the Azure Blob Storage service to verify that the data received matches the checksum provided. On download, the client can validate the integrity of the received data by comparing the checksum with the expected value. The SDKs abstract these operations, providing seamless integration for developers without requiring manual checksum computation or validation.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
Azure Blob Storage is often used in conjunction with services like Azure Data Lake, Azure Backup, and Azure Synapse Analytics. The enhanced client-side integrity protections can be leveraged in these scenarios to ensure reliable data movement and storage. The update does not alter integration patterns but provides additional assurance for data integrity in workflows involving Blob Storage.
Summary Sentence:
Azure Blob Storage now offers generally available client-side CRC64-NVME data integrity validation in its latest .NET, C++, and JavaScript SDKs, enabling robust and efficient integrity checks during blob uploads and downloads for improved reliability in critical data transfer scenarios.
Published: June 30, 2026 19:00:51 UTC Link: Generally Available: Toolboxes in Microsoft Foundry
Update ID: 563481 Data source: Azure Updates API
Categories: Launched, AI + machine learning, Microsoft Foundry, Microsoft Build, Feature
Summary:
What was updated
Toolboxes in Microsoft Foundry are now generally available (GA).
Key changes or new features
Toolboxes provide a unified endpoint for invoking commonly used tools within prompt agents and can also be called outside of prompt agents. This update standardizes tool access, eliminating the need for each agent team to manually assemble their own tool lists for similar tasks. Toolboxes enable shared, reusable tool definitions and consistent integration across projects.
Target audience affected
Developers and IT professionals building or managing prompt agents, AI solutions, or automation workflows in Microsoft Foundry.
Important notes if any
This GA release streamlines tool management, reduces duplication of effort, and promotes best practices by centralizing tool definitions. Teams can now leverage a common set of tools, improving maintainability and collaboration. Integration with existing prompt agents and external systems is supported via the unified endpoint. Review documentation for migration guidance if you have custom tool lists.
Details:
Azure Update Report: Generally Available – Toolboxes in Microsoft Foundry
Background and Purpose of the Update
The release of Toolboxes in Microsoft Foundry to General Availability (GA) addresses a common challenge in agent development: disparate tool lists and fragmented access mechanisms. Previously, each agent team was required to manually assemble and maintain their own set of tools to solve recurring tasks, resulting in duplicated effort and inconsistent tool usage across projects. The purpose of this update is to provide a unified, standardized endpoint for invoking commonly used tools, both within prompt agents and externally, thereby streamlining tool access and improving operational efficiency.
Specific Features and Detailed Changes
With Toolboxes now generally available, Microsoft Foundry introduces a consolidated endpoint that allows agent teams to access a curated set of tools without the need for custom integration. These Toolboxes encapsulate the most-used functionalities required by prompt agents, enabling direct invocation from agents or other services. The update eliminates the need for each team to hand-assemble tool lists, fostering standardization and reducing maintenance overhead. The unified endpoint supports both internal (prompt agent) and external (outside prompt agent) calls, expanding the usability of these tools across various workflows.
Technical Mechanisms and Implementation Methods
Toolboxes are implemented as a unified API endpoint within Microsoft Foundry. This endpoint exposes a set of callable tools, which can be invoked programmatically by agents or other services. The mechanism ensures that tool invocation is consistent, secure, and scalable. By centralizing tool access, the system leverages Foundry’s authentication and authorization infrastructure, ensuring that only permitted agents or services can utilize the tools. The endpoint is designed for high availability and performance, supporting concurrent calls from multiple agents or external applications.
Use Cases and Application Scenarios
Typical use cases for Toolboxes include automating repetitive tasks within prompt agents, such as data processing, information retrieval, or workflow orchestration. Agent teams can now leverage the same set of tools for common tasks without duplicating integration efforts. Additionally, external services can call the Toolboxes endpoint to utilize these functionalities, enabling broader application scenarios such as cross-agent collaboration, centralized task automation, and integration with other Azure services or third-party systems.
Important Considerations and Limitations
IT professionals should note that Toolboxes are designed to be invoked both inside and outside prompt agents, but access control and security policies must be carefully managed to prevent unauthorized usage. The update does not specify the full range of available tools or any customization options, so teams should review documentation to ensure their requirements are met. There may be limitations regarding tool extensibility or integration with legacy systems, depending on the supported API protocols and authentication mechanisms.
Integration with Related Azure Services
Toolboxes in Microsoft Foundry can be integrated with other Azure services by leveraging the unified endpoint. For example, agents hosted in Azure AI services can invoke Toolboxes for enhanced functionality, and workflows in Azure Logic Apps or Azure Functions can call the endpoint to automate tasks. The standardized access mechanism simplifies integration with Azure’s identity and access management, monitoring, and logging services, enabling comprehensive governance and observability.
Summary Sentence
Microsoft Foundry Toolboxes are now generally available, providing a unified endpoint for invoking commonly used tools in prompt agents and external applications, thereby standardizing tool access and reducing operational complexity for agent teams.
This report was automatically generated - 2026-07-01 03:01:40 UTC