Skip to content

Commit 569bfb0

Browse files
authored
Merge pull request #313773 from spelluru/egridfreshness0326
Azure Event Grid - Freshness - March 2
2 parents 87b4dfd + 0613d1a commit 569bfb0

3 files changed

Lines changed: 83 additions & 69 deletions

File tree

articles/event-grid/event-schema-key-vault.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,12 @@
11
---
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.
45
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
610
# Customer intent: As an architect or a developer, I want to know whether I can use Azure Key Vault as an Event Grid source.
711
---
812

@@ -33,7 +37,7 @@ An Azure Key Vault account generates the following event types:
3337

3438
# [Cloud event schema](#tab/cloud-event-schema)
3539

36-
The following example show schema for **Microsoft.KeyVault.SecretNewVersionCreated**:
40+
The following example shows the schema for **Microsoft.KeyVault.SecretNewVersionCreated**:
3741

3842
```JSON
3943
[
@@ -59,7 +63,7 @@ The following example show schema for **Microsoft.KeyVault.SecretNewVersionCreat
5963

6064
# [Event Grid event schema](#tab/event-grid-event-schema)
6165

62-
The following example show schema for **Microsoft.KeyVault.SecretNewVersionCreated**:
66+
The following example shows the schema for **Microsoft.KeyVault.SecretNewVersionCreated**:
6367

6468
```JSON
6569
[
@@ -95,7 +99,7 @@ An event has the following top-level data:
9599

96100
| Property | Type | Description |
97101
| -------- | ---- | ----------- |
98-
| `source` | string | Full resource path to the event source. This field isn't writeable. Event Grid provides this value. |
102+
| `source` | string | Full resource path to the event source. This field isn't writable. Event Grid provides this value. |
99103
| `subject` | string | Publisher-defined path to the event subject. |
100104
| `type` | string | One of the registered event types for this event source. |
101105
| `time` | string | The time the event is generated based on the provider's UTC time. |
@@ -108,7 +112,7 @@ An event has the following top-level data:
108112

109113
| Property | Type | Description |
110114
| -------- | ---- | ----------- |
111-
| `topic` | string | Full resource path to the event source. This field isn't writeable. Event Grid provides this value. |
115+
| `topic` | string | Full resource path to the event source. This field isn't writable. Event Grid provides this value. |
112116
| `subject` | string | Publisher-defined path to the event subject. |
113117
| `eventType` | string | One of the registered event types for this event source. |
114118
| `eventTime` | string | The time the event is generated based on the provider's UTC time. |

0 commit comments

Comments
 (0)