Skip to content

Commit 56dbb1a

Browse files
committed
remove event-grid from file names
1 parent 2c60d27 commit 56dbb1a

20 files changed

+32
-21
lines changed

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

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,16 @@
11
{
2-
"redirections": [
2+
"redirections": [
3+
4+
{
5+
"source_path": "event-hubs-integration.md",
6+
"redirect_url": "/azure/event-grid/event-hubs-integration",
7+
"redirect_document_id": false
8+
},
9+
{
10+
"source_path": "event-grid-faq.yml",
11+
"redirect_url": "/azure/event-grid/faq",
12+
"redirect_document_id": false
13+
},
314
{
415
"source_path": "custom-disaster-recovery.md",
516
"redirect_url": "/azure/event-grid/custom-disaster-recovery-client-side",

articles/event-grid/blob-event-quickstart-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,4 +144,4 @@ Now that you know how to create custom topics and event subscriptions, learn mor
144144
- [About Event Grid](overview.md)
145145
- [Route Blob storage events to a custom web endpoint](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json)
146146
- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-event-grid-logic-app.md)
147-
- [Stream big data into a data warehouse](event-grid-event-hubs-integration.md)
147+
- [Stream big data into a data warehouse](event-hubs-integration.md)

articles/event-grid/compare-messaging-services.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ For more information, see [Service Bus overview](../service-bus-messaging/servic
7777
## Use the services together
7878
In some cases, you use the services side by side to fulfill distinct roles. For example, an e-commerce site can use Service Bus to process the order, Event Hubs to capture site telemetry, and Event Grid to respond to events like an item was shipped.
7979

80-
In other cases, you link them together to form an event and data pipeline. You use Event Grid to respond to events in the other services. For an example of using Event Grid with Event Hubs to migrate data to Azure Synapse Analytics, see [Stream big data into a Azure Synapse Analytics](event-grid-event-hubs-integration.md). The following image shows the workflow for streaming the data.
80+
In other cases, you link them together to form an event and data pipeline. You use Event Grid to respond to events in the other services. For an example of using Event Grid with Event Hubs to migrate data to Azure Synapse Analytics, see [Stream big data into a Azure Synapse Analytics](event-hubs-integration.md). The following image shows the workflow for streaming the data.
8181

8282
:::image type="content" source="./media/compare-messaging-services/overview.svg" alt-text="Image showing how Event Hubs, Service Bus, and Event Grid can be connected together.":::
8383

articles/event-grid/configure-custom-topic.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ You can use similar steps to enable an identity for an Event Grid domain.
7070
1. On the left menu, select **Configuration** under **Settings**.
7171
1. 2. For **Data residency**, select whether you don't want any data to be replicated to another region (**Regional**) or you want the metadata to be replicated to a predefined secondary region (**Cross-Geo**).
7272

73-
The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./event-grid-faq.yml).
73+
The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./faq.yml).
7474

7575
If you select the **Regional** option, you may define your own disaster recovery plan.
7676

articles/event-grid/create-custom-topic.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ On the **Security** page of the **Create Topic** or **Create Event Grid Domain*
7272

7373
:::image type="content" source="./media/create-custom-topic/data-residency.png" alt-text="Screenshot showing the Data residency section of the Advanced page in the Create Topic wizard.":::
7474

75-
The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./event-grid-faq.yml).
75+
The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./faq.yml).
7676

7777
If you select the **Regional** option, you may define your own disaster recovery plan.
7878
3. Select **Next: Tags** to move to the **Tags** page.

articles/event-grid/custom-event-quickstart-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -214,7 +214,7 @@ Now that you know how to create custom topics and event subscriptions, learn mor
214214
- [About Event Grid](overview.md)
215215
- [Route Blob storage events to a custom web endpoint](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json)
216216
- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-event-grid-logic-app.md)
217-
- [Stream big data into a data warehouse](event-grid-event-hubs-integration.md)
217+
- [Stream big data into a data warehouse](event-hubs-integration.md)
218218
219219
See the following samples to learn about publishing events to and consuming events from Event Grid using different programming languages.
220220

articles/event-grid/custom-event-quickstart-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ Now that you know how to create topics and event subscriptions, learn more about
160160
- [About Event Grid](overview.md)
161161
- [Route Blob storage events to a custom web endpoint](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json)
162162
- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-event-grid-logic-app.md)
163-
- [Stream big data into a data warehouse](event-grid-event-hubs-integration.md)
163+
- [Stream big data into a data warehouse](event-hubs-integration.md)
164164

165165
See the following samples to learn about publishing events to and consuming events from Event Grid using different programming languages.
166166

articles/event-grid/custom-event-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ Now that you know how to create topics and event subscriptions, learn more about
149149
- [About Event Grid](overview.md)
150150
- [Route Blob storage events to a custom web endpoint](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json)
151151
- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-event-grid-logic-app.md)
152-
- [Stream big data into a data warehouse](event-grid-event-hubs-integration.md)
152+
- [Stream big data into a data warehouse](event-hubs-integration.md)
153153

154154
See the following samples to learn about publishing events to and consuming events from Event Grid using different programming languages.
155155

articles/event-grid/custom-event-to-eventhub.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ Now that you know how to create topics and event subscriptions, learn more about
130130
- [About Event Grid](overview.md)
131131
- [Route Blob storage events to a custom web endpoint](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json)
132132
- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-event-grid-logic-app.md)
133-
- [Stream big data into a data warehouse](event-grid-event-hubs-integration.md)
133+
- [Stream big data into a data warehouse](event-hubs-integration.md)
134134

135135
See the following samples to learn about publishing events to and consuming events from Event Grid using different programming languages.
136136

articles/event-grid/custom-event-to-function.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,7 @@ Now that you know how to create topics and event subscriptions, learn more about
239239
- [About Event Grid](overview.md)
240240
- [Route Blob storage events to a custom web endpoint](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json)
241241
- [Monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-event-grid-logic-app.md)
242-
- [Stream big data into a data warehouse](event-grid-event-hubs-integration.md)
242+
- [Stream big data into a data warehouse](event-hubs-integration.md)
243243

244244
See the following samples to learn about publishing events to and consuming events from Event Grid using different programming languages.
245245

0 commit comments

Comments
 (0)