Merge pull request #264706 from jonburchel/2024-01-30-merge-public-prs

2024 01 30 merge public prs

Author: prmerger-automator[bot]

articles/data-factory/continuous-integration-delivery-improvements.md

@@ -145,9 +145,9 @@ Follow these steps to get started:
 
    # Installs Node and the npm packages saved in your package.json file in the build
 
-   - task: NodeTool@0
+   - task: UseNode@1
      inputs:
-       versionSpec: '14.x'
+       version: '18.x'
      displayName: 'Install Node.js'
 
    - task: Npm@1

articles/data-factory/copy-activity-overview.md

@@ -170,6 +170,11 @@ For other scenarios than binary file copy, copy activity rerun starts from the b
 
 While copying data from source to sink, in scenarios like data lake migration, you can also choose to preserve the metadata and ACLs along with data using copy activity. See [Preserve metadata](copy-activity-preserve-metadata.md) for details.
 
+## Add metadata tags to file based sink
+When the sink is Azure Storage based (Azure data lake storage or Azure Blob Storage), we can opt to add some metadata to the files. These metadata will be appearing as part of the file properties as Key-Value pairs. 
+For all the types of file based sinks, you can add metadata involving dynamic content using the pipeline parameters, system variables, functions and variables. 
+In addition to this, for binary file based sink, you have the option to add Last Modified datetime (of the source file) using the keyword $$LASTMODIFIED, as well as custom values as a metadata to the sink file. 
+
 ## Schema and data type mapping
 
 See [Schema and data type mapping](copy-activity-schema-and-type-mapping.md) for information about how the Copy activity maps your source data to your sink.