Merge pull request #271430 from MicrosoftDocs/main

4/8 11:00 AM IST Publish

Author: Saisang

articles/ai-services/openai/concepts/use-your-data.md

@@ -8,7 +8,7 @@ ms.service: azure-ai-openai
 ms.topic: quickstart
 author: aahill
 ms.author: aahi
-ms.date: 02/26/2024
+ms.date: 04/08/2024
 recommendations: false
 ms.custom: references_regions 
 ---
@@ -58,13 +58,21 @@ There's an [upload limit](../quotas-limits.md), and there are some caveats about
 
 ## Supported data sources
 
-You need to connect to a data source to upload your data. When you want to use your data to chat with an Azure OpenAI model, your data is chunked in a search index so that relevant data can be found based on user queries. For some data sources such as uploading files from your local machine (preview) or data contained in a blob storage account (preview), Azure AI Search is used. 
+You need to connect to a data source to upload your data. When you want to use your data to chat with an Azure OpenAI model, your data is chunked in a search index so that relevant data can be found based on user queries.
+
+The [Integrated Vector Database in Azure Cosmos DB for MongoDB](/azure/cosmos-db/mongodb/vcore/vector-search) natively supports integration with Azure OpenAI On Your Data.
+
+For some data sources such as uploading files from your local machine (preview) or data contained in a blob storage account (preview), Azure AI Search is used.
+
+>[!TIP]
+>If you use [Azure Cosmos DB](/azure/cosmos-db/introduction) (except for its vCore-based API for MongoDB), you may take advantage of the Azure AI Advantage offer, which provides the equivalent of up to $6,000 in Azure Cosmos DB throughput credits.
 
 When you choose the following data sources, your data is ingested into an Azure AI Search index.
 
 |Data source  | Description  |
 |---------|---------|
 | [Azure AI Search](/azure/search/search-what-is-azure-search)  | Use an existing Azure AI Search index with Azure OpenAI On Your Data.      |
+| [Azure Cosmos DB](/azure/cosmos-db/introduction)  | Azure Cosmos DB's API for Postgres and vCore-based API for MongoDB have natively integrated vector indexing and do not require Azure AI Search; however, its other APIs do require Azure AI Search for vector indexing. Azure Cosmos DB will offer a natively integrated vector database by mid-2024.     |
 |Upload files (preview)      | Upload files from your local machine to be stored in an Azure Blob Storage database, and ingested into Azure AI Search.         |
 |URL/Web address (preview)        | Web content from the URLs is stored in Azure Blob Storage.         |
 |Azure Blob Storage (preview) | Upload files from Azure Blob Storage to be ingested into an Azure AI Search index.         |
@@ -141,7 +149,7 @@ If you want to implement additional value-based criteria for query execution, yo
 
 ### Limitations
 * Only Azure Cosmos DB for MongoDB vCore is supported.
-* The search type is limited to [Azure Cosmos DB for MongoDB vCore vector search](/azure/cosmos-db/mongodb/vcore/vector-search) with an Azure OpenAI embedding model.
+* The search type is limited to [Integrated Vector Database in Azure Cosmos DB for MongoDB vCore](/azure/cosmos-db/mongodb/vcore/vector-search) with an Azure OpenAI embedding model.
 * This implementation works best on unstructured and spatial data.
 
 ### Data preparation

articles/aks/azure-csi-disk-storage-provision.md

@@ -49,8 +49,8 @@ The following table includes parameters you can use to define a custom storage c
 |fsType | File System Type | `ext4`, `ext3`, `ext2`, `xfs`, `btrfs` for Linux, `ntfs` for Windows | No | `ext4` for Linux, `ntfs` for Windows|
 |cachingMode | [Azure Data Disk Host Cache Setting][disk-host-cache-setting] | `None`, `ReadOnly`, `ReadWrite` | No | `ReadOnly`|
 |resourceGroup | Specify the resource group for the Azure Disks | Existing resource group name | No | If empty, driver uses the same resource group name as current AKS cluster|
-|DiskIOPSReadWrite | [UltraSSD disk][ultra-ssd-disks] IOPS Capability (minimum: 2 IOPS/GiB) | 100~160000 | No | `500`|
-|DiskMBpsReadWrite | [UltraSSD disk][ultra-ssd-disks] Throughput Capability(minimum: 0.032/GiB) | 1~2000 | No | `100`|
+|DiskIOPSReadWrite | [UltraSSD disk][ultra-ssd-disks] or [Premium SSD v2][premiumv2_lrs_disks] IOPS Capability (minimum: 2 IOPS/GiB) | 100~160000 | No | `500`|
+|DiskMBpsReadWrite | [UltraSSD disk][ultra-ssd-disks] or [Premium SSD v2][premiumv2_lrs_disks] Throughput Capability(minimum: 0.032/GiB) | 1~2000 | No | `100`|
 |LogicalSectorSize | Logical sector size in bytes for ultra disk. Supported values are 512 ad 4096. 4096 is the default. | `512`, `4096` | No | `4096`|
 |tags | Azure Disk [tags][azure-tags] | Tag format: `key1=val1,key2=val2` | No | ""|
 |diskEncryptionSetID | ResourceId of the disk encryption set to use for [enabling encryption at rest][disk-encryption] | format: `/subscriptions/{subs-id}/resourceGroups/{rg-name}/providers/Microsoft.Compute/diskEncryptionSets/{diskEncryptionSet-name}` | No | ""|
