Merge pull request #261414 from MicrosoftDocs/main

12/15/2023 PM Publish

Author: Taojunshen

articles/ai-services/language-service/summarization/includes/quickstarts/rest-api.md

@@ -4,13 +4,17 @@ author: jboback
 manager: nitinme
 ms.service: azure-ai-language
 ms.topic: include
-ms.date: 02/17/2023
+ms.date: 12/13/2023
 ms.author: aahi
 ms.custom: ignite-fall-2021, event-tier1-build-2022, ignite-2022
 ---
 
+# [Document summarization](#tab/document-summarization)
+
 # [Conversation summarization](#tab/conversation-summarization)
 
+---
+
 Use this quickstart to send text summarization requests using the REST API. In the following example, you will use cURL to summarize documents or text-based customer service conversations.
 
 [!INCLUDE [Use Language Studio](../use-language-studio.md)]
@@ -111,8 +115,6 @@ curl -X GET $LANGUAGE_ENDPOINT/language/analyze-text/jobs/<my-job-id>?api-versio
 -H "Ocp-Apim-Subscription-Key: $LANGUAGE_KEY"
 ```
 
-
-
 ### Document extractive summarization example JSON response
 
 ```json
@@ -189,6 +191,8 @@ curl -X GET $LANGUAGE_ENDPOINT/language/analyze-text/jobs/<my-job-id>?api-versio
 }
 ```
 
+# [Conversation summarization](#tab/conversation-summarization)
+
 ## Conversation issue and resolution summarization
 
 The following example will get you started with conversation issue and resolution summarization:
@@ -296,8 +300,6 @@ curl -X GET $LANGUAGE_ENDPOINT/language/analyze-conversations/jobs/<my-job-id>?a
 -H "Ocp-Apim-Subscription-Key: $LANGUAGE_KEY"
 ```
 
