Skip to content

Commit 8d289fc

Browse files
committed
Updated articles
1 parent 1669b55 commit 8d289fc

6 files changed

+46
-32
lines changed

articles/event-grid/event-schema-health-resources.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -336,8 +336,7 @@ The following example shows the schema of a key-value modified event:
336336

337337
---
338338

339-
## Contact us
340-
If you have any questions or feedback on this feature, don't hesitate to reach us at [[email protected]](mailto:[email protected]).
339+
[!INCLUDE [contact-resource-notifications](./includes/contact-resource-notifications.md)]
341340

342341
## Next steps
343342
See [Subscribe to Azure Resource Notifications - Health Resources events](subscribe-to-resource-notifications-health-resources-events.md).

articles/event-grid/event-schema-resource-notifications.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ In addition to these permissions, you need to grant the following permissions to
2828
| Topic Type | Permission |
2929
| ---------- | ---------- |
3030
| HealthResources | `Microsoft.ResourceNotifications/systemTopics/subscribeToHealthResources/action` |
31+
| Azure Resource Management | `Microsoft.ResourceNotifications/systemTopics/subscribeToResources/action` |
3132

3233
To enhance customer experience, a built-in role definition that encompasses all the requisite permissions for receiving data through any ARN system topic is available. This role includes permissions mandated by Event Grid for system topic and event subscription creation. This built-in role definition is regularly updated to incorporate more topic types as they become accessible through our service. **As a result, users assigned this built-in role automatically gains access to all future ARN topic types**. You can choose to either utilize the provided built-in role definition or craft your own custom role definitions to enforce access control.
3334

@@ -64,4 +65,7 @@ If you have any questions or feedback on this feature, don't hesitate to reach u
6465

6566

6667
## Next steps
67-
See [Azure Resource Notifications - Health Resources events in Azure Event Grid](event-schema-health-resources.md).
68+
See the following articles:
69+
70+
- [Azure Resource Notifications - Health Resources events in Azure Event Grid](event-schema-health-resources.md).
71+
- [Azure Resource Notifications - Azure Resource Manager events in Azure Event Grid](event-schema-resources.md).

articles/event-grid/event-schema-resources.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -442,8 +442,7 @@ This section shows the `Deleted` event generated when an Azure Storage account i
442442

443443
---
444444

445-
## Contact us
446-
If you have any questions or feedback on this feature, don't hesitate to reach us at [[email protected]](mailto:[email protected]).
445+
[!INCLUDE [contact-resource-notifications](./includes/contact-resource-notifications.md)]
447446

448447
## Next steps
449448
See [Subscribe to Azure Resource Notifications - Resources events](subscribe-to-resource-notifications-resources-events.md).
Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: include file
3+
description: include file
4+
services: event-grid
5+
author: spelluru
6+
ms.service: event-grid
7+
ms.topic: include
8+
ms.date: 11/07/2023
9+
ms.author: spelluru
10+
ms.custom: include file
11+
---
12+
13+
## Contact us
14+
If you have any questions or feedback on this feature, don't hesitate to reach us at [[email protected]](mailto:[email protected]).
15+
16+
To better assist you with specific feedback about a certain event, provide the following information:
17+
18+
### For missing events:
19+
20+
- System topic type name
21+
- Approximate timestamp in UTC when the operation was executed
22+
- Base resource ID for which the notification was generated
23+
- Navigate to your resource in Azure portal and select JSON view at the far right corner. Resource ID is the first field on the JSON view page.
24+
- Expected event type
25+
- Operation executed (for example, VM started or stopped, Storage account created etc.)
26+
- Description of issue encountered (for example, VM started and no Microsoft.ResourceNotifications.HealthResources.AvailabilityStatusChanged event generated)
27+
- If possible, provide the correlation ID of operation executed
28+
29+
### For event that was delayed or has unexpected content
30+
31+
- System topic type name
32+
- Entire contents of the notification excluding data.resourceInfo.properties
33+
- Description of issue encountered and impacted field values
34+
35+
Ensure that you aren't providing any end user identifiable information while you're sharing this data.

articles/event-grid/subscribe-to-resource-notifications-health-resources-events.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell
66
ms.date: 09/08/2023
77
---
88

9-
# Subscribe to events raised by Azure Resource Notifications - Health Resources system topic
9+
# Subscribe to events raised by Azure Resource Notifications - Health Resources system topic (Preview)
1010
This article explains the steps needed to subscribe to events published by Azure Resource Notifications - Health Resources. For detailed information about these events, see [Azure Resource Notifications - Health Resources events](event-schema-health-resources.md).
1111

1212
## Create Health Resources system topic
@@ -243,8 +243,7 @@ Value = Microsoft.Compute/virtualMachines
243243

244244
---
245245

246-
## Contact us
247-
If you have any questions or feedback on this feature, don't hesitate to reach us at [[email protected]](mailto:[email protected]).
246+
[!INCLUDE [contact-resource-notifications](./includes/contact-resource-notifications.md)]
248247

249248
## Next steps
250249
For detailed information about these events, see [Azure Resource Notifications - Health Resources events](event-schema-health-resources.md).

articles/event-grid/subscribe-to-resource-notifications-resources-events.md

Lines changed: 2 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.topic: how-to
55
ms.date: 10/08/2023
66
---
77

8-
# Subscribe to events raised by Azure Resource Notifications - Resources system topic
8+
# Subscribe to Azure Resource Manager events - Resources system topic
99
This article explains the steps needed to subscribe to events published by Azure Resource Notifications - Resources. For detailed information about these events, see [Azure Resource Notifications - Resources events](event-schema-resources.md).
1010

1111
## Create Resources system topic
@@ -294,29 +294,7 @@ Value = "virtualMachines"
294294

295295
---
296296

297-
## Contact us
298-
If you have any questions or feedback on this feature, don't hesitate to reach us at [[email protected]](mailto:[email protected]).
299-
300-
To better assist you with specific feedback about a certain event, provide the following information:
301-
302-
### For missing events:
303-
304-
- System topic type name
305-
- Approximate timestamp in UTC when the operation was executed
306-
- Base resource ID for which the notification was generated
307-
- Navigate to your resource in Azure portal and select JSON view at the far right corner. Resource ID is the first field on the JSON view page.
308-
- Expected event type
309-
- Operation executed (for example, VM started or stopped, Storage account created etc.)
310-
- Description of issue encountered (for example, VM started and no Microsoft.ResourceNotifications.HealthResources.AvailabilityStatusChanged event generated)
311-
- If possible, provide the correlation ID of operation executed
312-
313-
### For event that was delayed or has unexpected content
314-
315-
- System topic type name
316-
- Entire contents of the notification excluding data.resourceInfo.properties
317-
- Description of issue encountered and impacted field values
318-
319-
Ensure that you aren't providing any end user identifiable information while you're sharing this data.
297+
[!INCLUDE [contact-resource-notifications](./includes/contact-resource-notifications.md)]
320298

321299
## Next steps
322300
For detailed information about these events, see [Azure Resource Notifications - Resources events](event-schema-resources.md).

0 commit comments

Comments
 (0)