Merge branch 'master' of https://github.com/Microsoftdocs/azure-docs-pr into funlanding

TerryLanfear · TerryLanfear · commit 9e27a35229d7 · 2020-01-15T18:10:56.000-08:00
diff --git a/articles/azure-app-configuration/quickstart-feature-flag-aspnet-core.md b/articles/azure-app-configuration/quickstart-feature-flag-aspnet-core.md
@@ -82,8 +82,8 @@ Add the [Secret Manager tool](https://docs.microsoft.com/aspnet/core/security/ap
 1. Add reference to the `Microsoft.Azure.AppConfiguration.AspNetCore` and the `Microsoft.FeatureManagement.AspNetCore` NuGet packages by running the following commands:
 
     ```
-    dotnet add package Microsoft.Azure.AppConfiguration.AspNetCore --version 2.0.0-preview-009470001-12
-    dotnet add package Microsoft.FeatureManagement.AspNetCore --version 1.0.0-preview-009000001-1251
+    dotnet add package Microsoft.Azure.AppConfiguration.AspNetCore --version 3.0.0-preview-010560002-1165
+    dotnet add package Microsoft.FeatureManagement.AspNetCore --version 2.0.0-preview-010610001-1263
     ```
 
 1. Run the following command to restore packages for your project:
@@ -106,12 +106,6 @@ Add the [Secret Manager tool](https://docs.microsoft.com/aspnet/core/security/ap
 
     You can access this secret with the App Configuration API. A colon (:) works in the configuration name with the App Configuration API on all supported platforms. See [Configuration by environment](https://docs.microsoft.com/aspnet/core/fundamentals/configuration).
 
-1. Open *Program.cs*, and add a reference to the .NET Core App Configuration provider:
-
-    ```csharp
-    using Microsoft.Extensions.Configuration.AzureAppConfiguration;
-    ```
-
 1. Update the `CreateWebHostBuilder` method to use App Configuration by calling the `config.AddAzureAppConfiguration()` method.
     
     > [!IMPORTANT]
diff --git a/articles/azure-app-configuration/quickstart-feature-flag-dotnet.md b/articles/azure-app-configuration/quickstart-feature-flag-dotnet.md
@@ -64,22 +64,32 @@ The .NET Feature Management libraries extend the framework with comprehensive fe
 1. Update the `Main` method to connect to App Configuration, specifying the `UseFeatureFlags` option so that feature flags are retrieved. Then display a message if the `Beta` feature flag is enabled.
 
     ```csharp
-        static void Main(string[] args)
+        public static void Main(string[] args)
+        {
+            AsyncMain().Wait();
+        }
+
+        private static async Task AsyncMain()
         {
             IConfigurationRoot configuration = new ConfigurationBuilder()
-                .AddAzureAppConfiguration(options => 
-                { 
+                .AddAzureAppConfiguration(options =>
+                {
                     options.Connect(Environment.GetEnvironmentVariable("ConnectionString"))
-                           .UseFeatureFlags(); 
+                           .UseFeatureFlags();
                 }).Build();
-            
-            IServiceCollection services = new ServiceCollection(); 
-            services.AddSingleton<IConfiguration>(configuration).AddFeatureManagement(); 
-            IFeatureManager featureManager = services.BuildServiceProvider().GetRequiredService<IFeatureManager>(); 
-            
-            if (featureManager.IsEnabled("Beta")) 
-            { 
-                Console.WriteLine("Welcome to the beta"); 
+
+            IServiceCollection services = new ServiceCollection();
+
+            services.AddSingleton<IConfiguration>(configuration).AddFeatureManagement();
+
+            using (ServiceProvider serviceProvider = services.BuildServiceProvider())
+            {
+                IFeatureManager featureManager = serviceProvider.GetRequiredService<IFeatureManager>();
+
+                if (await featureManager.IsEnabledAsync("Beta"))
+                {
+                    Console.WriteLine("Welcome to the beta!");
+                }
             }
 
             Console.WriteLine("Hello World!");
diff --git a/articles/azure-app-configuration/use-feature-flags-dotnet-core.md b/articles/azure-app-configuration/use-feature-flags-dotnet-core.md
@@ -175,7 +175,7 @@ The basic pattern of feature management is to first check if a feature flag is s
 ```csharp
 IFeatureManager featureManager;
 ...
-if (featureManager.IsEnabled(nameof(MyFeatureFlags.FeatureA)))
+if (await featureManager.IsEnabledAsync(nameof(MyFeatureFlags.FeatureA)))
 {
     // Run the following code
 }
@@ -252,7 +252,7 @@ The feature `<feature>` tag can also be used to show content if any or all featu
 
 ## MVC filters
 
-You can set up MVC filters so that they're activated based on the state of a feature flag. The following code adds an MVC filter named `SomeMvcFilter`. This filter is triggered within the MVC pipeline only if `FeatureA` is enabled.
+You can set up MVC filters so that they're activated based on the state of a feature flag. The following code adds an MVC filter named `SomeMvcFilter`. This filter is triggered within the MVC pipeline only if `FeatureA` is enabled. This capability is limited to `IAsyncActionFilter`. 
 
 ```csharp
 using Microsoft.FeatureManagement.FeatureFilters;
@@ -267,16 +267,6 @@ public void ConfigureServices(IServiceCollection services)
 }
 ```
 
-## Routes
-
-You can use feature flags to dynamically expose routes. The following code adds a route, which sets `Beta` as the default controller only when `FeatureA` is enabled:
-
-```csharp
-app.UseMvc(routes => {
-    routes.MapRouteForFeature(nameof(MyFeatureFlags.FeatureA), "betaDefault", "{controller=Beta}/{action=Index}/{id?}");
-});
-```
-
 ## Middleware
 
 You can also use feature flags to conditionally add application branches and middleware. The following code inserts a middleware component in the request pipeline only when `FeatureA` is enabled:
diff --git a/articles/cloud-services/cloud-services-guestos-msrc-releases.md b/articles/cloud-services/cloud-services-guestos-msrc-releases.md
@@ -10,12 +10,60 @@ ms.service: cloud-services
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: tbd
-ms.date: 01/08/2020
+ms.date: 01/15/2020
 ms.author: raiye
 ---
 # Azure Guest OS
 The following tables show the Microsoft Security Response Center (MSRC) updates applied to the Azure Guest OS. Search this article to determine if a particular update applies to the Guest OS you are using. Updates always carry forward for the particular [family][family-explain] they were introduced in.
 
+## January 2020 Guest OS
+
+>[!NOTE]
+>The January Guest OS is currently being rolled out to Cloud Service VMs that are configured for automatic updates. When the rollout is complete, this version will be made available for manual updates through the Azure portal and configuration files. The following patches are included in the January Guest OS. This list is subject to change.
+
+| Product Category | Parent KB Article | Vulnerability Description | Guest OS | Date First Introduced |
+| --- | --- | --- | --- | --- |
+|  Rel 20-01  |  [4532960]  |  Windows Security  | 2.94 | Jan 14, 2020 |
+|  Rel 20-01  |  [4534251]  |  Internet Explorer  | 2.94 | Jan 14, 2020 |
+|  Rel 20-01  |  [4534314]  |  Windows Security  | 2.94 | Jan 14, 2020 |
+|  Rel 20-01  |  [4532958]  |  Windows Security  | 3.81 | Jan 14, 2020 |
+|  Rel 20-01  |  [4532963]  |  Windows Security  | 3.81 | Jan 14, 2020 |
+|  Rel 20-01  |  [4534251]  |  Internet Explorer  | 3.81 | Jan 14, 2020 |
+|  Rel 20-01  |  [4534288]  |  Windows Security  | 3.81 | Jan 14, 2020 |
+|  Rel 20-01  |  [4532961]  |  Windows Security  | 4.74 | Jan 14, 2020 |
+|  Rel 20-01  |  [4532962]  |  Windows Security  | 4.74 | Jan 14, 2020 |
+|  Rel 20-01  |  [4534251]  |  Internet Explorer  | 4.74 | Jan 14, 2020 |
+|  Rel 20-01  |  [4534309]  |  Windows Security  | 4.74 | Jan 14, 2020 |
+|  Rel 20-01  |  [4494175]  |  Microcode v3  | 5.39 | Aug 29, 2019 |
+|  Rel 20-01  |  [4534271]  |  LCU  | 5.39 | Jan 14, 2020 |
+|  Rel 20-01  |  [4494174]  |  Microcode v4  | 6.15 | Aug 29, 2019 |
+|  Rel 20-01  |  [4532947]  |  Windows Security  | 6.15 | Jan 14, 2020 |
+|  Rel 20-01  |  [4534273]  |  LCU  | 6.15 | Jan 14, 2020 |
+|  Rel 20-01  |  [4530734]  |  Non-Security  | 2.94 | Dec 10, 2019 |
+|  Rel 20-01  |  [4530691]  |  Non-Security   | 3.81 | Dec 10, 2019 |
+|  Rel 20-01  |  [4530702]  |  Non-Security  | 4.74 | Dec 10, 2019 |
+
+[4532960]: https://support.microsoft.com/kb/4532960
+[4534251]: https://support.microsoft.com/kb/4534251
+[4534314]: https://support.microsoft.com/kb/4534314
+[4532958]: https://support.microsoft.com/kb/4532958
+[4532963]: https://support.microsoft.com/kb/4532963
+[4534251]: https://support.microsoft.com/kb/4534251
+[4534288]: https://support.microsoft.com/kb/4534288
+[4532961]: https://support.microsoft.com/kb/4532961
+[4532962]: https://support.microsoft.com/kb/4532962
+[4534251]: https://support.microsoft.com/kb/4534251
+[4534309]: https://support.microsoft.com/kb/4534309
+[4494175]: https://support.microsoft.com/kb/4494175
+[4534271]: https://support.microsoft.com/kb/4534271
+[4494174]: https://support.microsoft.com/kb/4494174
+[4532947]: https://support.microsoft.com/kb/4532947
+[4534273]: https://support.microsoft.com/kb/4534273
+[4530734]: https://support.microsoft.com/kb/4530734
+[4530691]: https://support.microsoft.com/kb/4530691
+[4530702]: https://support.microsoft.com/kb/4530702
+
+
 ## December 2019 Guest OS
 
 | Product Category | Parent KB Article | Vulnerability Description | Guest OS | Date First Introduced |
diff --git a/articles/cognitive-services/Speech-Service/how-to-automatic-language-detection.md b/articles/cognitive-services/Speech-Service/how-to-automatic-language-detection.md
@@ -8,8 +8,9 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: speech-service
 ms.topic: conceptual
-ms.date: 10/26/2019
+ms.date: 01/15/2020
 ms.author: qiohu
+zone_pivot_groups: programming-languages-set-seven
 ---
 
 # Automatic language detection for speech to text
@@ -19,7 +20,7 @@ Automatic language detection is used to determine the most likely match for audi
 In this article, you'll learn how to use `AutoDetectSourceLanguageConfig` to construct a `SpeechRecognizer` object and retrieve the detected language.
 
 > [!IMPORTANT]
-> This feature is only available for the Speech SDK for C++ and the Speech SDK for Java.
+> This feature is only available for the Speech SDK for C#, C++ and Java.
 
 ## Automatic language detection with the Speech SDK
 
@@ -30,6 +31,22 @@ Automatic language detection currently has a services-side limit of two language
 
 The following snippets illustrate how to use automatic language detection in your apps:
 
+::: zone pivot="programming-language-csharp"
+
+```csharp
+var autoDetectSourceLanguageConfig = AutoDetectSourceLanguageConfig.FromLanguages(new string[] { "en-US", "de-DE" });
+using (var recognizer = new SpeechRecognizer(speechConfig, autoDetectSourceLanguageConfig, audioConfig))
+{
+    var speechRecognitionResult = await recognizer.RecognizeOnceAsync();
+    var autoDetectSourceLanguageResult = AutoDetectSourceLanguageResult.FromResult(speechRecognitionResult);
+    var detectedLanguage = autoDetectSourceLanguageResult.Language;
+}
+```
+
+::: zone-end
+
+::: zone pivot="programming-language-cpp"
+
 ```C++
 auto autoDetectSourceLanguageConfig = AutoDetectSourceLanguageConfig::FromLanguages({ "en-US", "de-DE" });
 auto recognizer = SpeechRecognizer::FromConfig(speechConfig, autoDetectSourceLanguageConfig, audioConfig);
@@ -38,6 +55,10 @@ auto autoDetectSourceLanguageResult = AutoDetectSourceLanguageResult::FromResult
 auto detectedLanguage = autoDetectSourceLanguageResult->Language;
 ```
 
+::: zone-end
+
+::: zone pivot="programming-language-java"
+
 ```Java
 AutoDetectSourceLanguageConfig autoDetectSourceLanguageConfig = AutoDetectSourceLanguageConfig.fromLanguages(Arrays.asList("en-US", "de-DE"));
 SpeechRecognizer recognizer = new SpeechRecognizer(speechConfig, autoDetectSourceLanguageConfig, audioConfig);
@@ -53,26 +74,49 @@ audioConfig.close();
 result.close();
 ```
 
+::: zone-end
+
 ## Use a custom model for automatic language detection
 
 In addition to language detection using Speech service models, you can specify a custom model for enhanced recognition. If a custom model isn't provided, the service will use the default language model.
 
 The snippets below illustrate how to specify a custom model in your call to the Speech service. If the detected language is `en-US`, then the default model is used. If the detected language is `fr-FR`, then the endpoint for the custom model is used:
 
+::: zone pivot="programming-language-csharp"
+
+```csharp
+var sourceLanguageConfigs = new SourceLanguageConfig[]
+{
+    SourceLanguageConfig.FromLanguage("en-US"),
+    SourceLanguageConfig.FromLanguage("fr-FR", "The Endpoint Id for custom model of fr-FR")
+};
+var autoDetectSourceLanguageConfig = AutoDetectSourceLanguageConfig.FromSourceLanguageConfigs(sourceLanguageConfigs);
+```
+
+::: zone-end
+
+::: zone pivot="programming-language-cpp"
+
 ```C++
 std::vector<std::shared_ptr<SourceLanguageConfig>> sourceLanguageConfigs;
 sourceLanguageConfigs.push_back(SourceLanguageConfig::FromLanguage("en-US"));
 sourceLanguageConfigs.push_back(SourceLanguageConfig::FromLanguage("fr-FR", "The Endpoint Id for custom model of fr-FR"));
 auto autoDetectSourceLanguageConfig = AutoDetectSourceLanguageConfig::FromSourceLanguageConfigs(sourceLanguageConfigs);
 ```
 
+::: zone-end
+
+::: zone pivot="programming-language-java"
+
 ```Java
 List sourceLanguageConfigs = new ArrayList<SourceLanguageConfig>();
 sourceLanguageConfigs.add(SourceLanguageConfig.fromLanguage("en-US"));
 sourceLanguageConfigs.add(SourceLanguageConfig.fromLanguage("fr-FR", "The Endpoint Id for custom model of fr-FR"));
 AutoDetectSourceLanguageConfig autoDetectSourceLanguageConfig = AutoDetectSourceLanguageConfig.fromSourceLanguageConfigs(sourceLanguageConfigs);
 ```
 
+::: zone-end
+
 ## Next steps
 
 - [Speech SDK reference documentation](speech-sdk.md)
diff --git a/articles/cognitive-services/Speech-Service/how-to-specify-source-language.md b/articles/cognitive-services/Speech-Service/how-to-specify-source-language.md
@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: speech-service
 ms.topic: conceptual
-ms.date: 10/26/2019
+ms.date: 01/07/2020
 ms.author: qiohu
 zone_pivot_groups: programming-languages-set-two
 ---
@@ -21,24 +21,29 @@ In this article, you'll learn how to specify the source language for an audio in
 
 ## How to specify source language in C#
 
-The first step is to create a `SpeechConfig`:
+In this example, the source language is provided explicitly as a parameter using `SpeechRecognizer` construct.
 
 ```csharp
-var speechConfig = SpeechConfig.FromSubscription("YourSubscriptionKey", "YourServiceRegion");
+var recognizer = new SpeechRecognizer(speechConfig, "de-DE", audioConfig);
 ```
 
-Next, specify the source language of your audio with `SpeechRecognitionLanguage`:
+In this example, the source language is provided using `SourceLanguageConfig`. Then, the `sourceLanguageConfig` is passed as a parameter to `SpeechRecognizer` construct.
 
 ```csharp
-speechConfig.SpeechRecognitionLanguage = "de-DE";
+var sourceLanguageConfig = SourceLanguageConfig.FromLanguage("de-DE");
+var recognizer = new SpeechRecognizer(speechConfig, sourceLanguageConfig, audioConfig);
 ```
 
-If you're using a custom model for recognition, you can specify the endpoint with `EndpointId`:
+In this example, the source language and custom endpoint are provided using `SourceLanguageConfig`. Then, the `sourceLanguageConfig` is passed as a parameter to `SpeechRecognizer` construct.
 
 ```csharp
-speechConfig.EndpointId = "The Endpoint ID for your custom model.";
+var sourceLanguageConfig = SourceLanguageConfig.FromLanguage("de-DE", "The Endpoint ID for your custom model.");
+var recognizer = new SpeechRecognizer(speechConfig, sourceLanguageConfig, audioConfig);
 ```
 
+>[!Note]
+> `SpeechRecognitionLanguage` and `EndpointId` set methods are deprecated from the `SpeechConfig` class in C#. The use of these methods are discouraged, and shouldn't be used when constructing a `SpeechRecognizer`.
+
 ::: zone-end
 
 ::: zone pivot="programming-language-cpp"
diff --git a/articles/virtual-machines/linux/update-infrastructure-redhat.md b/articles/virtual-machines/linux/update-infrastructure-redhat.md
@@ -13,8 +13,8 @@ ms.service: virtual-machines-linux
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 6/6/2019
-ms.author: borisb
+ms.date: 1/15/2020
+ms.author: guybo
 
 ---
 # Red Hat Update Infrastructure for on-demand Red Hat Enterprise Linux VMs in Azure
@@ -197,19 +197,6 @@ In September 2016, we deployed an updated Azure RHUI. In April 2017, we shut dow
 
 The new Azure RHUI servers are deployed with [Azure Traffic Manager](https://azure.microsoft.com/services/traffic-manager/). In Traffic Manager, a single endpoint (rhui-1.microsoft.com) can be used by any VM, regardless of region.
 
-### Manual update procedure to use the Azure RHUI servers
-This procedure is provided for reference only. RHEL PAYG images already have the correct configuration to connect to Azure RHUI. To manually update the configuration to use the Azure RHUI servers, complete the following steps:
-
-- For RHEL 6:
-  ```bash
-  yum --config='https://rhelimage.blob.core.windows.net/repositories/rhui-microsoft-azure-rhel6.config' install 'rhui-azure-rhel6'
-  ```
-
-- For RHEL 7:
-  ```bash
-  yum --config='https://rhelimage.blob.core.windows.net/repositories/rhui-microsoft-azure-rhel7.config' install 'rhui-azure-rhel7'
-  ```
-
 ## Next steps
 * To create a Red Hat Enterprise Linux VM from an Azure Marketplace PAYG image and to use Azure-hosted RHUI, go to the [Azure Marketplace](https://azure.microsoft.com/marketplace/partners/redhat/).
 * To learn more about the Red Hat images in Azure, go to the [documentation page](./rhel-images.md).
diff --git a/articles/zone-pivot-groups.yml b/articles/zone-pivot-groups.yml
@@ -96,11 +96,21 @@ groups:
     title: Python
   - id: programming-language-nodejs
     title: Node.js
+- id: programming-languages-set-seven
+  title: Programming languages
+  prompt: Choose a programming language
+  pivots:
+  - id: programming-language-csharp
+    title: C#
+  - id: programming-language-cpp
+    title: C++
+  - id: programming-language-java
+    title: Java
 - id: URL-test-interface
   title: URL Test tool
   prompt: Choose one of the following
   pivots:
   - id: url-test-tool-curl
     title: cURL
   - id: url-test-tool-postman
-    title: Postman
+    title: Postman
