Merge pull request #107121 from MicrosoftDocs/master

3/10 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -15275,6 +15275,41 @@
       "redirect_url": "/azure/machine-learning/how-to-designer-sample-classification-flight-delay",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/machine-learning/how-to-designer-sample-classification-churn.md",
+      "redirect_url": "/azure/machine-learning/samples-designer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/machine-learning/how-to-designer-sample-classification-credit-risk-cost-sensitive.md",
+      "redirect_url": "/azure/machine-learning/samples-designer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/machine-learning/how-to-designer-sample-classification-flight-delay.md",
+      "redirect_url": "/azure/machine-learning/samples-designer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/machine-learning/how-to-designer-sample-classification-predict-income.md",
+      "redirect_url": "/azure/machine-learning/samples-designer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/machine-learning/how-to-designer-sample-regression-automobile-price-basic.md",
+      "redirect_url": "/azure/machine-learning/samples-designer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/machine-learning/how-to-designer-sample-regression-automobile-price-compare-algorithms.md",
+      "redirect_url": "/azure/machine-learning/samples-designer",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/machine-learning/how-to-designer-sample-text-classification.md",
+      "redirect_url": "/azure/machine-learning/samples-designer",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/log-analytics/log-analytics-add-solutions.md",
       "redirect_url": "/azure/monitoring/monitoring-solutions",
@@ -49215,6 +49250,11 @@
       "source_path": "articles/cognitive-services/Speech-Service/how-to-use-codec-compressed-audio-input-streams-ios.md",
       "redirect_url": "/azure/cognitive-services/Speech-Service/how-to-use-codec-compressed-audio-input-streams?pivots=programming-language-objectivec",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/power-bi-embedded/index.md",
+      "redirect_url": "https://docs.microsoft.com/power-bi/developer/azure-pbie-what-is-power-bi-embedded",
+      "redirect_document_id": false
     }
   ]
 }

articles/active-directory/develop/vs-active-directory-dotnet-what-happened.md

@@ -18,13 +18,13 @@ ms.custom: aaddev, vs-azure
 > - [Getting Started](vs-active-directory-dotnet-getting-started.md)
 > - [What Happened](vs-active-directory-dotnet-what-happened.md)
 
-This article identifies the exact changes made to am ASP.NET MVC project when adding the [Azure Active Directory connected service using Visual Studio](vs-active-directory-add-connected-service.md).
+This article identifies the exact changes made to an ASP.NET MVC project when adding the [Azure Active Directory connected service using Visual Studio](vs-active-directory-add-connected-service.md).
 
 For information on working with the connected service, see [Getting Started](vs-active-directory-dotnet-getting-started.md).
 
 ## Added references
 
-Affects the project file *.NET references) and `packages.config` (NuGet references).
+Affects the project file (*.NET references) and `packages.config` (NuGet references).
 
 | Type | Reference |
 | --- | --- |

articles/active-directory/hybrid/how-to-connect-fix-default-rules.md

@@ -68,7 +68,7 @@ If the extensions don't work for you, try adding two new sync rules, described i
 #### Add an inbound sync rule
 An inbound sync rule means the source for the attribute is a connector space, and the target is the metaverse. For example, to have a new attribute flow from on-premises Active Directory to Azure Active Directory, create a new inbound sync rule. Launch the **Synchronization Rules Editor**, select **Inbound** as the direction, and select **Add new rule**. 
 
- !Synchronization Rules Editor](media/how-to-connect-fix-default-rules/default3a.png)
+ ![Synchronization Rules Editor](media/how-to-connect-fix-default-rules/default3a.png)
 
 Follow your own naming convention to name the rule. Here, we use **Custom In from AD - User**. This means that the rule is a custom rule, and is an inbound rule from the Active Directory connector space to the metaverse.   
 

articles/active-directory/identity-protection/concept-identity-protection-risks.md

@@ -27,7 +27,7 @@ Identity Protection provides organizations access to powerful resources to see a
 
 There are two types of risk **User** and **Sign-in** and two types of detection or calculation **Real-time** and **Offline**.
 
-### User risk'
+### User risk
 
 A user risk represents the probability that a given identity or account is compromised. 
 
