encryption at rest

Author: banisadr

articles/event-grid/security-authentication.md

@@ -348,6 +348,10 @@ The following are sample Event Grid role definitions that allow users to take di
 
 You can create custom roles with [PowerShell](../role-based-access-control/custom-roles-powershell.md), [Azure CLI](../role-based-access-control/custom-roles-cli.md), and [REST](../role-based-access-control/custom-roles-rest.md).
 
+## Encryption at rest
+
+All events or data written to disk by the Event Grid service is encrypted by a Microsoft managed key ensuring that it is encrypted at rest. Additionally, the maximum period of time that events or data is retained is 24 hours in adherence with the [Event Grid retry policy](delivery-and-retry.md). Event Grid will automatically delete all events or data after 24 hours, or the the event time-to-live, whichever is less.
+
 ## Next steps
 
 * For an introduction to Event Grid, see [About Event Grid](overview.md)

articles/storage/blobs/storage-blob-event-overview.md

@@ -30,6 +30,9 @@ If you want to try this out now, see any of these quickstart articles:
 
 If your account has a hierarchical namespace, this tutorial will show you how to connect together an Event Grid subscription, an Azure Function, and a [Job](https://docs.azuredatabricks.net/user-guide/jobs.html) in Azure Databricks: [Tutorial: Use Azure Data Lake Storage Gen2 events to update a Databricks Delta table](data-lake-storage-events.md).
 
+>[!NOTE]
+> Only storage accounts of kind **StorageV2 (general purpose v2)** and **BlobStorage** support event integration. **Storage (genral purpose v1)** does *not* support integration with Event Grid.
+
 ## The event model
 
 Event Grid uses [event subscriptions](../../event-grid/concepts.md#event-subscriptions) to route event messages to subscribers. This image illustrates the relationship between event publishers, event subscriptions, and event handlers.