Adding retirement flag to most pages

Author: whhender

articles/data-lake-analytics/data-lake-analytics-account-policies.md

@@ -8,13 +8,15 @@ ms.date: 04/30/2018
 ---
 # Manage Azure Data Lake Analytics using Account Policies
 
-Account policies help you control how resources an Azure Data Lake Analytics account are used. These policies allow you to control the cost of using Azure Data Lake Analytics. For example, with these policies you can prevent unexpected cost spikes by limiting how many AUs the account can simultaneously use.## Account-level policies
-
-These policies apply to all jobs in a Data Lake Analytics account.
+Account policies help you control how resources an Azure Data Lake Analytics account are used. These policies allow you to control the cost of using Azure Data Lake Analytics. For example, with these policies you can prevent unexpected cost spikes by limiting how many AUs the account can simultaneously use.
 
 [!INCLUDE [retirement-flag](includes/retirement-flag.md)]
 
-## Maximum number of AUs in a Data Lake Analytics account
+## Account-level policies
+
+These policies apply to all jobs in a Data Lake Analytics account.
+
+### Maximum number of AUs in a Data Lake Analytics account
 
 A policy controls the total number of Analytics Units (AUs) your Data Lake Analytics account can use. By default, the value is set to 250. For example, if this value is set to 250 AUs, you can have one job running with 250 AUs assigned to it, or 10 jobs running with 25 AUs each. Additional jobs that are submitted are queued until the running jobs are finished. When running jobs are finished, AUs are freed up for the queued jobs to run.
 
@@ -28,7 +30,7 @@ To change the number of AUs for your Data Lake Analytics account:
    > [!NOTE]
    > If you need more than the default (250) AUs, in the portal, click **Help+Support** to submit a support request. The number of AUs available in your Data Lake Analytics account can be increased.
 
-## Maximum number of jobs that can run simultaneously
+### Maximum number of jobs that can run simultaneously
 
 This policy limits how many jobs can run simultaneously. By default, this value is set to 20. If your Data Lake Analytics has AUs available, new jobs are scheduled to run immediately until the total number of running jobs reaches the value of this policy. When you reach the maximum number of jobs that can run simultaneously, subsequent jobs are queued in priority order until one or more running jobs complete (depending on available AUs).
 
@@ -42,7 +44,7 @@ To change the number of jobs that can run simultaneously:
    > [!NOTE]
    > If you need to run more than the default (20) number of jobs, in the portal, click **Help+Support** to submit a support request. The number of jobs that can run simultaneously in your Data Lake Analytics account can be increased.
 
-## How long to keep job metadata and resources
+### How long to keep job metadata and resources
 
 When your users run U-SQL jobs, the Data Lake Analytics service keeps all related files. These files include the U-SQL script, the DLL files referenced in the U-SQL script, compiled resources, and statistics. The files are in the /system/ folder of the default Azure Data Lake Storage account. This policy controls how long these resources are stored before they are automatically deleted (the default is 30 days). You can use these files for debugging, and for performance-tuning of jobs that you'll rerun in the future.
 

articles/data-lake-analytics/data-lake-analytics-data-lake-tools-view-jobs.md

@@ -8,10 +8,11 @@ ms.topic: how-to
 ms.date: 08/02/2017
 ---
 # Use Job Browser and Job View for Azure Data Lake Analytics
-The Azure Data Lake Analytics service archives submitted jobs in a query store. In this article, you learn how to use Job Browser and Job View in Azure Data Lake Tools for Visual Studio to find the historical job information. 
 
 [!INCLUDE [retirement-flag](includes/retirement-flag.md)]
 
+The Azure Data Lake Analytics service archives submitted jobs in a query store. In this article, you learn how to use Job Browser and Job View in Azure Data Lake Tools for Visual Studio to find the historical job information. 
+
 By default, the Data Lake Analytics service archives the jobs for 30 days. The expiration period can be configured from the Azure portal by configuring the customized expiration policy. You will not be able to access the job information after expiration. 
 
 ## Prerequisites

articles/data-lake-analytics/data-lake-analytics-monitor-and-troubleshoot-jobs-tutorial.md

@@ -8,7 +8,7 @@ ms.date: 12/05/2016
 ---
 # Monitor jobs in Azure Data Lake Analytics using the Azure Portal
 
-v
+[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
 
 ## To see all the jobs
 

articles/data-lake-analytics/data-lake-analytics-u-sql-cognitive.md

@@ -8,8 +8,6 @@ ms.date: 06/05/2018
 ---
 # Get started with the Cognitive capabilities of U-SQL
 
-[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
-
 ## Overview
 Cognitive capabilities for U-SQL enable developers to use put intelligence in their big data programs. 
 

articles/data-lake-analytics/data-lake-analytics-u-sql-develop-user-defined-operators.md

@@ -10,8 +10,6 @@ ms.date: 12/05/2016
 # Develop U-SQL user-defined operators (UDOs)
 This article describes how to develop user-defined operators to process data in a U-SQL job.
 
-[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
-
 ## Define and use a user-defined operator in U-SQL
 
 ### To create and submit a U-SQL job

articles/data-lake-analytics/data-lake-analytics-u-sql-develop-with-python-r-csharp-in-vscode.md

@@ -12,9 +12,6 @@ Learn how to use Visual Studio Code (VSCode) to write Python, R and C# code behi
 
 Before writing code-behind custom code, you need to open a folder or a workspace in VSCode.
 
-[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
-
-
 ## Prerequisites for Python and R
 Register Python and, R extensions assemblies for your ADL account. 
 1. Open your account in portal.

articles/data-lake-analytics/data-lake-analytics-u-sql-programmability-guide-UDO.md

@@ -9,8 +9,6 @@ ms.date: 06/30/2017
 
 # U-SQL user-defined objects overview
 
-[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
-
 ## U-SQL: user-defined objects: UDO
 U-SQL enables you to define custom programmability objects, which are called user-defined objects or UDO.
 

articles/data-lake-analytics/data-lake-analytics-u-sql-programmability-guide-UDT-AGG.md

@@ -9,8 +9,6 @@ ms.date: 06/30/2017
 
 # U-SQL programmability guide - UDT and UDAGG
 
-[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
-
 ## Use user-defined types: UDT
 User-defined types, or UDT, is another programmability feature of U-SQL. U-SQL UDT acts like a regular C# user-defined type. C# is a strongly typed language that allows the use of built-in and custom user-defined types.
 

articles/data-lake-analytics/data-lake-analytics-u-sql-programmability-guide-applier.md

@@ -9,8 +9,6 @@ ms.date: 06/30/2017
 
 # Use user-defined applier 
 
-[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
-
 ## U-SQL UDO: user-defined applier
 A U-SQL user-defined applier enables you to invoke a custom C# function for each row that's returned by the outer table expression of a query. The right input is evaluated for each row from the left input, and the rows that are produced are combined for the final output. The list of columns that are produced by the APPLY operator are the combination of the set of columns in the left and the right input.
 

articles/data-lake-analytics/data-lake-analytics-u-sql-programmability-guide-combiner.md

@@ -9,8 +9,6 @@ ms.date: 06/30/2017
 
 # Use user-defined combiner
 
-[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
-
 ## U-SQL UDO: user-defined combiner
 User-defined combiner, or UDC, enables you to combine rows from left and right rowsets, based on custom logic. User-defined combiner is used with COMBINE expression.