@@ -38,7 +38,7 @@ These risks are calculated offline using Microsoft's internal and external threa
 | Leaked credentials | This risk detection type indicates that the user's valid credentials have been leaked. When cybercriminals compromise valid passwords of legitimate users, they often share those credentials. This sharing is typically done by posting publicly on the dark web, paste sites, or by trading and selling the credentials on the black market. When the Microsoft leaked credentials service acquires user credentials from the dark web, paste sites, or other sources, they are checked against Azure AD users' current valid credentials to find valid matches. |
 | Azure AD threat intelligence | This risk detection type indicates user activity that is unusual for the given user or is consistent with known attack patterns based on Microsoft's internal and external threat intelligence sources. |
 
-### Sign-in risk'
+### Sign-in risk
 
 A sign-in risk represents the probability that a given authentication request isn't authorized by the identity owner. 
 
@@ -66,4 +66,4 @@ These risks can be calculated in real-time or calculated offline using Microsoft
 - [Policies available to mitigate risks](concept-identity-protection-policies.md)
 
 - [Security overview](concept-identity-protection-security-overview.md)
-""'
+""'

articles/active-directory/manage-apps/application-proxy-qlik.md

@@ -47,7 +47,7 @@ Follow these steps to publish your app. For a more detailed walkthrough of steps
 ### Application #2: 
 Follow the same steps as for Application #1, with the following exceptions: 
 
-**Step #5**: The Internal URL should now be the QlikSense URL with the authentication port used by the application. The default is **4244** for HTTPS, and **4248** for HTTP for QlikSense releases prior to April 2018. The default for QlikSense releases after April 2018 is **443** for HTTPS and **80** for HTTP.  Ex: **https&#58;//demo.qlik.com:4244**</br></br> 
+**Step #5**: The Internal URL should now be the QlikSense URL with the authentication port used by the application. The default is **4244** for HTTPS, and **4248** for HTTP for QlikSense releases prior to April 2018. The default for QlikSense releases after April 2018 is **443** for HTTPS and **80** for HTTP.  Ex: **https&#58;//demo.qlik.com:4244**</br></br>
 **Step #10:** Don’t set up SSO, and leave the **Single sign-on disabled**
 
 

articles/active-directory/saas-apps/sharepoint-on-premises-tutorial.md

@@ -270,7 +270,7 @@ The objective of this section is to create a test user in the Azure portal calle
 10. Configure the AzureCP on the SharePoint on-premises farm or an alternative custom claims provider solution.  In this example, we are using AzureCP.
 
 	> [!NOTE]
