The Azure SDK team is pleased to make available the November 2020 client library release.
- Azure Identity
- Azure Tables
- Azure Storage Blob
- Azure Storage Data Lake
- Azure Storage File Share
- Azure Service Bus
- Azure Event Hubs
- Azure Storage Queue
- Azure Communication Administration
- Azure Communication Chat
- Azure Communication Common
- Azure Communication SMS
- Azure Metrics Advisor
- Azure Form Recognizer
- Azure Text Analytics
To install the packages, copy and paste the below into a terminal.
$> npm install @azure/identity $> npm install @azure/tables $> npm install @azure/storage-blob $> npm install @azure/storage-file-datalake $> npm install @azure/storage-file-share $> npm install @azure/service-bus $> npm install @azure/storage-queue $> npm install @azure/event-hubs $> npm install @azure/communication-administration@next $> npm install @azure/communication-chat@next $> npm install @azure/communication-common@next $> npm install @azure/communication-sms@next $> npm install @azure/ai-metrics-advisor@next $> npm install @azure/ai-form-recognizer@next $> npm install @azure/ai-text-analytics@next
If you have a bug or feature request for one of the libraries, please post an issue at the azure-sdk-for-js repository.
This release marks the general availability of version 7 of the
Breaking Changes on @firstname.lastname@example.org
- Please see the migration guide to move from Service Bus V1 to Service Bus V7 to understand the major breaking changes.
- For all the updates in version
1.1.x) across multiple previews, check out the Service Bus changelog
New Features on @email@example.com
- A new
ServiceBusAdministrationClientto perform operations like create/get/list/update/delete on queues/topics/subscriptions/rules. These were already available as part of a separate package
@azure/arm-servicebusthat uses Azure Resource Manager APIs but had the drawback of not supporting connection strings.
- Ability to create a batch of messages with the smarter
ServiceBusMessageBatch.tryAddMessage()APIs. This will help you manage the messages to be sent in the most optimal way.
- Ability to configure the retry policy used by the operations on the client, sender and receivers.
- Ability to cancel async operations on the client, sender and receivers and the management operations using the abort signal from @azure/abort-controller.
We’re glad to announce a new major release of our Identity package. This release includes standardized
ManagedIdentityCredential support across languages, as well as improvements to
New Features on @firstname.lastname@example.org
- A new dependency has been added: the Microsoft Authentication Library (MSAL). MSAL allows us to provide secure and reliable implementations for
InteractiveBrowserCredentialnow works for Node, which spawns the user’s browser and connects via a browser-based auth code flow.
- With 1.2, we’ve added support for Azure Arc to our Managed Identity credential.
- Identity now supports Subject Name/Issuer (SNI) as part of authentication for ClientCertificateCredential.
- Added Active Directory Federation Services authority host support to the node credentials.
- Added support for multiple clouds on
- Added support for authenticating with user assigned identities on Azure App Service.
We are releasing to add support for new service features in Azure Storage Service API version 2020-02-10.
New Features on @email@example.com
BlockBlobClient.uploadData(data: Buffer | Blob | ArrayBuffer | ArrayBufferView, options)for parallel uploading. It’s available in both Node.js and browsers.
Major Fixes on @firstname.lastname@example.org
- Fixed an issue where
DataLakePathClient.move()will give an
InvalidSourceUrierror when the copy source name contains characters that need to be URL encoded.
New Features on @email@example.com
ShareClient.setProperties(), which can be used to set both Share Tier and Share Quota.
New Features on @firstname.lastname@example.org
- Updated Azure Storage Service API version to 2020-02-10.
We’re releasing an Azure Event Hubs client patch update with bug fixes.
Major Fixes on @email@example.com
- Fixes an issue where the
processEventshandler passed to
EventHubConsumerClient.subscribe()could ignore the
maxWaitTimeInSecondsparameter after a disconnection, resulting in
processEventsbeing invoked rapidly without events.
We’re releasing a new preview of our Azure Tables library. System properties
Timestamp are renamed to
This version 1.0.0-beta.2 incorporates feedback from UX Studies and Architecture Board Review.
New Features on @firstname.lastname@example.org
- Parameters of
Datetype now also accept strings
- Handle potential new data feed source types gracefully
Breaking Changes on @email@example.com
- Various renames of types, methods, and properties to improve the API surface. Please see the CHANGELOG for more details.
New Features on @firstname.lastname@example.org
- Added support for long-running operations. See details under Breaking Changes.
Breaking Changes on @email@example.com
beginReservePhoneNumberswhich returns a poller for the long-running operation.
beginPurchaseReservationwhich returns a poller for the long-running operation.
beginReleasePhoneNumberswhich returns a poller for the long-running operation.
This release contains minor fixes.
This release contains minor fixes.
This release contains minor fixes.
This beta package targets Azure Form Recognizer API version
2.1-preview.2, and introduces support for its new form recognition features, including:
New Features on @firstname.lastname@example.org
- Support for two new prebuilt recognition models for invoices and business cards through the
beginRecognizeBusinessCardsmethods (as well as their
- Support for “Selection Marks” as a new fundamental form element. A selection mark is a mark such as a checkbox or a radio button on a form that can be either “selected” or “unselected”. This type is supported in content recognition where it is a new type of
FormElementas well as in custom and prebuilt model recognition where it is a new type of
- Support for the bitmap image format (with content type “image/bmp”) in prebuilt model recognition and content recognition. Custom form recognition does not currently support bitmap images.
localeoption for all prebuilt model methods, allowing for the specification of a document’s origin to assist the service with correct analysis of the documents contents.
languageoption for the content recognition method
beginRecognizeContentthat specifies the document’s language (the service supports language auto-detection, so this option allows for forcing the service to use a particular language).
pagesoption for the content recognition method
beginRecognizeContentthat specifies which pages in a multi-page document (a document with a content type of “application/pdf” or “image/tiff”) should be analyzed, allowing for the analysis of only certain pages of a document.
- Two new response fields:
boundingBoxproperty on recognized
FormTableobjects that indicates the extent of the entire table on the page (previously, only individual elements had
FormLineobjects that contains information about the line’s appearance in the document such as its style (e.g. “handwritten”).
In addition to the above form recognition features, there is also a new set of model training features, including:
- Creating composed models from an array of model GUIDs through the
FormTrainingClient. Composed models combine a set of custom labeled models into a single model with a unique model GUID, and when the new composed model is used for recognition, it will insert a classification step that determines the most appropriate of its submodels to use for recognition. This feature also encompasses some new fields, including:
CustomFormModelthat may optionally contain extra properties of the custom model. Currently, the only such property is
isComposedModel, which indicates that the model is a composed model rather than a standard trained model.
RecognizedFormthat contains the GUID of the specific submodel that was used to analyze the form and generate the result.
RecognizedFormthat represents the service’s confidence that it chose the correct submodel to use during analysis (and therefore the correct value of
modelNameoption for model training (both
beginCreateComposedModel) that can specify a human-readable name for a model. The model name does not have to be unique, and because models are immutable it cannot be changed. The
CustomFormModelwill now contain the name of the model, if one was associated during model creation.
This beta package targets Azure Text Analytics API version
3.1-preview.3, and introduces support for its new text analytics features, including:
New Features on @email@example.com
- Support for the new API for batch tasks processing through the
beginAnalyzemethod. The currently supported tasks are Named Entity Recognition, Personally identifiable Information, and Key Phrase Extraction.
- Support for the recognition of healthcare entities API with the introduction of the
beginAnalyzeHealthcaremethod. Since the Health API is currently only available in a gated preview, you need to have your subscription on the service’s allow list. Also, note that since this is a gated preview, AAD is not supported. For more information, see the Text Analytics for Health documentation.