add to RBAC role

Author: spelluru

articles/event-grid/delivery-and-retry.md

@@ -131,6 +131,9 @@ Before setting the dead-letter location, you must have a storage account with a
 
 You might want to be notified when an event has been sent to the dead-letter location. To use Event Grid to respond to undelivered events, [create an event subscription](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json) for the dead-letter blob storage. Every time your dead-letter blob storage receives an undelivered event, Event Grid notifies your handler. The handler responds with actions you wish to take for reconciling undelivered events. For an example of setting up a dead-letter location and retry policies, see [Dead letter and retry policies](manage-event-delivery.md).
 
+> [!NOTE]
+> If you enable managed identity for dead-lettering, you'll need to add the managed identity to the appropriate role-based access control (RBAC) role on the Azure Storage account that will hold the dead-lettered events. For more information, see [Supported destinations and Azure roles](add-identity-roles.md#supported-destinations-and-azure-roles).
+
 ## Delivery event formats
 This section gives you examples of events and dead-lettered events in different delivery schema formats (Event Grid schema, CloudEvents 1.0 schema, and custom schema). For more information about these formats, see [Event Grid schema](event-schema.md) and [Cloud Events 1.0 schema](cloud-event-schema.md) articles. 
 
@@ -321,7 +324,7 @@ Event Grid uses HTTP response codes to acknowledge receipt of events.
 
 ### Success codes
 
-Event Grid considers **only** the following HTTP response codes as successful deliveries. All other status codes are considered failed deliveries and will be retried or deadlettered as appropriate. Upon receiving a successful status code, Event Grid considers delivery complete.
+Event Grid considers **only** the following HTTP response codes as successful deliveries. All other status codes are considered failed deliveries and will be retried or deadlettered as appropriate. When Event Grid receives a successful status code, it considers delivery complete.
 
 - 200 OK
 - 201 Created

articles/event-grid/manage-event-delivery.md

@@ -128,6 +128,9 @@ New-AzEventGridSubscription `
 > [!NOTE]
 > If you set both `event-ttl` and `max-deliver-attempts`, Event Grid uses the first to expire to determine when to stop event delivery. For example, if you set 30 minutes as time-to-live (TTL) and 10 max delivery attempts. When an event isn't delivered after 30 minutes (or) isn't delivered after 10 attempts, whichever happens first, the event is dead-lettered.  
 
+## Managed identity
+If you enable managed identity for dead-lettering, you'll need to add the managed identity to the appropriate role-based access control (RBAC) role on the Azure Storage account that will hold the dead-lettered events. For more information, see [Supported destinations and Azure roles](add-identity-roles.md#supported-destinations-and-azure-roles).
+
 ## Next steps
 
 * For a sample application that uses an Azure Function app to process dead letter events, see [Azure Event Grid Dead Letter Samples for .NET](https://azure.microsoft.com/resources/samples/event-grid-dotnet-handle-deadlettered-events/).

articles/event-grid/subscribe-through-portal.md

@@ -2,12 +2,12 @@
 title: Azure Event Grid subscriptions through portal
 description: This article describes how to create Event Grid subscriptions for the supported sources, such as Azure Blob Storage, by using the Azure portal.
 ms.topic: conceptual
-ms.date: 07/07/2020
+ms.date: 09/12/2022
 ---
 
 # Subscribe to events through portal
 
-This article describes how to create Event Grid subscriptions through the portal.
+This article describes how to create Event Grid subscriptions through the portal. 
 
 ## Create event subscriptions
 
@@ -33,12 +33,13 @@ To create an Event Grid subscription for any of the supported [event sources](ov
 
    ![Select event types](./media/subscribe-through-portal/select-event-types.png)
 
-1. Provide additional details about the event subscription, such as the endpoint for handling events and a subscription name.
+1. Provide more details about the event subscription, such as the endpoint for handling events and a subscription name.
 
    ![Screenshot that shows the "Endpoint Details" and "Event Subscription Details" sections with a subscription name value entered.](./media/subscribe-through-portal/provide-subscription-details.png)
 
     > [!NOTE]
-    > For a list of supported event handlers, see [Event handlers](event-handlers.md).
+    > - For a list of supported event handlers, see [Event handlers](event-handlers.md).
+    > - If you enable managed identity for a topic or domain, you'll need to add the managed identity to the appropriate role-based access control (RBAC) role on the destination for the messages to be delivered successfully. For more information, see [Supported destinations and Azure roles](add-identity-roles.md#supported-destinations-and-azure-roles).
 1. To enable dead lettering and customize retry policies, select **Additional Features**.
 
    ![Select additional features](./media/subscribe-through-portal/select-additional-features.png)