Skip to content

Commit 1333242

Browse files
committed
updated para about webhook expiry limit
1 parent 9aa8179 commit 1333242

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automation/automation-webhooks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Starting an Azure Automation runbook with a webhook
33
description: A webhook that allows a client to start a runbook in Azure Automation from an HTTP call. This article describes how to create a webhook and how to call one to start a runbook.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 03/19/2019
6+
ms.date: 01/16/2020
77
ms.topic: conceptual
88
---
99
# Starting an Azure Automation runbook with a webhook
@@ -120,7 +120,7 @@ The client can't determine when the runbook job completes or its completion stat
120120

121121
## <a name="renew-webhook"></a>Renew a webhook
122122

123-
When a webhook is created, it has a validity time of one year. After that year time the webhook automatically expires. Once a webhook is expired it can't be reactivated, it must be removed and recreated. If a webhook has not reached its expiry time, it can be extended.
123+
When a webhook is created, it has a validity time of ten years. After that time period, the webhook automatically expires. Once a webhook is expired it can't be reactivated, it must be removed and recreated. If a webhook has not reached its expiry time, it can be extended.
124124

125125
To extend a webhook, navigate to the runbook that contains the webhook. Select **Webhooks** under **Resources**. Click the webhook that you want to extend, this action opens the **Webhook** page. Choose a new expiration date and time and click **Save**.
126126

0 commit comments

Comments
 (0)