Merge pull request #218612 from whhender/ADLA-freshness-sweep2

JamesJBarnett · web-flow · commit eff0a411e191 · 2022-11-16T12:18:48.000-07:00
Adla freshness sweep2
diff --git a/articles/data-lake-analytics/data-lake-analytics-data-lake-tools-get-started.md b/articles/data-lake-analytics/data-lake-analytics-data-lake-tools-get-started.md
@@ -2,9 +2,9 @@
 title: Query Azure Data Lake Analytics - Visual Studio
 description: Learn how to install Data Lake Tools for Visual Studio, and how to develop and test U-SQL scripts. 
 ms.service: data-lake-analytics
-ms.reviewer: jasonh
+ms.reviewer: whhender
 ms.topic: how-to
-ms.date: 08/30/2019
+ms.date: 11/15/2022
 ---
 
 # Develop U-SQL scripts by using Data Lake Tools for Visual Studio
@@ -96,7 +96,7 @@ After the job submission, the **Job view** tab opens to show the job progress.
 * **MetaData Operations** shows all the actions that were taken on the U-SQL catalog.
 * **Data** shows all the inputs and outputs.
 * **State History** shows the timeline and state details.
-* **AU Analysis** shows how many AUs were used in the job and explore simulations of different AU allocation strategies.
+* **AU Analysis** shows how many AUs (analytics units) were used in the job and explore simulations of different AU allocation strategies.
 * **Diagnostics** provides an advanced analysis for job execution and performance optimization.
 
 ![U-SQL Visual Studio Data Lake Analytics job performance graph](./media/data-lake-analytics-data-lake-tools-get-started/data-lake-analytics-data-lake-tools-performance-graph.png)
@@ -105,7 +105,7 @@ To see the latest job status and refresh the screen, select **Refresh**.
 
 ## Check job status
 
-1. In **Server Explorer**, select **Azure** > **Data Lake Analytics**.
+1. In **Data Lake Analytics Explorer**, select **Data Lake Analytics**.
 
 1. Expand the Data Lake Analytics account name.
 
@@ -115,9 +115,9 @@ To see the latest job status and refresh the screen, select **Refresh**.
 
 ## See the job output
 
-1. In **Server Explorer**, browse to the job you submitted.
+1. In **Data Lake Analytics Explorer**, browse to the job you submitted.
 
-1. Click the **Data** tab.
+1. Select the **Data** tab in your job.
 
 1. In the **Job Outputs** tab, select the `"/data.csv"` file.
 
diff --git a/articles/data-lake-analytics/data-lake-analytics-data-lake-tools-install.md b/articles/data-lake-analytics/data-lake-analytics-data-lake-tools-install.md
@@ -2,9 +2,9 @@
 title: Install Azure Data Lake Tools for Visual Studio
 description: This article describes how to install Azure Data Lake Tools for Visual Studio. 
 ms.service: data-lake-analytics
-ms.reviewer: jasonh
+ms.reviewer: whhender
 ms.topic: how-to
-ms.date: 08/30/2019
+ms.date: 11/15/2022
 ---
 # Install Data Lake Tools for Visual Studio
 