-
-
 ### Conversation issue and resolution summarization example JSON response
 
 ```json

articles/ai-services/openai/how-to/gpt-with-vision.md

@@ -143,6 +143,14 @@ Every response includes a `"finish_details"` field. The subfield `"type"` has th
 
 If `finish_details.type` is `stop`, then there is another `"stop"` property that specifies the token that caused the output to end.
 
+## Detail parameter settings in image processing: Low, High, Auto  
+
+The detail parameter in the model offers three choices: `low`, `high`, or `auto`, to adjust the way the model interprets and processes images. The default setting is auto, where the model decides between low or high based on the size of the image input. 
+- `low` setting: the model does not activate the "high res" mode, instead processes a lower resolution 512x512 version, resulting in quicker responses and reduced token consumption for scenarios where fine detail isn't crucial.
+- `high` setting: the model activates "high res" mode. Here, the model initially views the low-resolution image and then generates detailed 512x512 segments from the input image. Each segment uses double the token budget, allowing for a more detailed interpretation of the image.''
+
+For details on how the image parameters impact tokens used and pricing please see - [What is OpenAI? Image Tokens with GPT-4 Turbo with Vision](../overview.md#image-tokens-gpt-4-turbo-with-vision)
+
 ## Use Vision enhancement with images
 
 GPT-4 Turbo with Vision provides exclusive access to Azure AI Services tailored enhancements. When combined with Azure AI Vision, it enhances your chat experience by providing the chat model with more detailed information about visible text in the image and the locations of objects.
@@ -396,11 +404,33 @@ Every response includes a `"finish_details"` field. The subfield `"type"` has th
 
 If `finish_details.type` is `stop`, then there is another `"stop"` property that specifies the token that caused the output to end.
 
-## Detail parameter settings in image processing: Low, High, Auto  
+### Pricing example for Video prompts
+The pricing for GPT-4 Turbo with Vision is dynamic and depends on the specific features and inputs used. For a comprehensive view of Azure OpenAI pricing see [Azure OpenAI Pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/).
 
-The detail parameter in the model offers three choices: `low`, `high`, or `auto`, to adjust the way the model interprets and processes images. The default setting is auto, where the model decides between low or high based on the size of the image input. 
-- `low` setting: the model does not activate the "high res" mode, instead processes a lower resolution 512x512 version, resulting in quicker responses and reduced token consumption for scenarios where fine detail isn't crucial.
-- `high` setting: the model activates "high res" mode. Here, the model initially views the low-resolution image and then generates detailed 512x512 segments from the input image. Each segment uses double the token budget, allowing for a more detailed interpretation of the image.
+The base charges and additional features are outlined below:
+
+Base Pricing for GPT-4 Turbo with Vision is:
+- Input: $0.01 per 1000 tokens
+- Output: $0.03 per 1000 tokens
+  
+Video prompt integration with Video Retrieval Add-on:
+- Ingestion: $0.05 per minute of video
+- Transactions: $0.25 per 1000 queries of the Video Retrieval index
+
+Processing videos will involve the use of extra tokens to identify key frames for analysis. The number of these additional tokens will be roughly equivalent to the sum of the tokens in the text input plus 700 tokens.
+
+#### Calculation
+For a typical use case let's imagine that I have use a 3-minute video with a 100-token prompt input. The section of video has a transcript that's 100-tokens long and when I process the prompt, I generate 100-tokens of output. The pricing for this transaction would be as follows:
+
+| Item                                      | Detail                                                        | Total Cost   |
+|-------------------------------------------|---------------------------------------------------------------|--------------|
+| GPT-4 Turbo with Vision Input Tokens      | 100 text tokens                                               | $0.001       |
+| Additional Cost to identify frames        | 100 input tokens + 700 tokens + 1 Video Retrieval txn         | $0.00825     |
+| Image Inputs and Transcript Input         | 20 images (85 tokens each) + 100 transcript tokens            | $0.018       |
+| Output Tokens                             | 100 tokens (assumed)                                          | $0.003       |
+| **Total Cost**                            |                                                               | **$0.03025** |
+
+Additionally, there's a one-time indexing cost of $0.15 to generate the Video Retrieval index for this 3-minute segment of video. This index can be reused across any number of Video Retrieval and GPT-4 Turbo with Vision calls.
 
 ## Limitations
 

articles/aks/manage-ssh-node-access.md

@@ -19,8 +19,6 @@ This article describes how to configure the SSH key (preview) on your AKS cluste
 
 ## Install the `aks-preview` Azure CLI extension
 
-[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
-
 1. Install the aks-preview extension using the [`az extension add`][az-extension-add] command.
 
     ```azurecli
@@ -67,10 +65,6 @@ Use the [az aks update][az-aks-update] command to update the SSH public key on y
 > [!NOTE]
 > Updating of the SSH key is supported on Azure virtual machine scale sets with AKS clusters.
 
-|SSH parameter |Description |Default value |
-|-----|-----|-----|
-|--ssh-key-vaule |Public key path or key contents to install on node VMs for SSH access. For example, `ssh-rsa AAAAB...snip...UcyupgH azureuser@linuxvm`.|`~.ssh\id_rsa.pub` |
-
 The following are examples of this command:
 
 * To specify a new SSH public key value, include the `--ssh-key-value` argument:
@@ -96,8 +90,15 @@ To help troubleshoot any issues with SSH connectivity to your clusters nodes, yo
 
 <!-- LINKS - internal -->
 [install-azure-cli]: /cli/azure/install-azure-cli
+[az-feature-register]: /cli/azure/feature#az_feature_register
+[az-feature-show]: /cli/azure/feature#az-feature-show
+[az-extension-add]: /cli/azure/extension#az_extension_add
+[az-extension-update]: /cli/azure/extension#az_extension_update
+[az-provider-register]: /cli/azure/provider#az_provider_register
 [az-aks-update]: /cli/azure/aks#az-aks-update
 [az-aks-create]: /cli/azure/aks#az-aks-create
 [view-kubelet-logs]: kubelet-logs.md
 [view-master-logs]: monitor-aks-reference.md#resource-logs
 [node-image-upgrade]: node-image-upgrade.md
