Merge pull request #294625 from jonburchel/2025-02-13-adf-freshness-update

Q3 ADF Freshness updates

Author: Stacyrch140

articles/data-factory/airflow-configurations.md

@@ -5,7 +5,7 @@ author: nabhishek
 ms.author: abnarain
 ms.reviewer: jburchel
 ms.topic: how-to
-ms.date: 12/11/2023
+ms.date: 02/13/2025
 ---
 
 # Supported Apache Airflow configurations

articles/data-factory/airflow-get-ip-airflow-cluster.md

@@ -5,7 +5,7 @@ author: nabhishek
 ms.author: abnarain
 ms.reviewer: jburchel
 ms.topic: how-to
-ms.date: 09/19/2023
+ms.date: 02/13/2025
 ---
 
 # Retrieve the IP address of a Workflow Orchestration Manager cluster

articles/data-factory/airflow-import-dags-blob-storage.md

@@ -5,7 +5,7 @@ description: This article shows the steps required to import DAGs by using Azure
 ms.topic: conceptual
 author: nabhishek
 ms.author: abnarain
-ms.date: 10/20/2023
+ms.date: 02/13/2025
 ---
 
 # Import DAGs by using Azure Blob Storage

articles/data-factory/airflow-install-private-package.md

@@ -5,7 +5,7 @@ author: nabhishek
 ms.author: abnarain
 ms.reviewer: jburchel
 ms.topic: how-to
-ms.date: 09/23/2023
+ms.date: 02/13/2025
 ---
 
 # Install a Private package

articles/data-factory/airflow-pricing.md

@@ -4,7 +4,7 @@ description: This article describes the pricing for Workflow Orchestration Manag
 author: nabhishek
 ms.subservice: pricing
 ms.topic: conceptual
-ms.date: 10/20/2023
+ms.date: 02/13/2025
 ms.author: abnarain
 ---
 

articles/data-factory/airflow-sync-github-repository.md

@@ -5,7 +5,7 @@ author: nabhishek
 ms.author: abnarain
 ms.reviewer: jburchel
 ms.topic: how-to
-ms.date: 09/19/2023
+ms.date: 02/13/2025
 ---
 
 # Sync a GitHub repository in Workflow Orchestration Manager
@@ -45,7 +45,7 @@ To sync your GitHub repository by using the Workflow Orchestration Manager UI:
    - **GitLab**
    - **Bitbucket**
 
-   :::image type="content" source="media/airflow-git-sync-repository/git-service-type.png" alt-text="Screenshot that shows the Git service type selection dropdown in the  environment setup dialog that appears during creation of an Workflow Orchestration Manager integration runtime.":::
+   :::image type="content" source="media/airflow-git-sync-repository/git-service-type.png" alt-text="Screenshot that shows the Git service type selection dropdown in the  environment setup dialog that appears during creation of a Workflow Orchestration Manager integration runtime.":::
 
 1. Select a credential type:
 
@@ -59,7 +59,7 @@ To sync your GitHub repository by using the Workflow Orchestration Manager UI:
      - GitLab personal access token
      - Bitbucket personal access token
 
