Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into ds-updatetoc1

Author: davidsmatlak

articles/active-directory/hybrid/how-to-connect-sync-endpoint-api-v2.md

@@ -8,7 +8,7 @@ editor: ''
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 05/19/2020
+ms.date: 05/20/2020
 ms.subservice: hybrid
 ms.author: billmath
 ms.collection: M365-identity-device-management
@@ -27,6 +27,9 @@ Microsoft has deployed a new endpoint (API) for Azure AD Connect that improves t
 ## Pre-requisites  
 In order to use the new V2 endpoint, you will need to use [Azure AD Connect version 1.5.30.0](https://www.microsoft.com/download/details.aspx?id=47594) or later and follow the deployment steps provided below to enable the V2 endpoint for your Azure AD Connect server.   
 
+>[!NOTE]
+>Currently, this public preview is only available in the Azure global cloud and not available for [national clouds](https://docs.microsoft.com/azure/active-directory/develop/authentication-national-cloud).
+
 ### Public preview limitations  
 While this release has undergone extensive testing, you may still encounter issues. One of the goals of this public preview release is to find and fix any such issues.  
 

articles/active-directory/managed-identities-azure-resources/known-issues.md

@@ -46,27 +46,7 @@ The security boundary of the identity is the resource to which it is attached to
 - If system assigned managed identity is not enabled, and only one user assigned managed identity exists, IMDS will default to that single user assigned managed identity. 
 - If system assigned managed identity is not enabled, and multiple user assigned managed identities exist, then specifying a managed identity in the request is required.
 
-### Should I use the managed identities for Azure resources IMDS endpoint or the VM extension endpoint?
 
-When using managed identities for Azure resources with VMs, we recommend using the IMDS endpoint. The Azure Instance Metadata Service is a REST Endpoint accessible to all IaaS VMs created via the Azure Resource Manager. 
-
-Some of the benefits of using managed identities for Azure resources over IMDS are:
-- All Azure IaaS supported operating systems can use managed identities for Azure resources over IMDS.
-- No longer need to install an extension on your VM to enable managed identities for Azure resources. 
-- The certificates used by managed identities for Azure resources are no longer present in the VM.
-- The IMDS endpoint is a well-known non-routable IP address, only available from within the VM.
-- 1000 user-assigned managed identities can be assigned to a single VM. 
-
-The managed identities for Azure resources VM extension is still available; however, we are no longer developing new functionality on it. We recommend switching to use the IMDS endpoint. 
-
-Some of the limitations of using the VM extension endpoint are:
-- Limited support for Linux distributions: CoreOS Stable, CentOS 7.1, Red Hat 7.2, Ubuntu 15.04, Ubuntu 16.04
-- Only 32 user-assigned managed identities can be assigned to the VM.
-
-
-Note: The managed identities for Azure resources VM extension will be out of support in January 2019. 
-
-For more information on Azure Instance Metadata Service, see [IMDS documentation](https://docs.microsoft.com/azure/virtual-machines/windows/instance-metadata-service)
 
 ### Will managed identities be recreated automatically if I move a subscription to another directory?
 
@@ -83,16 +63,7 @@ No. Managed identities do not currently support cross-directory scenarios.
 - System-assigned managed identity: You need write permissions over the resource. For example, for virtual machines you need Microsoft.Compute/virtualMachines/write. This action is included in resource specific built-in roles like [Virtual Machine Contributor](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#virtual-machine-contributor).
 - User-assigned managed identity: You need write permissions over the resource. For example, for virtual machines you need Microsoft.Compute/virtualMachines/write. In addition to [Managed Identity Operator](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#managed-identity-operator) role assignment over the managed identity.
 
-### How do you restart the managed identities for Azure resources extension?
-On Windows and certain versions of Linux, if the extension stops, the following cmdlet may be used to manually restart it:
-
-```powershell
-Set-AzVMExtension -Name <extension name>  -Type <extension Type>  -Location <location> -Publisher Microsoft.ManagedIdentity -VMName <vm name> -ResourceGroupName <resource group name> -ForceRerun <Any string different from any last value used>
-```
 
-Where: 
-- Extension name and type for Windows is: ManagedIdentityExtensionForWindows
-- Extension name and type for Linux is: ManagedIdentityExtensionForLinux
 
 ## Known issues
 
@@ -128,12 +99,7 @@ Once the VM is started, the tag can be removed by using following command:
 az vm update -n <VM Name> -g <Resource Group> --remove tags.fixVM
 ```
 
-### VM extension provisioning fails
 
-Provisioning of the VM extension might fail due to DNS lookup failures. Restart the VM, and try again.
- 
-> [!NOTE]
-> The VM extension is planned for deprecation by January 2019. We recommend you move to using the IMDS endpoint.
 
 ### Transferring a subscription between Azure AD directories
 
@@ -146,4 +112,4 @@ Workaround for managed identities in a subscription that has been moved to anoth
 
 ### Moving a user-assigned managed identity to a different resource group/subscription
 
-Moving a user-assigned managed identity to a different resource group will cause the identity to break. As a result, resources (e.g. VM) using that identity will not be able to request tokens for it. 
+Moving a user-assigned managed identity to a different resource group is not supported.

articles/cognitive-services/LUIS/luis-interactive-test.md

@@ -2,7 +2,7 @@
 title: Test app in LUIS portal
 description: Use Language Understanding (LUIS) to continuously work on your application to refine it and improve its language understanding.
 ms.topic: conceptual
-ms.date: 05/17/2020
+ms.date: 05/20/2020
 ---
 
 # Test your LUIS app in the LUIS portal
@@ -37,18 +37,23 @@ The test utterance should not be exactly the same as any example utterances in t
 
 1. The utterance, its top intent, and score are added to the list of utterances under the text box.
 
-    ![Interactive testing identifies the wrong intent](./media/luis-how-to-interactive-test/test-weather-1.png)
+    > [!div class="mx-imgBorder"]
+    > ![Interactive testing identifies the wrong intent](./media/luis-how-to-interactive-test/test-weather-1.png)
 
 ## Inspect the prediction
 
 You inspect details of the test result in the **Inspect** panel.
 
 1. With the **Test** slide-out panel open, select **Inspect** for an utterance you want to compare.
 
-    ![Select Inspect button to see more details about the test results](./media/luis-how-to-interactive-test/inspect.png)
+    > [!div class="mx-imgBorder"]
+    > ![Select Inspect button to see more details about the test results](./media/luis-how-to-interactive-test/inspect.png)
 
 1. The **Inspection** panel appears. The panel includes the top scoring intent as well as any identified entities. The panel shows the prediction of the selected utterance.
 
+    > [!div class="mx-imgBorder"]
+    > ![Partial screenshot of Test Inspect panel](./media/luis-how-to-interactive-test/inspect-panel.png)
+
 ## Add to example utterances
 
 From the inspection panel, you can add the test utterance to an intent by selecting **Add to example utterances**.
@@ -71,12 +76,14 @@ If you are using [Patterns](luis-concept-patterns.md) and the utterance matched
 
 You can test the active version of your app with the published [endpoint](luis-glossary.md#endpoint) version. In the **Inspect** panel, select **Compare with published**. Any testing against the published model is deducted from your Azure subscription quota balance.
 
-![Compare with published](./media/luis-how-to-interactive-test/inspect-panel-compare.png)
+> [!div class="mx-imgBorder"]
+> ![Compare with published](./media/luis-how-to-interactive-test/inspect-panel-compare.png)
 
 ## View endpoint JSON in test panel
 You can view the endpoint JSON returned for the comparison by selecting the **Show JSON view**.
 
-![Published JSON response](./media/luis-how-to-interactive-test/inspect-panel-compare-json.png)
+> [!div class="mx-imgBorder"]
+> ![Published JSON response](./media/luis-how-to-interactive-test/inspect-panel-compare-json.png)
 
 ## Additional settings in test panel
 

articles/cognitive-services/LUIS/media/luis-how-to-interactive-test/inspect-panel-compare-json.png

@@ -76,7 +76,7 @@ Begin by configuring your new app and linking it to a GitHub repository.
 - Select your _Azure subscription_
 - Select or create a new _Resource Group_
 - Name the app **my-first-static-web-app**.
-  - Valid characters are `a-z` (case insensitive), `0-9`, and `_`.
+  - Valid characters are `a-z` (case insensitive), `0-9`, and `-`.
 - Select a _Region_ closest to you
 - Select the **Free** _SKU_
 - Click the **Sign-in with GitHub** button and authenticate with GitHub

articles/cognitive-services/LUIS/media/luis-how-to-interactive-test/inspect-panel-compare.png

@@ -39,7 +39,7 @@ The transaction safety limits only apply to fully logged operations.
 
 The following operations are capable of being minimally logged:
 
-* CREATE TABLE AS SELECT ([CTAS](../sql-data-warehouse/sql-data-warehouse-develop-ctas.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json)
+* CREATE TABLE AS SELECT ([CTAS])(../sql-data-warehouse/sql-data-warehouse-develop-ctas.md?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json)
 * INSERT..SELECT
 * CREATE INDEX
 * ALTER INDEX REBUILD

articles/cognitive-services/LUIS/media/luis-how-to-interactive-test/inspect-panel.png

@@ -5,16 +5,16 @@
  author: tamram
  ms.service: storage
  ms.topic: include
- ms.date: 03/13/2020
+ ms.date: 05/20/2020
  ms.author: tamram
  ms.custom: include file
 ---
 
-The following table describes default limits for Azure general-purpose v1, v2, Blob storage, block blob storage, and Data Lake Storage Gen2 enabled storage accounts. The *ingress* limit refers to all data that is sent to a storage account. The *egress* limit refers to all data that is received from a storage account.
+The following table describes default limits for Azure general-purpose v1, v2, Blob storage, and block blob storage accounts. The *ingress* limit refers to all data that is sent to a storage account. The *egress* limit refers to all data that is received from a storage account.
 
 | Resource | Limit |
 | --- | --- |
-| Number of storage accounts per region per subscription, including standard, premium, and Data Lake Storage Gen2 enabled storage accounts.<sup>3</sup> | 250 |
+| Number of storage accounts per region per subscription, including standard, and premium storage accounts.| 250 |
 | Maximum storage account capacity | 5 PiB <sup>1</sup>|
 | Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account | No limit |
 | Maximum request rate<sup>1</sup> per storage account | 20,000 requests per second |
@@ -32,8 +32,6 @@ The following table describes default limits for Azure general-purpose v1, v2, B
 
 [!INCLUDE [azure-storage-redundancy](azure-storage-redundancy.md)]
 
-<sup>3</sup> [Azure Data Lake Storage Gen2](../articles/storage/blobs/data-lake-storage-introduction.md) is a set of capabilities dedicated to big data analytics, built on Azure Blob storage. Azure Storage and blob storage limitations apply to Data Lake Storage Gen2.
-
 > [!NOTE]
 > Microsoft recommends that you use a general-purpose v2 storage account for most scenarios. You can easily upgrade a general-purpose v1 or an Azure Blob storage account to a general-purpose v2 account with no downtime and without the need to copy data. For more information, see [Upgrade to a general-purpose v2 storage account](../articles/storage/common/storage-account-upgrade.md).