You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/scheduler/migrate-from-scheduler-to-logic-apps.md
+32-22Lines changed: 32 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,30 +14,26 @@ ms.date: 09/20/2018
14
14
# Migrate Azure Scheduler jobs to Azure Logic Apps
15
15
16
16
> [!IMPORTANT]
17
-
> Azure Logic Apps is replacing Azure Scheduler,
18
-
> which is being retired. To schedule jobs,
19
-
> follow this article for moving to Azure Logic Apps instead.
17
+
> [Azure Logic Apps](../logic-apps/logic-apps-overview.md) is replacing Azure Scheduler,
18
+
> which is [being retired](#retire-date). To continue working with the jobs that you set
19
+
> up in Scheduler, please move to Azure Logic Apps as soon as possible by following this article.
20
20
21
-
This article shows how you can schedule one-time
22
-
and recurring jobs by creating automated workflows
23
-
with Azure Logic Apps, rather than with Azure Scheduler.
24
-
When you create scheduled jobs with Logic Apps, you get these benefits:
21
+
This article shows how you can schedule one-time and recurring jobs by creating automated workflows with Azure Logic Apps, rather than with Azure Scheduler. When you create scheduled jobs with Logic Apps, you get these benefits:
25
22
26
-
* You don't have to worry about the concept of a *job collection*
27
-
because each logic app is a separate Azure resource.
23
+
* Build your job by using a visual designer and connectors for hundreds of services, including Azure Blob Storage, Azure Service Bus, Office 365 Outlook, and SAP.
28
24
29
-
*You can run multiple one-time jobs by using a single logic app.
25
+
*Manage each scheduled workflow as a first-class Azure resource. You don't have to worry about the concept of a *job collection* because each logic app is an individual Azure resource.
30
26
31
-
*The Azure Logic Apps service supports time zone and daylight savings time (DST).
27
+
*Run multiple one-time jobs by using a single logic app.
32
28
33
-
To learn more, see [What is Azure Logic Apps?](../logic-apps/logic-apps-overview.md)
34
-
or try creating your first logic app in this quickstart:
35
-
[Create your first logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
29
+
* Set schedules that support time zones and automatically adjust to daylight savings time (DST).
30
+
31
+
To learn more, see [What is Azure Logic Apps?](../logic-apps/logic-apps-overview.md) or try creating your first logic app in this quickstart: [Create your first logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
36
32
37
33
## Prerequisites
38
34
39
35
* An Azure subscription. If you don't have an Azure subscription,
40
-
<ahref="https://azure.microsoft.com/free/"target="_blank">sign up for a free Azure account</a>.
36
+
[sign up for a free Azure account](https://azure.microsoft.com/free/).
41
37
42
38
* To trigger your logic app by sending HTTP requests,
43
39
use a tool such as the [Postman desktop app](https://www.getpostman.com/apps).
@@ -160,9 +156,7 @@ app run instance. To cancel a one-time job, you can use
160
156
in the Logic Apps REST API. When you send a call to the trigger,
161
157
provide the [workflow run ID](#workflow-run-id).
162
158
163
-
## Schedule recurring jobs
164
-
165
-
### Create your logic app
159
+
## Schedule recurring jobs with a logic app
166
160
167
161
1. In the [Azure portal](https://portal.azure.com),
168
162
create a blank logic app in Logic App Designer.
@@ -249,13 +243,29 @@ To learn more about exception handling, see
249
243
250
244
## FAQ
251
245
252
-
<aname="retire-date"></a>
246
+
<aname="retire-date"></a>
253
247
254
248
**Q**: When is Azure Scheduler retiring? <br>
255
-
**A**: Azure Scheduler is scheduled to retire on September 30, 2019.
249
+
**A**: Azure Scheduler is scheduled to fully retire on December 31, 2019. Here is more information about this process:
250
+
251
+
**September 30, 2019*
252
+
253
+
* Free SKU Scheduler job collection is disabled. Although existing jobs will stop running, you can still retrieve data for migration.
254
+
255
+
* New job collections are disabled in the Azure portal for all SKUs. Existing Standard, P10, and P20 resources continue to run. You can also still manage existing job collections.
256
+
257
+
**October 31, 2019*
258
+
259
+
* Scheduler is removed from the Azure portal.
260
+
261
+
* Existing Standard, P10, and P20 resources continue to run and are accessible by using the API and SDKs.
262
+
263
+
* For jobs that you don't want to continue running after Scheduler is removed from the portal, please [disable or delete your job collections](https://docs.microsoft.com/azure/scheduler/scheduler-get-started-portal#monitor-and-manage-jobs) before October 31, 2019.
264
+
265
+
**December 31, 2019*: Scheduler is fully retired. *All jobs* stop running, and *all data* is deleted from the system.
256
266
257
-
**Q**: What happens to my Scheduler job collections and jobs after the service retires? <br>
258
-
**A**: All Scheduler job collections and jobs will be deleted from the system.
267
+
**Q**: What happens to my job collections and jobs after the service retires? <br>
268
+
**A**: All Scheduler job collections and jobs will stop running and be deleted from the system.
259
269
260
270
**Q**: Do I have to back up or perform any other tasks before migrating my Scheduler jobs to Logic Apps? <br>
261
271
**A**: As a best practice, always back up your work. Check that the logic apps you created are running as expected before deleting or disabling your Scheduler jobs.
0 commit comments