Merge pull request #3236 from jboback/summarization-updates-2-25

updates to summarization, remove language studio quickstart

Author: AnnaMHuff

.openpublishing.redirection.json

@@ -245,6 +245,16 @@
       "redirect_url": "/azure/open-datasets/dataset-catalog",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/ai-services/language-service/language-studio.md",
+      "redirect_url": "/azure/ai-services/language-service/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/language-service/summarization/region-support.md",
+      "redirect_url": "/azure/ai-services/language-service/concepts/regional-support",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/open-datasets/dataset-genomics-data-lake.md",
       "redirect_url": "/azure/open-datasets/dataset-catalog",

articles/ai-services/language-service/concepts/regional-support.md

@@ -175,13 +175,33 @@ Custom text classification is only available in some Azure regions. Some regions
 
 ## Summarization
 
-|Region|Document abstractive summarization|Conversation issue and resolution summarization|Conversation narrative summarization with chapters|Custom summarization|
-|------------|------------------|------------------|------------------|------------------|-|
-|North Europe| ✓ | ✓ | ✓ | |
-|East US| ✓ | ✓ | ✓ | ✓ |
-|UK South| ✓ | ✓ | ✓ | |
-|Southeast Asia| ✓ | ✓ | ✓ | |
-
+|Region                |Text abstractive summarization|Conversation summarization               |
+|----------------------|------------------------------|-----------------------------------------|
+|US Gov Virginia       |✓                             |✓                                        |
+|US Gov Arizona        |✓                             |✓                                        |
+|Australia East        |✓                             |✓                                        |
+|Canada Central        |✓                             |✓                                        |
+|Central US            |✓                             |✓                                        |
+|China North 3         |✓                             |✓                                        |
+|East US               |✓                             |✓                                        |
+|East US 2             |✓                             |✓                                        |
+|France Central        |✓                             |✓                                        |
+|Germany West Central  |✓                             |✓                                        |
+|Italy North           |✓                             |✓                                        |
+|Japan East            |✓                             |✓                                        |
+|North Central US      |✓                             |✓                                        |
+|North Europe          |✓                             |✓                                        |
+|South Central US      |✓                             |✓                                        |
+|South UK              |✓                             |✓                                        |
+|Southeast Asia        |✓                             |✓                                        |
+|Switzerland North     |✓                             |✓                                        |
+|USNat East            |✓                             |✓                                        |
+|USNat West            |✓                             |✓                                        |
+|USSec East            |✓                             |✓                                        |
+|USSec West            |✓                             |✓                                        |
+|West Europe           |✓                             |✓                                        |
+|West US               |✓                             |✓                                        |
+|West US 2             |✓                             |✓                                        |
 
 ## Custom Text Analytics for health
 

articles/ai-services/language-service/entity-linking/includes/development-options.md

@@ -13,5 +13,5 @@ To use entity linking, you submit raw unstructured text for analysis and handle
 
 |Development option  |Description  |
 |---------|---------|
