Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

CODEOWNERS

@@ -19,3 +19,10 @@
 /articles/virtual-machines-scale-sets @jasonwhowell @thomps23
 /articles/container-instances @jasonwhowell @thomps23
 /articles/service-fabric @jasonwhowell @thomps23
+/articles/machine-learning @jasonwhowell @thomps23
+/articles/ai-studio @jasonwhowell @thomps23
+/articles/ai-services @jasonwhowell @thomps23
+/articles/genomics @jasonwhowell @thomps23
+/articles/open-datasets @jasonwhowell @thomps23
+/articles/search @jasonwhowell @thomps23
+

articles/azure-app-configuration/feature-management-dotnet-reference.md

@@ -1131,7 +1131,7 @@ Compared to normal feature flags, variant feature flags have two additional prop
 
 #### Defining Variants
 
-Each variant has two properties: a name and a configuration. The name is used to refer to a specific variant, and the configuration is the value of that variant. The configuration can be set using either the `configuration_reference` or `configuration_value` properties. `configuration_reference` is a string path that references a section of the current configuration that contains the feature flag declaration. `configuration_value` is an inline configuration that can be a string, number, boolean, or configuration object. If both are specified, `configuration_value` is used. If neither are specified, the returned variant's `Configuration` property will be null.
+Each variant has two properties: a name and a configuration. The name is used to refer to a specific variant, and the configuration is the value of that variant. The configuration can be set using `configuration_value` property. `configuration_value` is an inline configuration that can be a string, number, boolean, or configuration object. If `configuration_value` is not specified, the returned variant's `Configuration` property will be null.
 
 A list of all possible variants is defined for each feature under the `variants` property.
 
@@ -1144,7 +1144,9 @@ A list of all possible variants is defined for each feature under the `variants`
                 "variants": [
                     { 
                         "name": "Big", 
-                        "configuration_reference": "ShoppingCart:Big" 
+                        "configuration_value": {
+                            "Size": 500
+                        }
                     },  
                     { 
                         "name": "Small", 
@@ -1155,17 +1157,6 @@ A list of all possible variants is defined for each feature under the `variants`
                 ]
             }
         ]
-    },
-
-    "ShoppingCart": {
-        "Big": {
-            "Size": 600,
-            "Color": "green"
-        },
-        "Small": {
-            "Size": 300,
-            "Color": "gray"
-        }
     }
 }
 ```
@@ -1206,7 +1197,7 @@ The process of allocating a feature's variants is determined by the `allocation`
 "variants": [
     { 
         "name": "Big", 
-        "configuration_reference": "ShoppingCart:Big" 
+        "configuration_value": "500px"
     },  
     { 
         "name": "Small", 

articles/migrate/common-questions-server-migration.md

@@ -132,7 +132,7 @@ Migration and modernization tool migrates all the UEFI-based machines to Azure a
 | SUSE Linux Enterprise Server 12 SP4                     | Y                                                                                                                                         | Y                              | Y                                                          |
 | Ubuntu Server 16.04, 18.04, 19.04, 19.10                | Y                                                                                                                                         | Y                              | Y                                                          |
 | RHEL 8.1, 8.0, 7.8, 7.7, 7.6, 7.5, 7.4, 7.0, 6.x        | Y      | Y                              | Y                                                          |
-| Cent OS 8.1, 8.0, 7.7, 7.6, 7.5, 7.4, 6.x               | Y | Y                              | Y                                                          |
+| CentOS Stream               | Y | Y                              | Y                                                          |
 | Oracle Linux 7.7, 7.7-CI                                |  Y                                                                                                                                        | Y                              | Y                                                          |
 
 ### Can I migrate Active Directory domain-controllers using Azure Migrate?

articles/migrate/prepare-for-migration.md

@@ -6,8 +6,8 @@ ms.author: sunishvohra
 ms.manager: vijain
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 07/05/2024
-ms.custom: engagement-fy24
+ms.date: 08/23/2024
+ms.custom: engagement-fy25
 ---
 
 # Prepare on-premises machines for migration to Azure
@@ -113,7 +113,7 @@ Configure this setting manually as follows:
 Azure Migrate completes these actions automatically for these versions
 
 - Red Hat Enterprise Linux  8.x, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.0, 6.x (Azure Linux VM agent is also installed automatically during migration)
-- Cent OS 8.x, 7.7, 7.6, 7.5, 7.4, 6.x (Azure Linux VM agent is also installed automatically during migration)
+- CentOS Stream (Azure Linux VM agent is also installed automatically during migration)
 - SUSE Linux Enterprise Server 15 SP0, 15 SP1, 12, 11 SP4, 11 SP3
 - Ubuntu 20.04, 19.04, 19.10, 18.04LTS, 16.04LTS, 14.04LTS (Azure Linux VM agent is also installed automatically during migration)
 - Debian 10, 9, 8, 7