[ACR] Task data/log retention

Author: dlepow

articles/container-registry/container-registry-tasks-overview.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: container-registry
 ms.topic: article
-ms.date: 03/28/2019
+ms.date: 05/20/2019
 ms.author: danlep
 ---
 
@@ -91,6 +91,12 @@ Multi-step tasks enable you to split the building, running, and testing of an im
 
 Learn about multi-step tasks in [Run multi-step build, test, and patch tasks in ACR Tasks](container-registry-tasks-multi-step.md).
 
+## View task data
+
+Each task run generates log output that you can inspect to determine whether the tasks ran successfully. If you use the [az acr build](/cli/azure/acr#az-acr-build) or [az acr task run](/cli/azure/acr/task#az-acr-task-run) command to trigger the task, log output for the task run is streamed to the console and also stored for later retrieval. To view the logs for a task run, you can use the [az acr task logs](/cli/azure/acr/task#az-acr-task-logs) command.
+
+By default, data and logs for task runs in a registry are retained for 30 days and then automatically purged. If you want to archive the data for a task run, you can enable archiving using the [az acr task update-run](/cli/azure/acr/task#az-acr-task-update-run) command.
+
 ## Next steps
 
 When you're ready to automate OS and framework patching by building your container images in the cloud, check out the three-part [ACR Tasks tutorial series](container-registry-tutorial-quick-task.md).