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

commit

Author: asudbring

articles/active-directory-b2c/custom-policy-disable-email-verification.md

@@ -24,8 +24,11 @@ Complete the steps in [Get started with custom policies](custom-policy-get-start
 
 ## Add the metadata to the self-asserted technical profile
 
-The **LocalAccountSignUpWithLogonEmail** technical profile is a [self-asserted](self-asserted-technical-profile.md), which is invoked during the sign-up flow. To disable the email verification, set the `EnforceEmailVerification` metadata to false. Override the LocalAccountSignUpWithLogonEmail technical profiles in the extension file. Find the `ClaimsProviders` element. Add the following claims provider to the `ClaimsProviders` element:
+The **LocalAccountSignUpWithLogonEmail** technical profile is a [self-asserted](self-asserted-technical-profile.md), which is invoked during the sign-up flow. To disable the email verification, set the `EnforceEmailVerification` metadata to false. Override the LocalAccountSignUpWithLogonEmail technical profiles in the extension file. 
 
+1. Open the extensions file of your policy. For example, <em>`SocialAndLocalAccounts/`**`TrustFrameworkExtensions.xml`**</em>.
+1. Find the `ClaimsProviders` element. If the element doesn't exist, add it.
+1. Add the following claims provider to the `ClaimsProviders` element:
 
 ```XML
 <ClaimsProvider>

articles/active-directory-b2c/custom-policy-password-complexity.md

@@ -149,4 +149,4 @@ To configure the password complexity, override the `newPassword` and `reenterPas
 ## Next steps
 
 - Learn how to [Configure password change using custom policies in Azure Active Directory B2C](custom-policy-password-change.md).
-- - Learn more about the [Predicates](predicates.md) and [PredicateValidations](predicates.md#predicatevalidations) elements in the IEF reference.
+- Learn more about the [Predicates](predicates.md) and [PredicateValidations](predicates.md#predicatevalidations) elements in the IEF reference.

articles/app-service/containers/quickstart-multi-container.md

@@ -93,6 +93,9 @@ When the App Service plan has been created, the Azure CLI shows information simi
 
 ## Create a Docker Compose app
 
+> [!NOTE]
+> Docker Compose on Azure App Services currently has a limit of 4,000 characters at this time.
+
 In your Cloud Shell terminal, create a multi-container [web app](app-service-linux-intro.md) in the `myAppServicePlan` App Service plan with the [az webapp create](/cli/azure/webapp?view=azure-cli-latest#az-webapp-create) command. Don't forget to replace _\<app_name>_ with a unique app name (valid characters are `a-z`, `0-9`, and `-`).
 
 ```azurecli

articles/azure-databricks/TOC.yml

@@ -31,44 +31,9 @@
   items:
   - name: Getting started 
     items:
-    - name: Data overview
-      href: /azure/databricks/getting-started/data
-      maintainContext: true
     - name: Azure Databricks concepts
       href: /azure/databricks/getting-started/concepts
       maintainContext: true
-    - name: Azure Databricks datasets 
-      href: /azure/databricks/getting-started/databricks-datasets
-      maintainContext: true
-    - name: Apache Spark
-      items: 
-      - name: Apache Spark overview
-        href: /azure/databricks/getting-started/spark/index
-        maintainContext: true
-      - name: Get started with Apache Spark 
-        href: /azure/databricks/getting-started/spark/quick-start
-        maintainContext: true
-      - name: DataFrames
-        href: /azure/databricks/getting-started/spark/dataframes
-        maintainContext: true 
-      - name: Datasets
-        href: /azure/databricks/getting-started/spark/datasets
-        maintainContext: true 
-      - name: Machine learning
-        href: /azure/databricks/getting-started/spark/machine-learning
-        maintainContext: true
-      - name: Structured streaming
-        href: /azure/databricks/getting-started/spark/streaming
-        maintainContext: true
-      - name: What's next
-        href: /azure/databricks/getting-started/spark/next
-        maintainContext: true
-    - name: Training and FAQ 
-      href: /azure/databricks/getting-started/training-faq
-      maintainContext: true
-    - name: Supported browsers 
-      href: /azure/databricks/getting-started/supported-browsers
-      maintainContext: true
   - name: Databricks runtimes
     items:
     - name: Runtime overview
@@ -220,6 +185,9 @@
     maintainContext: true
   - name: Data
     items:
+    - name: Data overview
+      href: /azure/databricks/getting-started/data
+      maintainContext: true
     - name: Databases and tables
       href: /azure/databricks/data/tables
       maintainContext: true
@@ -311,6 +279,9 @@
     - name: Databricks File System (DBFS)
       href: /azure/databricks/data/databricks-file-system
       maintainContext: true
+    - name: Azure Databricks Datasets
+      href:  /azure/databricks/getting-started/databricks-datasets
+      maintainContext: true
     - name: FileStore
       href: /azure/databricks/data/filestore
       maintainContext: true
@@ -732,6 +703,9 @@
     - name: RStudio on Azure Databricks
       href: /azure/databricks/spark/latest/sparkr/rstudio
       maintainContext: true 
+    - name: Shiny on Azure Databricks 
+      href: /azure/databricks/spark/latest/sparkr/shiny
+      maintainContext: true
   - name: Machine learning
     items:
     - name: Machine learning overview
@@ -1385,6 +1359,9 @@
       - name: Ensure idempotency
         href: /azure/databricks/kb/jobs/jobs-idempotency
         maintainContext: true
+      - name: Long jobs fail with credential passthrough
+        href: /azure/databricks/kb/jobs/azure-long-job-failed-auth
+        maintainContext: true
     - name: Libraries
       items:
       - name: Can't uninstall library from UI
@@ -1495,6 +1472,12 @@
       - name: Run SQL queries
         href: /azure/databricks/kb/python/sql-in-python
         maintainContext: true
+      - name: Use the HDFS API to read files in Python 
+        href: /azure/databricks/kb/python/hdfs-to-read-files
+        maintainContext: true
+      - name: Python 2 sunset status 
+        href: /azure/databricks/kb/python/python-2-eol
+        maintainContext: true
     - name: R with Spark
       items:
       - name: Change version of R
@@ -1650,6 +1633,35 @@
     href: /azure/templates/microsoft.databricks/workspaces  
 - name: Resources
   items:
+  - name: Apache Spark
+    items: 
+    - name: Apache Spark overview
+      href: /azure/databricks/getting-started/spark/index
+      maintainContext: true
+    - name: Get started with Apache Spark
+      href: /azure/databricks/getting-started/spark/quick-start
+      maintainContext: true
+    - name: DataFrames
+      href: /azure/databricks/getting-started/spark/dataframes
+      maintainContext: true
+    - name: Datasets
+      href: /azure/databricks/getting-started/spark/datasets
+      maintainContext: true
+    - name: Machine learning
+      href: /azure/databricks/getting-started/spark/machine-learning
+      maintainContext: true
+    - name: Structured streaming
+      href: /azure/databricks/getting-started/spark/streaming
+      maintainContext: true
+    - name: What's next
+      href: /azure/databricks/getting-started/spark/next
+      maintainContext: true
+  - name: Training and FAQ
+    href: /azure/databricks/getting-started/training-faq
+    maintainContext: true
+  - name: Supported browsers
+    href: /azure/databricks/getting-started/supported-browsers
+    maintainContext: true
   - name: Release notes
     items:
     - name: Platform 

articles/azure-functions/functions-create-maven-eclipse.md

@@ -37,7 +37,7 @@ It's highly recommended to also install [Azure Functions Core Tools, version 2](
 1. Select **Add Archetype** and add the entries for the [azure-functions-archetype](https://mvnrepository.com/artifact/com.microsoft.azure/azure-functions-archetype).
     - Archetype Group ID: com.microsoft.azure
     - Archetype Artifact ID: azure-functions-archetype
-    - Version: Use latest version **1.22** from [the central repository](https://mvnrepository.com/artifact/com.microsoft.azure/azure-functions-archetype)
+    - Version: Check and use latest version from [the central repository](https://mvnrepository.com/artifact/com.microsoft.azure/azure-functions-archetype)
     ![Eclipse Maven create](media/functions-create-first-java-eclipse/functions-create-eclipse.png)  
 1. Click **OK** and then click **Next**.  Be sure to fill in values for all of the fields including `resourceGroup`, `appName`, and `appRegion` (please use a different appName other than **fabrikam-function-20170920120101928**), and eventually **Finish**.
     ![Eclipse Maven create2](media/functions-create-first-java-eclipse/functions-create-eclipse2.png)  

articles/azure-functions/functions-create-maven-intellij.md

@@ -41,7 +41,7 @@ To develop a function with Java and IntelliJ, install the following software:
 1. In the **Add Archetype** window, complete the fields as follows:
     - _GroupId_: com.microsoft.azure
     - _ArtifactId_: azure-functions-archetype
-    - _Version_: Use the latest version **1.22** from [the central repository](https://mvnrepository.com/artifact/com.microsoft.azure/azure-functions-archetype)
+    - _Version_: Check and use the latest version from [the central repository](https://mvnrepository.com/artifact/com.microsoft.azure/azure-functions-archetype)
     ![Create a Maven project from archetype in IntelliJ IDEA](media/functions-create-first-java-intellij/functions-create-intellij.png)  
 1. Select **OK**, and then select **Next**.
 1. Enter your details for current project, and select **Finish**.

articles/azure-monitor/app/app-insights-overview.md

@@ -98,7 +98,7 @@ There are several ways to get started. Begin with whichever works best for you.
   * [.NET Console Applications](../../azure-monitor/app/console.md)
   * [Java](../../azure-monitor/app/java-get-started.md)
   * [Node.js](../../azure-monitor/app/nodejs.md)
-  * [Python (preview)](../../azure-monitor/app/opencensus-python.md)
+  * [Python](../../azure-monitor/app/opencensus-python.md)
   * [Other platforms](../../azure-monitor/app/platforms.md)
 * **[Instrument your web pages](../../azure-monitor/app/javascript.md)** for page view, AJAX, and other client-side telemetry.
 * **[Analyze mobile app usage](../../azure-monitor/learn/mobile-center-quickstart.md)** by integrating with Visual Studio App Center.
@@ -117,7 +117,7 @@ Get started at development time with:
 * [ASP.NET Core](../../azure-monitor/app/asp-net-core.md)
 * [Java](../../azure-monitor/app/java-get-started.md)
 * [Node.js](../../azure-monitor/app/nodejs.md)
-* [Python (preview)](../../azure-monitor/app/opencensus-python.md)
+* [Python](../../azure-monitor/app/opencensus-python.md)
 
 
 ## Support and feedback

articles/azure-monitor/app/distributed-tracing.md

@@ -11,11 +11,11 @@ ms.reviewer: mbullwin
 
 # What is Distributed Tracing?
 
-The advent of modern cloud and [microservices](https://azure.com/microservices) architectures has given rise to simple, independently deployable services that can help reduce costs while increasing availability and throughput. But while these movements have made individual services easier to understand as a whole, they’ve made overall systems more difficult to reason about and debug.
+The advent of modern cloud and [microservices](https://azure.com/microservices) architectures has given rise to simple, independently deployable services that can help reduce costs while increasing availability and throughput. But while these movements have made individual services easier to understand as a whole, they've made overall systems more difficult to reason about and debug.
 
-In monolithic architectures, we’ve gotten used to debugging with call stacks. Call stacks are brilliant tools for showing the flow of execution (Method A called Method B, which called Method C), along with details and parameters about each of those calls. This is great for monoliths or services running on a single process, but how do we debug when the call is across a process boundary, not simply a reference on the local stack? 
+In monolithic architectures, we've gotten used to debugging with call stacks. Call stacks are brilliant tools for showing the flow of execution (Method A called Method B, which called Method C), along with details and parameters about each of those calls. This is great for monoliths or services running on a single process, but how do we debug when the call is across a process boundary, not simply a reference on the local stack? 
 
-That’s where distributed tracing comes in.  
+That's where distributed tracing comes in.  
 
 Distributed tracing is the equivalent of call stacks for modern cloud and microservices architectures, with the addition of a simplistic performance profiler thrown in. In Azure Monitor, we provide two experiences for consuming distributed trace data. The first is our [transaction diagnostics](https://docs.microsoft.com/azure/application-insights/app-insights-transaction-diagnostics) view, which is like a call stack with a time dimension added in. The transaction diagnostics view provides visibility into one single transaction/request, and is helpful for finding the root cause of reliability issues and performance bottlenecks on a per request basis.
 
@@ -34,7 +34,7 @@ The Application Insights SDKs for .NET, .NET Core, Java, Node.js, and JavaScript
 * [Java](https://docs.microsoft.com/azure/application-insights/app-insights-java-get-started)
 * [Node.js](https://docs.microsoft.com/azure/application-insights/app-insights-nodejs-quick-start)
 * [JavaScript](https://docs.microsoft.com/azure/application-insights/app-insights-javascript)
-* [Python (preview)](opencensus-python.md)
+* [Python](opencensus-python.md)
 
 With the proper Application Insights SDK installed and configured, tracing information is automatically collected for popular frameworks, libraries, and technologies by SDK dependency auto-collectors. The full list of supported technologies is available in [the Dependency auto-collection documentation](https://docs.microsoft.com/azure/application-insights/auto-collect-dependencies).
 
@@ -44,7 +44,7 @@ With the proper Application Insights SDK installed and configured, tracing infor
 
 In addition to the Application Insights SDKs, Application Insights also supports distributed tracing through [OpenCensus](https://opencensus.io/). OpenCensus is an open source, vendor-agnostic, single distribution of libraries to provide metrics collection and distributed tracing for services. It also enables the open source community to enable distributed tracing with popular technologies like Redis, Memcached, or MongoDB. [Microsoft collaborates on OpenCensus with several other monitoring and cloud partners](https://open.microsoft.com/2018/06/13/microsoft-joins-the-opencensus-project/).
 
-[Python (preview)](opencensus-python.md) 
+[Python](opencensus-python.md) 
 
 The OpenCensus website maintains API reference documentation for [Python](https://opencensus.io/api/python/trace/usage.html) and [Go](https://godoc.org/go.opencensus.io), as well as various different guides for using OpenCensus. 
 

articles/azure-monitor/app/platforms.md

@@ -13,7 +13,7 @@ ms.reviewer: olegan
 * [Java](../../azure-monitor/app/java-get-started.md)
 * [JavaScript](../../azure-monitor/app/javascript.md)
 * [Node.JS](../../azure-monitor/app/nodejs.md)
-* [Python (preview)](../../azure-monitor/app/opencensus-python.md)
+* [Python](../../azure-monitor/app/opencensus-python.md)
 
 ## Supported platforms and frameworks
 
@@ -30,7 +30,7 @@ ms.reviewer: olegan
 * [iOS](../../azure-monitor/learn/mobile-center-quickstart.md) (App Center)
 * [Java EE](../../azure-monitor/app/java-get-started.md)
 * [Node.JS](https://www.npmjs.com/package/applicationinsights)
-* [Python (preview)](../../azure-monitor/app/opencensus-python.md)
+* [Python](../../azure-monitor/app/opencensus-python.md)
 * [Universal Windows app](../../azure-monitor/learn/mobile-center-quickstart.md) (App Center)
 * [Windows desktop applications, services, and worker roles](../../azure-monitor/app/windows-desktop.md)
 
@@ -46,4 +46,4 @@ ms.reviewer: olegan
 * [Stream Analytics](../../azure-monitor/app/export-power-bi.md)
 
 ## Unsupported SDKs
-We're aware that several other community-supported SDKs exist. However, Azure Monitor only provides support when using the supported SDKs listed on this page. We’re constantly assessing opportunities to expand our support for other languages, so follow our [GitHub Announcements](https://github.com/microsoft/ApplicationInsights-Announcements/issues) page to receive the latest SDK news. 
+We're aware that several other community-supported SDKs exist. However, Azure Monitor only provides support when using the supported SDKs listed on this page. We're constantly assessing opportunities to expand our support for other languages, so follow our [GitHub Announcements](https://github.com/microsoft/ApplicationInsights-Announcements/issues) page to receive the latest SDK news. 

articles/azure-monitor/app/sdk-connection-string.md

@@ -102,7 +102,7 @@ See also: https://docs.microsoft.com/azure/azure-monitor/app/custom-endpoints#re
 
 In this example, only the Instrumentation Key has been set.
 
-- Authorization scheme defaults to “ikey” 
+- Authorization scheme defaults to "ikey" 
 - Instrumentation Key: 00000000-0000-0000-0000-000000000000
 - The regional service URIs are based on the [SDK defaults](https://github.com/microsoft/ApplicationInsights-dotnet/blob/e50d569cebf485e72e98f4a08a0bc0e30cdf42bc/BASE/src/Microsoft.ApplicationInsights/Extensibility/Implementation/Endpoints/Constants.cs#L6) and will connect to the public global Azure:
    - Ingestion: https://dc.services.visualstudio.com/
@@ -118,7 +118,7 @@ In this example, only the Instrumentation Key has been set.
 
 In this example, this connection string specifies the endpoint suffix and the SDK will construct service endpoints.
 
-- Authorization scheme defaults to “ikey” 
+- Authorization scheme defaults to "ikey" 
 - Instrumentation Key: 00000000-0000-0000-0000-000000000000
 - The regional service URIs are based on provided endpoint suffix: 
    - Ingestion: https://dc.ai.contoso.com
@@ -134,7 +134,7 @@ In this example, this connection string specifies the endpoint suffix and the SD
 
 In this example, this connection string specifies explicit overrides for every service. The SDK will use the exact endpoints provided without modification.
 
-- Authorization scheme defaults to “ikey” 
+- Authorization scheme defaults to "ikey" 
 - Instrumentation Key: 00000000-0000-0000-0000-000000000000
 - The regional service URIs are based on the explicit override values: 
    - Ingestion: https:\//custom.com:111/
@@ -275,4 +275,4 @@ Get started at development time with:
 * [ASP.NET Core](../../azure-monitor/app/asp-net-core.md)
 * [Java](../../azure-monitor/app/java-get-started.md)
 * [Node.js](../../azure-monitor/app/nodejs.md)
-* [Python (preview)](../../azure-monitor/app/opencensus-python.md)
+* [Python](../../azure-monitor/app/opencensus-python.md)