Merge pull request #269206 from MicrosoftDocs/main

huypub · web-flow · commit 165291c1155f · 2024-03-15T11:56:25.000-07:00
3/15 OOB publish
diff --git a/articles/ai-services/openai/references/azure-machine-learning.md b/articles/ai-services/openai/references/azure-machine-learning.md
@@ -5,14 +5,14 @@ description: Learn how to use Azure OpenAI on your Azure Machine Learning index
 manager: nitinme
 ms.service: azure-ai-openai
 ms.topic: conceptual
-ms.date: 02/14/2024
+ms.date: 03/14/2024
 author: mrbullwinkle
 ms.author: mbullwin
 recommendations: false
 ms.custom: devx-track-python
 ---
 
-# Data source - Azure Machine Learning index
+# Data source - Azure Machine Learning index (preview)
 
 The configurable options of Azure Machine Learning index when using Azure OpenAI On Your Data. This data source is supported in API version `2024-02-15-preview`.
 
diff --git a/articles/ai-services/openai/references/elasticsearch.md b/articles/ai-services/openai/references/elasticsearch.md
@@ -5,14 +5,14 @@ description: Learn how to use Azure OpenAI on your Elasticsearch data Python & R
 manager: nitinme
 ms.service: azure-ai-openai
 ms.topic: conceptual
-ms.date: 02/14/2024
+ms.date: 03/14/2024
 author: mrbullwinkle
 ms.author: mbullwin
 recommendations: false
 ms.custom: devx-track-python
 ---
 
-# Data source - Elasticsearch
+# Data source - Elasticsearch (preview)
 
 The configurable options for Elasticsearch when using Azure OpenAI On Your Data. This data source is supported in API version `2024-02-15-preview`.
 
diff --git a/articles/ai-services/openai/references/on-your-data.md b/articles/ai-services/openai/references/on-your-data.md
@@ -32,7 +32,7 @@ POST {endpoint}/openai/deployments/{deployment-id}/chat/completions?api-version=
 * `2024-02-01` [Swagger spec](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/cognitiveservices/data-plane/AzureOpenAI/inference/stable/2024-02-01).
 
 > [!NOTE]
-> [Azure Machine learning indexes](./azure-machine-learning.md), [Pinecone](./pinecone.md), and [Elasticsearch](./elasticsearch.md) are only supported in the `2024-02-15-preview` API version.
+> [Azure Machine learning indexes](./azure-machine-learning.md), [Pinecone](./pinecone.md), and [Elasticsearch](./elasticsearch.md) are only supported in the `2024-02-15-preview` API version as a preview.
 
 ## URI parameters
 
@@ -84,9 +84,9 @@ This list shows the supported data sources.
 
 * [Azure AI Search](./azure-search.md)
 * [Azure Cosmos DB for MongoDB vCore](./cosmos-db.md)
-* [Azure Machine Learning index](./azure-machine-learning.md)
-* [Elasticsearch](./elasticsearch.md)
-* [Pinecone](./pinecone.md)
+* [Azure Machine Learning index (preview)](./azure-machine-learning.md)
+* [Elasticsearch (preview)](./elasticsearch.md)
+* [Pinecone (preview)](./pinecone.md)
 
 ## Examples
 
diff --git a/articles/ai-services/openai/references/pinecone.md b/articles/ai-services/openai/references/pinecone.md
@@ -5,14 +5,14 @@ description: Learn how to use Azure OpenAI on your Pinecone data Python & REST A
 manager: nitinme
 ms.service: azure-ai-openai
 ms.topic: conceptual
-ms.date: 02/14/2024
+ms.date: 03/14/2024
 author: mrbullwinkle
 ms.author: mbullwin
 recommendations: false
 ms.custom: devx-track-python
 ---
 
-# Data source - Pinecone
+# Data source - Pinecone (preview)
 
 The configurable options of Pinecone when using Azure OpenAI On Your Data. This data source is supported in API version `2024-02-15-preview`.
 
diff --git a/articles/ai-services/openai/toc.yml b/articles/ai-services/openai/toc.yml
@@ -213,11 +213,11 @@ items:
           href: ./references/azure-search.md
         - name: Data source - Azure Cosmos DB for MongoDB vCore
           href: ./references/cosmos-db.md
-        - name: Data source - Azure Machine Learning index
+        - name: Data source - Azure Machine Learning index (preview)
           href: ./references/azure-machine-learning.md
-        - name: Data source - Elasticsearch
+        - name: Data source - Elasticsearch (preview)
           href: ./references/elasticsearch.md
-        - name: Data source - Pinecone
+        - name: Data source - Pinecone (preview)
           href: ./references/pinecone.md
         - name: Ingestion API (preview)
           href: /rest/api/azureopenai/ingestion-jobs
