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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.date: 02/29/2020
16
16
> [!IMPORTANT]
17
17
> [Azure Logic Apps](../logic-apps/logic-apps-overview.md) is replacing Azure Scheduler,
18
18
> which is [being retired](#retire-date). To continue working with the jobs that you set
19
-
> up in Scheduler, please migrate to Azure Logic Apps as soon as possible by following this article.
19
+
> up in Scheduler, please migrate to Azure Logic Apps as soon as possible by following this article. > Scheduler is no longer available in the Azure portal.
20
20
21
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:
> To continue working with the jobs that you set up in Scheduler, please
20
20
> [migrate to Azure Logic Apps](../scheduler/migrate-from-scheduler-to-logic-apps.md) as soon as possible.
21
+
> Scheduler is no longer available in the Azure portal.
21
22
22
23
[Azure Scheduler](https://azure.microsoft.com/services/scheduler/) helps you create [jobs](../scheduler/scheduler-concepts-terms.md) that run in the cloud by declaratively describing actions. The service then automatically schedules and runs those actions. For example, you can call services inside and outside Azure, such as calling HTTP or HTTPS endpoints, and also post messages to Azure Storage queues and Azure Service Bus queues or topics. You can run jobs immediately or at a later time. Scheduler easily supports [complex schedules and advanced recurrence](../scheduler/scheduler-advanced-complexity.md). Scheduler specifies when to run jobs, keeps a history of job results that you can review, and then predictably and reliably schedules workloads to run.
23
24
24
-
Although you can use Scheduler to create, maintain, and run scheduled workloads, Scheduler doesn't host the workloads or run code. The service only *invokes* the services or code hosted elsewhere, for example, in Azure, on-premises, or with another provider. Scheduler can invoke through HTTP, HTTPS, a Storage queue, a Service Bus queue, or a Service Bus topic.
25
-
26
-
To create, schedule, manage, update, or delete jobs and [job collections](../scheduler/scheduler-concepts-terms.md), you can use code, the [Scheduler REST API](https://docs.microsoft.com/rest/api/scheduler/), or the [Azure Scheduler PowerShell cmdlets](scheduler-powershell-reference.md).
27
-
28
25
Other Azure scheduling capabilities also use Scheduler in the background, for example, [Azure WebJobs](../app-service/webjobs-create.md), which is a [Web Apps](https://azure.microsoft.com/services/app-service/web/) feature in Azure App Service. You can manage communication for these actions by using the [Scheduler REST API](https://docs.microsoft.com/rest/api/scheduler/). helps manage the communication for these actions.
29
26
30
27
Here are some scenarios where Scheduler can help you:
31
28
32
-
***Run recurring app actions**: For example, periodically collect data from Twitter into a feed.
29
+
* Run recurring app actions: For example, periodically collect data from Twitter into a feed.
33
30
34
-
***Perform daily maintenance**: Such as pruning logs daily, performing backups, and other maintenance tasks.
31
+
* Perform daily maintenance: Such as pruning logs daily, performing backups, and other maintenance tasks.
35
32
36
33
For example, as an administrator, you might want to back up your database at 1:00 AM every day for the next nine months.
37
34
35
+
Although you can use Scheduler to create, maintain, and run scheduled workloads, Scheduler doesn't host the workloads or run code. The service only *invokes* the services or code hosted elsewhere, for example, in Azure, on-premises, or with another provider. Scheduler can invoke through HTTP, HTTPS, a Storage queue, a Service Bus queue, or a Service Bus topic.
36
+
37
+
To create, schedule, manage, update, or delete jobs and [job collections](../scheduler/scheduler-concepts-terms.md), you can use code, the [Scheduler REST API](https://docs.microsoft.com/rest/api/scheduler/), or the [Azure Scheduler PowerShell cmdlets](scheduler-powershell-reference.md).
38
+
38
39
## Next steps
39
40
40
41
* Learn about [plans and billing for Azure Scheduler](scheduler-plans-billing.md)
0 commit comments