Skip to content

Commit 35d354d

Browse files
authored
(Forums Team) fix omission #18881
fix omission.
1 parent 033d884 commit 35d354d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/monitoring-and-diagnostics/monitoring-archive-activity-log.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ In this article, we show how you can use the Azure portal, PowerShell Cmdlets, o
2121
Before you begin, you need to [create a storage account](../storage/common/storage-quickstart-create-account.md) to which you can archive your Activity Log. We highly recommend that you do not use an existing storage account that has other, non-monitoring data stored in it so that you can better control access to monitoring data. However, if you are also archiving Diagnostic Logs and metrics to a storage account, it may make sense to use that storage account for your Activity Log as well to keep all monitoring data in a central location. The storage account does not have to be in the same subscription as the subscription emitting logs as long as the user who configures the setting has appropriate RBAC access to both subscriptions.
2222

2323
> [!NOTE]
24-
> You cannot currently archive data to a storage account that behind a secured virtual network.
24+
> You cannot currently archive data to a storage account created behind a secured virtual network.
2525
2626
## Log Profile
2727
To archive the Activity Log using any of the methods below, you set the **Log Profile** for a subscription. The Log Profile defines the type of events that are stored or streamed and the outputs—storage account and/or event hub. It also defines the retention policy (number of days to retain) for events stored in a storage account. If the retention policy is set to zero, events are stored indefinitely. Otherwise, this can be set to any value between 1 and 2147483647. Retention policies are applied per-day, so at the end of a day (UTC), logs from the day that is now beyond the retention policy will be deleted. For example, if you had a retention policy of one day, at the beginning of the day today the logs from the day before yesterday would be deleted. The delete process begins at midnight UTC, but note that it can take up to 24 hours for the logs to be deleted from your storage account. [You can read more about log profiles here](monitoring-overview-activity-logs.md#export-the-activity-log-with-a-log-profile).

0 commit comments

Comments
 (0)