Merge pull request #278531 from spelluru/egridkeynote0617

Event Grid SAS key length

Author: v-ccolin

articles/event-grid/get-access-keys.md

@@ -2,16 +2,21 @@
 title: Get access key for an Event Grid resource
 description: This article describes how to get access key for an Event Grid topic or domain
 ms.topic: how-to
-ms.date: 07/07/2020 
+ms.date: 06/17/2024 
 ms.custom: devx-track-azurepowershell, devx-track-azurecli 
 ms.devlang: azurecli
 ---
 
 # Get access keys for Event Grid resources (topics or domains)
-Access keys are used to authenticate an application publishing events to Azure Event Grid resources (topics and domains). We recommend regenerating your keys regularly and storing them securely. You are provided with two access keys so that you can maintain connections using one key while regenerating the other.
+Access keys are used to authenticate an application publishing events to Azure Event Grid resources (topics and domains). We recommend regenerating your keys regularly and storing them securely. You're provided with two access keys so that you can maintain connections using one key while regenerating the other.
 
 This article describes how to get access keys for an Event Grid resource (topic or domain) using Azure portal, PowerShell, or CLI. 
 
+> [!IMPORTANT]
+> From August 1, 2024 to August 10, 2024, Azure Event Grid will rollout a security improvement extending the Shared Access Signature (SAS) key length from 44 to 84 characters. This change is being made to strengthen the security of your data in Event Grid resources. The change doesn't impact any application or service that currently publishes events to Event Grid with the old SAS key but it may impact only if you regenerate the SAS key of your Event Grid topics, domains, namespaces, and partner topics, after the update. 
+> 
+> We recommend that you regenerate your SAS key on or after August 11, 2024. After regenerating the key, update any event publishing applications or services that use the old key to use the enhanced SAS key. 
+
 ## Azure portal
 In the Azure portal, switch to **Access keys** tab of the **Event Grid Topic** or **Event Grid Domain** page for your topic or domain.  
 
@@ -31,13 +36,13 @@ Get-AzEventGridDomainKey -ResourceGroup <RESOURCE GROUP NAME> -Name <DOMAIN NAME
 ```
 
 ## Azure CLI
-Use the [az eventgrid topic key list](/cli/azure/eventgrid/topic/key#az-eventgrid-topic-key-list) to get access keys for topics. 
+Use the [`az eventgrid topic key list`](/cli/azure/eventgrid/topic/key#az-eventgrid-topic-key-list) to get access keys for topics. 
 
 ```azurecli-interactive
 az eventgrid topic key list --resource-group <RESOURCE GROUP NAME> --name <TOPIC NAME>
 ```
 
-Use [az eventgrid domain key list](/cli/azure/eventgrid/domain/key#az-eventgrid-domain-key-list) to get access keys for domains. 
+Use [`az eventgrid domain key list`](/cli/azure/eventgrid/domain/key#az-eventgrid-domain-key-list) to get access keys for domains. 
 
 ```azurecli-interactive
 az eventgrid domain key list --resource-group <RESOURCE GROUP NAME> --name <DOMAIN NAME>

articles/event-grid/media/post-to-custom-topic/cloud-shell.png

@@ -1,8 +1,9 @@
 ---
 title: Post event to custom Azure Event Grid topic
 description: This article describes how to post an event to a custom topic. It shows the format of the post and event data.
-ms.topic: conceptual
-ms.date: 01/18/2024 
+ms.topic: concept-article
+ms.date: 06/18/2024 
+#customer intent: As a developer, I want to know how to publish events to an Azure Event Grid custom topic
 ---
 
 # Publish events to Azure Event Grid custom topics using access keys
@@ -17,30 +18,48 @@ This article describes how to post an event to a custom topic using an access ke
 
 When sending the HTTP POST to a custom topic, use the URI format: `https://<topic-endpoint>?api-version=2018-01-01`. For example, a valid URI is: `https://exampletopic.westus2-1.eventgrid.azure.net/api/events?api-version=2018-01-01`. To get the endpoint for a custom topic using Azure CLI, use:
 
+# [Azure portal](#tab/azure-portal)
+You can find the topic's endpoint on the **Overview** tab of the **Event Grid Topic** page in the Azure portal. 
+
+:::image type="content" source="./media/post-to-custom-topic/topic-endpoint.png" alt-text="Screenshot that shows the Event Grid topic page on the Azure portal with the topic endpoint highlighted." lightbox="./media/post-to-custom-topic/topic-endpoint.png":::
+
+# [Azure CLI](#tab/azure-cli)
+
 ```azurecli-interactive
 az eventgrid topic show --name <topic-name> -g <topic-resource-group> --query "endpoint"
 ```
 
-To get the endpoint for a custom topic using Azure PowerShell, use:
+# [Azure PowerShell](#tab/azure-powershell)
 
 ```powershell
 (Get-AzEventGridTopic -ResourceGroupName <topic-resource-group> -Name <topic-name>).Endpoint
 ```
 
+---
+
 ## Header
 
 In the request, include a header value named `aeg-sas-key` that contains a key for authentication. For example, a valid header value is `aeg-sas-key: xxxxxxxxxxxxxxxxxxxxxxx`. To get the key for a custom topic using Azure CLI, use:
 