diff --git a/articles/aks/operator-best-practices-storage.md b/articles/aks/operator-best-practices-storage.md
@@ -3,6 +3,7 @@ title: Best practices for storage and backup
 titleSuffix: Azure Kubernetes Service
 description: Learn the cluster operator best practices for storage, data encryption, and backups in Azure Kubernetes Service (AKS)
 ms.topic: conceptual
+ms.subservice: aks-storage
 ms.date: 04/28/2023
 
 ---
diff --git a/articles/app-service/configure-ssl-certificate.md b/articles/app-service/configure-ssl-certificate.md
@@ -53,7 +53,9 @@ To secure a custom domain in a TLS binding, the certificate has more requirement
 > **Elliptic Curve Cryptography (ECC) certificates** work with App Service but aren't covered by this article. For the exact steps to create ECC certificates, work with your certificate authority.
 
 > [!NOTE]
-> After you upload a private certificate to an app, the certificate is stored in a deployment unit that's bound to the App Service plan's resource group, region, and operating system combination, internally called a *webspace*. That way, the certificate is accessible to other apps in the same resource group and region combination. Private certificates uploaded or imported to App Service are shared with App Services in the same deployment unit. 
+> After you add a private certificate to an app, the certificate is stored in a deployment unit that's bound to the App Service plan's resource group, region, and operating system combination, internally called a *webspace*. That way, the certificate is accessible to other apps in the same resource group, region, and OS combination. Private certificates uploaded or imported to App Service are shared with App Services in the same deployment unit.
+>
+> You can add up to 1000 private certificates per webspace.
 
 ## Create a free managed certificate
 
diff --git a/articles/cdn/cdn-purge-endpoint.md b/articles/cdn/cdn-purge-endpoint.md
@@ -7,7 +7,7 @@ manager: kumud
 ms.assetid: 0b50230b-fe82-4740-90aa-95d4dde8bd4f
 ms.service: azure-cdn
 ms.topic: how-to
-ms.date: 02/21/2023
+ms.date: 03/15/2024
 ms.author: duau
 
 ---
@@ -47,13 +47,7 @@ This guide walks you through purging assets from all edge nodes of an endpoint.
 	3. **Root domain purge**: Purge the root of the endpoint with "/" in the path.
    
    > [!TIP]