-	> Please note that AzureCP is not a Microsoft product or supported by Microsoft Technical Support. Download, install and configure AzureCP on the on-premises SharePoint farm per https://yvand.github.io/AzureCP/ 
+	> Please note that AzureCP is not a Microsoft product or supported by Microsoft Technical Support. Download, install and configure AzureCP on the on-premises SharePoint farm per [https://yvand.github.io/AzureCP/](https://yvand.github.io/AzureCP/) 
 
 11. **Grant access to the Azure Active Directory Security Group in the on-premises SharePoint** :- The groups must be granted access to the application in SharePoint on-premises.  Use the following steps to set the permissions to access the web application.
 

articles/app-service/networking/private-endpoint.md

@@ -1,6 +1,6 @@
 ---
-title: Connect privately to a Web App and secure data exfiltration using Azure Private Endpoint
-description: Connect privately to a Web App and secure data exfiltration using Azure Private Endpoint
+title: Connect privately to a Web App using Azure Private Endpoint
+description: Connect privately to a Web App using Azure Private Endpoint
 author: ericgre
 ms.assetid: 2dceac28-1ba6-4904-a15d-9e91d5ee162c
 ms.topic: article
@@ -13,16 +13,14 @@ ms.workload: web
 
 # Using Private Endpoints for Azure Web App (Preview)
 
-You can use Private Endpoint for your Azure Web App to allow clients located in your private network to securely access to the app over Private Link. The Private Endpoint uses an IP address from your Azure VNet address space. Network traffic between client on your private network and the Web App traverses over the Vnet and a Private Link on the Microsoft backbone network, eliminating exposure from the public Internet. With Private Endpoint, you can disable outgoing network flows from the subnet with NSG and eliminate the data leakage risk.
+You can use Private Endpoint for your Azure Web App to allow clients located in your private network to securely access to the app over Private Link. The Private Endpoint uses an IP address from your Azure VNet address space. Network traffic between client on your private network and the Web App traverses over the Vnet and a Private Link on the Microsoft backbone network, eliminating exposure from the public Internet.
 
 Using Private Endpoint for your Web App enables you to:
 
 - Secure your Web App by configuring the Service Endpoint, eliminating public exposure
-- Increase security for the Vnet by enabling you to block data exfiltration from the Vnet
 - Securely connect to Web App from on-premises networks that connect to the Vnet using a VPN or ExpressRoute private peering.
 
-If you just need a secure connection between your Vnet and your Web App, Service Endpoint is the simplest solution. 
-If you need to protect against data exfiltration or route access from on-premises, Private Endpoint is the solution.
+If you just need a secure connection between your Vnet and your Web App, Service Endpoint is the simplest solution. If you also need to reach the web app from on-premises through an Azure gateway, a regionally peered Vnet or a globally peered Vnet, Private Endpoint is the solution.  
 
 For more information about [Service Endpoint][serviceendpoint]
 
@@ -33,22 +31,24 @@ When you create a Private Endpoint for your Web App, it provides a secure connec
 The connection between the Private Endpoint and the Web App uses a secure [Private Link][privatelink]. Private endpoint is only used for incoming flows to your Web App. Outgoing flows will not use this Private Endpoint, but you can inject outgoing flows to your network in a different subnet through the [Vnet integration feature][vnetintegrationfeature].
 
 The Subnet where you plug the Private Endpoint can have other resources in it, you don't need a dedicated empty Subnet.
-You can deploy Private Endpoint in region A for the Web App deployed in region B. 
+You can deploy Private Endpoint in a different region than the Web App. 
 
 > [!Note]
 >The Vnet integration feature cannot use the same subnet than Private Endpoint, this is a limitation of the Vnet integration feature
 
 From the security perspective:
 
 - When you enable Service Endpoint to your Web App, you disable all public access
-- You can enable multiple Private Endpoints in others Vnets and Subnets
+- You can enable multiple Private Endpoints in others Vnets and Subnets, including Vnets in other regions
+- The IP address of the Private endpoint NIC must be dynamic, but will remain the same until you delete the Private Endpoint
 - The NIC of the Private Endpoint cannot have an NSG associated
-- The Subnet that hosts the Private Endpoint can have an NSG associated, but you must disable the network policies enforcement for the Private Endpoint see [this article] [disablesecuritype]. As a result, you cannot filter by any NSG the access to your Private Endpoint.
+- The Subnet that hosts the Private Endpoint can have an NSG associated, but you must disable the network policies enforcement for the Private Endpoint see [this article][disablesecuritype]. As a result, you cannot filter by any NSG the access to your Private Endpoint
 - When you enable Private Endpoint to your Web App, the [access restrictions][accessrestrictions] configuration of the Web App is not evaluated.
+- You can reduce data exfiltration risk from the vnet by removing all NSG rules where destination is tag Internet or Azure services. But adding a Web App Service Endpoint in your subnet, will let you reach any Web App hosted in the same stamp and exposed to Internet.
 
 Private Endpoint for Web App is available for tier PremiumV2, and Isolated with an external ASE.
 
-In the Web http logs of your Web App, you will discover that we are aware of the client source IP. We implemented the TCP Proxy protocol, forwarding up to the Web App the client IP. For more information, see [this article][tcpproxy].
+In the Web http logs of your Web App, you will find the client source IP. We implemented the TCP Proxy protocol, forwarding up to the Web App the client IP property. For more information, see [this article][tcpproxy].
 
 ![Global overview][1]
 

articles/azure-monitor/platform/alerts-enable-template.md

@@ -4,17 +4,16 @@ description: Learn how to use a Resource Manager template to create a classic me
 author: rboucher
 ms.author: robb
 ms.topic: conceptual
-ms.date: 4/27/2018
+ms.date: 03/09/2020
 ms.subservice: alerts
 ---
 # Create a classic metric alert with a Resource Manager template
-This article shows how you can use an [Azure Resource Manager template](../../azure-resource-manager/templates/template-syntax.md) to configure Azure metric alerts. This enables you to automatically set up alerts on your resources when they are created to ensure that all resources are monitored correctly.
-
-> [!NOTE]
+> [!WARNING]
 > 
-> This article describes creating **classic metric alerts** using Resource Manager templates. If you are looking for creating [newer metric alerts](../../azure-monitor/platform/alerts-metric-near-real-time.md) using templates, [this article](alerts-metric-create-templates.md) provides the details.
+> This article describes creating **classic metric alerts** using Resource Manager templates. Classic alerts were retired in August 2019 and set to be fully deprecated in June 2020. You cannot create new classic alerts public Azure. Some regional versions of Azure may still have the option, but we suggest you instead create [newer metric alerts](../../azure-monitor/platform/alerts-metric-near-real-time.md) using templates if at all possible. [This article](alerts-metric-create-templates.md) provides the details.
 >
 
+This article shows how you can use an [Azure Resource Manager template](../../azure-resource-manager/templates/template-syntax.md) to configure Azure classic metric alerts. This enables you to automatically set up alerts on your resources when they are created to ensure that all resources are monitored correctly.
 
 The basic steps are as follows:
 

articles/cognitive-services/Computer-vision/computer-vision-how-to-install-containers.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: computer-vision
 ms.topic: conceptual
-ms.date: 11/21/2019
+ms.date: 03/10/2020
 ms.author: pafarley
 ms.custom: seodec18
 ---
@@ -149,71 +149,26 @@ The `operation-location` is the fully qualified URL and is accessed via an HTTP
       "unit": "pixel",
       "lines": [
         {
-          "boundingBox": [
-            56,
-            39,
-            317,
-            50,
-            313,
-            134,
-            53,
-            123
-          ],
+          "boundingBox": [ 56, 39, 317, 50, 313, 134, 53, 123 ],
           "text": "Tabs VS",
           "words": [
             {
-              "boundingBox": [
-                90,
-                43,
-                243,
-                53,
-                243,
-                123,
-                94,
-                125
-              ],
+              "boundingBox": [ 90, 43, 243, 53, 243, 123, 94, 125 ],
               "text": "Tabs",
               "confidence": "Low"
             },
             {
-              "boundingBox": [
-                259,
-                55,
-                313,
-                62,
-                313,
-                122,
-                259,
-                123
-              ],
+              "boundingBox": [ 259, 55, 313, 62, 313, 122, 259, 123 ],
               "text": "VS"
             }
           ]
         },
         {
-          "boundingBox": [
-            221,
-            148,
-            417,
-            146,
-            417,
-            206,
-            227,
-            218
-          ],
+          "boundingBox": [ 221, 148, 417, 146, 417, 206, 227, 218 ],
           "text": "Spaces",
           "words": [
             {
-              "boundingBox": [
-                230,
-                148,
-                416,
-                141,
-                419,
-                211,
-                232,
-                218
-              ],
+              "boundingBox": [ 230, 148, 416, 141, 419, 211, 232, 218 ],
               "text": "Spaces"
             }
           ]

articles/cognitive-services/Speech-Service/includes/audio-input-format-chart.md

@@ -2,19 +2,20 @@
 title: Audio input format
 titleSuffix: Azure Cognitive Services
 services: cognitive-services
-author: markamos
+author: IEvangelist
 manager: nitinme
-
 ms.service: cognitive-services
-ms.topic: include 
-ms.date: 11/20/2019
-ms.author: erhopf
+ms.topic: include
+ms.date: 03/10/2020
+ms.author: dapine
 ---
 
 ## Supported audio input format
 
 The Speech SDK uses the following format for audio input.
 
-| Format | Codec | Bitrate | Sample Rate | Channels |
-|--------|-------|---------|-------------|----------|
-| WAV | PCM | 16-bit | 8 kHz or 16 kHz | 1 (mono) |
+| Format | Codec | Bitrate | Sample Rate     | Channels |
+|--------|-------|---------|-----------------|----------|
+| WAV    | PCM   | 16-bit  | 8 kHz or 16 kHz | 1 (mono) |
+
+[!INCLUDE [supported-audio-formats](supported-audio-formats.md)]