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
Copy file name to clipboardExpand all lines: articles/event-grid/event-schema-key-vault.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,12 @@
1
1
---
2
-
title: Azure Key Vault as Event Grid source
3
-
description: This article describes the properties and schema provided for Azure Key Vault events with Azure Event Grid
2
+
title: Azure Key Vault as Event Grid Source Overview
3
+
description: "Azure Key Vault events: Discover how to use Azure Key Vault as an Event Grid source, including event types, schema details, and integration tips."
4
+
#customer intent: As an architect, I want to understand which Azure Key Vault events are available in Event Grid so that I can design event-driven solutions.
4
5
ms.topic: concept-article
5
-
ms.date: 02/14/2025
6
+
ms.date: 03/26/2026
7
+
author: spelluru
8
+
ms.author: spelluru
9
+
ms.reviewer: spelluru
6
10
# Customer intent: As an architect or a developer, I want to know whether I can use Azure Key Vault as an Event Grid source.
7
11
---
8
12
@@ -33,7 +37,7 @@ An Azure Key Vault account generates the following event types:
33
37
34
38
# [Cloud event schema](#tab/cloud-event-schema)
35
39
36
-
The following example show schema for **Microsoft.KeyVault.SecretNewVersionCreated**:
40
+
The following example shows the schema for **Microsoft.KeyVault.SecretNewVersionCreated**:
37
41
38
42
```JSON
39
43
[
@@ -59,7 +63,7 @@ The following example show schema for **Microsoft.KeyVault.SecretNewVersionCreat
Copy file name to clipboardExpand all lines: articles/event-grid/security-authorization.md
+18-14Lines changed: 18 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,26 @@
1
1
---
2
-
title: Azure Event Grid security and authentication
3
-
description: This article describes how you can authorize access to Azure Event Grid resources using role-based access control roles.
2
+
title: Event Grid Access Control with Azure RBAC
3
+
description: Azure Event Grid security controls access to resources using Azure RBAC built-in and custom roles. Learn how to configure role-based permissions for Event Grid operations.
4
+
#customer intent: As an IT admin, I want to understand how to control access to Azure Event Grid resources using role-based access control so that I can ensure only authorized users can perform management operations.
4
5
ms.topic: concept-article
5
-
ms.date: 12/16/2024
6
+
ms.date: 03/26/2026
7
+
author: spelluru
8
+
ms.author: spelluru
9
+
ms.reviewer: spelluru
6
10
# Customer intent: I want to know how to secure access to Azure Event Grid resources.
7
11
---
8
12
9
13
# Authorizing access to Event Grid resources
10
-
Azure Event Grid allows you to control the level of access given to different users to do various **management operations** such as list event subscriptions, create new ones, and generate keys. Event Grid uses Azure role-based access control (Azure RBAC).
14
+
Azure Event Grid enables you to control the level of access different users have for various **management operations** such as listing event subscriptions, creating new ones, and generating keys. Event Grid uses Azure role-based access control (Azure RBAC).
11
15
12
16
## Operation types
13
-
For a list of operation supported by Azure Event Grid, run the following Azure CLI command:
17
+
To see a list of operations supported by Azure Event Grid, run the following Azure CLI command:
14
18
15
19
```azurecli-interactive
16
20
az provider operation show --namespace Microsoft.EventGrid
17
21
```
18
22
19
-
The following operations return potentially secret information, which gets filtered out of normal read operations. We recommend that you restrict access to these operations.
23
+
The following operations return potentially secret information, which gets filtered out of normal read operations. Restrict access to these operations.
@@ -48,9 +52,9 @@ The **Event Grid Contributor** role allows you to create and manage Event Grid r
48
52
49
53
If you need to specify permissions that are different than the built-in roles, create custom roles.
50
54
51
-
The following are sample Event Grid role definitions that allow users to take different actions. These custom roles are different from the built-in roles because they grant broader access than just event subscriptions.
55
+
The following sample Event Grid role definitions grant users different permissions. These custom roles differ from the built-in roles because they grant broader access than just event subscriptions.
52
56
53
-
**EventGridReadOnlyRole.json**: Only allow read-only operations.
57
+
-**EventGridReadOnlyRole.json**: Grants only read-only operations.
54
58
55
59
```json
56
60
{
@@ -69,7 +73,7 @@ The following are sample Event Grid role definitions that allow users to take di
69
73
}
70
74
```
71
75
72
-
**EventGridNoDeleteListKeysRole.json**: Allow restricted post actions but disallow delete actions.
76
+
-**EventGridNoDeleteListKeysRole.json**: Grants restricted post actions but disallows delete actions.
73
77
74
78
```json
75
79
{
@@ -92,7 +96,7 @@ The following are sample Event Grid role definitions that allow users to take di
92
96
}
93
97
```
94
98
95
-
**EventGridContributorRole.json**: Allows all Event Grid actions.
99
+
-**EventGridContributorRole.json**: Grants all Event Grid actions.
96
100
97
101
```json
98
102
{
@@ -120,15 +124,15 @@ You can create custom roles with [PowerShell](../role-based-access-control/custo
120
124
121
125
### Encryption at rest
122
126
123
-
All events or data written to disk by the Event Grid service is encrypted by a Microsoft-managed key ensuring that it's encrypted at rest. Additionally, the maximum period of time that events or data retained is 24 hours in adherence with the [Event Grid retry policy](delivery-and-retry.md). Event Grid will automatically delete all events or data after 24 hours, or the event time-to-live, whichever is less.
127
+
The Event Grid service encrypts all events or data written to disk by using a Microsoft-managed key, ensuring that it's encrypted at rest. Additionally, the maximum period of time that events or data are retained is 24 hours in adherence with the [Event Grid retry policy](delivery-and-retry.md). Event Grid automatically deletes all events or data after 24 hours, or the event time-to-live, whichever is less.
124
128
125
129
## Permissions for event subscriptions
126
-
If you're using an event handler that isn't a WebHook (such as an event hub or queue storage), you need write access to that resource. This permissions check prevents an unauthorized user from sending events to your resource.
130
+
If you use an event handler that isn't a WebHook (such as an event hub or queue storage), you need write access to that resource. This permissions check prevents an unauthorized user from sending events to your resource.
127
131
128
132
You must have the **Microsoft.EventGrid/EventSubscriptions/Write** permission on the resource that is the event source. You need this permission because you're writing a new subscription at the scope of the resource. The required resource differs based on whether you're subscribing to a system topic or custom topic. Both types are described in this section.
129
133
130
134
### System topics (Azure service publishers)
131
-
For system topics, if you aren't the owner or contributor of the source resource, you need permission to write a new event subscription at the scope of the resource publishing the event. The format of the resource is:
135
+
For system topics, if you're not the owner or contributor of the source resource, you need permission to write a new event subscription at the scope of the resource that publishes the event. The format of the resource is:
0 commit comments