Skip to content

Commit 4f25b8e

Browse files
FinVamp1ggailey777
andauthored
Update articles/azure-functions/functions-deployment-technologies.md
Co-authored-by: Glenn Gailey <[email protected]>
1 parent fe3e8cc commit 4f25b8e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-functions/functions-deployment-technologies.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -70,10 +70,10 @@ You can sync triggers in one of three ways:
7070

7171

7272
When you deploy an updated version of the deployment package and maintain the same external package URL, you need to manually restart your function app. This indicates to the host that it should synchronize and redeploy your updates from the same package URL.
73-
The Azure Functions Host also performs background trigger syncing once the application has started. Howver for the Consumption and Elastic Premium plans we would recommend calling Sync Triggers as above for these scenarios.
73+
The Functions host also performs a background trigger sync after the application has started. However, for the Consumption and Elastic Premium hosting plans you should also [manually sync triggers](#trigger-syncing) in these scenarios:
7474

75-
+ Deploying with an External Package URL using ARM or Terraform
76-
+ Updating the package at the External Package URL.
75+
+ Deployments using an external package URL with either ARM Templates or Terraform.
76+
+ When updating the deployment package at the same external package URL.
7777

7878

7979

0 commit comments

Comments
 (0)