More zones and remove all inclusive moniker ranges

Author: Steve Danielson

docs/pipelines/process/scheduled-triggers.md

@@ -76,8 +76,6 @@ schedules:
 
 ::: moniker-end
 
-::: moniker range="<=azure-devops"
-
 Scheduled pipelines in YAML have the following constraints.
 
 - The time zone for cron schedules is UTC. [You can get AI assistance from GitHub Copilot to create your cron expressions](#use-github-copilot-to-create-a-cron-expression).
@@ -150,8 +148,6 @@ schedules:
 
 Because `release` was added to the branch filters in the `main` branch, but **not** to the branch filters in the `release` branch, the `release` branch won't be built on that schedule. Only when the `release` branch is added to the branch filters in the YAML file **in the release branch** will the scheduled build be added to the scheduler.
 
-::: moniker-end
-
 ::: moniker range=">=azure-devops-2022"
 
 ### Batch considerations for scheduled triggers
@@ -220,9 +216,7 @@ If your repository is Azure Repos Git, GitHub, or Other Git, then you can also s
 
 ## Examples
 
-#### [YAML](#tab/yaml/)
-
-::: moniker range="<=azure-devops"
+:::zone pivot="pipelines-yaml"
 
 The following example defines two schedules: 
 
@@ -253,14 +247,12 @@ The second schedule, **Weekly Sunday build**, runs a pipeline at noon on Sundays
 
 For more examples, see [Migrating from the classic editor](#migrating-from-the-classic-editor).
 
-::: moniker-end
+:::zone-end
 
-#### [Classic](#tab/classic/)
+:::zone pivot="pipelines-classic"
 
 #### Example: Nightly build of Git repo in multiple time zones
 
-::: moniker range="<=azure-devops"
-
 In this example, the classic editor scheduled trigger has two entries, which produce the following builds.
 
 * Every Monday - Friday at 3:00 AM (UTC + 5:30 time zone), build branches that meet the `features/india/*` branch filter criteria
@@ -271,14 +263,8 @@ In this example, the classic editor scheduled trigger has two entries, which pro
 
     ![Scheduled trigger UTC -5:00 time zone](media/triggers/scheduled-trigger-git-nc.png)
 
-::: moniker-end
-
 #### Example: Nightly build with different frequencies
 
-::: moniker range="<=azure-devops"
-
-**Azure Pipelines and Azure DevOps 2019 Server**
-
 In this example, the classic editor scheduled trigger has two entries, producing the following builds.
 
 * Every Monday - Friday at 3:00 AM UTC, build branches that meet the `main` and `releases/*` branch filter criteria
@@ -289,16 +275,12 @@ In this example, the classic editor scheduled trigger has two entries, producing
 
     ![Scheduled trigger frequency 2, Azure Pipelines and Azure DevOps 2019 Server.](media/triggers/scheduled-trigger-git-weekly-night.png)
 
-::: moniker-end
+:::zone-end
 
-* * *
+:::zone pivot="pipelines-yaml"
 
 ## Cron syntax
 
-#### [YAML](#tab/yaml/)
-
-::: moniker range="<=azure-devops"
-
 Each Azure Pipelines scheduled trigger cron expression is a space-delimited expression with five entries in the following order. The expression is enclosed in single quotes `'`.
 
 ```
@@ -370,19 +352,11 @@ Build a UTC cron expression for Monday through Friday at 12:30 AM Central Europe
 
 *Copilot is powered by AI, so surprises and mistakes are possible. For more information, see [Copilot general use FAQs](https://aka.ms/copilot-general-use-faqs).*
 
-::: moniker-end
-
-#### [Classic](#tab/classic/)
-
-Classic schedules are defined using a graphical editor instead of cron syntax. For information on defining classic schedules, see [Examples](#examples).
-
-* * *
+:::zone-end
 
 ## Scheduled runs view
 
-#### [YAML](#tab/yaml/)
-
-::: moniker range="<=azure-devops"
+:::zone pivot="pipelines-yaml"
 
 You can view a preview of upcoming scheduled builds by choosing **Scheduled runs** from the context menu on the [pipeline details page](../create-first-pipeline.md#view-pipeline-details) for your pipeline.
 
@@ -411,10 +385,9 @@ The **Scheduled runs** windows displays the times converted to the local time zo
 > [!NOTE]
 > If you update the schedule for a running pipeline, the **Scheduled runs** view isn't updated with the new schedule until the currently running pipeline completes.
 
-::: moniker-end
+:::zone-end
 
-#### [Classic](#tab/classic/)
-::: moniker range=">= azure-devops-2020"
+:::zone pivot="pipelines-classic"
 
 You can view a preview of upcoming scheduled builds by choosing **Scheduled runs** from the context menu on the [pipeline details page](../create-first-pipeline.md#view-pipeline-details) for your pipeline. 
 
@@ -424,22 +397,14 @@ After you create or update your scheduled triggers, you can verify them using th
 
 ![Scheduled runs](media/triggers/scheduled-runs-classic.png)
 
-::: moniker-end
-
-* * *
+:::zone-end
 
 <a name="always"></a>
 ## Running even when there are no code changes
 
-::: moniker range="<=azure-devops"
-
 By default, your pipeline doesn't run as scheduled if there have been no code changes since the last successful scheduled run. For instance, consider that you've scheduled a pipeline to run every night at 9:00pm. During the weekdays, you push various changes to your code. The pipeline runs as per schedule. During the weekends, you don't make any changes to your code. If there have been no code changes since the scheduled run on Friday, then the pipeline doesn't run as scheduled during the weekend. 
 
-::: moniker-end
-
-#### [YAML](#tab/yaml/)
-
-::: moniker range="<=azure-devops"
+:::zone pivot="pipelines-yaml"
 
 To force a pipeline to run even when there are no code changes, you can use the `always` keyword.
 
@@ -450,19 +415,17 @@ schedules:
   always: true
 ```
 
-::: moniker-end
+:::zone-end
 
-#### [Classic](#tab/classic/)
-
-::: moniker range="<=azure-devops"
+:::zone pivot="pipelines-classic"
 
 To configure the scheduled pipeline to build only if there has been a change since the last build, check **Only schedule builds if the source or pipeline has changed**.
 
 ![Scheduled trigger UTC + 5:30 time zone](media/triggers/scheduled-trigger-git-india.png)
 
-::: moniker-end
+:::zone-end
 
-* * *
+:::zone pivot="pipelines-yaml"
 
 <a name="limits"></a>
 ## Limits on the number of scheduled runs in YAML pipelines
@@ -471,7 +434,8 @@ There are certain limits on how often you can schedule a pipeline to run. These
 - around 1000 runs per pipeline per week
 - 10 runs per pipeline per 15 minutes
 
-::: moniker range="<=azure-devops"
+:::zone-end
+
 ## Migrating from the classic editor
 
 The following examples show you how to migrate your schedules from the classic editor to YAML.
@@ -568,10 +532,6 @@ In the second schedule, **Sunday 3:00 AM (UTC) weekly latest version build**, th
 * Days of the week - `Sun` - Because our timezone conversions don't span multiple days of the week for our desired schedule, we don't need to do any conversion here. We could also specify the days of the week as `0`.
 * We also specify `always: true` since this build is scheduled to run whether or not the source code has been updated.
 
-::: moniker-end
-
-::: moniker range=">=azure-devops-2020"
-
 ## FAQ
 
 * [I want my pipeline to run only on the schedule and not when someone pushes a change to a branch](#i-want-my-pipeline-to-run-only-on-the-schedule-and-not-when-someone-pushes-a-change-to-a-branch)
@@ -650,4 +610,4 @@ schedules:
 
 For more information, see [Branch considerations for scheduled triggers](#branch-considerations-for-scheduled-triggers).
 
-::: moniker-end
+