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

SnehaGunda · SnehaGunda · commit 0ff97f7daa69 · 2020-05-15T10:39:47.000-07:00
diff --git a/articles/iot-central/core/TOC.yml b/articles/iot-central/core/TOC.yml
@@ -63,6 +63,8 @@
           href: howto-set-up-template.md
         - name: Prepare and connect an MXChip IoT DevKit
           href: howto-connect-devkit.md
+        - name: Prepare and connect an Azure Sphere DevKit
+          href: howto-connect-sphere.md
         - name: Prepare and connect a RuuviTag device
           href: howto-connect-ruuvi.md
         - name: Prepare and connect a Rigado Cascade 500
diff --git a/articles/iot-central/core/howto-connect-sphere.md b/articles/iot-central/core/howto-connect-sphere.md
@@ -0,0 +1,83 @@
+---
+title: Connect an Azure Sphere device in Azure IoT Central | Microsoft Docs
+description: Learn how to connect an Azure Sphere (DevKit) device to an Azure IoT Central application. 
+services: iot-central
+ms.service: iot-central
+ms.topic: how-to
+ms.author: sandeepu
+author: sandeeppujar
+ms.date: 04/30/2020
+---
+
+# Connect an Azure Sphere device to your Azure IoT Central application
+
+*This article applies to device developers.*
+
+This article shows you how to connect an Azure Sphere (DevKit) device to an Azure IoT Central application.
+
+Azure Sphere is a secured, high-level application platform with built-in communication and security features for internet-connected devices. It includes a secured, connected, crossover microcontroller unit (MCU), a custom high-level Linux-based operating system (OS), and a cloud-based security service that provides continuous, renewable security. For more information, see[What is Azure Sphere?](https://docs.microsoft.com/azure-sphere/product-overview/what-is-azure-sphere).
+
+[Azure Sphere development kits](https://azure.microsoft.com/services/azure-sphere/get-started/) provide everything you need to start prototyping and developing Azure Sphere applications. Azure IoT Central with Azure Sphere enables an end-to-end stack for an IoT Solution. Azure Sphere provides the device support and IoT Central as a zero-code, managed IoT application platform.
+
+In this how-to article, you:
+
+- Create an Azure Sphere device in IoT Central using the Azure Sphere DevKit device template from the library.
+- Prepare Azure Sphere DevKit device for Azure IoT.
+- Connect Azure Sphere DevKit to Azure IoT Central.
+- View the telemetry from the device in IoT Central.
+
+## Prerequisites
+
+To complete the steps in this article, you need the following resources:
+
+- An Azure IoT Central application.
+- Visual Studio 2019, version 16.4 or later.
+- An [Azure Sphere MT3620 development kit from Seeed Studios](https://docs.microsoft.com/azure-sphere/hardware/mt3620-reference-board-design).
+
+> [!NOTE]
+> If you don't have a physical device, then after the first step step skip to the last section to try a simulated device.
+
+## Create the device in IoT Central
+
+To create an Azure Sphere device in IoT Central:
+
+1. In your Azure IoT Central application, select the **Device Templates** tab and select **+ New**. In the section **Use a featured device template**, select **Azure Sphere Sample Device**.
+
+    :::image type="content" source="media/howto-connect-sphere/sphere-create-template.png" alt-text="Device template for Azure Sphere DevKit":::
+
+1. In the device template, edit the view called **Overview** to show **Temperature** and **Button Press**.
+
+1. Select the **Editing Device and Cloud Data** view type to add another view that shows the read/write property **Status LED**. Drag the **Status LED** property to the empty, dotted rectangle on the right-side of the form. Select **Save**.
+
+## Prepare the device
+
+Before you can connect the Azure Sphere DevKit device to IoT Central, you need to [setup the device and development environment](https://github.com/Azure/azure-sphere-samples/tree/master/Samples/AzureIoT).
+
+## Connect the device
+
+To enable the sample to connect to IoT Central, you must [configure an Azure IoT Central application and then modify the sample's application manifest](https://aka.ms/iotcentral-sphere-git-readme).
+
+## View the telemetry from the device
+
+When the device is connected to IoT Central, you can see the telemetry on the dashboard.
+
+:::image type="content" source="media/howto-connect-sphere/sphere-view.png" alt-text="Dashboard for Azure Sphere DevKit":::
+
+## Create a simulated device
+
+If you don't have a physical Azure Sphere DevKit device, you can create a simulated device to try Azure IoT Central application.
+
+To create a simulated device:
+
+- Select **Devices > Azure IoT Sphere**
+- Select **+ New**.
+- Enter a unique **Device ID** and a friendly **Device name**.
+- Enable the **Simulated** setting.
+- Select **Create**.
+
+## Next steps
+
+If you're a device developer, some suggested next steps are to:
+
+- Read about [Device connectivity in Azure IoT Central](./concepts-get-connected.md)
+- Learn how to [Monitor device connectivity using Azure CLI](./howto-monitor-devices-azure-cli.md)
diff --git a/articles/iot-central/core/media/howto-connect-sphere/sphere-create-template.png b/articles/iot-central/core/media/howto-connect-sphere/sphere-create-template.png
diff --git a/articles/iot-central/core/media/howto-connect-sphere/sphere-view.png b/articles/iot-central/core/media/howto-connect-sphere/sphere-view.png
diff --git a/articles/synapse-analytics/overview-what-is.md b/articles/synapse-analytics/overview-what-is.md
@@ -19,11 +19,11 @@ Today enterprise analytics requires operating at massive scale on any kind of da
 
 Solutions like this are difficult to build, configure, secure, and maintain, which delays the swift extraction of intelligent insight.
 
-**Azure Synapse** is an integrated analytics service that accelerates time to insight from all data at any scale, across data warehouses and big data analytics systems​. It brings together the best of the **SQL** technologies used in enterprise data warehousing, **Spark** technologies used in big data analytics, and **Pipelines** to orchestrate activities and data movement. 
+**Azure Synapse** is an integrated analytics service that accelerates time to insight from all data at any scale, across data warehouses and big data analytics systems​. It brings together the best of the **SQL** technologies used in enterprise data warehousing, **Spark** technologies used in big data analytics, and **Pipelines** to orchestrate activities and data movement.
 
 Azure Synapse comes with a web-native **Studio** user experience that provides a single experience and model for management, monitoring, coding, and security.
 
-Azure Synapse provides the simplest and fastest way for an enterprise to gather insights on any data at any size, using the analytics they're most familiar with. It integrates deeply with **Power BI** allowing data engineers to build analytics solutions that work end-to-end to provide Business Intelligence. 
+Azure Synapse provides the simplest and fastest way for an enterprise to gather insights on any data at any size, using the analytics they're most familiar with. It integrates deeply with **Power BI** allowing data engineers to build analytics solutions that work end-to-end to provide Business Intelligence.
 
 Additionally, Azure Synapse facilitates predictive model building and advanced analytics with machine learning via its built-in support for **AzureML**.
 
@@ -40,14 +40,14 @@ scenarios using standard T-SQL experiences familiar to data engineers. It also e
 
 ### Industry-standard Apache Spark
 
-**Synapse Spark** deeply and seamlessly integrates Apache Spark--the most popular open source big data engine used for data preparation, data engineering, ETL, and machine learning.
+**Apache Spark for Azure Synapse** deeply and seamlessly integrates Apache Spark--the most popular open source big data engine used for data preparation, data engineering, ETL, and machine learning.
 
 * ML models with SparkML algorithms and AzureML integration for Apache Spark 2.4 with built-in support for Linux Foundation Delta Lake.
 * Simplified resource model that frees you from having to worry about managing clusters.
 * Fast Spark start-up and aggressive autoscaling.
 * Built-in support for .NET for Spark allowing you to reuse your C# expertise and existing .NET code within a Spark application.
 
-### Interop of SQL and Spark on your Data Lake
+### Interop of SQL and Apache Spark on your Data Lake
 
 Azure Synapse removes the traditional technology barriers between using SQL and Spark together. You can seamlessly mix and match based on your needs and expertise.
 
diff --git a/articles/synapse-analytics/quickstart-apache-spark-notebook.md b/articles/synapse-analytics/quickstart-apache-spark-notebook.md
@@ -1,5 +1,5 @@
 ---
-title: 'Quickstart: Create an Apache Spark notebook'
+title: 'Quickstart: Create an Apache Spark for Azure Synapse Analytics notebook'
 description: This quickstart shows how to use the web tools to create an Apache Spark pool (preview) in Azure Synapse Analytics, and run a Spark SQL query.
 services: synapse-analytics
 author: euangMS
diff --git a/articles/synapse-analytics/quickstart-connect-synapse-link-cosmos-db.md b/articles/synapse-analytics/quickstart-connect-synapse-link-cosmos-db.md
@@ -26,15 +26,16 @@ Before you connect an Azure Cosmos DB account to your workspace, there are a few
 
 To run large-scale analytics into Azure Cosmos DB without impacting your operational performance, we recommend enabling Synapse Link for Azure Cosmos DB. This function brings HTAP capability to a container and built-in support in Azure Synapse. Follow this quickstart to enable Synapse Link for Cosmos DB containers.
 
-## Navigate to Synapse Studio 
+## Navigate to Synapse Studio
 
 From your Synapse workspace, select **Launch Synapse Studio**. On the Synapse Studio home page, select **Data, which will take you to the **Data Object Explorer**.
 
-## Connect an Azure Cosmos DB database to a Synapse workspace 
+## Connect an Azure Cosmos DB database to a Synapse workspace
 
-Connecting an Azure Cosmos DB database is done as linked service. A Cosmos DB linked service enables users to browse and explore data, read, and write from Synapse Spark or SQL into Azure Cosmos DB. 
+Connecting an Azure Cosmos DB database is done as linked service. A Cosmos DB linked service enables users to browse and explore data, read, and write from Apache Spark for Azure Synapse Analytics or SQL into Azure Cosmos DB.
 
 From the Data Object Explorer, you can directly connect an Azure Cosmos DB database by doing the following steps:
+
 1. Select ***+*** icon near Data
 2. Select **Connect to external data**
 3. Select the API that you want to connect to: SQL or MongoDB
@@ -61,4 +62,4 @@ When you right-click into a container, you'll have a list of gestures that will
 ## Next steps
 
 * [Learn what is supported between Synapse and Azure Cosmos DB](./synapse-link/concept-synapse-link-cosmos-db-support.md)
-* [Learn how to query an analytical store with Synapse Spark](synapse-link/how-to-query-analytical-store-spark.md)
+* [Learn how to query an analytical store with Apache Spark for Azure Synapse Analytics](synapse-link/how-to-query-analytical-store-spark.md)
diff --git a/articles/synapse-analytics/security/how-to-set-up-access-control.md b/articles/synapse-analytics/security/how-to-set-up-access-control.md
@@ -22,7 +22,7 @@ To secure a Synapse workspace (preview), you'll follow a pattern of configuring
 - Synapse roles – these roles are unique to Synapse and aren't based on Azure roles. There are three of these roles:
   - Synapse workspace admin
   - Synapse SQL admin
-  - Synapse Spark admin
+  - Apache Spark for Azure Synapse Analytics admin
 - Access control for data in Azure Data Lake Storage Gen 2 (ADLSGEN2).
 - Access control for Synapse SQL and Spark databases
 
diff --git a/articles/synapse-analytics/spark/apache-spark-autoscale.md b/articles/synapse-analytics/spark/apache-spark-autoscale.md
@@ -12,7 +12,7 @@ ms.date: 03/31/2020
 
 # Automatically scale Azure Synapse Analytics Apache Spark pools
 
-Azure Synapse Spark pool's Autoscale feature automatically scales the number of nodes in a cluster instance up and down. During the creation of a new Azure Synapse Spark pool, a minimum and maximum number of nodes can be set when Autoscale is selected. Autoscale then monitors the resource requirements of the load and scales the number of nodes up or down. There's no additional charge for this feature.
+Apache Spark for Azure Synapse Analytics pool's Autoscale feature automatically scales the number of nodes in a cluster instance up and down. During the creation of a new Apache Spark for Azure Synapse Analytics pool, a minimum and maximum number of nodes can be set when Autoscale is selected. Autoscale then monitors the resource requirements of the load and scales the number of nodes up or down. There's no additional charge for this feature.
 
 ## Metrics monitoring
 
diff --git a/articles/synapse-analytics/spark/apache-spark-job-definitions.md b/articles/synapse-analytics/spark/apache-spark-job-definitions.md
@@ -1,6 +1,6 @@
 ---
-title: 'Tutorial - Azure Synapse Analytics: Spark job definition for Synapse'
-description: Tutorial - Use the Azure Synapse Analytics to create Spark job definitions, and submit them to a Synapse Spark pool.
+title: 'Tutorial - Apache Spark for Azure Synapse Analytics: Apache Spark job definition for Synapse'
+description: Tutorial - Use the Azure Synapse Analytics to create Spark job definitions, and submit them to a Apache Spark for Azure Synapse Analytics pool.
 author: hrasheed-msft
 ms.author: jejiang
 ms.reviewer: jasonh
diff --git a/articles/synapse-analytics/spark/apache-spark-version-support.md b/articles/synapse-analytics/spark/apache-spark-version-support.md
@@ -1,5 +1,5 @@
 ---
-title: Synapse Spark version support 
+title: Apache Spark for Azure Synapse Analytics version support 
 description: Supported versions of Spark, Scala, Python
 services: synapse-analytics
 author: euangMS 
@@ -37,11 +37,11 @@ Apache Spark in Azure Synapse includes .NET Core 3.0
 
 ## .NET Support for Apache Spark
 
-Azure Synapse includes .NET Support for Apache Spark 0.5.0
+Azure Synapse includes .NET Support for Apache Spark 0.11.0
 
 ## Delta Lake
 
-Synapse Analytics includes support for Delta Lake 0.5.0
+Synapse Analytics includes support for Delta Lake 0.6.0
 
 ## Python version
 
diff --git a/articles/synapse-analytics/spark/spark-dotnet.md b/articles/synapse-analytics/spark/spark-dotnet.md
@@ -15,7 +15,7 @@ ms.reviewer: jrasnick
 
 [.NET for Apache Spark](https://dot.net/spark) is free, open-source, and cross-platform .NET support for Spark. .NET for Apache Spark provides .NET bindings for Spark which allow you to access Spark APIs through C# and F#. With .NET for Apache Spark, you have the ability to write and execute user-defined functions for Spark using .NET. The .NET APIs for Spark enable you to access all aspects of Spark that help you analyze your data, including Spark SQL and Structured Streaming.
 
-You can analyze data with .NET for Apache Spark through Spark batch job definitions or with interactive Azure Synapse Analytics notebooks. In this article, you learn how to use .NET for Apache Spark with Azure Synapse using both techniques. 
+You can analyze data with .NET for Apache Spark through Spark batch job definitions or with interactive Azure Synapse Analytics notebooks. In this article, you learn how to use .NET for Apache Spark with Azure Synapse using both techniques.
 
 ## Submit batch jobs using the Spark job definition
 
@@ -48,9 +48,9 @@ Notebooks are a great option for prototyping your .NET for Apache Spark pipeline
 
 ### How to use notebooks
 
-When you create a new notebook, you choose a language kernel that you wish to express your business logic. There is kernel support for several languages, including C#. 
+When you create a new notebook, you choose a language kernel that you wish to express your business logic. There is kernel support for several languages, including C#.
 
-To use .NET for Apache Spark in your Azure Synapse Analytics notebook, select **.NET Spark (C#)** as your kernel and attach the notebook to an existing Spark pool. 
+To use .NET for Apache Spark in your Azure Synapse Analytics notebook, select **.NET Spark (C#)** as your kernel and attach the notebook to an existing Spark pool.
 
 The .NET Spark notebook is based on the .NET interactive experiences and provides interactive C# experiences with the ability to use .NET for Spark out of the box with the Spark session variable `spark` already predefined.
 
diff --git a/articles/synapse-analytics/sql/best-practices-sql-on-demand.md b/articles/synapse-analytics/sql/best-practices-sql-on-demand.md
@@ -114,7 +114,7 @@ For more information, check [filename](develop-storage-files-overview.md#filenam
 > Always cast result of filepath and fileinfo functions to appropriate data types. If you use character data types, make sure appropriate length is used.
 
 > [!NOTE]
-> Functions used for partition elimination, filepath and fileinfo, are not currently supported for external tables other than those created automatically for each table created in Synapse Spark.
+> Functions used for partition elimination, filepath and fileinfo, are not currently supported for external tables other than those created automatically for each table created in Apache Spark for Azure Synapse Analytics.
 
 If your stored data isn't partitioned, consider partitioning it so you can use these functions to optimize queries targeting those files. When [querying partitioned Spark tables](develop-storage-files-spark-tables.md) from SQL on-demand, the query will automatically target only the files needed.
 
diff --git a/articles/synapse-analytics/sql/develop-openrowset.md b/articles/synapse-analytics/sql/develop-openrowset.md
@@ -43,7 +43,7 @@ This is a quick and easy way to read the content of the files without pre-config
     This option enables you to configure location of the storage account in the data source and specify the authentication method that should be used to access storage. 
     
     > [!IMPORTANT]
-    > `OPENROWSET` without `DATA_SOURCE` provides quick and easy way to access the storage files but offers limited authentication options. As an example, Azure AD principal can access files only using their [Azure AD identity](develop-storage-files-storage-access-control.md#user-identity) and cannot access publicly available files. If you need more powerful authentication options, use `DATA_SOURCE` option and define credential that you want to use to access storage.
+    > `OPENROWSET` without `DATA_SOURCE` provides quick and easy way to access the storage files but offers limited authentication options. As an example, Azure AD principal can access files only using their [Azure AD identity](develop-storage-files-storage-access-control.md?tabs=user-identity#force-azure-ad-pass-through) and cannot access publicly available files. If you need more powerful authentication options, use `DATA_SOURCE` option and define credential that you want to use to access storage.
 
 ## Security
 
@@ -53,9 +53,9 @@ The storage administrator must also enable a user to access the files by providi
 
 `OPENROWSET` use the following rules to determine how to authenticate to storage:
 - In `OPENROWSET` with `DATA_SOURCE` the authentication mechanism depends on caller type.
-  - AAD logins can access files only using their own [Azure AD identity](develop-storage-files-storage-access-control.md#user-identity) if Azure storage allows the Azure AD user to access underlying files (for example, if the caller has Storage Reader permission on storage) and if you [enable Azure AD passthrough authentication](develop-storage-files-storage-access-control.md#force-azure-ad-pass-through) on Synapse SQL service.
+  - AAD logins can access files only using their own [Azure AD identity](develop-storage-files-storage-access-control.md?tabs=user-identity#force-azure-ad-pass-through) if Azure storage allows the Azure AD user to access underlying files (for example, if the caller has Storage Reader permission on storage) and if you [enable Azure AD passthrough authentication](develop-storage-files-storage-access-control.md#force-azure-ad-pass-through) on Synapse SQL service.
   - SQL logins can also use `OPENROWSET` without `DATA_SOURCE` to access publicly available files, files protected using SAS token or Managed Identity of Synapse workspace. You would need to [create server-scoped credential](develop-storage-files-storage-access-control.md#examples) to allow access to storage files. 
-- In `OPENROWSET` with `DATA_SOURCE` authentication mechanism is defined in database scoped credential assigned to the referenced data source. This option enables you to access publicly available storage, or access storage using SAS token, Managed Identity of workspace, or [Azure AD identity of caller](develop-storage-files-storage-access-control.md#user-identity) (if caller is Azure AD principal). If `DATA_SOURCE` references Azure storage that is not public, you would need to [create database-scoped credential](develop-storage-files-storage-access-control.md#examples) and reference it in `DATA SOURCE` to allow access to storage files.
+- In `OPENROWSET` with `DATA_SOURCE` the authentication mechanism is defined in the database scoped credential assigned to the referenced data source. This option enables you to access publicly available storage, or access storage using SAS token, Managed Identity of workspace, or [Azure AD identity of caller](develop-storage-files-storage-access-control.md?tabs=user-identity#) (if caller is Azure AD principal). If `DATA_SOURCE` references Azure storage that is not public, you would need to [create database-scoped credential](develop-storage-files-storage-access-control.md#examples) and reference it in `DATA SOURCE` to allow access to storage files.
 
 Caller must have `REFERENCES` permission on credential to use it to authenticate to storage.
 
diff --git a/articles/synapse-analytics/sql/develop-storage-files-storage-access-control.md b/articles/synapse-analytics/sql/develop-storage-files-storage-access-control.md
diff --git a/articles/synapse-analytics/synapse-link/how-to-connect-synapse-link-cosmos-db.md b/articles/synapse-analytics/synapse-link/how-to-connect-synapse-link-cosmos-db.md
diff --git a/articles/synapse-analytics/synapse-link/how-to-query-analytical-store-spark.md b/articles/synapse-analytics/synapse-link/how-to-query-analytical-store-spark.md
diff --git a/articles/synapse-analytics/toc.yml b/articles/synapse-analytics/toc.yml