+[az-aks-nodepool-upgrade]: /cli/azure/aks/nodepool#az-aks-nodepool-upgrade
+[network-security-group-rules-overview]: concepts-security.md#azure-network-security-groups

articles/api-management/breaking-changes/api-version-retirement-sep-2023.md

@@ -56,7 +56,7 @@ We also recommend setting the **Minimum API version** in your API Management ins
 
 ### Update Minimum API version setting on your API Management instance
 
-We recommend setting the **Minimum API version** for your API Management instance using the Azure portal. This setting limits control plane API calls to your instance with an API version equal to or newer than this value. Currently you can set this to **2019-12-01**.
+We recommend setting the **Minimum API version** for your API Management instance using the Azure portal. This setting limits control plane API calls to your instance with an API version equal to or newer than this value. Currently you can set this to **2021-08-01**.
 
 To set the **Minimum API version** in the portal:
 

articles/api-management/self-hosted-gateway-overview.md

@@ -100,7 +100,7 @@ To operate properly, each self-hosted gateway needs outbound connectivity on por
 
 | Description | Required for v1 | Required for v2 | Notes |
 |:------------|:---------------------|:---------------------|:------|
-| Hostname of the configuration endpoint | `<apim-service-name>.management.azure-api.net` | `<apim-service-name>.configuration.azure-api.net` | Custom hostnames are also supported and can be used instead of the default hostname. |
+| Hostname of the configuration endpoint | `<apim-service-name>.management.azure-api.net` | `<apim-service-name>.configuration.azure-api.net`<sup>1</sup> | Custom hostnames are also supported and can be used instead of the default hostname. |
 | Public IP address of the API Management instance | ✔️ | ✔️ | IP address of primary location is sufficient. |
 | Public IP addresses of Azure Storage [service tag](../virtual-network/service-tags-overview.md) | ✔️ | Optional<sup>2</sup> | IP addresses must correspond to primary location of API Management instance. |
 | Hostname of Azure Blob Storage account | ✔️ | Optional<sup>2</sup> | Account associated with instance (`<blob-storage-account-name>.blob.core.windows.net`) |

articles/azure-arc/data/release-notes.md

@@ -7,7 +7,7 @@ ms.reviewer: mikeray
 services: azure-arc
 ms.service: azure-arc
 ms.subservice: azure-arc-data
-ms.date: 11/14/2023
+ms.date: 12/12/2023
 ms.topic: conceptual
 ms.custom:
   - references_regions
@@ -21,6 +21,12 @@ ms.custom:
 
 This article highlights capabilities, features, and enhancements recently released or improved for Azure Arc-enabled data services.
 