-|Language studio     | Language Studio is a web-based platform that lets you try entity linking with text examples without an Azure account, and your own data when you sign up. For more information, see the [Language Studio website](https://language.cognitive.azure.com/tryout/linkedEntities) or [language studio quickstart](../../language-studio.md).         |
+|Language studio     | Language Studio is a web-based platform that lets you try entity linking with text examples without an Azure account, and your own data when you sign up. For more information, see the [Language Studio website](https://language.cognitive.azure.com/tryout/linkedEntities).         |
 |REST API or Client library (Azure SDK)      | Integrate entity linking into your applications using the REST API, or the client library available in a variety of languages. For more information, see the [entity linking quickstart](../quickstart.md).        |

articles/ai-services/language-service/entity-linking/overview.md

@@ -36,5 +36,5 @@ An AI system includes not only the technology, but also the people who will use
 ## Next steps
 
 There are two ways to get started using the entity linking feature:
-* [Language Studio](../language-studio.md), which is a web-based platform that enables you to try several Azure AI Language features without needing to write code.
+* [Language Studio](https://language.cognitive.azure.com/tryout/linkedEntities), which is a web-based platform that enables you to try several Azure AI Language features without needing to write code.
 * The [quickstart article](quickstart.md) for instructions on making requests to the service using the REST API and client library SDK.  

articles/ai-services/language-service/index.yml

@@ -23,9 +23,6 @@ highlightedContent:
     - title: What's new?
       itemType: whats-new
       url: whats-new.md
-    - title: Get started with Language Studio
-      itemType: get-started
-      url: language-studio.md
     - title: Responsible use of AI
       itemType: concept
       url: /legal/cognitive-services/language-service/transparency-note?context=/azure/ai-services/language-service/context/context

articles/ai-services/language-service/language-studio.md

@@ -27,7 +27,7 @@ The Language service also provides several new features as well, which can eithe
 > [!TIP]
 > Unsure which feature to use? See [Which Language service feature should I use?](#which-language-service-feature-should-i-use) to help you decide.
 
-[**Language Studio**](./language-studio.md) enables you to use the below service features without needing to write code.
+[**Azure AI Foundry**](https://ai.azure.com) enables you to use most of the below service features without needing to write code.
 
 ### Named Entity Recognition (NER)
 
@@ -87,8 +87,8 @@ The Language service also provides several new features as well, which can eithe
       :::image type="content" source="media/overview/text-summarization.png" alt-text="A screenshot of text summarization in Azure AI Foundry." lightbox="media/overview/text-summarization.png":::
    :::column-end:::
    :::column span="":::
-      [Summarization](./summarization/overview.md) condenses information for text and conversations (chat and transcripts). 
-Text summarization generates a summary, supporting two approaches: [Extractive summarization](summarization/how-to/document-summarization.md) produces a summary by extracting salient sentences within the document along with the positioning information of these sentences, and abstractive summarization, which generates a summary with concise, coherent sentences or words that aren't verbatim extract sentences from the original document.  
+      [Summarization](./summarization/overview.md) condenses information for text and conversations (chat and transcripts).
+      Text summarization generates a summary, supporting two approaches: Extractive summarization produces a summary by extracting salient sentences within the document along with the positioning information of these sentences, and abstractive summarization, which generates a summary with concise, coherent sentences or words that aren't verbatim extract sentences from the original document.  
 Conversation summarization recaps and segments long meetings into timestamped chapters. Call center summarization summarizes customer issues and resolution.
    :::column-end:::
 :::row-end:::
@@ -219,7 +219,7 @@ After you've had a chance to get started with the Language service, try our tuto
 * [Use Power Automate to sort information in Microsoft Excel](named-entity-recognition/tutorials/extract-excel-information.md) 
 * [Use Flask to translate text, analyze sentiment, and synthesize speech](/training/modules/python-flask-build-ai-web-app/)
 * [Use Azure AI services in canvas apps](/powerapps/maker/canvas-apps/cognitive-services-api?context=/azure/ai-services/language-service/context/context)
-* [Create a FAQ Bot](question-answering/tutorials/bot-service.md)
+* [Create an FAQ Bot](question-answering/tutorials/bot-service.md)
 
 ## Additional code samples
 

articles/ai-services/language-service/overview.md

@@ -36,9 +36,6 @@ The conversational PII API supports all Azure regions supported by the Language
 
 ## Submitting data
 
-> [!NOTE]
-> See the [Language Studio](../language-studio.md#valid-text-formats-for-conversation-features) article for information on formatting conversational text to submit using Language Studio. 
-
 You can submit the input to the API as list of conversation items. Analysis is performed upon receipt of the request. Because the API is asynchronous, there may be a delay between sending an API request, and receiving the results. For information on the size and number of requests you can send per minute and second, see the data limits below.
 
 When using the async feature, the API results are available for 24 hours from the time the request was ingested, and is indicated in the response. After this time period, the results are purged and are no longer available for retrieval.