Merge branch 'master' of https://github.com/microsoftdocs/azure-docs-pr into akv-managedid

Author: msmbaldwin

.openpublishing.publish.config.json

@@ -233,6 +233,11 @@
       "url": "https://github.com/Azure-Samples/azure-iot-samples-node",
       "branch": "master"
     },
+    {
+      "path_to_root": "azure-iot-sdk-node",
+      "url": "https://github.com/Azure/azure-iot-sdk-node",
+      "branch": "master"
+    },
     {
       "path_to_root": "iot-samples-c",
       "url": "https://github.com/Azure/azure-iot-sdk-c",

articles/cognitive-services/LUIS/luis-concept-data-alteration.md

@@ -2,7 +2,7 @@
 title: Data alteration - LUIS
 description: Learn how data can be changed before predictions in Language Understanding (LUIS)
 ms.topic: conceptual
-ms.date: 05/05/2020
+ms.date: 05/06/2020
 ---
 
 # Alter utterance data before or during prediction
@@ -70,18 +70,15 @@ The Bing spell check API used in LUIS does not support a list of words to ignore
 ## Change time zone of prebuilt datetimeV2 entity
 When a LUIS app uses the prebuilt [datetimeV2](luis-reference-prebuilt-datetimev2.md) entity, a datetime value can be returned in the prediction response. The timezone of the request is used to determine the correct datetime to return. If the request is coming from a bot or another centralized application before getting to LUIS, correct the timezone LUIS uses.
 
-### Endpoint querystring parameter
-The timezone is corrected by adding the user's timezone to the endpoint using the appropriate parameter based on the API version. The value of the parameter should be the positive or negative number, in minutes, to alter the time.
+### V3 prediction API to alter timezone
 
-|API version|Querystring parameter|
-|--|--|
-|v2|`timezoneOffset`|
-|v3|`datetimeReference`|
+In V3, the `datetimeReference` determines the timezone offset. Learn more about [V3 predictions](luis-migration-api-v3.md#v3-post-body).
 
-### Daylight savings example
-If you need the returned prebuilt datetimeV2 to adjust for daylight savings time, you should use the querystring parameter with a +/- value in minutes for the [endpoint](https://go.microsoft.com/fwlink/?linkid=2092356) query.
+### V2 prediction API to alter timezone
+The timezone is corrected by adding the user's timezone to the endpoint using the `timezoneOffset` parameter based on the API version. The value of the parameter should be the positive or negative number, in minutes, to alter the time.
 
-#### [V2 prediction endpoint request](#tab/V2)
+#### V2 prediction daylight savings example
+If you need the returned prebuilt datetimeV2 to adjust for daylight savings time, you should use the querystring parameter with a +/- value in minutes for the [endpoint](https://go.microsoft.com/fwlink/?linkid=2092356) query.
 
 Add 60 minutes:
 
@@ -91,21 +88,7 @@ Remove 60 minutes:
 
 `https://{region}.api.cognitive.microsoft.com/luis/v2.0/apps/{appId}?q=Turn the lights on?timezoneOffset=-60&verbose={boolean}&spellCheck={boolean}&staging={boolean}&bing-spell-check-subscription-key={string}&log={boolean}`
 
-#### [V3 prediction endpoint request](#tab/V3)
-
-Add 60 minutes:
-
-`https://{region}.api.cognitive.microsoft.com/luis/v3.0-preview/apps/{appId}/slots/production/predict?query=Turn the lights on?datetimeReference=60&spellCheck={boolean}&bing-spell-check-subscription-key={string}&log={boolean}`
-
-Remove 60 minutes:
-
-`https://{region}.api.cognitive.microsoft.com/luis/v3.0-preview/apps/{appId}/slots/production/predict?query=Turn the lights on?datetimeReference=-60&spellCheck={boolean}&bing-spell-check-subscription-key={string}&log={boolean}`
-
-Learn more about the [V3 prediction endpoint](luis-migration-api-v3.md).
-
-* * *
-
-## C# code determines correct value of parameter
+#### V2 prediction C# code determines correct value of parameter
 
 The following C# code uses the [TimeZoneInfo](https://docs.microsoft.com/dotnet/api/system.timezoneinfo) class's [FindSystemTimeZoneById](https://docs.microsoft.com/dotnet/api/system.timezoneinfo.findsystemtimezonebyid#examples) method to determine the correct offset value based on system time:
 

articles/iot-central/core/concepts-get-connected.md

@@ -89,6 +89,14 @@ To bulk connect devices using X.509 certificates, first register the devices in
 
 Generate X.509 leaf certificates for your devices using the uploaded root or intermediate certificate. Use the **Device ID** as the `CNAME` value in the leaf certificates. Your device code needs the **ID scope** value for your application, the **device ID**, and the corresponding device certificate.
 
+#### Sample device code
+
+The following sample from the [Azure IoT Node.JS SDK](https://github.com/Azure/azure-iot-sdk-node/blob/master/provisioning/device/samples/register_x509.js) shows how a Node.js device client uses an X.509 leaf certificate and DPS to register with an IoT Central application:
+
+:::code language="nodejs" source="~/azure-iot-sdk-node/provisioning/device/samples/register_x509.js":::
+
+For an equivalent C sample, see [prov_dev_client_sample.c](https://github.com/Azure/azure-iot-sdk-c/blob/master/provisioning_client/samples/prov_dev_client_sample/prov_dev_client_sample.c) in the [Azure IoT C Provisioning Device Client SDK](https://github.com/Azure/azure-iot-sdk-c/blob/master/provisioning_client/devdoc/using_provisioning_client.md).
+
 ### For testing purposes only
 
 For testing only, you can use the following utilities to generate root, intermediate, and device certificates:
@@ -101,11 +109,6 @@ For testing only, you can use the following utilities to generate root, intermed
   - Use the verification code from the IoT Central application to generate the verification certificate.
   - Create leaf certificates for your devices using your device IDs as a parameter to the tool.
 
-### Further reference
-
-- [Sample implementation for RaspberryPi](https://aka.ms/iotcentral-docs-Raspi-releases)
-- [Sample device client in C](https://github.com/Azure/azure-iot-sdk-c/blob/master/provisioning_client/devdoc/using_provisioning_client.md)
-
 ## Connect without registering devices
 
 The previously described scenarios all require you to register devices in your application before they connect. IoT Central also enables OEMs to mass manufacture devices that can connect without first being registered. An OEM generates suitable device credentials, and configures the devices in the factory. When a customer turns on a device for the first time, it connects to DPS, which then automatically connects the device to the correct IoT Central application. An IoT Central operator must approve the device before it starts sending data to the application.

articles/load-balancer/concepts.md

@@ -67,7 +67,7 @@ Availability Zones | Standard load balancer supports additional abilities in reg
 
 - Load balancer provides load balancing and port forwarding for specific TCP or UDP protocols. Load-balancing rules and inbound NAT rules support TCP and UDP, but not other IP protocols including ICMP.
 
-- Internal load balancers don't translate outbound originated connections to the frontend of an internal load balancer because both are in private IP address space. Outbound flow from a backend VM to a frontend of an internal load balancer will fail. The failure occurs when the flow is mapped backed to itself. The two legs of the flow don't match and the flow will fail.
+- Outbound flow from a backend VM to a frontend of an internal Load Balancer will fail.
 
 - Forwarding IP fragments isn't supported on load-balancing rules. IP fragmentation of UDP and TCP packets isn't supported on load-balancing rules. HA ports load-balancing rules can be used to forward existing IP fragments. For more information, see [High availability ports overview](load-balancer-ha-ports-overview.md).
 

articles/load-balancer/upgrade-basicInternal-standard.md

@@ -26,6 +26,7 @@ An Azure PowerShell script is available that does the following:
 ### Caveats\Limitations
 
 * Script only supports Internal Load Balancer upgrade where no outbound connection is required. If you required [outbound connection](https://docs.microsoft.com/azure/load-balancer/load-balancer-outbound-connections) for some of your VMs, please refer to this [page](upgrade-InternalBasic-To-PublicStandard.md) for instructions. 
+* The Basic Load Balancer needs to be in the same resource group as the backend VMs and NICs.
 * If the Standard load balancer is created in a different region, you won’t be able to associate the VMs existing in the old region to the newly created Standard Load Balancer. To work around this limitation, make sure to create a new VM in the new region.
 * If your Load Balancer does not have any frontend IP configuration or backend pool, you are likely to hit an error running the script. Make sure they are not empty.
 
@@ -42,7 +43,7 @@ An Azure PowerShell script is available that does the following:
 
 ## Download the script
 
-Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzureILBUpgrade/2.0).
+Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzureILBUpgrade/3.0).
 ## Use the script
 
 There are two options for you depending on your local PowerShell environment setup and preferences:

articles/machine-learning/concept-designer.md

@@ -78,7 +78,7 @@ A module may have a set of parameters that you can use to configure the module's
 
 ![Module properties](./media/concept-designer/properties.png)
 
-For some help navigating through the library of machine learning algorithms available, see [Algorithm & module reference overview](algorithm-module-reference/module-reference.md)
+For some help navigating through the library of machine learning algorithms available, see [Algorithm & module reference overview](algorithm-module-reference/module-reference.md). For help choosing an algorithm, see the [Azure Machine Learning Algorithm Cheat Sheet](algorithm-cheat-sheet.md).
 
 ## <a name="compute"></a> Compute resources
 
@@ -90,7 +90,7 @@ Use compute resources from your workspace to run your pipeline and host your dep
 | Azure Machine Learning compute instance | ✓ | |
 | Azure Kubernetes Service | | ✓ |
 
-Compute targets are attached to your [Azure Machine Learning workspace](concept-workspace.md). You manage your compute targets in your workspace in [Azure Machine Learning Studio (classic)](https://ml.azure.com).
+Compute targets are attached to your [Azure Machine Learning workspace](concept-workspace.md). You manage your compute targets in your workspace in the [Azure Machine Learning studio](https://ml.azure.com).
 
 ## Deploy
 

articles/marketplace/preferred-solutions.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Marketplace and AppSource preferred solutions
-description: Overview of preferred solutions within the Marketplace and how they are selected
+title: Azure Marketplace and AppSource preferred solutions - Microsoft commercial marketplace
+description: Preferred solutions within the Marketplace and how they are selected
 author: dsindona
 ms.service: marketplace
 ms.subservice: partnercenter-marketplace-publisher
@@ -9,6 +9,6 @@ ms.date: 06/27/2018
 ms.author: dsindona
 ---
 
-# Preferred Solutions in Azure Marketplace and AppSource
+# Preferred solutions in Microsoft AppSource and Azure Marketplace
 
 A Microsoft preferred solution is a cloud application selected for its quality, performance, and ability to address customer needs in a certain industry vertical or solution area. A team of Microsoft experts validates solutions from partners with specific proven competencies and capabilities. These solutions are featured in our cloud marketplace storefronts, Azure Marketplace, and AppSource, as well as in the Azure portal. Preferred solutions on AppSource can be discovered by industry verticals. Preferred solutions on Azure Marketplace and the Azure portal can be discovered across horizontal solution categories.

articles/marketplace/private-offers.md

@@ -1,6 +1,6 @@
 ---
-title: Private offers | Azure Marketplace
-description: Private offers in the Azure Marketplace for app and service publishers.
+title: Private offers in Microsoft commercial marketplace
+description: Private offers in the Microsoft commercial marketplace for app and service publishers.
 author: qianw211
 ms.service: marketplace
 ms.subservice: partnercenter-marketplace-publisher
@@ -9,9 +9,9 @@ ms.date: 04/19/2020
 ms.author: dsindona
 ---
 
-# Private offers
+# Private offers in the Microsoft commercial marketplace
 
-Private offers on [Microsoft Azure Marketplace](https://azuremarketplace.microsoft.com/) enable publishers to create SKUs that are only visible to targeted customers.
+Private offers in [Microsoft Azure Marketplace](https://azuremarketplace.microsoft.com/) enable publishers to create plans that are only visible to targeted customers. In this article, you'll learn about the options and benefits of private offers.
 
 ## Unlock enterprise deals with private offers
 

articles/marketplace/publisher-guide-by-offer-type.md

@@ -1,6 +1,6 @@
 ---
-title: Microsoft commercial marketplace publishing guide by offer type
-description: This article describes the offer types available in the Microsoft commercial marketplace.
+title: Publishing guide by offer type - Microsoft commercial marketplace
+description: This article describes the offer types that are available in the Microsoft commercial marketplace.
 author: dsindona
 ms.service: marketplace
 ms.subservice: partnercenter-marketplace-publisher
@@ -11,13 +11,11 @@ ms.author: dsindona
 
 # Publishing guide by offer type
 
-Once you [decide on a publishing option](https://docs.microsoft.com/azure/marketplace/determine-your-listing-type), you are ready to select the offer type that will be used to present your offer.
+This article describes the offer types that are available in the commercial marketplace. The *offer type* defines the offer structure, which includes the metadata, artifacts, and other content used to present the offer in the marketplace.
 
- The *offer type* defines the offer structure, which includes the metadata, artifacts, and other content used to present the offer in the marketplace.
+Before you can create an offer, and after you [decide on a publishing option](https://docs.microsoft.com/azure/marketplace/determine-your-listing-type), you must choose an offer type that will be used to present your offer. The offer type will correspond to the type of solution, app, or service offer that you wish to publish, as well as its alignment to Microsoft products and services.
 
-Before you can create an offer, you must choose an offer type. The offer type will correspond to the type of solution, app, or service offer that you wish to publish, as well as its alignment to Microsoft products and services.
-
-A single offer type can be configured differently to enable different publishing options, calls-to-action, provisioning, or pricing. The publishing option and configuration of the offer type also align to the offer eligibility and technical requirements.
+A single offer type can be configured in different ways to enable different publishing options, calls-to-action, provisioning, or pricing. The publishing option and configuration of the offer type also align to the offer eligibility and technical requirements.
 
 Be sure to review the storefront and offer type eligibility requirements and the technical publishing requirements before creating your offer.
 

articles/marketplace/standard-contract.md

@@ -1,6 +1,6 @@
 ---
-title: Standard Contract | Azure Marketplace
-description: Standard Contract for Azure Marketplace and AppSource
+title: Standard Contract for Microsoft commercial marketplace
+description: Standard Contract for Azure Marketplace and AppSource in Partner Center
 author: dsindona
 ms.service: marketplace
 ms.subservice: partnercenter-marketplace-publisher
@@ -9,9 +9,9 @@ ms.date: 04/14/2020
 ms.author: dsindona
 ---
 
-# Standard Contract for the Microsoft commercial marketplace
+# Standard Contract for Microsoft commercial marketplace
 
-To simplify the procurement process for customers and reduce legal complexity for software vendors, Microsoft offers a Standard Contract for the Microsoft commercial marketplace in order to help facilitate transactions in the marketplace. Rather than crafting custom terms and conditions, commercial marketplace publishers can choose to offer their software under the Standard Contract, which customers only need to vet and accept once. The Standard Contract can be found here: [https://go.microsoft.com/fwlink/?linkid=2041178](https://go.microsoft.com/fwlink/?linkid=2041178).
+Microsoft offers a Standard Contract for Microsoft commercial marketplace. This helps to simplify the procurement process for customers,  reduce legal complexity for software vendors, and facilitate transactions in the marketplace. Rather than crafting custom terms and conditions, as a commercial marketplace publisher, you can choose to offer your software under the [Standard Contract](https://go.microsoft.com/fwlink/?linkid=2041178), which customers only need to vet and accept one time.
 
 The terms and conditions for an offer are defined when creating the offer in Partner Center. You can select to use the Standard Contract for the Microsoft commercial marketplace instead of providing your own custom terms and conditions.
 
@@ -35,7 +35,7 @@ You can leverage the Standard Contract for the Microsoft commercial marketplace
 
 ## Customer experience
 
-During the discovery experience in Azure marketplace or AppSource, customers will be able to see the terms associated with the offer as the Standard Contract for the Microsoft commercial marketplace and any universal amendments.
+During the discovery experience in Azure Marketplace or AppSource, customers will be able to see the terms associated with the offer as the Standard Contract for the Microsoft commercial marketplace and any universal amendments.
 
 ![The Azure portal customer discovery experience.](media/marketplace-publishers-guide/azure-discovery-process.png)