+## December 12, 2023
+
+**Image tag**: `v1.26.0_2023-12-12`
+
+For complete release version information, review [Version log](version-log.md#december-12-2023).
+
 ## November 14, 2023
 
 **Image tag**: `v1.25.0_2023-11-14`

articles/azure-arc/kubernetes/agent-upgrade.md

@@ -58,7 +58,7 @@ Azure Arc-enabled Kubernetes follows the standard [semantic versioning scheme](h
 
 While the schedule may vary, a new minor version of Azure Arc-enabled Kubernetes agents is [released approximately once per month](release-notes.md).
 
-The following command manually upgrades the agent to version 1.8.14:
+The following command manually upgrades the agents to version 1.8.14:
 
 ```azurecli
 az connectedk8s upgrade -g AzureArcTest1 -n AzureArcTest --agent-version 1.8.14

articles/azure-arc/kubernetes/release-notes.md

@@ -1,57 +1,39 @@
 ---
 title: "What's new with Azure Arc-enabled Kubernetes"
-ms.date: 10/19/2023
+ms.date: 12/15/2023
 ms.topic: overview
 description: "Learn about the latest releases of Arc-enabled Kubernetes."
 ---
 
 # What's new with Azure Arc-enabled Kubernetes
 
-Azure Arc-enabled Kubernetes is updated on an ongoing basis. To stay up to date with the most recent developments, this article provides you with information about the latest releases of the Azure CLI `connectedk8s` extension, the [Azure Arc-enabled Kubernetes agents](conceptual-agent-overview.md), and other changes.
+Azure Arc-enabled Kubernetes is updated on an ongoing basis. To stay up to date with the most recent developments, this article provides you with information about the latest releases of the [Azure Arc-enabled Kubernetes agents](conceptual-agent-overview.md).
 
-> [!NOTE]
-> When any of the Arc-enabled Kubernetes agents are updated, all of the agents in the `azure-arc` namespace are incremented with a new version number, so that the version numbers are consistent across agents. If you have enabled automatic updates, all of the agents will be upgraded together to the newest version (whether or not there are functionality changes in a given agent).
->
-> We generally recommend using the most recent versions of the agents. The [version support policy](agent-upgrade.md#version-support-policy) covers the most recent version and the two previous versions (N-2).
+When any of the Arc-enabled Kubernetes agents are updated, all of the agents in the `azure-arc` namespace are incremented with a new version number, so that the version numbers are consistent across agents. When a new version is released, all of the agents are upgraded together to the newest version (whether or not there are functionality changes in a given agent), unless you have [disabled automatic upgrades](agent-upgrade.md) for the cluster.
 
-## October 2023
+We generally recommend using the most recent versions of the agents. The [version support policy](agent-upgrade.md#version-support-policy) covers the most recent version and the two previous versions (N-2).
 
-### Arc agents - Version 1.13.4
+## Version 1.13.4 (October 2023)
 
 - Various enhancements and bug fixes
 
-## September 2023
-
-### Arc agents - Version 1.13.1
+## Version 1.13.1 (September 2023)
 
 - Various enhancements and bug fixes
 
-## July 2023
-
-### Arc agents - Version 1.12.5
+## Version 1.12.5 (July 2023)
 
 - Alpine base image powering our Arc agent containers has been updated from 3.7.12 to 3.18.0
 
-## May 2023
-
-### Arc agents - Version 1.11.7
+## Version 1.11.7 (May 2023)
 
 - Updates to enable users that belong to more than 200 groups in cluster connect scenarios
 
-### Azure CLI `connectedk8s` extension - Version 1.3.17
-
-- Onboarding enhancements to track ARM resource provisioning
-- Enhancements for better troubleshooting and logging to improve onboarding experience
-
-## April 2023
-
-### Arc agents - Version 1.11.3
+## Version 1.11.3 (April 2023)
 
 - Updates to base image of Arc-enabled Kubernetes agents to address security CVE
 
-### Azure CLI `connectedk8s` extension - Version 1.3.16
-
-- Force delete added to connect command to clear stale resources, if any, during onboarding
-- Diagnoser enhancements to capture and store agent metadata
-- Heuristics detection in connect command
+## Next steps
 
+- Learn how to [enable or disable automatic agent upgrades](agent-upgrade.md).
+- Learn how to [connect a Kubernetes cluster to Azure Arc](quickstart-connect-cluster.md).

articles/azure-cache-for-redis/cache-best-practices-server-load.md

@@ -44,6 +44,8 @@ The **CPU** metric indicates the CPU usage for the node that hosts the cache. Th
 
 The **Server Load** metric represents the load on the Redis Server alone. We recommend monitoring the **Server Load** metric instead of **CPU**.
 
+When monitoring server load, we also recommend that you examine the max spikes of Server Load rather than average because even brief spikes can trigger failovers and command timeouts.
+
 ## Plan for server maintenance
 
 Ensure you have enough server capacity to handle your peak load while your cache servers are undergoing maintenance. Test your system by rebooting nodes while under peak load. For more information on how to simulate deployment of a patch, see [reboot](cache-administration.md#reboot).