Merge pull request #271867 from MicrosoftDocs/main

4/11 11:00 AM IST Publish

Author: Saisang

articles/ai-services/openai/how-to/chatgpt.md

@@ -1,7 +1,7 @@
 ---
-title: How to work with the GPT-35-Turbo and GPT-4 models 
+title: Work with the GPT-35-Turbo and GPT-4 models 
 titleSuffix: Azure OpenAI Service
-description: Learn about the options for how to use the GPT-35-Turbo and GPT-4 models 
+description: Learn about the options for how to use the GPT-35-Turbo and GPT-4 models.
 author: mrbullwinkle #dereklegenzoff
 ms.author: mbullwin #delegenz
 ms.service: azure-ai-openai
@@ -12,10 +12,10 @@ manager: nitinme
 keywords: ChatGPT
 ---
 
-# Learn how to work with the GPT-3.5-Turbo and GPT-4 models
+# Work with the GPT-3.5-Turbo and GPT-4 models
 
-The GPT-3.5-Turbo and GPT-4 models are language models that are optimized for conversational interfaces. The models behave differently than the older GPT-3 models. Previous models were text-in and text-out, meaning they accepted a prompt string and returned a completion to append to the prompt. However, the GPT-3.5-Turbo and GPT-4 models are conversation-in and message-out. The models expect input formatted in a specific chat-like transcript format, and return a completion that represents a model-written message in the chat. While this format was designed specifically for multi-turn conversations, you'll find it can also work well for non-chat scenarios too.
+The GPT-3.5-Turbo and GPT-4 models are language models that are optimized for conversational interfaces. The models behave differently than the older GPT-3 models. Previous models were text-in and text-out, which means they accepted a prompt string and returned a completion to append to the prompt. However, the GPT-3.5-Turbo and GPT-4 models are conversation-in and message-out. The models expect input formatted in a specific chat-like transcript format. They return a completion that represents a model-written message in the chat. This format was designed specifically for multi-turn conversations, but it can also work well for nonchat scenarios.
 
-This article walks you through getting started with the GPT-3.5-Turbo and GPT-4 models. It's important to use the techniques described here to get the best results. If you try to interact with the models the same way you did with the older model series, the models will often be verbose and provide less useful responses.
+This article walks you through getting started with the GPT-3.5-Turbo and GPT-4 models. To get the best results, use the techniques described here. Don't try to interact with the models the same way you did with the older model series because the models are often verbose and provide less useful responses.
 
 [!INCLUDE [Chat Completions](../includes/chat-completion.md)]

articles/ai-services/openai/includes/chat-completion.md

@@ -1,12 +1,12 @@
 ---
 title: Using Redis modules with Azure Cache for Redis
-description: You can use Redis modules with your Azure Cache for Redis instances.
+description: You can use Redis modules with your Azure Cache for Redis instances to extend your caches on the Enterprise tiers.
 author: flang-msft
 
 ms.author: franlanglois
 ms.service: cache
 ms.topic: conceptual
-ms.date: 03/02/2023
+ms.date: 04/10/2024
 ms.custom: template-concept
 
 ---
@@ -29,13 +29,12 @@ Some popular modules are available for use in the Enterprise tier of Azure Cache
 |RedisTimeSeries |   No    |    Yes   |   No    |
 |RedisJSON  |     No    |  Yes    |   Yes      |
 
-
 > [!NOTE]
 > Currently, you can't manually load any modules into Azure Cache for Redis. Manually updating modules version is also not possible.
 
-
 ## Using modules with active geo-replication
-Only the `RediSearch` and `RedisJSON` modules can be used concurrently with [active geo-replication](cache-how-to-active-geo-replication.md). 
+
+Only the `RediSearch` and `RedisJSON` modules can be used concurrently with [active geo-replication](cache-how-to-active-geo-replication.md).
 
 Using these modules, you can implement searches across groups of caches that are synchronized in an active-active configuration. Also, you can search JSON structures in your active-active configuration.
 
@@ -78,11 +77,11 @@ Features include:
 - Geo-filtering
 - Boolean queries
 
