Merge pull request #298555 from whhender/jasonhorner-updates

Jasonhorner updates

Author: prmerger-automator[bot]

articles/data-factory/author-management-hub.md

@@ -50,7 +50,7 @@ To override the generated Resource Manager template parameters when publishing f
 
 ### Triggers
 
-Triggers determine when a pipeline run should be kicked off. Currently triggers can be on a wall clock schedule, operate on a periodic interval, or depend on an event. For more information, learn about [trigger execution](concepts-pipeline-execution-triggers.md#trigger-execution-with-json). In the management hub, you can create, edit, delete, or view the current state of a trigger.
+Triggers determine when a pipeline run should be kicked off. Currently triggers can be on a wall clock schedule, operate on a periodic interval, or depend on an event. For more information, learn about [trigger execution](concepts-pipeline-execution-triggers.md#trigger-types). In the management hub, you can create, edit, delete, or view the current state of a trigger.
 
 :::image type="content" source="media/author-management-hub/management-hub-triggers.png" alt-text="Screenshot that shows where to create, edit, delete, nor view the current state of a trigger.":::
 

articles/data-factory/concepts-pipeline-execution-triggers.md

@@ -33,10 +33,10 @@ You will see the trigger configuration window, allowing you to choose the trigge
 
 :::image type="content" source="media/concepts-pipeline-execution-triggers/new-trigger-configuration.png" alt-text="Shows the new trigger configuration window with the type dropdown showing the various types of triggers you can create.":::
 
-Read more about [scheduled](#schedule-trigger-with-json), [tumbling window](#tumbling-window-trigger), [storage event](#event-based-trigger), and [custom event](#event-based-trigger) triggers below.
+Read more about [scheduled](#schedule-trigger), [tumbling window](#tumbling-window-trigger), [storage event](#event-based-trigger), and [custom event](#event-based-trigger) triggers below.
 
 
-## Manual execution with JSON
+## Manual execution
 
 The manual execution of a pipeline is also referred to as _on-demand_ execution.
 
@@ -152,7 +152,7 @@ https://management.azure.com/subscriptions/mySubId/resourceGroups/myResourceGrou
 
 For a complete sample, see [Quickstart: Create a data factory by using the REST API](quickstart-create-data-factory-rest-api.md).
 
-## Trigger execution with JSON
+## Trigger Types
 
 Triggers are another way that you can execute a pipeline run. Triggers represent a unit of processing that determines when a pipeline execution needs to be kicked off. Currently, the service supports three types of triggers:
 
@@ -190,7 +190,7 @@ Pipelines and triggers have a many-to-many relationship (except for the tumbling
 }
 ```
 
-## Schedule trigger with JSON
+## Schedule trigger
 A schedule trigger runs pipelines on a wall-clock schedule. This trigger supports periodic and advanced calendar options. For example, the trigger supports intervals like "weekly" or "Monday at 5:00 PM and Thursday at 9:00 PM." The schedule trigger is flexible because the dataset pattern is agnostic, and the trigger doesn't discern between time-series and non-time-series data.
 
 For more information about schedule triggers and, for examples, see [Create a trigger that runs a pipeline on a schedule](how-to-create-schedule-trigger.md).
@@ -259,6 +259,12 @@ The following table provides a high-level overview of the major schema elements
 | **interval** | A positive integer that denotes the interval for the **frequency** value. The **frequency** value determines how often the trigger runs. For example, if the **interval** is 3 and the **frequency** is "week", the trigger recurs every three weeks. |
 | **schedule** | The recurrence schedule for the trigger. A trigger with a specified **frequency** value alters its recurrence based on a recurrence schedule. The **schedule** property contains modifications for the recurrence that are based on minutes, hours, weekdays, month days, and week number. |
 
+ > [!NOTE]
+ > For time zones that observe daylight saving, trigger time auto-adjusts for the twice-a-year change, if the recurrence is set to **Days** or above. To opt out of the daylight saving change, select a time zone that doesn't observe daylight saving, for instance, UTC.
+ >
+ > Daylight saving adjustment only happens for a trigger with the recurrence set to **Days** or above. If the trigger is set to **Hours** or **Minutes** frequency, it continues to fire at regular intervals.
+
+
 ### Schedule trigger example
 
 ```json
@@ -376,6 +382,15 @@ The examples assume that the **interval** value is 1 and that the **frequency**
 | `{"minutes":[0,15,30,45], "monthlyOccurrences":[{"day":"friday", "occurrence":-1}]}` | Run every 15 minutes on the last Friday of the month. |
 | `{"minutes":[15,45], "hours":[5,17], "monthlyOccurrences":[{"day":"wednesday", "occurrence":3}]}` | Run at 5:15 AM, 5:45 AM, 5:15 PM, and 5:45 PM on the third Wednesday of every month. |
 
+## Event-based trigger
+
+An event-based trigger runs pipelines in response to an event. From behavior perspective, if you stop and start an event-based trigger, it resumes old trigger pattern which may result in unwanted trigger of the pipeline. In this case, you should delete and create new event based trigger. The new trigger starts fresh without history. There are two flavors of event-based triggers.
+
+* _Storage event trigger_ runs a pipeline against events happening in a Storage account, such as the arrival of a file, or the deletion of a file in Azure Blob Storage account.
+* _Custom event trigger_ processes and handles [custom articles](../event-grid/custom-topics.md) in Event Grid
+
+For more information about event-based triggers, see [Storage Event Trigger](how-to-create-event-trigger.md) and [Custom Event Trigger](how-to-create-custom-event-trigger.md).
+
 ## Trigger type comparison
 
 The tumbling window trigger and the schedule trigger both operate on time heartbeats. How are they different?
@@ -394,16 +409,6 @@ The following table provides a comparison of the tumbling window trigger and sch
 | **System variables** | Along with @trigger().scheduledTime and @trigger().startTime, it also supports the use of the **WindowStart** and **WindowEnd** system variables. Users can access `trigger().outputs.windowStartTime` and `trigger().outputs.windowEndTime` as trigger system variables in the trigger definition. The values are used as the window start time and window end time, respectively. For example, for a tumbling window trigger that runs every hour, for the window 1:00 AM to 2:00 AM, the definition is `trigger().outputs.windowStartTime = 2017-09-01T01:00:00Z` and `trigger().outputs.windowEndTime = 2017-09-01T02:00:00Z`. | Only supports default @trigger().scheduledTime and @trigger().startTime variables. |
 | **Pipeline-to-trigger relationship** | Supports a one-to-one relationship. Only one pipeline can be triggered. | Supports many-to-many relationships. Multiple triggers can kick off a single pipeline. A single trigger can kick off multiple pipelines. |
 
-## Event-based trigger
-
-An event-based trigger runs pipelines in response to an event. From behavior perspective, if you stop and start an event-based trigger, it resumes old trigger pattern which may result in unwanted trigger of the pipeline. In this case, you should delete and create new event based trigger. The new trigger starts fresh without history. There are two flavors of event-based triggers.
-
-* _Storage event trigger_ runs a pipeline against events happening in a Storage account, such as the arrival of a file, or the deletion of a file in Azure Blob Storage account.
-* _Custom event trigger_ processes and handles [custom articles](../event-grid/custom-topics.md) in Event Grid
-
-For more information about event-based triggers, see [Storage Event Trigger](how-to-create-event-trigger.md) and [Custom Event Trigger](how-to-create-custom-event-trigger.md).
-
-
 ## Related content
 
 See the following tutorials:

articles/data-factory/control-flow-system-variables.md

@@ -39,7 +39,7 @@ These system variables can be referenced anywhere in the pipeline JSON.
 
 ## Schedule trigger scope
 
-These system variables can be referenced anywhere in the trigger JSON for triggers of type [ScheduleTrigger](concepts-pipeline-execution-triggers.md#schedule-trigger-with-json).
+These system variables can be referenced anywhere in the trigger JSON for triggers of type [ScheduleTrigger](concepts-pipeline-execution-triggers.md#schedule-trigger).
 
 | Variable Name | Description |
 | --- | --- |

articles/data-factory/how-to-create-custom-event-trigger.md

@@ -168,5 +168,5 @@ Specifically, you need `Microsoft.EventGrid/EventSubscriptions/Write` permission
 
 ## Related content
 
-* Get detailed information about [trigger execution](concepts-pipeline-execution-triggers.md#trigger-execution-with-json).
+* Get detailed information about [trigger execution](concepts-pipeline-execution-triggers.md#trigger-types).
 * Learn how to [reference trigger metadata in pipeline runs](how-to-use-trigger-parameterization.md).

articles/data-factory/how-to-create-event-trigger.md

@@ -154,5 +154,5 @@ Three noticeable callouts in the workflow are related to event triggering pipeli
 
 ## Related content
 
-* For more information about triggers, see [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md#trigger-execution-with-json).
+* For more information about triggers, see [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md#trigger-types).
 * To reference trigger metadata in a pipeline, see [Reference trigger metadata in pipeline runs](how-to-use-trigger-parameterization.md).

articles/data-factory/how-to-create-schedule-trigger.md

@@ -590,5 +590,5 @@ The examples assume that the `interval` value is `1` and that the `frequency` va
 
 ## Related content
 
-- For more information about triggers, see [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md#trigger-execution-with-json).
+- For more information about triggers, see [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md#trigger-types).
 - To learn how to reference trigger metadata in pipeline, see [Reference trigger metadata in pipeline runs](how-to-use-trigger-parameterization.md).

articles/data-factory/how-to-create-tumbling-window-trigger.md

@@ -365,6 +365,6 @@ To monitor trigger runs and pipeline runs in the Azure portal, see [Monitor pipe
 
 ## Related content
 
-* [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md#trigger-execution-with-json)
+* [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md#trigger-types)
 * [Create a tumbling window trigger dependency](tumbling-window-trigger-dependency.md)
 * [Reference trigger metadata in pipeline runs](how-to-use-trigger-parameterization.md)

articles/data-factory/how-to-use-trigger-parameterization.md

@@ -141,4 +141,4 @@ To use the values in a pipeline, utilize parameters, like `@pipeline().parameter
 
 ## Related content
 
-For more information about triggers, see [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md#trigger-execution-with-json).
+For more information about triggers, see [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md#trigger-types).