-     :::image type="content" source="media/airflow-git-sync-repository/git-pat-credentials.png" alt-text="Screenshot that shows the Git PAT credential options in the Airflow environment setup dialog that appears during creation of an AWorkflow Orchestration Manager integration runtime.":::
+     :::image type="content" source="media/airflow-git-sync-repository/git-pat-credentials.png" alt-text="Screenshot that shows the Git PAT credential options in the Airflow environment setup dialog that appears during creation of a Workflow Orchestration Manager integration runtime.":::
    - **SPN** ([service principal name](https://devblogs.microsoft.com/devops/introducing-service-principal-and-managed-identity-support-on-azure-devops/)): Only ADO supports this credential type.
      After you select this option, fill out the remaining fields based on the selected **Git service type**:
      - **Git repo url** (required): The clone URL to the Git repository to sync.
@@ -68,7 +68,7 @@ To sync your GitHub repository by using the Workflow Orchestration Manager UI:
      - **Service principal secret** (required): A manually generated secret in the service principal whose value is used to authenticate and access the ADO repo.
      - **Service principal tenant id** (required): The service principal tenant ID.
 
-     :::image type="content" source="media/airflow-git-sync-repository/git-spn-credentials.png" alt-text="Screenshot that shows the Git SPN credential options in the Airflow environment setup dialog that appears during creation of an Workflow Orchestration Manager integration runtime.":::
+     :::image type="content" source="media/airflow-git-sync-repository/git-spn-credentials.png" alt-text="Screenshot that shows the Git SPN credential options in the Airflow environment setup dialog that appears during creation of a Workflow Orchestration Manager integration runtime.":::
 
 1. Fill in the rest of the fields with the required information.
 1. Select **Create**.
@@ -295,7 +295,7 @@ This process assumes that your private package was autosynced via Git sync. You
 
 For example, if your private package is in `/dags/test/private.whl` in a GitHub repo, you should add the requirement `/opt/airflow/git/\<repoName\>.git/dags/test/private.whl` in the Workflow Orchestration Manager environment.
 
-:::image type="content" source="media/airflow-git-sync-repository/airflow-private-package.png" alt-text="Screenshot that shows the Airflow requirements section in the Airflow environment setup dialog that appears during creation of an Workflow Orchestration Manager integration runtime.":::
+:::image type="content" source="media/airflow-git-sync-repository/airflow-private-package.png" alt-text="Screenshot that shows the Airflow requirements section in the Airflow environment setup dialog that appears during creation of a Workflow Orchestration Manager integration runtime.":::
 
 ## Related content
 

articles/data-factory/author-global-parameters.md

@@ -5,15 +5,15 @@ ms.subservice: authoring
 ms.topic: conceptual
 author: nabhishek
 ms.author: abnarain
-ms.date: 01/05/2024
+ms.date: 02/13/2025
 ai-usage: ai-assisted
 ---
 
 # Global parameters in Azure Data Factory
 
 [!INCLUDE[appliesto-adf-xxx-md](includes/appliesto-adf-xxx-md.md)]
 
-Global parameters are constants across a data factory that can be consumed by a pipeline in any expression. They're useful when you have multiple pipelines with identical parameter names and values. When promoting a data factory using the continuous integration and deployment process (CI/CD), you can override these parameters in each environment. 
+Global parameters are constants across a data factory that pipelines can consume in any expression. They're useful when you have multiple pipelines with identical parameter names and values. When promoting a data factory using the continuous integration and deployment process (CI/CD), you can override these parameters in each environment. 
 
 ## Creating global parameters
 
@@ -38,17 +38,18 @@ Global parameters can be used in any [pipeline expression](control-flow-expressi
 
 ## <a name="cicd"></a> Global parameters in CI/CD
 
-We recommend including global parameters in the ARM template during the CI/CD. The new mechanism of including global parameters in the ARM template (from 'Manage hub' -> 'ARM template' -> ‘Include global parameters in ARM template') as illustrated below, will not conflict/ override the factory-level settings as it used to do earlier, hence not requiring additional PowerShell for global parameters deployment during CI/CD.
+We recommend including global parameters in the ARM template during the CI/CD. The new mechanism of including global parameters in the ARM template (from 'Manage hub' -> 'ARM template' -> ‘Include global parameters in ARM template') as illustrated in the following image, won't conflict/ override the factory-level settings as it used to do earlier, hence not requiring extra PowerShell for global parameters deployment during CI/CD.
 
 :::image type="content" source="media/author-global-parameters/include-arm-template.png" alt-text="Screenshot of 'Include in ARM template'.":::
 
 > [!NOTE]
-> We have moved the UI experience for including global parameters from the 'Global parameters' section to the 'ARM template' section in the manage hub. 
-If you are already using the older mechanism (from 'Manage hub' -> 'Global parameters' -> 'Include in ARM template'), you can continue. We will continue to support it.
+> We moved the UI experience for including global parameters from the 'Global parameters' section to the 'ARM template' section in the Manage hub.
+
+If you're already using the older mechanism (from 'Manage hub' -> 'Global parameters' -> 'Include in ARM template'), you can continue. We'll continue to support it.
 
 The **Parameters** folder in the downloaded ARM template contains JSON files that define the parameters used in the ARM template. Each file corresponds to a specific global parameter.
 
-If you are using the older flow of integrating global parameters in your continuous integration and deployment solution, it will continue to work:
+If you're using the older flow of integrating global parameters in your continuous integration and deployment solution, it continues to work:
 
 * Include global parameters in the ARM template (from 'Manage hub' -> 'Global parameters' -> 'Include in ARM template')
 :::image type="content" source="media/author-global-parameters/include-arm-template-deprecated.png" alt-text="Screenshot of deprecated 'Include in ARM template'.":::
@@ -58,10 +59,10 @@ If you are using the older flow of integrating global parameters in your continu
 We strongly recommend using the new mechanism of including global parameters in the ARM template (from 'Manage hub' -> 'ARM template' -> 'Include global parameters in an ARM template') since it makes the CICD with global parameters much more straightforward and easier to manage.
 
 > [!NOTE]
-> The **Include global parameters in an ARM template** configuration is only available in "Git mode". Currently it is disabled in "live mode" or "Data Factory" mode.  
+> The **Include global parameters in an ARM template** configuration is only available in "Git mode". Currently it's disabled in "live mode" or "Data Factory" mode.  
 
 > [!WARNING]
->You cannot use  ‘-‘ in the parameter name. You will receive an errorcode "{"code":"BadRequest","message":"ErrorCode=InvalidTemplate,ErrorMessage=The expression >'pipeline().globalParameters.myparam-dbtest-url' is not valid: .....}". But, you can use the ‘_’ in the parameter name. 
+>You can't use  ‘-‘ in the parameter name. You receive an errorcode "{"code":"BadRequest","message":"ErrorCode=InvalidTemplate,ErrorMessage=The expression >'pipeline().globalParameters.myparam-dbtest-url' isn't valid: .....}". But, you can use the ‘_’ in the parameter name. 
 
 ## Related content
 

articles/data-factory/azure-integration-runtime-ip-addresses.md

@@ -5,7 +5,7 @@ ms.author: lle
 author: lrtoyou1223
 ms.subservice: integration-runtime
 ms.topic: conceptual
-ms.date: 01/05/2024
+ms.date: 02/13/2025
 ---
 
 # Azure Integration Runtime IP addresses
@@ -15,9 +15,7 @@ ms.date: 01/05/2024
 The IP addresses that Azure Integration Runtime uses depends on the region where your Azure integration runtime is located. *All* Azure integration runtimes that are in the same region use the same IP address ranges.
 
 > [!IMPORTANT]  
-> Azure Integration Runtime which enable Managed Virtual Network  and all data flows don't support the use of fixed IP ranges.
->
-> You can use these IP ranges for Data Movement, Pipeline and External activities executions. These IP ranges can be used for filtering in data stores/ Network Security Group (NSG)/ Firewalls for inbound access from Azure Integration runtime. 
+> The Azure integration runtime lets you used a managed virtual network. Some data flows require the use of fixed IP ranges. You can use these IP ranges for data movement, pipeline and external activity executions, as well as for filtering in data stores, network security groups (NSGs), and firewalls for inbound access from the Azure integration runtime.
 
 ## Azure Integration Runtime IP addresses: Specific regions