-Additionally, **RediSearch** can function as a secondary index, expanding your cache beyond a key-value structure and offering more sophisticated queries. 
+Additionally, **RediSearch** can function as a secondary index, expanding your cache beyond a key-value structure and offering more sophisticated queries.
 
-**RediSearch** also includes functionality to perform [vector similarity queries](https://redis.io/docs/stack/search/reference/vectors/) such as K-nearest neighbor (KNN) search. This feature allows Azure Cache for Redis to be used as a vector database, which is useful in AI use-cases like [semantic answer engines or any other application that requires the comparison of embeddings vectors](https://redis.com/blog/rediscover-redis-for-vector-similarity-search/) generated by machine learning models. 
+**RediSearch** also includes functionality to perform [vector similarity queries](https://redis.io/solutions/vector-search/) such as K-nearest neighbor (KNN) search. This feature allows Azure Cache for Redis to be used as a vector database, which is useful in AI use-cases like [semantic answer engines or any other application that requires the comparison of embeddings vectors](https://redis.com/blog/rediscover-redis-for-vector-similarity-search/) generated by machine learning models.
 
-You can use **RediSearch** is used in a wide variety of additional use-cases, including real-time inventory, enterprise search, and in indexing external databases. [For more information, see the RediSearch documentation page](https://redis.io/docs/stack/search/).
+You can use **RediSearch** is used in a wide variety of use-cases, including real-time inventory, enterprise search, and in indexing external databases. [For more information, see the RediSearch documentation page](https://redis.io/search/).
 
 >[!IMPORTANT]
 > The RediSearch module requires use of the `Enterprise` clustering policy and the `NoEviction` eviction policy. For more information, see [Clustering Policy](quickstart-create-redis-enterprise.md#clustering-policy) and [Memory Policies](cache-configure.md#memory-policies)
@@ -101,7 +100,7 @@ RedisBloom adds four probabilistic data structures to a Redis server: **bloom fi
 **Bloom and Cuckoo** filters are similar to each other, but each has a unique set of advantages and disadvantages that are beyond the scope of
 this documentation.
 
-For more information, see [RedisBloom](https://redis.io/docs/stack/bloom/).
+For more information, see [RedisBloom](https://redis.io/bloom/).
 
 ### RedisTimeSeries
 
@@ -115,7 +114,7 @@ The **RedisTimeSeries** module adds high-throughput time series capabilities to
 
 This module is useful for many applications that involve monitoring streaming data, such as IoT telemetry, application monitoring, and anomaly detection.
 
-For more information, see [RedisTimeSeries](https://redis.io/docs/stack/timeseries/).
+For more information, see [RedisTimeSeries](https://redis.io/timeseries/).
 
 ### RedisJSON
 
@@ -131,9 +130,12 @@ The **RedisJSON** module is also designed for use with the **RediSearch** module
 
 Some common use-cases for **RedisJSON** include applications such as searching product catalogs, managing user profiles, and caching JSON-structured data.
 
-For more information, see [RedisJSON](https://redis.io/docs/stack/json/).
+For more information, see [RedisJSON](https://redis.io/json/).
+
+> [!NOTE]
+> The `FT.CONFIG` command is not supported for updating module configuration parameters. However, this can be achieved by passing in arguments configuring the modules when using management APIs. For instance, you can see samples of configuring the `ERROR_RATE` and `INITIAL_SIZE` properties of the RedisBloom module using the `args` parameter with the [REST API](/rest/api/redis/redisenterprisecache/databases/create), [Azure CLI](/cli/azure/redisenterprise), or [PowerShell](/powershell/module/az.redisenterprisecache/new-azredisenterprisecache).
 
-## Next steps
+## Related content
 
 - [Quickstart: Create a Redis Enterprise cache](quickstart-create-redis-enterprise.md)
 - [Client libraries](cache-best-practices-client-libraries.md)

articles/azure-cache-for-redis/cache-redis-modules.md

@@ -275,7 +275,7 @@ To learn more about how to send device-to-cloud telemetry, and the other way aro
 [Get Search Address Reverse]: /rest/api/maps/search/getsearchaddressreverse?view=rest-maps-1.0&preserve-view=true
 [How to create data registry]: how-to-create-data-registries.md
 [IoT Hub message routing]: ../iot-hub/iot-hub-devguide-routing-query-syntax.md
-[IoT Plug and Play]: ../iot-develop/index.yml
+[IoT Plug and Play]: ../iot/overview-iot-plug-and-play.md
 [geofence JSON data file]: https://raw.githubusercontent.com/Azure-Samples/iothub-to-azure-maps-geofencing/master/src/Data/geofence.json?token=AKD25BYJYKDJBJ55PT62N4C5LRNN4
 [Plug and Play schema for geospatial data]: https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v1-preview/schemas/geospatial.md
 [Postman]: https://www.postman.com/

articles/azure-maps/tutorial-iot-hub-maps.md

@@ -7,18 +7,21 @@ ms.custom: references_regions
 ms.reviewer: aul
 ---
 
-# Region mappings supported by Container insights
+# Regions supported by Container insights
 
-When enabling Container insights, only certain regions are supported for linking a Log Analytics workspace and an AKS cluster, and collecting custom metrics submitted to Azure Monitor.
+## Kubernetes cluster region
+The following table specifies the regions that are supported for Container insights on different platforms.
 
-> [!NOTE]
-> Container insights is supported in all regions supported by AKS as specified in [Azure Products by Region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=kubernetes-service), but AKS must be in the same region as the AKS workspace for most regions. This article lists the mapping for those regions where AKS can be in a different workspace from the Log Analytics workspace. 
+| Platform | Regions |
+|:---|:---|
+| AKS | All regions supported by AKS as specified in [Azure Products by Region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=kubernetes-service). | 
+| Arc-enabled Kubernetes | All public regions supported by Arc-enabled Kubernetes as specified in [Azure Products by Region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-arc). |
 
-## Log Analytics workspace supported mappings
-Supported AKS regions are listed in [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service). The Log Analytics workspace must be in the same region except for the regions listed in the following table. Watch [AKS release notes](https://github.com/Azure/AKS/releases) for updates.
+## Log Analytics workspace region
+The Log Analytics workspace supporting Container insights must be in the same region except for the regions listed in the following table. 
 
 
-|**AKS Cluster region** | **Log Analytics Workspace region** |
+|**Cluster region** | **Log Analytics Workspace region** |
 |-----------------------|------------------------------------|
 |**Africa** | |
 |SouthAfricaNorth |WestEurope |
@@ -40,9 +43,9 @@ Supported AKS regions are listed in [Products available by region](https://azure
 |**Korea** | |
 |KoreaSouth |KoreaCentral |
 |**US** | |
-|WestCentralUS<sup>1</sup>|EastUS |
+|WestCentralUS|EastUS |
 
 
 ## Next steps
 
-To begin monitoring your AKS cluster, review [How to enable the Container insights](container-insights-onboard.md) to understand the requirements and available methods to enable monitoring.  
+To begin monitoring your cluster, see [Enable monitoring for Kubernetes clusters](kubernetes-monitoring-enable.md) to understand the requirements and available methods to enable monitoring.  

articles/azure-monitor/containers/container-insights-region-mapping.md

@@ -142,8 +142,14 @@ The configuration change can take a few minutes to complete. Because Helm tracks
 
 Use the following `az aks update` Azure CLI command with the `--disable-azure-monitor-metrics` parameter to remove the metrics add-on from your AKS cluster or `az k8s-extension delete` Azure CLI command with the `--name azuremonitor-metrics` parameter to remove the metrics add-on from Arc-enabled cluster, and stop sending Prometheus metrics to Azure Monitor managed service for Prometheus. It doesn't remove the data already collected and stored in the Azure Monitor workspace for your cluster.
 
+### AKS Cluster:
+
 ```azurecli
 az aks update --disable-azure-monitor-metrics -n <cluster-name> -g <cluster-resource-group>
+```
+
+### Azure Arc-enabled Cluster:
+```
 az k8s-extension delete --name azuremonitor-metrics --cluster-name <cluster-name> --resource-group <cluster-resource-group> --cluster-type connectedClusters 
 ```