Skip to content

Commit 75efb33

Browse files
authored
Update articles/operational-excellence/relocation-functions.md
1 parent 5cf1660 commit 75efb33

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/operational-excellence/relocation-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ This section is a planning checklist in the following areas:
5959
- Service Endpoints
6060

6161

62-
### State, Storage and downstream dependencies
62+
### State, storage and downstream dependencies
6363

6464
- **Verify that your functions are stateless.** We [recommend that your function executions be stateless](../azure-functions/performance-reliability#write-functions-to-be-stateless). However, we don't prevent you from writing data to the local file system. While the files on the `%HOME%\site` drive should be only those required to run the deployed application and any temporary files, it's possible to store runtime application state on the `%HOME%\site` virtual drive. If your application writes state on the app shared storage path, make sure to plan how you are going to manage that state during a resource move. If your scenario requires you to maintain state between function executions, consider instead using [Durable Functions](../azure-functions/durable/durable-functions-overview.md).
6565

0 commit comments

Comments
 (0)