@@ -410,6 +410,7 @@ kubectl delete -f azure-pvc.yaml
 [disk-host-cache-setting]: ../virtual-machines/windows/premium-storage-performance.md#disk-caching
 [use-ultra-disks]: use-ultra-disks.md
 [ultra-ssd-disks]: ../virtual-machines/linux/disks-ultra-ssd.md
+[premiumv2_lrs_disks]: ../virtual-machines/disks-types.md#premium-ssd-v2
 [azure-tags]: ../azure-resource-manager/management/tag-resources.md
 [disk-encryption]: ../virtual-machines/windows/disk-encryption.md
 [azure-disk-write-accelerator]: ../virtual-machines/windows/how-to-enable-write-accelerator.md

articles/machine-learning/prompt-flow/how-to-deploy-to-code.md

@@ -153,11 +153,11 @@ identity:
     - resource_id: user_identity_ARM_id_place_holder
 ```
 
-Besides, you also need to specify the `Clicn ID` of the user-assigned identity under `environment_variables` the `deployment.yaml` as following. You can find the `Clicn ID` in the `Overview` of the managed identity in Azure portal.
+Besides, you also need to specify the `Client ID` of the user-assigned identity under `environment_variables` the `deployment.yaml` as following. You can find the `Client ID` in the `Overview` of the managed identity in Azure portal.
 
 ```yaml
 environment_variables:
-  AZURE_CLIENT_ID: <cliend_id_of_your_user_assigned_identity>
+  AZURE_CLIENT_ID: <client_id_of_your_user_assigned_identity>
 ```
 
 > [!IMPORTANT]

articles/mysql/flexible-server/release-notes/april-2024.md

@@ -19,8 +19,9 @@ All existing engine version server upgrades to 8.0.36 engine version.
 To check your engine version, run `SELECT VERSION();` command at the MySQL prompt
 
 ## Features
-- Support for Azure Defender for Azure DB for MySQL Flexible Server
-
+### [Microsoft Defender for Cloud](https://learn.microsoft.com/azure/defender-for-cloud/defender-for-databases-introduction) 
+- Introducing Defender for Cloud support to simplify security management with threat protection from anomalous database activities in Azure Database for MySQL flexible server instances.
+  
 ## Improvement
 - Expose old_alter_table for 8.0.x.
 

articles/mysql/flexible-server/whats-new.md

@@ -24,6 +24,13 @@ This article summarizes new releases and features in Azure Database for MySQL fl
 > [!NOTE]  
 > This article references the term slave, which Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
 
+## April 2024 
+- **Microsoft Defender for Cloud supports Azure Database for MySQL flexible server (General Availability)**
+
+  We’re excited to announce the general availability of the Microsoft Defender for Cloud feature for Azure Database for MySQL flexible server in all service tiers. The Microsoft Defender Advanced Threat Protection feature simplifies security management of Azure Database for MySQL flexible server instances. It monitors the server for anomalous or suspicious databases activities to detect potential threats and provides security alerts for you to investigate and take appropriate action, allowing you to actively improve the security posture of your database without being a security expert. [Learn more](https://learn.microsoft.com/azure/defender-for-cloud/defender-for-databases-introduction)
+- **Known Issues**
+
+  While attempting to enable the Microsoft Defender for Cloud feature for an Azure Database for MySQL flexible server, you may encounter the following error: ‘The server <server_name> is not compatible with Advanced Threat Protection. Please contact Microsoft support to update the server to a supported version.’ This issue can occur on MySQL Flexible Servers that are still awaiting an internal update. It will be automatically resolved in the next internal update of your server. Alternatively, you can open a support ticket to expedite an immediate update.”
 
 ## March 2024
 

articles/storage/blobs/secure-file-transfer-protocol-support.md

@@ -177,6 +177,7 @@ The following clients have compatible algorithm support with SFTP for Azure Blob
 - JSCH 0.1.54+
 - curl 7.85.0+
 - AIX<sup>1</sup>
+- MobaXterm v21.3
 
 <sup>1</sup>    Must set `AllowPKCS12KeystoreAutoOpen` option to `no`.
 

articles/storage/files/geo-redundant-storage-for-large-file-shares.md

@@ -4,7 +4,7 @@ description: Azure Files geo-redundancy for large file shares significantly impr
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: conceptual
-ms.date: 04/05/2024
+ms.date: 04/07/2024
 ms.author: kendownie
 ms.custom: references_regions
 ---
@@ -56,8 +56,8 @@ Azure Files geo-redundancy for large file shares is generally available in the m
 | Australia Southeast | GA |
 | Brazil South | Preview |
 | Brazil Southeast | Preview |
-| Canada Central | Preview |
-| Canada East | Preview |
+| Canada Central | GA |
+| Canada East | GA |
 | Central India | Preview |
 | Central US | GA |
 | China East | GA |