Merge pull request #80925 from MicrosoftDocs/master

6/28 AM Publish

Author: huypub

articles/active-directory/develop/registration-config-sso-how-to.md

@@ -1,5 +1,5 @@
 ---
-title: How to configure a new multi-tenant application | Microsoft Docs
+title: How to configure single sign-on | Microsoft Docs
 description: How to configure single sign-on for a custom application you are developing and registering with Azure AD.
 services: active-directory
 documentationcenter: ''
@@ -19,7 +19,7 @@ ms.author: ryanwi
 ms.collection: M365-identity-device-management
 ---
 
-# How to configure a new multi-tenant application
+# How to configure single sign-on for an application
 
 Enabling federated single sign-on (SSO) in your app is automatically enabled when federating through Azure AD for OpenID Connect, SAML 2.0, or WS-Fed. If your end users are having to sign in despite already having an existing session with Azure AD, it’s likely your app may be misconfigured.
 

articles/aks/istio-install.md

@@ -79,6 +79,8 @@ In PowerShell, use `Invoke-WebRequest` to download the latest Istio release and
 $ISTIO_VERSION="1.1.3"
 
 # Windows
+# Use TLS 1.2
+[Net.ServicePointManager]::SecurityProtocol = "tls12"
 $ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -URI "https://github.com/istio/istio/releases/download/$ISTIO_VERSION/istio-$ISTIO_VERSION-win.zip" -OutFile "istio-$ISTIO_VERSION.zip"
 Expand-Archive -Path "istio-$ISTIO_VERSION.zip" -DestinationPath .
 ```
@@ -566,4 +568,4 @@ To learn how to monitor your AKS application using Application Insights and Isti
 <!-- LINKS - internal -->
 [aks-quickstart]: ./kubernetes-walkthrough.md
 [istio-scenario-routing]: ./istio-scenario-routing.md
-[helm-install]: ./kubernetes-helm.md
+[helm-install]: ./kubernetes-helm.md

articles/azure-databricks/databricks-extract-load-sql-data-warehouse.md

@@ -35,7 +35,7 @@ If you don’t have an Azure subscription, create a [free account](https://azure
 
 > [!Note]
 > This tutorial cannot be carried out using **Azure Free Trial Subscription**.
-> If you have a free account, go to your profile and change your subscription to **pay-as-you-go**. For more information, see [Azure free account](https://azure.microsoft.com/free/). Then, [remove the spending limit](https://docs.microsoft.com/en-us/azure/billing/billing-spending-limit#remove-the-spending-limit-in-account-center), and [request a quota increase](https://docs.microsoft.com/en-us/azure/azure-supportability/resource-manager-core-quotas-request) for vCPUs in your region. When you create your Azure Databricks workspace, you can select the **Trial (Premium - 14-Days Free DBUs)** pricing tier to give the workspace access to free Premium Azure Databricks DBUs for 14 days.
+> If you have a free account, go to your profile and change your subscription to **pay-as-you-go**. For more information, see [Azure free account](https://azure.microsoft.com/free/). Then, [remove the spending limit](https://docs.microsoft.com/azure/billing/billing-spending-limit#remove-the-spending-limit-in-account-center), and [request a quota increase](https://docs.microsoft.com/azure/azure-supportability/resource-manager-core-quotas-request) for vCPUs in your region. When you create your Azure Databricks workspace, you can select the **Trial (Premium - 14-Days Free DBUs)** pricing tier to give the workspace access to free Premium Azure Databricks DBUs for 14 days.
      
 ## Prerequisites
 

articles/azure-monitor/app/proactive-diagnostics.md

@@ -14,9 +14,9 @@ ms.date: 02/07/2019
 ms.author: mbullwin
 ---
 # Smart Detection in Application Insights
- Smart Detection automatically warns you of potential performance problems in your web application. It performs proactive analysis of the telemetry that your app sends to [Application Insights](../../azure-monitor/app/app-insights-overview.md). If there is a sudden rise in failure rates, or abnormal patterns in client or server performance, you get an alert. This feature needs no configuration. It operates if your application sends enough telemetry.
+ Smart Detection automatically warns you of potential performance problems and failure anomalies in your web application. It performs proactive analysis of the telemetry that your app sends to [Application Insights](../../azure-monitor/app/app-insights-overview.md). If there is a sudden rise in failure rates, or abnormal patterns in client or server performance, you get an alert. This feature needs no configuration. It operates if your application sends enough telemetry.
 
-You can access Smart Detection alerts both from the emails you receive, and from the Smart Detection blade.
+You can access the detections issued by Smart Detection both from the emails you receive, and from the Smart Detection blade.
 
 ## Review your Smart Detections
 You can discover detections in two ways:
@@ -26,24 +26,24 @@ You can discover detections in two ways:
     ![Email alert](./media/proactive-diagnostics/03.png)
 
     Click the big button to open more detail in the portal.
-* **The Smart Detection tile** on your app's overview blade shows a count of recent alerts. Click the tile to see a list of recent alerts.
+* **The Smart Detection blade** in Application Insights. Select **Smart Detection** under the **Investigate** menu to see a list of recent detections.
 
 ![View recent detections](./media/proactive-diagnostics/04.png)
 
-Select an alert to see its details.
+Select a detection to see its details.
 
 ## What problems are detected?
-There are three kinds of detection:
+Smart Detection detects and notifies about a variety of issues, such as:
 
 * [Smart detection - Failure Anomalies](../../azure-monitor/app/proactive-failure-diagnostics.md). We use machine learning to set the expected rate of failed requests for your app, correlating with load and other factors. If the failure rate goes outside the expected envelope, we send an alert.
 * [Smart detection - Performance Anomalies](../../azure-monitor/app/proactive-performance-diagnostics.md). You get notifications if response time of an operation or dependency duration is slowing down compared to historical baseline or if we identify an anomalous pattern in response time or page load time.   
-* [Smart detection - Azure Cloud Service issues](https://azure.microsoft.com/blog/proactive-notifications-on-cloud-service-issues-with-azure-diagnostics-and-application-insights/). You get alerts if your app is hosted in Azure Cloud Services and a role instance has startup failures, frequent recycling, or runtime crashes.
+* General degradations and issues, like [Trace degredation](https://docs.microsoft.com/azure/azure-monitor/app/proactive-trace-severity), [Memory leak](https://docs.microsoft.com/azure/azure-monitor/app/proactive-potential-memory-leak), [Abnormal rise in Exception volume](https://docs.microsoft.com/azure/azure-monitor/app/proactive-exception-volume) and [Security anti-patterns](https://docs.microsoft.com/azure/azure-monitor/app/proactive-application-security-detection-pack).
 
 (The help links in each notification take you to the relevant articles.)
 
 ## Smart Detection email notifications
 
-All Smart Detection rules, except for rules marked as Preview, are configured by default to send email notifications when detections are found.
+All Smart Detection rules, except for rules marked as _preview_, are configured by default to send email notifications when detections are found.
 
 Configuring email notifications for a specific Smart Detection rule can be done by opening the Smart Detection **Settings** blade and selecting the rule, which will open the **Edit rule** blade.
 

articles/azure-monitor/app/proactive-failure-diagnostics.md

@@ -17,7 +17,7 @@ ms.author: mbullwin
 # Smart Detection - Failure Anomalies
 [Application Insights](../../azure-monitor/app/app-insights-overview.md) automatically notifies you in near real time if your web app experiences an abnormal rise in the rate of failed requests. It detects an unusual rise in the rate of HTTP requests or dependency calls that are reported as failed. For requests, failed requests are usually those with response codes of 400 or higher. To help you triage and diagnose the problem, an analysis of the characteristics of the failures and related telemetry is provided in the notification. There are also links to the Application Insights portal for further diagnosis. The feature needs no set-up nor configuration, as it uses machine learning algorithms to predict the normal failure rate.
 
-This feature works for Java and ASP.NET web apps, hosted in the cloud or on your own servers. It also works for any app that generates request or dependency telemetry - for example, if you have a worker role that calls [TrackRequest()](../../azure-monitor/app/api-custom-events-metrics.md#trackrequest) or [TrackDependency()](../../azure-monitor/app/api-custom-events-metrics.md#trackdependency).
+This feature works for any web app, hosted in the cloud or on your own servers, that generates request or dependency telemetry - for example, if you have a worker role that calls [TrackRequest()](../../azure-monitor/app/api-custom-events-metrics.md#trackrequest) or [TrackDependency()](../../azure-monitor/app/api-custom-events-metrics.md#trackdependency).
 
 After setting up [Application Insights for your project](../../azure-monitor/app/app-insights-overview.md), and provided your app generates a certain minimum amount of telemetry, Smart Detection of failure anomalies takes 24 hours to learn the normal behavior of your app, before it is switched on and can send alerts.
 
@@ -38,6 +38,26 @@ Notice that it tells you:
 * The exception, log traces, and dependency failure (databases or other external components) that appear to be associated with the characterized failures.
 * Links directly to relevant searches on the telemetry in Application Insights.
 
+## Failure Anomalies v2
+A new version of the Failure Anomalies alert rule is now available. This new version  is running on the new Azure alerting platform and introduces a variety of improvements over the existing version.
+
+### What's new in this version?
+- Faster detection of issues
+- A richer set of actions - The alert rule is created with an associated [Action Group](https://docs.microsoft.com/azure/azure-monitor/platform/action-groups) named "Application Insights Smart Detection" that contains email and webhook actions, and can be extended to trigger additional actions when the alert fires.
+- More focused notifications - Email notifications sent from this alert rule are now sent by default to users associated with the subscription's Monitoring Reader and Monitoring Contributor roles. More information on this is available [here](https://docs.microsoft.com/azure/azure-monitor/app/proactive-email-notification).
+- Easier configuration via ARM templates - See example [here](https://docs.microsoft.com/azure/azure-monitor/app/proactive-arm-config).
+- Common alert schema support - Notifications sent from this alert rule follow the [common alert schema](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-common-schema).
+- Unified email template - Email notifications from this alert rule have a consistent look & feel with other alert types. With this change, the option to get Failure Anomalies alerts with detailed diagnostics information is no longer available.
+
+### How do I get the new version?
+- Newly created Application Insights resources are now provisioned with the new version of the Failure Anomalies alert rule.
+- Existing Application Insights resources with the classic version of the Failure Anomalies alert rule will get the new version once their hosting subscription is migrated to the new alerting platform as part of the [classic alerts retirement process](https://docs.microsoft.com/azure/azure-monitor/platform/monitoring-classic-retirement).
+
+> [!NOTE]
+> The new version of the Failure Anomalies alert rule remains free. In addition, email and webhook actions triggered by the associated "Application Insights Smart Detection" Action Group are free as well.
+> 
+> 
+
 ## Benefits of Smart Detection
 Ordinary [metric alerts](../../azure-monitor/app/alerts.md) tell you there might be a problem. But Smart Detection starts the diagnostic work for you, performing a lot of the analysis you would otherwise have to do yourself. You get the results neatly packaged, helping you to get quickly to the root of the problem.
 

articles/azure-monitor/insights/vminsights-enable-overview.md

@@ -11,7 +11,7 @@ ms.service: azure-monitor
 ms.topic: conceptual
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 06/19/2019
+ms.date: 06/28/2019
 ms.author: magoedte
 ---
 
@@ -81,7 +81,7 @@ The following table lists the Windows and Linux operating systems that Azure Mon
 |Red Hat Enterprise Linux (RHEL) 6, 7| X | X| X |
 |Ubuntu 14.04, 16.04, 18.04 | X | X | X |
 |CentOS Linux 6, 7 | X | X | X |
-|SUSE Linux Enterprise Server (SLES) 11, 12 | X | X | X |
+|SUSE Linux Enterprise Server (SLES) 12 | X | X | X |
 |Debian 8, 9.4 | X<sup>1</sup> | | X |
 
 <sup>1</sup> The Performance feature of Azure Monitor for VMs is available only from Azure Monitor. It isn't available directly from the left pane of the Azure VM.
@@ -127,18 +127,14 @@ The following table lists the Windows and Linux operating systems that Azure Mon
 | 16.04 | 4.4.\*<br>4.8.\*<br>4.10.\*<br>4.11.\*<br>4.13.\* |
 | 14.04 | 3.13.\*<br>4.4.\* |
 
-#### SUSE Linux 11 Enterprise Server
-
-| OS version | Kernel version
-|:--|:--|
-|11 SP4 | 3.0.* |
-
 #### SUSE Linux 12 Enterprise Server
 
 | OS version | Kernel version
 |:--|:--|
 |12 SP2 | 4.4.* |
 |12 SP3 | 4.4.* |
+|12 SP4 | 4.4.* |
+|12 SP4 | Azure-Tuned Kernel |
 
 ### The Microsoft Dependency agent
 

articles/azure-monitor/log-query/unify-app-resource-data.md

@@ -136,7 +136,7 @@ The following table shows the schema differences between Log Analytics and Appli
 | SessionId | session_Id | 
 | SourceSystem | operation_SyntheticSource |
 | TelemetryTYpe | type |
-| URL | _url |
+| URL | url |
 | UserAccountId | user_AccountId |
 
 ## Next steps

articles/azure-monitor/platform/manage-cost-storage.md

@@ -101,11 +101,11 @@ The following steps describe how to configure how long log data is kept by in yo
 
     ![Change workspace data retention setting](media/manage-cost-storage/manage-cost-change-retention-01.png)
 
-The retention can also be [set via ARM](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/template-workspace-configuration#configure-a-log-analytics-workspace) using the `dataRetention` parameter. Additionally, if you set the data retention to 30 days, you can trigger an immediate purge of older data using the `immediatePurgeDataOn30Days` parameter, which may be useful for compliance-related scenarios. This functionality is only exposed via ARM. 
+The retention can also be [set via ARM](https://docs.microsoft.com/azure/azure-monitor/platform/template-workspace-configuration#configure-a-log-analytics-workspace) using the `dataRetention` parameter. Additionally, if you set the data retention to 30 days, you can trigger an immediate purge of older data using the `immediatePurgeDataOn30Days` parameter, which may be useful for compliance-related scenarios. This functionality is only exposed via ARM. 
 
 ## Legacy pricing tiers
 
-Subscriptions who had a Log Analytics workspace or Application Insights resource in it before April 2, 2018, or are linked to an Enterprise Agreement that started prior to February 1, 2019, will continue to have access to the legacy pricing tiers: **Free**, **Standalone (Per GB)** and **Per Node (OMS)**.  Workspaces in the Free pricing tier will have daily data ingestion limited to 500 MB (except for security data types collected by Azure Security Center) and the data retention is limited to 7 days. The Free pricing tier is intended only for evaluation purposes. Workspaces in the Standalone or Per Node pricing tiers have user-configurable retention of up to 2 years. Workspaces created prior to April 2016 also have access the original **Standard** and **Premium** pricing tiers. More details of pricing tier limitations are available [here](https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits#log-analytics-workspaces).
+Subscriptions who had a Log Analytics workspace or Application Insights resource in it before April 2, 2018, or are linked to an Enterprise Agreement that started prior to February 1, 2019, will continue to have access to the legacy pricing tiers: **Free**, **Standalone (Per GB)** and **Per Node (OMS)**.  Workspaces in the Free pricing tier will have daily data ingestion limited to 500 MB (except for security data types collected by Azure Security Center) and the data retention is limited to 7 days. The Free pricing tier is intended only for evaluation purposes. Workspaces in the Standalone or Per Node pricing tiers have user-configurable retention of up to 2 years. Workspaces created prior to April 2016 also have access the original **Standard** and **Premium** pricing tiers. More details of pricing tier limitations are available [here](https://docs.microsoft.com/azure/azure-subscription-service-limits#log-analytics-workspaces).
 
 > [!NOTE]
 > To use the entitlements that come from purchasing OMS E1 Suite, OMS E2 Suite or OMS Add-On for System Center, choose the Log Analytics *Per Node* pricing tier.
@@ -123,7 +123,7 @@ If your Log Analytics workspace has access to legacy pricing tiers, to change be
 3. Under **Pricing tier**, select a pricing tier and then click **Select**.  
     ![Selected pricing plan](media/manage-cost-storage/workspace-pricing-tier-info.png)
 
-You can also [set the pricing tier via ARM](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/template-workspace-configuration#configure-a-log-analytics-workspace) using the `ServiceTier` parameter. 
+You can also [set the pricing tier via ARM](https://docs.microsoft.com/azure/azure-monitor/platform/template-workspace-configuration#configure-a-log-analytics-workspace) using the `ServiceTier` parameter. 
 
 ## Troubleshooting why Log Analytics is no longer collecting data
 

articles/cognitive-services/QnAMaker/How-To/troubleshooting-runtime.md

@@ -17,7 +17,8 @@ ms.custom: seodec18
 QnAMaker comprises of components hosted in the user's Azure account. Debugging may require users to manipulate their QnAMaker Azure resources or provide QnAMaker support team with additional information about their setup.
 
 ## How to get latest QnAMaker runtime updates
-QnAMaker runtime is part of the Azure App Service deployed when you [create a QnAMaker service](./set-up-qnamaker-service-azure.md) in Azure portal. Updates are made periodically to the runtime. To apply the latest updates to apply to your QnAMaker setup, you must restart the App Service.
+QnAMaker runtime is part of the Azure App Service deployed when you [create a QnAMaker service](./set-up-qnamaker-service-azure.md) in Azure portal. Updates are made periodically to the runtime. QnA Maker App Service is on auto update mode post our Apr 2019 site extension release (version 5+). This is already designed to take care of ZERO downtime during upgrades. You can check your current version at https://www.qnamaker.ai/UserSettings. If your version is older than version 5.x, you must restart the App Service to apply the latest updates to apply to your QnAMaker setup.
+
 1. Go to your QnAMaker service (resource group) in the [Azure portal](https://portal.azure.com)
 
     ![QnAMaker Azure resource group](../media/qnamaker-how-to-troubleshoot/qnamaker-azure-resourcegroup.png)