-   > 1. Paths must be specified for purge and must be a relative URL that fit the following [regular expression](/dotnet/standard/base-types/regular-expression-language-quick-reference).
-   >
-   >    1. Single URL purge `@"^\/(?>(?:[a-zA-Z0-9-_.%=\(\)\u0020]+\/?)*)$";`  
-   >    1. Query string `@"^(?:\?[-\@_a-zA-Z0-9\/%:;=!,.\+'&\(\)\u0020]*)?$";`  
-   >    1. Wildcard purge `@"^\/(?:[a-zA-Z0-9-_.%=\(\)\u0020]+\/)*\*$";`. 
-   > 
-   >    More **Path** textboxes will appear after you enter text to allow you to build a list of multiple assets.  You can delete assets from the list by clicking the ellipsis (...) button.
+   > 1. Paths must be specified for purge and must be a relative URL that fit the following [RFC 3986 - Uniform Resource Identifier (URI: Generic Syntax](https://datatracker.ietf.org/doc/html/rfc3986#section-3.3).
    > 
    > 1. In Azure CDN from Microsoft, query strings in the purge URL path are not considered. If the path to purge is provided as `/TestCDN?myname=max`, only `/TestCDN` is considered. The query string `myname=max` is omitted. Both `TestCDN?myname=max` and `TestCDN?myname=clark` will be purged.
 
diff --git a/articles/frontdoor/end-to-end-tls.md b/articles/frontdoor/end-to-end-tls.md
@@ -5,7 +5,7 @@ services: frontdoor
 author: duongau
 ms.service: frontdoor
 ms.topic: conceptual
-ms.date: 02/15/2024
+ms.date: 03/15/2024
 ms.author: duau
 zone_pivot_groups: front-door-tiers
 ---
@@ -36,6 +36,10 @@ Although Azure Front Door supports TLS 1.2, which introduced client/mutual authe
 
 You can configure the minimum TLS version in Azure Front Door in the custom domain HTTPS settings using the Azure portal or the [Azure REST API](/rest/api/frontdoorservice/frontdoor/frontdoors/createorupdate#minimumtlsversion). Currently, you can choose between 1.0 and 1.2. As such, specifying TLS 1.2 as the minimum version controls the minimum acceptable TLS version Azure Front Door will accept from a client. For minimum TLS version 1.2 the negotiation will attempt to establish TLS 1.3 and then TLS 1.2, while for minimum TLS version 1.0 all four versions will be attempted. When Azure Front Door initiates TLS traffic to the origin, it will attempt to negotiate the best TLS version that the origin can reliably and consistently accept. Supported TLS versions for origin connections are TLS 1.0, TLS 1.1, TLS 1.2 and TLS 1.3.
 
+> [!NOTE]
+> * Clients with TLS 1.3 enabled are required to support one of the Microsoft SDL compliant EC Curves, including Secp384r1, Secp256r1, and Secp521, in order to successfully make requests with Azure Front Door using TLS 1.3.
+> * It is recommended that clients use one of these curves as their preferred curve during requests to avoid increased TLS handshake latency, which may result from multiple round trips to negotiate the supported EC curve.
+
 ## Supported certificates
 
 When you create your TLS/SSL certificate, you must create a complete certificate chain with an allowed Certificate Authority (CA) that is part of the [Microsoft Trusted CA List](https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT). If you use a non-allowed CA, your request will be rejected.
diff --git a/articles/operator-insights/concept-mcc-data-product.md b/articles/operator-insights/concept-mcc-data-product.md
@@ -69,6 +69,7 @@ To use the Quality of Experience - Affirmed MCC Data Product:
     1. [Install the Azure Operator Insights ingestion agent and configure it to upload data](set-up-ingestion-agent.md).
 
     Alternatively, you can provide your own ingestion agent.
+1. Configure your Affirmed MCCs to send EDRs to the ingestion agent. See [Configuration for Affirmed MCCs](#configuration-for-affirmed-mccs).
 
 ## Requirements for the Azure Operator Insights ingestion agent
 
@@ -118,19 +119,18 @@ The ingestion agent must use MCC EDRs as a data source.
 
 For more information about all the configuration options, see [Configuration reference for Azure Operator Insights ingestion agent](ingestion-agent-configuration-reference.md).
 
-### Configure Affirmed MCCs
+## Configuration for Affirmed MCCs
 
-Once the agents are installed and running, configure the MCCs to send EDRs to them.
+When you have installed and configured your ingestion agents, configure the MCCs to send EDRs to them.
 
-1. Follow the steps under "Generating SESSION, BEARER, FLOW, and HTTP Transaction EDRs" in the [Affirmed Networks Active Intelligent vProbe System Administration Guide](https://manuals.metaswitch.com/vProbe/latest/vProbe_System_Admin/Content/02%20AI-vProbe%20Configuration/Generating_SESSION__BEARER__FLOW__and_HTTP_Transac.htm) (only available to customers with Affirmed support), making the following changes:
+Follow the steps in "Generating SESSION, BEARER, FLOW, and HTTP Transaction EDRs" in the [Affirmed Networks Active Intelligent vProbe System Administration Guide](https://manuals.metaswitch.com/vProbe/latest) (only available to customers with Affirmed support), making the following changes:
 
-    - Replace the IP addresses of the MSFs in MCC configuration with the IP addresses of the VMs running the ingestion agents.
+- Replace the IP addresses of the MSFs in MCC configuration with the IP addresses of the VMs running the ingestion agents.
+- Confirm that the following EDR server parameters are set.
 
-    - Confirm that the following EDR server parameters are set.
-
-        - port: 36001
-        - encoding: protobuf
-        - keep-alive: 2 seconds
+    - `port`: 36001
+    - `encoding`: protobuf
+    - `keep-alive`: 2 seconds
 
 ## Related content
 
diff --git a/articles/storage/blobs/assign-azure-role-data-access.md b/articles/storage/blobs/assign-azure-role-data-access.md
@@ -167,12 +167,10 @@ To learn how to use an Azure Resource Manager template to assign an Azure role,
 Keep in mind the following points about Azure role assignments in Azure Storage:
 
 - When you create an Azure Storage account, you aren't automatically assigned permissions to access data via Microsoft Entra ID. You must explicitly assign yourself an Azure role for Azure Storage. You can assign it at the level of your subscription, resource group, storage account, or container.
+- When you assign roles or remove role assignments, it can take up to 10 minutes for changes to take effect.
 - If the storage account is locked with an Azure Resource Manager read-only lock, then the lock prevents the assignment of Azure roles that are scoped to the storage account or a container.
 - If you set the appropriate allow permissions to access data via Microsoft Entra ID and are unable to access the data, for example you're getting an "AuthorizationPermissionMismatch" error. Be sure to allow enough time for the permissions changes you made in Microsoft Entra ID to replicate, and be sure that you don't have any deny assignments that block your access, see [Understand Azure deny assignments](../../role-based-access-control/deny-assignments.md).
 
-> [!NOTE]
-> When you assign roles or remove role assignments, it can take up to 10 minutes for changes to take effect.
-
 > [!NOTE]
 > You can create custom Azure RBAC roles for granular access to blob data. For more information, see [Azure custom roles](../../role-based-access-control/custom-roles.md).
 
diff --git a/articles/storage/common/storage-use-azcopy-authorize-azure-active-directory.md b/articles/storage/common/storage-use-azcopy-authorize-azure-active-directory.md
@@ -179,13 +179,10 @@ Then, run any azcopy command (For example: `azcopy list https://contoso.blob.cor
 
 ### Authorize by using the AzCopy login command
 
-As an alternative to using in-memory variables, you authorize access by using the azcopy login command. However, this approach is not recommended as the azcopy login command will soon be deprecated. 
+As an alternative to using in-memory variables, you authorize access by using the azcopy login command.
 
 The azcopy login command retrieves an OAuth token and then places that token into a secret store on your system. If your operating system doesn't have a secret store such as a Linux keyring, the azcopy login command won't work because there is nowhere to place the token.
 
-> [!IMPORTANT]
-> The azcopy login command will soon be deprecated.
-
 #### Authorize a user identity (azcopy login command)
 
 After you've verified that your user identity has been given the necessary authorization level, open a command prompt, type the following command, and then press the ENTER key.
diff --git a/articles/virtual-machines/TOC.yml b/articles/virtual-machines/TOC.yml
@@ -203,10 +203,18 @@
           href: basv2.md
         - name: Bpsv2-series
           href: bpsv2-arm.md
-      - name: DCsv2-series
-        href: dcv2-series.md
-      - name: DCsv3 and DCdsv3-series
-        href: dcv3-series.md
+      - name: DC-series confidential
+        items:
+        - name: DCsv2-series
+          href: dcv2-series.md
+        - name: DCsv3 and DCdsv3-series
+          href: dcv3-series.md
+        - name: DCasv5 and DCadsv5-series
+          href: dcasv5-dcadsv5-series.md
+        - name: DCas_cc_v5 and DCads_cc_v5-series
+          href: dcasccv5-dcadsccv5-series.md
+        - name: DCesv5 and DCedsv5-series
+          href: dcesv5-dcedsv5-series.md  
       - name: Dv2 and DSv2-series
         href: dv2-dsv2-series.md
       - name: Dv3 and DSv3-series
@@ -225,12 +233,6 @@
         href: dasv5-dadsv5-series.md
       - name: Dalsv6 and Daldsv6-series
         href: dalsv6-daldsv6-series.md
-      - name: DCasv5 and DCadsv5-series
-        href: dcasv5-dcadsv5-series.md
-      - name: DCas_cc_v5 and DCads_cc_v5-series
-        href: dcasccv5-dcadsccv5-series.md
-      - name: DCesv5 and DCedsv5-series
-        href: dcesv5-dcedsv5-series.md
       - name: Dpsv5 and Dpdsv5-series
         href: dpsv5-dpdsv5-series.md
       - name: Dplsv5 and Dpldsv5-series
@@ -261,6 +263,14 @@
         href: eav4-easv4-series.md
       - name: Easv6 and Eadsv6-series
         href: easv6-eadsv6-series.md
+      - name: EC-series confidential
+        items:
+        - name: ECasv5 and ECadsv5-series
+          href: ecasv5-ecadsv5-series.md
+        - name: ECas_cc_v5 and ECads_cc_v5-series
+          href: ecasccv5-ecadsccv5-series.md
+        - name: ECesv5 and ECedsv5-series
+          href: ecesv5-ecedsv5-series.md  
       - name: Edv4 and Edsv4-series
         href: edv4-edsv4-series.md
       - name: Ev4 and Esv4-series
@@ -273,18 +283,14 @@
         href: edv5-edsv5-series.md
       - name: Easv5 and Eadsv5-series
         href: easv5-eadsv5-series.md
-      - name: ECasv5 and ECadsv5-series
-        href: ecasv5-ecadsv5-series.md
-      - name: ECas_cc_v5 and ECads_cc_v5-series
-        href: ecasccv5-ecadsccv5-series.md
-      - name: ECesv5 and ECedsv5-series
-        href: ecesv5-ecedsv5-series.md
       - name: Epsv5 and Epdsv5-series
         href: epsv5-epdsv5-series.md
       - name: M-series
         href: m-series.md
       - name: Msv2 and Mdsv2 Medium Memory series
         href: msv2-mdsv2-series.md
+      - name: Msv2 and Mdsv2 migration guide
+        href: msv2-mdsv2-isolated-retirement.md
       - name: Mv2-series
         href: mv2-series.md
       - name: Msv3 and Mdsv3 Medium Memory Series
diff --git a/articles/virtual-machines/msv2-mdsv2-isolated-retirement.md b/articles/virtual-machines/msv2-mdsv2-isolated-retirement.md
diff --git a/articles/web-application-firewall/ag/upgrade-ag-waf-policy.md b/articles/web-application-firewall/ag/upgrade-ag-waf-policy.md
