Merge pull request #268894 from MicrosoftDocs/main

Merge main to live, 4 AM

Author: v-ccolin

.openpublishing.redirection.active-directory.json

@@ -33690,6 +33690,6 @@
             "source_path_from_root": "/articles/active-directory-domain-services/contact-us.md",
             "redirect_url": "/azure/active-directory/fundamentals/support-help-options",
             "redirect_document_id": false
-        },
+        }
     ]
-}
+}

.openpublishing.redirection.sql-database.json

@@ -2580,6 +2580,6 @@
             "source_path_from_root": "/articles/sql-data-warehouse/sql-data-warehouse-security-threat-detection.md",
             "redirect_url": "/azure/sql-database/sql-database-threat-detection-overview",
             "redirect_document_id": false
-        },
+        }
     ]
 }

articles/advisor/advisor-reference-cost-recommendations.md

@@ -136,7 +136,7 @@ Learn more about [Log Analytics workspace - DeleteRestoredTables (Consider remov
 
 ### Consider enabling autopause on Spark compute
 
-Auto-pause releases and shuts down unused Compute resources after a set idle period of inactivity.
+Autopause releases and shuts down unused Compute resources after a set idle period of inactivity.
 
 Learn more about [Synapse workspace - EnableSynapseSparkComputeAutoPauseGuidance (Consider enabling autopause feature on spark compute.)](https://aka.ms/EnableSynapseSparkComputeAutoPauseGuidance).
 
@@ -154,15 +154,15 @@ Learn more about [Synapse workspace - EnableSynapseSparkComputeAutoScaleGuidance
 
 Customers running high IO workloads in Standard HDDs can upgrade to Standard SSDs and benefit from better performance and SLA and now experience a limit on the maximum number of billed transactions.
 
-Learn more about [Disk - UpgradeHDDtoSDD (Standard SSD disks billing caps.)]().
+Learn more about [Understand Azure Disk Storage billing](/azure/virtual-machines/disks-understand-billing).
 
 ### Underutilized Disks Identified
 
 You have disks that are utilized less than 10%, right-size to save cost.
 
-Learn more about [Disk - wiprounderutilizeddisks (Underutilized Disks Identified)]().
+Learn more about [Managed disks: Find and delete unattached disks](/azure/virtual-machines/disks-find-unattached-portal).
 
-### You have disks that have not been attached to a VM for more than 30 days. Evaluate if you still need the disk.
+### You have disks that haven't been attached to a VM for more than 30 days. Evaluate if you still need the disk.
 
 We've observed that you have disks that haven't been attached to a VM for more than 30 days. Evaluate if you still need the disk. If you decide to delete the disk, recovery isn't possible. We recommend that you create a snapshot before deletion or ensure the data in the disk is no longer required.
 
@@ -176,7 +176,7 @@ Learn more about [Virtual machine scale set - LowUsageVmss (Right-size or shutdo
 
 ### Use Virtual Machines with Ephemeral OS Disk enabled to save cost and get better performance
 
-With Ephemeral OS Disk, You get these benefits: Save on storage cost for OS disk. Get lower read/write latency to OS disk. Faster VM Reimage operation by resetting OS (and Temporary disk) to its original state. It is preferable to use Ephemeral OS Disk for short-lived IaaS VMs or VMs with stateless workloads.
+With Ephemeral OS Disk, You get these benefits: Save on storage cost for OS disk. Get lower read/write latency to OS disk. Faster VM Reimage operation by resetting OS (and Temporary disk) to its original state. It's preferable to use Ephemeral OS Disk for short-lived IaaS VMs or VMs with stateless workloads.
 
 Learn more about [Subscription - EphemeralOsDisk (Use Virtual Machines with Ephemeral OS Disk enabled to save cost and get better performance)](/azure/virtual-machines/windows/ephemeral-os-disks).
 
@@ -205,7 +205,7 @@ Learn more about [PostgreSQL server - OrcasPostgreSqlCpuRightSize (Right-size un
 
 ### Review the configuration of your Azure Cosmos DB free tier account
 
-Your Azure Cosmos DB free tier account currently contains resources with a total provisioned throughput exceeding 1000 Request Units per second (RU/s). Because the free tier only covers the first 1000 RU/s of throughput provisioned across your account, any throughput beyond 1000 RU/s is billed at the regular pricing. As a result, we anticipate that you're charged for the throughput currently provisioned on your Azure Cosmos DB account.
+Your Azure Cosmos DB free tier account currently contains resources with a total provisioned throughput exceeding 1,000 Request Units per second (RU/s). Because the free tier only covers the first 1000 RU/s of throughput provisioned across your account, any throughput beyond 1000 RU/s is billed at the regular pricing. As a result, we anticipate that you're charged for the throughput currently provisioned on your Azure Cosmos DB account.
 
 Learn more about [Azure Cosmos DB account - CosmosDBFreeTierOverage (Review the configuration of your Azure Cosmos DB free tier account)](../cosmos-db/understand-your-bill.md#azure-free-tier).
 
@@ -256,13 +256,13 @@ Learn more about [ExpressRoute circuit - ExpressRouteCircuit (Delete ExpressRout
 
 ### Repurpose or delete idle virtual network gateways
 
-We noticed that your virtual network gateway has been idle for over 90 days. This gateway is being billed hourly. Reconfigure this gateway, or delete it if you do not intend to use it anymore.
+We noticed that your virtual network gateway has been idle for over 90 days. This gateway is being billed hourly. Reconfigure this gateway, or delete it if you don't intend to use it anymore.
 
 Learn more about [Virtual network gateway - IdleVNetGateway (Repurpose or delete idle virtual network gateways)](https://aka.ms/aa_idlevpngateway_learnmore).
 
 ### Consider migrating to Front Door Standard/Premium
 
-Your Front Door Classic tier contains a large number of domains or routing rules, which adds extra charges. Front Door Standard or Premium do not charge per additional domain or routing rule. Consider migrating to save costs.
+Your Front Door Classic tier contains a large number of domains or routing rules, which adds extra charges. Front Door Standard or Premium tiers don't charge per additional domain or routing rule. Consider migrating to save costs.
 
 Learn more about [Front Door pricing](https://aka.ms/afd-pricing).
 

articles/ai-services/openai/concepts/model-retirements.md

@@ -4,7 +4,7 @@ titleSuffix: Azure OpenAI
 description: Learn about the model deprecations and retirements in Azure OpenAI.
 ms.service: azure-ai-openai
 ms.topic: conceptual
-ms.date: 03/13/2024
+ms.date: 03/12/2024
 ms.custom: 
 manager: nitinme
 author: mrbullwinkle

articles/ai-services/speech-service/batch-transcription-create.md

@@ -255,7 +255,7 @@ Azure AI Speech supports OpenAI's Whisper model by using the batch transcription
 To use a Whisper model for batch transcription, you need to set the `model` property. Whisper is a display-only model, so the lexical field isn't populated in the response.
 
 > [!IMPORTANT]
-> Whisper models are currently in preview. You should always use [version 3.2](./migrate-v3-1-to-v3-2.md) of the speech to text API, which is available in a separate preview, for Whisper models.
+> For Whisper models, you should always use [version 3.2](./migrate-v3-1-to-v3-2.md) of the speech to text API.
 
 Whisper models by batch transcription are supported in the East US, Southeast Asia, and West Europe regions.
 
@@ -285,36 +285,38 @@ spx csr list --base --api-version v3.2-preview.1
 
 ::: zone-end
 
-The `displayName` property of a Whisper model contains "Whisper Preview" as shown in this example. Whisper is a display-only model, so the lexical field isn't populated in the transcription.
+The `displayName` property of a Whisper model contains "Whisper" as shown in this example. Whisper is a display-only model, so the lexical field isn't populated in the transcription.
 
 ```json
 {
-  "self": "https://eastus.api.cognitive.microsoft.com/speechtotext/v3.2-preview.1/models/base/d9cbeee6-582b-47ad-b5c1-6226583c92b6",
+  "self": "https://eastus.api.cognitive.microsoft.com/speechtotext/v3.2-preview.1/models/base/e418c4a9-9937-4db7-b2c9-8afbff72d950",
   "links": {
-    "manifest": "https://eastus.api.cognitive.microsoft.com/speechtotext/v3.2-preview.1/models/base/d9cbeee6-582b-47ad-b5c1-6226583c92b6/manifest"
+    "manifest": "https://eastus.api.cognitive.microsoft.com/speechtotext/v3.2-preview.1/models/base/e418c4a9-9937-4db7-b2c9-8afbff72d950/manifest"
   },
   "properties": {
     "deprecationDates": {
-      "adaptationDateTime": "2024-10-15T00:00:00Z",
-      "transcriptionDateTime": "2025-10-15T00:00:00Z"
+      "adaptationDateTime": "2025-04-15T00:00:00Z",
+      "transcriptionDateTime": "2026-04-15T00:00:00Z"
     },
     "features": {
       "supportsTranscriptions": true,
       "supportsEndpoints": false,
       "supportsTranscriptionsOnSpeechContainers": false,
-      "supportsAdaptationsWith": [],
+      "supportsAdaptationsWith": [
+        "Acoustic"
+      ],
       "supportedOutputFormats": [
         "Display"
       ]
     },
-    "chargeForAdaptation": false
+    "chargeForAdaptation": true
   },
-  "lastActionDateTime": "2023-07-19T12:46:27Z",
+  "lastActionDateTime": "2024-02-29T15:53:28Z",
   "status": "Succeeded",
-  "createdDateTime": "2023-07-19T12:39:52Z",
+  "createdDateTime": "2024-02-29T15:46:07Z",
   "locale": "en-US",
-  "displayName": "20230707 Whisper Preview",
-  "description": "en-US base model"
+  "displayName": "20240228 Whisper Large V2",
+  "description": "OpenAI Whisper Model in Azure AI Speech (Whisper v2-large)"
 },
 ```
 

articles/aks/azure-cni-overlay.md

@@ -138,7 +138,7 @@ az aks nodepool add  -g $resourceGroup --cluster-name $clusterName \
 >
 > - The cluster is on Kubernetes version 1.22+.
 > - Doesn't use the dynamic pod IP allocation feature.
-> - Doesn't have network policies enabled.
+> - Doesn't have network policies enabled. Network Policy engine can be uninstalled before the upgrade, see [Uninstall Azure Network Policy Manager or Calico](use-network-policies.md#uninstall-azure-network-policy-manager-or-calico-preview)
 > - Doesn't use any Windows node pools with docker as the container runtime.
 
 > [!NOTE]

articles/aks/azure-cni-powered-by-cilium.md

@@ -116,10 +116,13 @@ az aks create -n <clusterName> -g <resourceGroupName> -l <location> \
 > You can update an existing cluster to Azure CNI Powered by Cilium if the cluster meets the following criteria:
 >
 > - The cluster uses either [Azure CNI Overlay](./azure-cni-overlay.md) or [Azure CNI with dynamic IP allocation](./configure-azure-cni-dynamic-ip-allocation.md). This does **not** include [Azure CNI](./configure-azure-cni.md).
-> - The cluster does not have Azure NPM or Calico enabled.
-> - The cluster does not have any Windows node pools.
+> - The cluster does not have any Windows node pools.  
 
-The upgrade process triggers each node pool to be re-imaged simultaneously. Upgrading each node pool separately isn't supported. Any disruptions to cluster networking are similar to a node image upgrade or [Kubernetes version upgrade](./upgrade-cluster.md) where each node in a node pool is re-imaged.
+> [!NOTE]
+> When enabling Cilium in a cluster with a different network policy engine (Azure NPM or Calico), the network policy engine will be uninstalled and replaced with Cilium. See [Uninstall Azure Network Policy Manager or Calico](./use-network-policies.md#uninstall-azure-network-policy-manager-or-calico-preview) for more details.
+
+> [!WARNING]
+> The upgrade process triggers each node pool to be re-imaged simultaneously. Upgrading each node pool separately isn't supported. Any disruptions to cluster networking are similar to a node image upgrade or [Kubernetes version upgrade](./upgrade-cluster.md) where each node in a node pool is re-imaged.
 
 Cilium will begin enforcing network policies only after all nodes have been re-imaged.
 
@@ -132,6 +135,7 @@ az aks update -n <clusterName> -g <resourceGroupName> \
   --network-dataplane cilium
 ```
 
+
 ## Frequently asked questions
 
 - **Can I customize Cilium configuration?**

articles/aks/support-policies.md

@@ -58,7 +58,7 @@ Microsoft provides technical support for the following examples:
   * Connectivity to other Azure services and applications
   * Ingress controllers and ingress or load balancer configurations
   * Network performance and latency
-  * [Network policies](use-network-policies.md#compare-azure-network-policy-manager-and-calico-network-policy)
+  * [Network policies](use-network-policies.md#differences-between-network-policy-engines-cilium-azure-npm-and-calico)
 
 > [!NOTE]
 > Any cluster actions taken by Microsoft/AKS are made with your consent under a built-in Kubernetes role `aks-service` and built-in role binding `aks-service-rolebinding`. This role enables AKS to troubleshoot and diagnose cluster issues, but can't modify permissions nor create roles or role bindings, or other high privilege actions. Role access is only enabled under active support tickets with just-in-time (JIT) access.