Skip to content

Commit 9eb30a3

Browse files
Merge pull request #230775 from spelluru/egridfilenames0314
removing event-grid from file names
2 parents 2b099e3 + b54c558 commit 9eb30a3

File tree

86 files changed

+201
-166
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

86 files changed

+201
-166
lines changed

articles/event-grid/.openpublishing.redirection.event-grid.json

Lines changed: 36 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,40 @@
11
{
2-
"redirections": [
2+
"redirections": [
3+
{
4+
"source_path": "edge/forward-events-event-grid-cloud.md",
5+
"redirect_url": "/azure/event-grid/edge/forward-events-cloud",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "edge/configure-event-grid.md",
10+
"redirect_url": "/azure/event-grid/edge/configure",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "scripts/event-grid-powershell-webhook-secure-delivery-azure-ad-user.md",
15+
"redirect_url": "/azure/event-grid/scripts/powershell-webhook-secure-delivery-azure-ad-user",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "scripts/event-grid-powershell-webhook-secure-delivery-azure-ad-app.md",
20+
"redirect_url": "/azure/event-grid/scripts/powershell-webhook-secure-delivery-azure-ad-app",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "scripts/event-grid-powershell-subscribe-custom-topic.md",
25+
"redirect_url": "/azure/event-grid/scripts/powershell-subscribe-custom-topic",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "scripts/event-grid-powershell-resource-group.md",
30+
"redirect_url": "/azure/event-grid/scripts/powershell-resource-group",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "scripts/event-grid-powershell-resource-group-filter.md",
35+
"redirect_url": "/azure/event-grid/scripts/powershell-resource-group-filter",
36+
"redirect_document_id": false
37+
},
338
{
439
"source_path": "scripts/event-grid-powershell-create-custom-topic.md",
540
"redirect_url": "/azure/event-grid/scripts/powershell-create-custom-topic",

articles/event-grid/auth0-how-to.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ To send Auth0 events to Azure:
2121
5. [Subscribe to events](#subscribe-to-events).
2222

2323

24-
[!INCLUDE [register-event-grid-provider](includes/register-event-grid-provider.md)]
24+
[!INCLUDE [register-provider](includes/register-provider.md)]
2525

2626
[!INCLUDE [authorize-verified-partner-to-create-topic](includes/authorize-verified-partner-to-create-topic.md)]
2727

articles/event-grid/cloudevents-schema.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ For a detailed description of the available fields, their types, and definitions
5151

5252
The headers values for events delivered in the CloudEvents schema and the Event Grid schema are the same except for `content-type`. For the CloudEvents schema, that header value is `"content-type":"application/cloudevents+json; charset=utf-8"`. For the Event Grid schema, that header value is `"content-type":"application/json; charset=utf-8"`.
5353

54-
## Configure Event Grid for CloudEvents
54+
## Configure for CloudEvents
5555

5656
You can use Event Grid for both input and output of events in the CloudEvents schema. The following table describes the possible transformations:
5757

articles/event-grid/custom-topics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ The following sections provide links to tutorials to create custom topics using
6969
|---------|---------|
7070
| [Quickstart: create and route custom events with Azure PowerShell](custom-event-quickstart-powershell.md) | Shows how to use Azure PowerShell to send custom events. |
7171
| [PowerShell: create Event Grid custom topic](./scripts/powershell-create-custom-topic.md)|Sample script that creates a custom topic. The script retrieves the endpoint and a key.|
72-
| [PowerShell: subscribe to events for a custom topic](./scripts/event-grid-powershell-subscribe-custom-topic.md)|Sample script that creates a subscription for a custom topic. It sends events to a WebHook.|
72+
| [PowerShell: subscribe to events for a custom topic](./scripts/powershell-subscribe-custom-topic.md)|Sample script that creates a subscription for a custom topic. It sends events to a WebHook.|
7373

7474
## ARM template tutorials
7575
|Title |Description |
File renamed without changes.

articles/event-grid/edge/forward-events-event-grid-cloud.md renamed to articles/event-grid/edge/forward-events-cloud.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -17,31 +17,31 @@ This article walks through all the steps needed to forward edge events to Event
1717
* React to edge events in the cloud.
1818
* Forward events to Event Grid in the cloud and use Azure Event Hubs or Azure Storage queues to buffer events before processing them in the cloud.
1919

20-
To complete this tutorial, you need have an understanding of Event Grid concepts on [edge](concepts.md) and [Azure](../concepts.md). For additional destination types, see [event handlers](event-handlers.md).
20+
To complete this tutorial, you need to have an understanding of Event Grid concepts on [edge](concepts.md) and [Azure](../concepts.md). For more destination types, see [event handlers](event-handlers.md).
2121

2222
> [!IMPORTANT]
2323
> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge](transition.md).
2424
2525

2626

2727
## Prerequisites
28-
In order to complete this tutorial, you will need:
28+
In order to complete this tutorial, you need:
2929

3030
* **Azure subscription** - Create a [free account](https://azure.microsoft.com/free) if you don't already have one.
3131
* **Azure IoT Hub and IoT Edge device** - Follow the steps in the quick start for [Linux](../../iot-edge/quickstart-linux.md) or [Windows devices](../../iot-edge/quickstart.md) if you don't already have one.
3232

33-
[!INCLUDE [event-grid-deploy-iot-edge](../includes/event-grid-deploy-iot-edge.md)]
34-
## Create event grid topic and subscription in cloud
33+
[!INCLUDE [deploy-iot-edge](../includes/deploy-iot-edge.md)]
34+
## Create Event Grid topic and subscription in cloud
3535

36-
Create an event grid topic and subscription in the cloud by following [this tutorial](../custom-event-quickstart-portal.md). Note down `topicURL`, `sasKey`, and `topicName` of the newly created topic that you'll use later in the tutorial.
36+
Create an Event Grid topic and subscription in the cloud by following [this tutorial](../custom-event-quickstart-portal.md). Note down `topicURL`, `sasKey`, and `topicName` of the newly created topic that you use later in the tutorial.
3737

3838
For example, if you created a topic named `testegcloudtopic` in West US, the values would look something like:
3939

4040
* **TopicUrl**: `https://testegcloudtopic.westus2-1.eventgrid.azure.net/api/events`
4141
* **TopicName**: `testegcloudtopic`
4242
* **SasKey**: Available under **AccessKey** of your topic. Use **key1**.
4343

44-
## Create event grid topic at the edge
44+
## Create Event Grid topic at the edge
4545

4646
1. Create topic3.json with the following content. See our [API documentation](api.md) for details about the payload.
4747

@@ -82,7 +82,7 @@ For example, if you created a topic named `testegcloudtopic` in West US, the val
8282

8383
## Create Event Grid subscription at the edge
8484

85-
[!INCLUDE [event-grid-deploy-iot-edge](../includes/event-grid-edge-persist-event-subscriptions.md)]
85+
[!INCLUDE [deploy-iot-edge](../includes/edge-persist-event-subscriptions.md)]
8686

8787
1. Create subscription3.json with the following content. See our [API documentation](api.md) for details about the payload.
8888

articles/event-grid/edge/forward-events-iothub.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -28,16 +28,16 @@ To complete this tutorial, you need to understand the following concepts:
2828
- [IoT Edge hub](../../iot-edge/module-composition.md)
2929

3030
## Prerequisites
31-
In order to complete this tutorial, you will need:
31+
In order to complete this tutorial, you need:
3232

3333
* **Azure subscription** - Create a [free account](https://azure.microsoft.com/free) if you don't already have one.
3434
* **Azure IoT Hub and IoT Edge device** - Follow the steps in the quick start for [Linux](../../iot-edge/quickstart-linux.md) or [Windows devices](../../iot-edge/quickstart.md) if you don't already have one.
3535

36-
[!INCLUDE [event-grid-deploy-iot-edge](../includes/event-grid-deploy-iot-edge.md)]
36+
[!INCLUDE [deploy-iot-edge](../includes/deploy-iot-edge.md)]
3737

3838
## Create topic
3939

40-
As a publisher of an event, you need to create an event grid topic. The topic refers to an end point where publishers can then send events to.
40+
As a publisher of an event, you need to create an Event Grid topic. The topic refers to an end point where publishers can then send events to.
4141

4242
1. Create topic4.json with the following content. See our [API documentation](api.md) for details about the payload.
4343

@@ -79,9 +79,9 @@ As a publisher of an event, you need to create an event grid topic. The topic re
7979

8080
## Create event subscription
8181

82-
Subscribers can register for events published to a topic. To receive any event, they'll need to create an Event grid subscription on a topic of interest.
82+
Subscribers can register for events published to a topic. To receive any event, they need to create an Event Grid subscription on a topic of interest.
8383

84-
[!INCLUDE [event-grid-deploy-iot-edge](../includes/event-grid-edge-persist-event-subscriptions.md)]
84+
[!INCLUDE [deploy-iot-edge](../includes/edge-persist-event-subscriptions.md)]
8585

8686
1. Create subscription4.json with the below content. Refer to our [API documentation](api.md) for details about the payload.
8787

@@ -206,11 +206,11 @@ See the IoT Hub [routing tutorial](../../iot-hub/tutorial-routing.md) for the st
206206

207207
## Next steps
208208

209-
In this tutorial, you created an event grid topic, edge hub subscription, and published events. Now that you know the basic steps to forward to an edge hub, see the following articles:
209+
In this tutorial, you created an Event Grid topic, edge hub subscription, and published events. Now that you know the basic steps to forward to an edge hub, see the following articles:
210210

211211
* To troubleshoot issues with using Azure Event Grid on IoT Edge, see [Troubleshooting guide](troubleshoot.md).
212212
* Use [edge hub](../../iot-edge/module-composition.md) route filters to partition events
213213
* Set up persistence of Event Grid module on [linux](persist-state-linux.md) or [Windows](persist-state-windows.md)
214214
* Follow [documentation](configure-client-auth.md) to configure client authentication
215-
* Forward events to Azure Event Grid in the cloud by following this [tutorial](forward-events-event-grid-cloud.md)
215+
* Forward events to Azure Event Grid in the cloud by following this [tutorial](forward-events-cloud.md)
216216
* [Monitor topics and subscriptions on the edge](monitor-topics-subscriptions.md)

articles/event-grid/edge/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,9 +49,9 @@ landingContent:
4949
- text: Publish and subscribe to events in the cloud
5050
url: pub-sub-events-webhook-cloud.md
5151
- text: Forward events to Azure Event Grid
52-
url: forward-events-event-grid-cloud.md
52+
url: forward-events-cloud.md
5353
- text: Forward events to Azure IoT Hub
54-
url: forward-events-event-grid-cloud.md
54+
url: forward-events-cloud.md
5555
- text: React to Azure Blob storage events locally
5656
url: react-blob-storage-events-locally.md
5757
# Card

articles/event-grid/edge/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,6 @@ Report any issues with using Event Grid on IoT Edge at [https://github.com/Azure
8282

8383
* [Publish, subscribe to events locally](pub-sub-events-webhook-local.md)
8484
* [Publish, subscribe to events in cloud](pub-sub-events-webhook-cloud.md)
85-
* [Forward events to Event Grid cloud](forward-events-event-grid-cloud.md)
85+
* [Forward events to Event Grid cloud](forward-events-cloud.md)
8686
* [Forward events to IoTHub](forward-events-iothub.md)
8787
* [React to Blob Storage events locally](react-blob-storage-events-locally.md)

articles/event-grid/edge/pub-sub-events-webhook-cloud.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -14,22 +14,22 @@ ms.custom: devx-track-csharp
1414

1515
# Tutorial: Publish, subscribe to events in cloud
1616

17-
This article walks through all the steps needed to publish and subscribe to events using Event Grid on IoT Edge. This tutorial uses and Azure Function as the Event Handler. For additional destination types, see [event handlers](event-handlers.md).
17+
This article walks through all the steps needed to publish and subscribe to events using Event Grid on IoT Edge. This tutorial uses and Azure Function as the Event Handler. For more destination types, see [event handlers](event-handlers.md).
1818

19-
See [Event Grid Concepts](concepts.md) to understand what an event grid topic and subscription are before proceeding.
19+
See [Event Grid Concepts](concepts.md) to understand what an Event Grid topic and subscription are before proceeding.
2020

2121
> [!IMPORTANT]
2222
> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge](transition.md).
2323
2424

2525

2626
## Prerequisites
27-
In order to complete this tutorial, you will need:
27+
In order to complete this tutorial, you need:
2828

2929
* **Azure subscription** - Create a [free account](https://azure.microsoft.com/free) if you don't already have one.
3030
* **Azure IoT Hub and IoT Edge device** - Follow the steps in the quick start for [Linux](../../iot-edge/quickstart-linux.md) or [Windows devices](../../iot-edge/quickstart.md) if you don't already have one.
3131

32-
[!INCLUDE [event-grid-deploy-iot-edge](../includes/event-grid-deploy-iot-edge.md)]
32+
[!INCLUDE [deploy-iot-edge](../includes/deploy-iot-edge.md)]
3333

3434
## Create an Azure function in the Azure portal
3535

@@ -59,14 +59,14 @@ public static async Task<IActionResult> Run(HttpRequest req, ILogger log)
5959
}
6060
```
6161

62-
In your new function, select **Get function URL** at the top right, select default (**Function key**), and then select **Copy**. You will use the function URL value later in the tutorial.
62+
In your new function, select **Get function URL** at the top right, select default (**Function key**), and then select **Copy**. You use the function URL value later in the tutorial.
6363

6464
> [!NOTE]
6565
> Refer to the [Azure Functions](../../azure-functions/functions-overview.md) documentation for more samples and tutorials on reacting to events and using EventGrid event triggers.
6666
6767
## Create a topic
6868

69-
As a publisher of an event, you need to create an event grid topic. Topic refers to an end point where publishers can send events to.
69+
As a publisher of an event, you need to create an Event Grid topic. Topic refers to an end point where publishers can send events to.
7070

7171
1. Create topic2.json with the following content. See our [API documentation](api.md) for details about the payload.
7272

@@ -107,9 +107,9 @@ As a publisher of an event, you need to create an event grid topic. Topic refers
107107

108108
## Create an event subscription
109109

110-
Subscribers can register for events published to a topic. To receive any event, the subscribers will need to create an Event grid subscription on a topic of interest.
110+
Subscribers can register for events published to a topic. To receive any event, the subscribers need to create an Event Grid subscription on a topic of interest.
111111

112-
[!INCLUDE [event-grid-deploy-iot-edge](../includes/event-grid-edge-persist-event-subscriptions.md)]
112+
[!INCLUDE [deploy-iot-edge](../includes/edge-persist-event-subscriptions.md)]
113113

114114
1. Create subscription2.json with the following content. Refer to our [API documentation](api.md) for details about the payload.
115115

@@ -199,11 +199,11 @@ You can view the event delivered in the Azure portal under the **Monitor** optio
199199

200200
## Next steps
201201

202-
In this tutorial, you created an event grid topic, subscription, and published events. Now that you know the basic steps, see the following articles:
202+
In this tutorial, you created an Event Grid topic, subscription, and published events. Now that you know the basic steps, see the following articles:
203203

204204
* To troubleshoot issues with using Azure Event Grid on IoT Edge, see [Troubleshooting guide](troubleshoot.md).
205205
* Create/update subscription with [filters](advanced-filtering.md).
206206
* Set up persistence of Event Grid module on [linux](persist-state-linux.md) or [Windows](persist-state-windows.md)
207207
* Follow [documentation](configure-client-auth.md) to configure client authentication
208-
* Forward events to Azure Event Grid in the cloud by following this [tutorial](forward-events-event-grid-cloud.md)
208+
* Forward events to Azure Event Grid in the cloud by following this [tutorial](forward-events-cloud.md)
209209
* [Monitor topics and subscriptions on the edge](monitor-topics-subscriptions.md)

0 commit comments

Comments
 (0)