You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -54,7 +55,7 @@ This section contains an example of what that data would look like for each even
54
55
> Possible values for `Status` are:
55
56
> -`Delivered`: The message was successfully handed over to the intended destination (recipient Mail Transfer Agent).
56
57
> -`Suppressed`: The recipient email had hard bounced previously, and all subsequent emails to this recipient are being temporarily suppressed as a result.
57
-
> -`Bounced`: The email hard bounced, which may have happened because the email address does not exist or the domain is invalid.
58
+
> -`Bounced`: The email hard bounced, which might happen because the email address doesn't exist or the domain is invalid.
58
59
> -`Quarantined`: The message was quarantined (as spam, bulk mail, or phishing).
59
60
> -`FilteredSpam`: The message was identified as spam, and was rejected or blocked (not quarantined).
60
61
> -`Expanded`: A distribution group recipient was expanded before delivery to the individual members of the group.
# Customer intent: I want to know how to enable private only access for my Azure Event Grid topics or domains.
7
8
---
8
9
9
10
# Configure private endpoints for Azure Event Grid custom topics or domains
10
-
You can use [private endpoints](../private-link/private-endpoint-overview.md) to allow ingress of events directly from your virtual network to your custom topics and domains securely over a [private link](../private-link/private-link-overview.md) without going through the public internet. The private endpoint uses an IP address from the VNet address space for your custom topic or domain. For more conceptual information, see [Network security](network-security.md).
11
+
You can use [private endpoints](../private-link/private-endpoint-overview.md) to allow ingress of events directly from your virtual network to your custom topics and domains securely over a [private link](../private-link/private-link-overview.md) without going through the public internet. The private endpoint uses an IP address from the virtual network address space for your custom topic or domain. For more conceptual information, see [Network security](network-security.md).
11
12
12
13
This article describes how to configure private endpoints for custom topics or domains.
13
14
@@ -30,7 +31,19 @@ This section shows you how to enable private network access for an Event Grid to
30
31
1. To allow access to the Event Grid topic via a private endpoint, select the **Private access** option.
31
32
32
33
:::image type="content" source="./media/configure-firewall/networking-page-private-access.png" alt-text="Image showing the selection of Private access option on the Networking page of the Create topic wizard. ":::
33
-
1. See the next section for steps to add a private endpoint.
34
+
1. In the **Private endpoint connections** section, select **+ Private endpoint** button.
35
+
36
+
:::image type="content" source="./media/configure-private-endpoints/create-topic-add-private-endpoint-button.png" alt-text="Screenshot showing the Private endpoint button on the Create topic page.":::
37
+
1. On the **Create private endpoint** page, follow these steps:
38
+
1. For **Name**, enter a name for the private endpoint.
39
+
1. Select a **virtual network**. Only virtual networks in the currently selected subscription and location are listed in the drop-down list.
40
+
1. Select a **subnet** in the virtual network you selected.
41
+
1. Select whether you want the private endpoint to be integrated with a **private DNS zone**.
Copy file name to clipboardExpand all lines: articles/event-grid/create-view-manage-system-topics.md
+6-13Lines changed: 6 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
---
2
-
title: Create, view, and manage system topics in Azure Event Grid (portal)
2
+
title: Manage system topics in Azure Event Grid (portal)
3
3
description: This article shows how view existing system topic, create Azure Event Grid system topics using the Azure portal.
4
-
ms.topic: conceptual
5
-
ms.date: 11/30/2023
4
+
ms.topic: how-to
5
+
ms.date: 01/21/2025
6
+
# Customer intent: I want to know how to create, manage, and delete Azure Event Grid system topics in the Azure portal.
6
7
---
7
8
8
9
# Create, view, and manage Event Grid system topics in the Azure portal
@@ -20,7 +21,7 @@ You can create a system topic for an Azure resource (Storage account, Event Hubs
20
21
2. In the search box at the top, type **Event Grid System Topics**, and then press **ENTER**.
21
22
22
23
:::image type="content" source="./media/create-view-manage-system-topics/search-system-topics.png" alt-text="Screenshot that shows the Azure portal with Event Grid System Topics in the search box.":::
23
-
3.On the **Event Grid System Topics** page, select **+ Create** on the toolbar.
24
+
3.Select **System Topics** on the left navigation bar. Then, on the **Event Grid System Topics** page, select **+ Create** on the toolbar.
24
25
25
26
:::image type="content" source="./media/create-view-manage-system-topics/add-system-topic-menu.png" alt-text="Screenshot that shows in the Event Grid System Topics page with the Create button selected." lightbox="./media/create-view-manage-system-topics/add-system-topic-menu.png":::
26
27
4. On the **Create Event Grid System Topic** page, do the following steps:
@@ -56,14 +57,6 @@ Follow these steps to view all existing Event Grid system topics.
56
57
:::image type="content" source="./media/create-view-manage-system-topics/system-topic-delete-button.png" alt-text="Screenshot that shows the System Topic page with the Delete button selected.":::
57
58
3. On the confirmation page, select **OK** to confirm the deletion. It deletes the system topic and also all the event subscriptions for the system topic.
58
59
59
-
## Create an event subscription
60
-
1. Follow instructions from the [View system topics](#view-all-system-topics) section to view all system topics, and select the system topic that you want to delete from the list.
61
-
2. On the **Event Grid System Topic** page, select **+ Event Subscription** from the toolbar.
62
-
63
-
:::image type="content" source="./media/create-view-manage-system-topics/add-event-subscription-button.png" alt-text="Screenshot that shows the System Topic page with Add Event Subscription button selected.":::
64
-
3. Confirm that the **Topic Type**, **Source Resource**, and **Topic Name** are automatically populated. Enter a name, select an **Endpoint Type**, and specify the **endpoint**. Then, select **Create** to create the event subscription.
Copy file name to clipboardExpand all lines: articles/event-grid/handler-functions.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
---
2
-
title: Use a function in Azure as an event handler for Azure Event Grid events
2
+
title: Function as event handler for Azure Event Grid events
3
3
description: Describes how you can use functions created in and hosted by Azure Functions as event handlers for Event Grid events.
4
-
ms.topic: conceptual
5
-
ms.date: 08/31/2023
4
+
ms.topic: concept-article
5
+
ms.date: 01/21/2025
6
+
# Customer intent: I want to know details about using an Azure function as an event handler for Azure Event Grid events.
6
7
---
7
8
8
9
# Use a function as an event handler for Event Grid events
@@ -12,8 +13,8 @@ An event handler is the place where the event is sent. The handler takes an acti
12
13
13
14
To use a function in Azure as a handler for events, follow one of these approaches:
14
15
15
-
- Use [Event Grid trigger](../azure-functions/functions-bindings-event-grid-trigger.md). Specify **Azure Function** as the **endpoint type**. Then, specify the function app and the function that will handle events.
16
-
- Use [HTTP trigger](../azure-functions/functions-bindings-http-webhook.md). Specify **Web Hook** as the **endpoint type**. Then, specify the URL for the function that will handle events.
16
+
- Use [Event Grid trigger](../azure-functions/functions-bindings-event-grid-trigger.md). Specify **Azure Function** as the **endpoint type**. Then, specify the function app and the function that will handle events.
17
+
- Use [HTTP trigger](../azure-functions/functions-bindings-http-webhook.md). Specify **Web Hook** as the **endpoint type**. Then, specify the URL for the function that will handle events.
17
18
18
19
We recommend that you use the first approach (Event Grid trigger) as it has the following advantages over the second approach:
19
20
- Event Grid automatically validates Event Grid triggers. With generic HTTP triggers, you must implement the [validation response](end-point-validation-event-grid-events-schema.md) yourself.
@@ -28,7 +29,7 @@ We recommend that you use the first approach (Event Grid trigger) as it has the
28
29
|Title |Description |
29
30
|---------|---------|
30
31
|[Quickstart: Handle events with function](custom-event-to-function.md)| Sends a custom event to a function for processing. |
31
-
|[Tutorial: stream big data into a data warehouse](event-hubs-integration.md)| When Event Hubs creates a Capture file, Event Grid sends an event to a function app. The app retrieves the Capture file and migrates data to a data warehouse. |
32
+
|[Tutorial: stream big data into a data warehouse](event-hubs-integration.md)| When an event hub creates a Capture file, Event Grid sends an event to a function app. The app retrieves the Capture file and migrates data to a data warehouse. |
32
33
|[Tutorial: Azure Service Bus to Azure Event Grid integration examples](../service-bus-messaging/service-bus-to-event-grid-integration-example.md?toc=%2fazure%2fevent-grid%2ftoc.json)| Event Grid sends messages from Service Bus topic to a function app and a logic app. |
33
34
34
35
## REST example (for PUT)
@@ -78,5 +79,5 @@ You can use the [New-AzEventGridSubscription](/powershell/module/az.eventgrid/ne
78
79
> [!NOTE]
79
80
> When you use Event Grid Trigger, the Event Grid service fetches the client secret for the target Azure function, and uses it to deliver events to the Azure function. If you protect your Azure function with a Microsoft Entra application, you have to take the generic web hook approach and use the HTTP Trigger.
80
81
81
-
## Next steps
82
+
## Related content
82
83
See the [Event handlers](event-handlers.md) article for a list of supported event handlers.
Copy file name to clipboardExpand all lines: articles/event-grid/includes/system-topics.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,11 @@
1
1
---
2
-
title: include file
3
-
description: include file
2
+
title: View all Azure Event Grid system topics
3
+
description: Provides instructions to view all Azure Event Grid system topics.
4
+
services: event-grid
4
5
author: spelluru
5
-
ms.service: azure-event-grid
6
+
ms.service: event-grid
6
7
ms.topic: include
7
-
ms.date: 11/30/2023
8
+
ms.date: 01/21/2025
8
9
ms.author: spelluru
9
10
ms.custom: include file
10
11
---
@@ -18,11 +19,11 @@
18
19
:::image type="content" source="./media/system-topics/list-system-topics.png" alt-text="Screenshot that shows the list of system topics." lightbox="./media/system-topics/list-system-topics.png":::
19
20
4. Select a **system topic** from the list to see details about it.
20
21
21
-
:::image type="content" source="./media/system-topics/system-topic-details.png" alt-text="Screenshot that shows the topic page in the Azure portal.":::
22
+
:::image type="content" source="../media/create-view-manage-system-topics/system-topic-page.png" alt-text="Screenshot that shows the System Topic home page." lightbox="../media/create-view-manage-system-topics/system-topic-page.png":::
22
23
23
24
This page shows you details about the system topic such as the following information:
24
25
- Source. Name of the resource on which the system topic was created.
25
-
- Source type. Type of the resource. For example: `Microsoft.Storage.StorageAccounts`, `Microsoft.EventHub.Namespaces`, `Microsoft.Resources.ResourceGroups` and so on.
26
+
- Source type. Type of the resource. For example: `Microsoft.Storage.StorageAccounts`, `Microsoft.EventHub.Namespaces`, `Microsoft.Resources.ResourceGroups`, and so on.
26
27
- Any subscriptions created for the system topic.
27
28
28
29
This page allows operations such as the following ones:
0 commit comments