+# [Azure portal](#tab/azure-portal)
+To get the access key for the custom topic, select **Access keys** tab on the **Event Grid Topic** page in the Azure portal. 
+
+:::image type="content" source="./media/post-to-custom-topic/custom-topic-access-keys.png" alt-text="Screenshot that shows the Access Keys tab of the Event Grid topic page on the Azure portal." lightbox="./media/post-to-custom-topic/custom-topic-access-keys.png":::
+
+# [Azure CLI](#tab/azure-cli)
+
 ```azurecli
 az eventgrid topic key list --name <topic-name> -g <topic-resource-group> --query "key1"
 ```
 
-To get the key for a custom topic using PowerShell, use:
+# [Azure PowerShell](#tab/azure-powershell)
 
 ```powershell
 (Get-AzEventGridTopicKey -ResourceGroupName <topic-resource-group> -Name <topic-name>).Key1
 ```
 
+---
+
 ## Event data
 
 For custom topics, the top-level data contains the same fields as standard resource-defined events. One of those properties is a `data` property that contains properties unique to the custom topic. As an event publisher, you determine properties for that data object. Here's the schema:
@@ -60,7 +79,7 @@ For custom topics, the top-level data contains the same fields as standard resou
 ]
 ```
 
-For a description of these properties, see [Azure Event Grid event schema](event-schema.md). When posting events to an Event Grid topic, the array can have a total size of up to 1 MB. The maximum allowed size for an event is also 1 MB. Events over 64 KB are charged in 64-KB increments. When receiving events in a batch, the maximum allowed number of events is 5,000 per batch.
+For a description of these properties, see [Azure Event Grid event schema](event-schema.md). When a client sends events to an Event Grid topic, the array can have a total size of up to 1 MB. The maximum allowed size for an event is also 1 MB. Events over 64 KB are charged in 64-KB increments. When a client receives events in a batch, the maximum allowed number of events is 5,000 per batch.
 
 For example, a valid event data schema is:
 
@@ -78,6 +97,65 @@ For example, a valid event data schema is:
 }]
 ```
 
+## Send the sample event 
+This section shows how to send a sample event to the custom topic. 
+
+# [Azure portal](#tab/azure-portal)
+
+1. In the [Azure portal](https://portal.azure.com), launch Cloud Shell. 
+1. In the Cloud Shell, run the commands from the Azure PowerShell or Azure CLI in the **Bash** or **PowerShell** session.
+
+    :::image type="content" source="./media/post-to-custom-topic/cloud-shell.png" alt-text="Screenshot that shows the Cloud Shell in the Azure portal." lightbox="./media/post-to-custom-topic/cloud-shell.png":::
+
+
+# [Azure CLI](#tab/azure-cli)
+
+```azurecli
+endpoint=$(az eventgrid topic show --name <topic name> -g <resource group name> --query "endpoint" --output tsv)
+
+key=$(az eventgrid topic key list --name <topic name> -g <resource group name> --query "key1" --output tsv)
+
+event='[ {"id": "'"$RANDOM"'", "eventType": "recordInserted", "subject": "myapp/vehicles/motorcycles", "eventTime": "'`date +%Y-%m-%dT%H:%M:%S%z`'", "data":{ "make": "Ducati", "model": "Monster"},"dataVersion": "1.0"} ]'
+
+curl -X POST -H "aeg-sas-key: $key" -d "$event" $endpoint
+```
+
+# [Azure PowerShell](#tab/azure-powershell)
+
+```azurepowershell
+$resourceGroupName = "<resource group name>"
+$topicName = "<topic name>"
+
+$endpoint = (Get-AzEventGridTopic -ResourceGroupName $resourceGroupName -Name $topicName).Endpoint
+
+$keys = Get-AzEventGridTopicKey -ResourceGroupName $resourceGroupName -Name $topicName
+
+$eventID = Get-Random 99999
+#Date format should be SortableDateTimePattern (ISO 8601)
+$eventDate = Get-Date -Format s
+
+#Construct body using Hashtable
+$htbody = @{
+    id= $eventID
+    eventType="recordInserted"
+    subject="myapp/vehicles/motorcycles"
+    eventTime= $eventDate   
+    data= @{
+        make="Ducati"
+        model="Monster"
+    }
+    dataVersion="1.0"
+}
+
+#Use ConvertTo-Json to convert event body from Hashtable to JSON Object
+#Append square brackets to the converted JSON payload since they are expected in the event's JSON payload syntax
+$body = "["+(ConvertTo-Json $htbody)+"]"
+
+Invoke-WebRequest -Uri $endpoint -Method POST -Body $body -Headers @{"aeg-sas-key" = $keys.Key1}
+```
+
+---
+
 ## Response
 
 After posting to the topic endpoint, you receive a response. The response is a standard HTTP response code. Some common responses are:
@@ -105,7 +183,7 @@ For errors, the message body has the following format:
 }
 ```
 
-## Next steps
+## Related content
 
 * For information about monitoring event deliveries, see [Monitor Event Grid message delivery](monitor-event-delivery.md).
 * For more information about the authentication key, see [Event Grid security and authentication](security-authentication.md).