12.27.0b1 (2026-11-04)
Breaking Changes
- Custom transports that use legacy
azure-coreRequest/Response types will no longer be supported and may now cause errors if used. Please ensure custom transports are utilizing types fromazure.core.rest. - Changed the default
max_single_get_sizefrom 32 MiB to 4 MiB. This means the initial download request will now be 4 MiB rather than 32 MiB which may result in more requests than previous versions depending on file size. This also means some file downloads may use parallel requests when they were not previously, ifmax_concurrencyis set greater than 1. To restore the previous behavior, passmax_single_get_size = 32 * 1024 * 1024when constructing the client.
Features Added
- Added support for service versions 2026-12-06 and 2027-03-07.
- Added opt-in client session-based authentication via the new
use_sessionkeyword argument. When enabled, eligible file read requests are authenticated with a short-lived, per-file-system session credential obtained from the service rather than the bearer token. Requires aTokenCredential. Sessions are managed by a session provider, which can be shared across clients via thesession_providerkeyword, and the account name used for signing can be set explicitly withsession_account_name.
Bugs Fixed
- Fixed an issue where a SAS generated for a path containing a backslash (
\) was invalid because the backslash was not normalized to a forward slash when building the signed resource.
Other Changes
- Content-Type for append_data has changed from application/json to octet-stream
- Migrated generated code to use the new TypeSpec generator.