You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-services/language-service/whats-new.md
+31-6Lines changed: 31 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,15 +17,40 @@ Azure AI Language is updated on an ongoing basis. To stay up-to-date with recent
17
17
18
18
## March 2025
19
19
20
-
* Document and text abstractive summarization is now powered by fine-tuned Phi-3.5-mini! See the [announcement blog](https://techcommunity.microsoft.com/blog/azure-ai-services-blog/exciting-update-abstractive-summarization-in-azure-ai-language-now-powered-by-ph/4369025) for more information.
21
-
* Our [Conversational PII redaction service](personally-identifiable-information/how-to/redact-conversation-pii.md) is now powered by an upgraded GA model. This updated 2025-02-01 version includes improved quality and accuracy for Credit card number entities and Numeric identification entities, such as Social security numbers, Driver’s license numbers, Policy numbers, Medicare Beneficiary Identifier, and Financial account numbers.
22
-
* Both our [Text PII redaction service](personally-identifiable-information/overview.md) and our Conversational PII service preview API (version 2024-11-15-preview) now support the option to mask detected sensitive entities with a label beyond just redaction characters. Customers can specify if personal data content such as names and phone numbers, that is, "John Doe received a call from 424-878-9192", are masked with a redaction character, that is, "******** received a call from ************", or masked with an entity label, such as "`PERSON_1` received a call from `PHONENUMBER_1`". More on how to specify the redaction policy style for your outputs can be found in our [how-to guides](personally-identifiable-information/how-to/redact-text-pii.md).
23
-
* In the [Named Entity Recognition service](named-entity-recognition/overview.md), [Entity Resolution](named-entity-recognition/concepts/entity-resolutions.md) was upgraded to use [Entity Metadata](named-entity-recognition/concepts/entity-metadata.md) starting in API version 2023-04-15-preview. If you're calling the preview version of the API equal or newer than 2023-04-15-preview, check out the [Entity Metadata](named-entity-recognition/concepts/entity-metadata.md) article for information on how to use the resolution feature.
24
-
*[Named Entity recognition](named-entity-recognition/overview.md) now supports the ability to specify a list of entity tags to be included in the response or excluded from the response. If a piece of text is classified as more than one entity type, the `overlapPolicy` parameter allows customers to specify how the service will handle the overlap. The `inferenceOptions` parameter allows for users to adjust the inference, such as excluding the detected entity values from being normalized and included in the metadata. Learn more on [our documentation](named-entity-recognition/how-to/skill-parameters.md).
20
+
* Our [Conversational PII redaction](personally-identifiable-information/how-to/redact-conversation-pii?tabs=client-libraries.md) service is now powered by an upgraded GA model. This updated 2024-02-01 version includes improved quality and accuracy in Credit card number entities and numeric identification entities, such as Social Security numbers, driver’s license numbers, policy numbers, Medicare Beneficiary Identifiers, and Financial account numbers.
21
+
22
+
## February 2025
23
+
24
+
* Document and text abstractive summarization is now powered by fine-tuned Phi-3.5-mini! Check out the [Announcing Blog](https://techcommunity.microsoft.com/blog/azure-ai-services-blog/exciting-update-abstractive-summarization-in-azure-ai-language-now-powered-by-ph/4369025) for more information.
25
+
* More skills are available in [Azure AI Foundry](https://ai.azure.com): Extract key phrase, Extract named entities, Analyze sentiment and Detect language. More skills are yet to come.
26
+
27
+
## January 2025
28
+
29
+
* .NET SDK for Azure AI Language text analytics, [Azure.AI.Language.Text 1.0.0-beta.2](https://www.nuget.org/packages/Azure.AI.Language.Text/1.0.0-beta.2#readme-body-tab), is now available. This client library supports the latest REST API version, 2024-11-01 and 2024-11-15-preview, for the following features:
30
+
* Language detection
31
+
* Sentiment analysis
32
+
* Key phrase extraction
33
+
* Named entity recognition (NER)
34
+
* Personally identifiable information (PII) entity recognition
35
+
* Entity linking
36
+
* Text analytics for health
37
+
* Custom named entity recognition (Custom NER)
38
+
* Custom text classification
39
+
* Extractive text summarization
40
+
* Abstractive text summarization
41
+
* Custom sentiment analysis (preview), custom text analytics for health (preview) and custom summarization (preview) were retired on January 10th, 2025, as Azure AI features are constantly evaluated based on customer demand and feedback. Based on the customers’ feedback of these preview features, Microsoft has decided to retire this feature and prioritize new custom model features leveraging the power of generative AI to better serve customers’ needs.
25
42
26
43
## November 2024
27
44
28
-
*[Native document support](native-document-support/overview.md) is now available in public preview `2024-11-15-preview` without gated preview limitations.
45
+
* Azure AI Language is moving to [Azure AI Foundry](https://ai.azure.com). These skills are now available in AI Foundry playground: Extract health information, Extract PII from conversation, Extract PII from text, Summarize text, Summarize conversation, Summarize for call center. More skills follow.
46
+
* Runtime Container for Conversational Language Understanding (CLU) is available for on-premise connection.
47
+
* Both our [Text PII redaction service](personally-identifiable-information/overview?tabs=text-pii.md) and our Conversational PII service preview API (version 2024-11-15-preview) now support the option to mask detected sensitive entities with a label beyond just redaction characters. Customers can specify if personal data content such as names and phone numbers, that is, "John Doe received a call from 424-878-9192", are masked with a redaction character, that is, "******** received a call from ************", or masked with an entity label, that is, "`PERSON_1` received a call from `PHONENUMBER_1`". More on how to specify the redaction policy style for your outputs can be found in our [how-to guides](personally-identifiable-information/how-to-call.md).
48
+
* Native document support gating is removed with the latest API version, 2024-11-15-preview, allowing customers to access native document support for PII redaction and summarization. Key updates in this version include:
49
+
* Increased Maximum File Size Limits (from 1 MB to 10 MB).
50
+
* Enhanced PII Redaction Customization: Customers can now specify whether they want only the redacted document or both the redacted document and a JSON file containing the detected entities.
51
+
* Language detection is a preconfigured feature that can detect the language a document is written in and returns a language code for a wide range of languages, variants, dialects, and some regional/cultural languages. Today the general availability of [scription detection capability](language-detection/how-to/call-api#script-name-and-script-code.md), and 16 more languages support, which adds up to [139 total supported languages](language-detection/language-support.md) is announced.
52
+
* [Named Entity Recognition service](named-entity-recognition/overview.md), [Entity Resolution](named-entity-recognition/concepts/entity-resolutions.md) was upgraded to the Entity Metadata starting in API version 2023-04-15-preview. If you're calling the preview version of the API equal or newer than 2023-04-15-preview, check out the Entity Metadata article to use the resolution feature. The service now supports the ability to specify a list of entity tags to be included into the response or excluded from the response. If a piece of text is classified as more than one entity type, the overlapPolicy parameter allows customers to specify how the service will handle the overlap. The inferenceOptions parameter allows for users to adjust the inference, such as excluding the detected entity values from being normalized and included in the metadata. Along with these optional input parameters we support an updated output structure (with new fields tags, type, and metadata) to ensure enhanced user customization and deeper analysis Learn more on our documentation.
53
+
* Text analytics for health (TA4H) is a preconfigured feature that extracts and labels relevant medical information from unstructured texts such as doctor's notes, discharge summaries, clinical documents, and electronic health records. Today, we released support for Fast Healthcare Interoperability Resources (FHIR) structuring and temporal [assertion detection](text-analytics-for-health/concepts/assertion-detection.md) in the Generally Available API.
0 commit comments