@@ -20,7 +20,7 @@ information about Data Lake Analytics, see [Azure Data Lake Analytics overview](
   * Visual Studio 2015
   * Visual Studio 2013
 
-* **Microsoft Azure SDK for .NET** version 2.7.1 or later. Install it by using the [Web platform installer](https://www.microsoft.com/web/downloads/platform.aspx).
+* **Microsoft Azure SDK for .NET** [version 2.7.1 or later](https://azure.microsoft.com/downloads/).
 * A **Data Lake Analytics** account. To create an account, see [Get Started with Azure Data Lake Analytics using Azure portal](data-lake-analytics-get-started-portal.md).
 
 ## Install Azure Data Lake Tools for Visual Studio 2017 or Visual Studio 2019
diff --git a/articles/data-lake-analytics/data-lake-analytics-diagnostic-logs.md b/articles/data-lake-analytics/data-lake-analytics-diagnostic-logs.md
@@ -2,10 +2,8 @@
 title: Enable and view diagnostic logs for Azure Data Lake Analytics
 description: Understand how to set up and access diagnostic logs for Azure Data Lake Analytics
 ms.service: data-lake-analytics
-
-
 ms.topic: how-to
-ms.date: 10/14/2022
+ms.date: 11/15/2022
 ---
 # Accessing diagnostic logs for Azure Data Lake Analytics
 
diff --git a/articles/data-lake-analytics/data-lake-analytics-manage-use-portal.md b/articles/data-lake-analytics/data-lake-analytics-manage-use-portal.md
@@ -2,45 +2,41 @@
 title: Manage Azure Data Lake Analytics by using the Azure portal
 description: This article describes how to use the Azure portal to manage Data Lake Analytics accounts, data sources, users, & jobs.
 ms.service: data-lake-analytics
-ms.reviewer: jasonh
+ms.reviewer: whhender
 ms.topic: how-to
-ms.date: 12/05/2016
+ms.date: 11/15/2022
 ms.custom: subject-rbac-steps
 ---
 # Manage Azure Data Lake Analytics using the Azure portal
 [!INCLUDE [manage-selector](../../includes/data-lake-analytics-selector-manage.md)]
 
-This article describes how to manage Azure Data Lake Analytics accounts, data sources, users, and jobs by using the Azure portal.
-
+[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
 
-<!-- ################################ -->
-<!-- ################################ -->
+This article describes how to manage Azure Data Lake Analytics accounts, data sources, users, and jobs by using the Azure portal.
 
 ## Manage Data Lake Analytics accounts
 
 ### Create an account
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Click **Create a resource** > **Intelligence + analytics** > **Data Lake Analytics**.
+2. Select **Create a resource** and search for **Data Lake Analytics**.
 3. Select values for the following items: 
    1. **Name**: The name of the Data Lake Analytics account.
    2. **Subscription**: The Azure subscription used for the account.
    3. **Resource Group**: The Azure resource group in which to create the account. 
    4. **Location**: The Azure datacenter for the Data Lake Analytics account. 
    5. **Data Lake Store**: The default store to be used for the Data Lake Analytics account. The Azure Data Lake Store account and the Data Lake Analytics account must be in the same location.
-4. Click **Create**. 
+4. Select **Create**. 
 
 ### Delete a Data Lake Analytics account
 
 Before you delete a Data Lake Analytics account, delete its default Data Lake Store account.
 
 1. In the Azure portal, go to your Data Lake Analytics account.
-2. Click **Delete**.
+2. Select **Delete**.
 3. Type the account name.
-4. Click **Delete**.
+4. Select **Delete**.
 
-<!-- ################################ -->
-<!-- ################################ -->
 
 ## Manage data sources
 
@@ -54,11 +50,11 @@ You can use Data Explorer to browse data sources and perform basic file manageme
 ### Add a data source
 
 1. In the Azure portal, go to your Data Lake Analytics account.
-2. Click **Data Sources**.
-3. Click **Add Data Source**.
+2. Select **Data explorer**.
+3. Select **Add Data Source**.
     
    * To add a Data Lake Store account, you need the account name and access to the account to be able to query it.
-   * To add Azure Blob storage, you need the storage account and the account key. To find them, go to the storage account in the portal.
+   * To add Azure Blob storage, you need the storage account and the account key. To find them, go to the storage account in the portal and select **Access keys**.
 
 ## Set up firewall rules
 
@@ -69,20 +65,20 @@ If other Azure services, like Azure Data Factory or VMs, connect to the Data Lak
 ### Set up a firewall rule
 
 1. In the Azure portal, go to your Data Lake Analytics account.
-2. On the menu on the left, click **Firewall**.
+2. On the menu on the left, select **Firewall**.
 
 ## Add a new user
 
 You can use the **Add User Wizard** to easily provision new Data Lake users.
 
 1. In the Azure portal, go to your Data Lake Analytics account.
-2. On the left, under **Getting Started**, click **Add User Wizard**.
-3. Select a user, and then click **Select**.
-4. Select a role, and then click **Select**. To set up a new developer to use Azure Data Lake, select the **Data Lake Analytics Developer** role.
-5. Select the access control lists (ACLs) for the U-SQL databases. When you're satisfied with your choices, click **Select**.
-6. Select the ACLs for files. For the default store, don't change the ACLs for the root folder "/" and for the /system folder. Click **Select**.
-7. Review all your selected changes, and then click **Run**.
-8. When the wizard is finished, click **Done**.
+2. On the left, under **Getting Started**, select **Add User Wizard**.
+3. Select a user, and then select **Select**.
+4. Select a role, and then select **Select**. To set up a new developer to use Azure Data Lake, select the **Data Lake Analytics Developer** role.
+5. Select the access control lists (ACLs) for the U-SQL databases. When you're satisfied with your choices, select **Select**.
+6. Select the ACLs for files. For the default store, don't change the ACLs for the root folder "/" and for the /system folder. select **Select**.
+7. Review all your selected changes, and then select **Run**.
+8. When the wizard is finished, select **Done**.
 
 ## Manage Azure role-based access control
 
@@ -94,6 +90,7 @@ The standard Azure roles have the following capabilities:
 * **Reader**: Can monitor jobs.
 
 Use the Data Lake Analytics Developer role to enable U-SQL developers to use the Data Lake Analytics service. You can use the Data Lake Analytics Developer role to:
+
 * Submit jobs.
 * Monitor job status and the progress of jobs submitted by any user.
 * See the U-SQL scripts from jobs submitted by any user.
@@ -115,46 +112,48 @@ Use the Data Lake Analytics Developer role to enable U-SQL developers to use the
 >If a user or a security group needs to submit jobs, they also need permission on the store account. For more information, see [Secure data stored in Data Lake Store](../data-lake-store/data-lake-store-secure-data.md).
 >
 
-<!-- ################################ -->
-<!-- ################################ -->
-
 ## Manage jobs
 
 ### Submit a job
 
 1. In the Azure portal, go to your Data Lake Analytics account.
 
-2. Click **New Job**. For each job,  configure:
+2. Select **New Job**. For each job,  configure:
 
     1. **Job Name**: The name of the job.
-    2. **Priority**: Lower numbers have higher priority. If two jobs are queued, the one with lower priority value runs first.
-    3. **Parallelism**: The maximum number of compute processes to reserve for this job.
+    2. **Priority**: This is under **More options**. Lower numbers have higher priority. If two jobs are queued, the one with lower priority value runs first.
+    3. **AUs**: The maximum number of Analytics Units, or compute processes to reserve for this job.
+    4. **Runtime**: Also under **More options**. Select the Default runtime unless you've received a custom runtime.
+
+3. Add your script.
 
-3. Click **Submit Job**.
+4. Select **Submit Job**.
 
 ### Monitor jobs
 
 1. In the Azure portal, go to your Data Lake Analytics account.
-2. Click **View All Jobs**. A list of all the active and recently finished jobs in the account is shown.
-3. Optionally, click **Filter** to help you find the jobs by **Time Range**, **Job Name**, and **Author** values. 
+2. Select **View All Jobs** at the top of the page. A list of all the active and recently finished jobs in the account is shown.
+3. Optionally, select **Filter** to help you find the jobs by **Time Range**, **Status**, **Job Name**, **Job ID**, **Pipeline name** or **Pipeline ID**, **Recurrence name** or **Recurrence ID**, and **Author** values.
 
 ### Monitoring pipeline jobs
+
 Jobs that are part of a pipeline work together, usually sequentially, to accomplish a specific scenario. For example, you can have a pipeline that cleans, extracts, transforms, aggregates usage for customer insights. Pipeline jobs are identified using the "Pipeline" property when the job was submitted. Jobs scheduled using ADF V2 will automatically have this property populated. 
 
 To view a list of U-SQL jobs that are part of pipelines: 
 
 1. In the Azure portal, go to your Data Lake Analytics accounts.
-2. Click **Job Insights**. The "All Jobs" tab will be defaulted, showing a list of running, queued, and ended jobs.
-3. Click the **Pipeline Jobs** tab. A list of pipeline jobs will be shown along with aggregated statistics for each pipeline.
+2. Select **Job Insights**. The "All Jobs" tab will be defaulted, showing a list of running, queued, and ended jobs.
+3. Select the **Pipeline Jobs** tab. A list of pipeline jobs will be shown along with aggregated statistics for each pipeline.
 
 ### Monitoring recurring jobs
+
 A recurring job is one that has the same business logic but uses different input data every time it runs. Ideally, recurring jobs should always succeed, and have relatively stable execution time; monitoring these behaviors will help ensure the job is healthy. Recurring jobs are identified using the "Recurrence" property. Jobs scheduled using ADF V2 will automatically have this property populated.
 
 To view a list of U-SQL jobs that are recurring: 
 
 1. In the Azure portal, go to your Data Lake Analytics accounts.
-2. Click **Job Insights**. The "All Jobs" tab will be defaulted, showing a list of running, queued, and ended jobs.
-3. Click the **Recurring Jobs** tab. A list of recurring jobs will be shown along with aggregated statistics for each recurring job.
+2. Select **Job Insights**. The "All Jobs" tab will be defaulted, showing a list of running, queued, and ended jobs.
+3. Select the **Recurring Jobs** tab. A list of recurring jobs will be shown along with aggregated statistics for each recurring job.
 
 ## Next steps
 
diff --git a/articles/data-lake-analytics/data-lake-analytics-whats-new.md b/articles/data-lake-analytics/data-lake-analytics-whats-new.md
@@ -5,11 +5,13 @@ author: xujiang1
 ms.service: data-lake-analytics
 ms.topic: overview
 ms.author: xujiang1
-ms.date: 07/31/2020
+ms.date: 11/16/2022
 ---
 
 # What's new in Data Lake Analytics?
 
+[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
+
 Azure Data Lake Analytics is updated on an aperiodic basis for certain components. To stay updated with the most recent update, this article provides you with information about:
 
 - The notification of key component beta preview
@@ -18,7 +20,7 @@ Azure Data Lake Analytics is updated on an aperiodic basis for certain component
 
 ## Notification of key component beta preview
 
-No key component beta version available for preview. 
+No key component beta version available for preview.
 
 ## U-SQL runtime
 
@@ -32,17 +34,13 @@ The runtime version will be updated aperiodically. And the previous runtime will
 > - Choosing a runtime that is different from the default has the potential to break your U-SQL jobs. It is highly recommended not to use these non-default versions for production, but for testing only.
 > - The non-default runtime version has a fixed lifecycle. It will be automatically expired.
 
-The following version is the current default runtime version.
-
-- **release_20200707_scope_2b8d563_usql**
-
 To get understanding how to troubleshoot U-SQL runtime failures, refer to [Troubleshoot U-SQL runtime failures](runtime-troubleshoot.md).
 
 ## .NET Framework
 
 Azure Data Lake Analytics now is using the **.NET Framework v4.7.2**. 
 
-If your Azure Data Lake Analytics U-SQL script code uses custom assemblies, and those custom assemblies use .NET libraries, validate your code to check if there is any breakings.
+If your Azure Data Lake Analytics U-SQL script code uses custom assemblies, and those custom assemblies use .NET libraries, validate your code to check if there are any errors.
 
 To get understanding how to troubleshoot a .NET upgrade using [Troubleshoot a .NET upgrade](runtime-troubleshoot.md).
 
diff --git a/articles/data-lake-analytics/migrate-azure-data-lake-analytics-to-synapse.md b/articles/data-lake-analytics/migrate-azure-data-lake-analytics-to-synapse.md
@@ -6,12 +6,12 @@ ms.author: lingluo
 ms.service: data-lake-analytics
 ms.topic: how-to
 ms.custom: migrate-azure-data-lake-analytics-to-synapse
-ms.date: 08/25/2021
+ms.date: 11/15/2022
 ---
 
 # Migrate Azure Data Lake Analytics to Azure Synapse Analytics
 
-Microsoft launched the Azure Synapse Analytics which aims at bringing both data lakes and data warehouse together for a unique big data analytics experience. It will help customers gather and analyze all the varying data, to solve data inefficiency, and work together. Moreover, Synapse’s integration with Azure Machine Learning and Power BI will allow the improved ability for organizations to get insights from its data as well as execute machine learning to all its smart apps. 
+Microsoft launched the Azure Synapse Analytics that aims at bringing both data lakes and data warehouse together for a unique big data analytics experience. It will help customers gather and analyze all the varying data, to solve data inefficiency, and work together. Moreover, Synapse’s integration with Azure Machine Learning and Power BI will allow the improved ability for organizations to get insights from its data and execute machine learning to all its smart apps. 
 
 The document shows you how to do the migration from Azure Data Lake Analytics to Azure Synapse Analytics. 
 
@@ -38,7 +38,7 @@ The document shows you how to do the migration from Azure Data Lake Analytics to
 
 1.	Identify jobs and data that you'll migrate.
     -	Take this opportunity to clean up those jobs that you no longer use. Unless you plan to migrate all your jobs at one time, take this time to identify logical groups of jobs that you can migrate in phases.
-    -	Evaluate the size of the data and understand Apache Spark data format. Review your U-SQL scripts and evaluate the scripts re-writing efforts and understand the Apache Spark code concept.
+    -	Evaluate the size of the data and understand Apache Spark data format. Review your U-SQL scripts and evaluate the scripts rewriting efforts and understand the Apache Spark code concept.
 
 2.	Determine the impact that a migration will have on your business. For example, whether you can afford any downtime while migration takes place.
 
