Merge pull request #168786 from v-rajagt/jafernan-aug9

PRMerger18 · web-flow · commit 30f1ed77ef1e · 2021-08-24T03:12:50.000+05:30
broken links fixed.
diff --git a/articles/event-grid/kubernetes/event-handlers.md b/articles/event-grid/kubernetes/event-handlers.md
@@ -11,7 +11,7 @@ ms.topic: conceptual
 # Event handlers destinations in Event Grid on Kubernetes
 An event handler is any system that exposes an endpoint and is the destination for events sent by Event Grid. An event handler receiving an event acts upon it and uses the event payload to execute some logic, which might lead to the occurrence of new events.
 
-The way to configure Event Grid to send events to a destination is through the creation of an event subscription. It can be done through [Azure CLI](/cli/azure/eventgrid/event-subscription#az_eventgrid_event_subscription_create), [management SDK](../sdk-overview.md#management-sdks), or using direct HTTPs calls using the [2020-10-15-preview API](/rest/api/eventgrid/version2020-10-15-preview/eventsubscriptions/createorupdate) version.
+The way to configure Event Grid to send events to a destination is through the creation of an event subscription. It can be done through [Azure CLI](/cli/azure/eventgrid/event-subscription#az_eventgrid_event_subscription_create), [management SDK](../sdk-overview.md#management-sdks), or using direct HTTPs calls using the [2020-10-15-preview API](/rest/api/eventgrid/version2021-06-01-preview/event-subscriptions/create-or-update) version.
 
 In general, Event Grid on Kubernetes can send events to any destination via **Webhooks**. Webhooks are HTTP(s) endpoints exposed by a service or workload to which Event Grid has access. The webhook can be a workload hosted in the same cluster, in the same network space, on the cloud, on-prem or anywhere that Event Grid can reach. 
 
@@ -34,15 +34,15 @@ In addition to Webhooks, Event Grid on Kubernetes can send events to the followi
 
 
 ## Feature parity
-Event Grid on Kubernetes offers a good level of feature parity with Azure Event Grid's support for event subscriptions. The following list enumerates the main differences in event subscription functionality. Apart from those differences, you can use Azure Event Grid's [REST api version 2020-10-15-preview](/rest/api/eventgrid/version2020-10-15-preview/eventsubscriptions) as a reference when managing event subscriptions on Event Grid on Kubernetes.
+Event Grid on Kubernetes offers a good level of feature parity with Azure Event Grid's support for event subscriptions. The following list enumerates the main differences in event subscription functionality. Apart from those differences, you can use Azure Event Grid's [REST api version 2020-10-15-preview](/rest/api/eventgrid/version2021-06-01-preview/event-subscriptions) as a reference when managing event subscriptions on Event Grid on Kubernetes.
 
-1. Use [REST api version 2020-10-15-preview](/rest/api/eventgrid/version2020-10-15-preview/eventsubscriptions).
+1. Use [REST api version 2020-10-15-preview](/rest/api/eventgrid/version2021-06-01-preview/event-subscriptions).
 2. [Azure Event Grid trigger for Azure Functions](../../azure-functions/functions-bindings-event-grid-trigger.md?tabs=csharp%2Cconsole) isn't supported. You can use a WebHook destination type to deliver events to Azure Functions.
 3. There's no [dead letter location](../manage-event-delivery.md#set-dead-letter-location) support. That means that you cannot use ``properties.deadLetterDestination`` in your event subscription payload.
 4. Azure Relay's Hybrid Connections as a destination isn't supported yet.
-5. Only CloudEvents schema is supported. The supported schema value is "[CloudEventSchemaV1_0](/rest/api/eventgrid/version2020-10-15-preview/eventsubscriptions/createorupdate#eventdeliveryschema)". Cloud Events schema is extensible and based on open standards.  
-6. Labels ([properties.labels](/rest/api/eventgrid/version2020-10-15-preview/eventsubscriptions/createorupdate#request-body)) aren't applicable to Event Grid on Kubernetes. Hence, they are not available.
-7. [Delivery with resource identity](/rest/api/eventgrid/version2020-10-15-preview/eventsubscriptions/createorupdate#deliverywithresourceidentity) isn't supported. So, all properties for [Event Subscription Identity](/rest/api/eventgrid/version2020-10-15-preview/eventsubscriptions/createorupdate#eventsubscriptionidentity) aren't supported.
+5. Only CloudEvents schema is supported. The supported schema value is "[CloudEventSchemaV1_0](/rest/api/eventgrid/version2021-06-01-preview/event-subscriptions/create-or-update#eventdeliveryschema)". Cloud Events schema is extensible and based on open standards.  
+6. Labels ([properties.labels](/rest/api/eventgrid/version2021-06-01-preview/event-subscriptions/create-or-update#request-body)) aren't applicable to Event Grid on Kubernetes. Hence, they are not available.
+7. [Delivery with resource identity](/rest/api/eventgrid/version2021-06-01-preview/event-subscriptions/create-or-update#deliverywithresourceidentity) isn't supported. So, all properties for [Event Subscription Identity](/rest/api/eventgrid/version2021-06-01-preview/event-subscriptions/create-or-update#eventsubscriptionidentity) aren't supported.
 8. [Destination endpoint validation](../webhook-event-delivery.md#endpoint-validation-with-event-grid-events) isn't supported yet.
 
 ## Event filtering in event subscriptions
@@ -169,4 +169,4 @@ To publish to a Storage Queue, set the  `endpointType` to `storageQueue` and pro
 
 ## Next steps
 * Add [filter configuration](filter-events.md) to your event subscription to select the events to be delivered. 
-* To learn about schemas supported by Event Grid on Azure Arc for Kubernetes, see [Event Grid on Kubernetes - Event schemas](event-schemas.md).
+* To learn about schemas supported by Event Grid on Azure Arc for Kubernetes, see [Event Grid on Kubernetes - Event schemas](event-schemas.md).
diff --git a/articles/event-grid/kubernetes/features.md b/articles/event-grid/kubernetes/features.md
@@ -9,7 +9,7 @@ ms.topic: conceptual
 ---
 
 # Event Grid on Kubernetes with Azure Arc features
-Event Grid on Kubernetes offers a rich set of features that help you integrate your Kubernetes workloads and realize hybrid architectures. It shares the same [rest API](/rest/api/eventgrid/version2020-10-15-preview/topics) (starting with version 2020-10-15-preview), [Event Grid CLI](/cli/azure/eventgrid), Azure portal experience, [management SDKs](../sdk-overview.md#management-sdks), and [data plane SDKs](../sdk-overview.md#data-plane-sdks) with Azure Event Grid, the other edition of the same service. When you're ready to publish events, you can use the [data plane SDK examples provided in different languages](https://devblogs.microsoft.com/azure-sdk/event-grid-ga/) that work for both editions of Event Grid.
+Event Grid on Kubernetes offers a rich set of features that help you integrate your Kubernetes workloads and realize hybrid architectures. It shares the same [rest API](/rest/api/eventgrid/version2021-06-01-preview/topics) (starting with version 2020-10-15-preview), [Event Grid CLI](/cli/azure/eventgrid), Azure portal experience, [management SDKs](../sdk-overview.md#management-sdks), and [data plane SDKs](../sdk-overview.md#data-plane-sdks) with Azure Event Grid, the other edition of the same service. When you're ready to publish events, you can use the [data plane SDK examples provided in different languages](https://devblogs.microsoft.com/azure-sdk/event-grid-ga/) that work for both editions of Event Grid.
 
 Although Event Grid on Kubernetes and Azure Event Grid share many features and the goal is to provide the same user experience, there are some differences given the unique requirements they seek to meet and the stage in which they are on their software lifecycle. For example, the only type of topic available in Event Grid on Kubernetes are Event Grid Topics that sometimes are also referred as custom topics. Other types of topics (see below) are either not applicable or support for them is not yet available. The main differences between the two editions of Event Grid are presented in the table below.
 
@@ -20,7 +20,7 @@ Although Event Grid on Kubernetes and Azure Event Grid share many features and t
 
 | Feature | Event Grid on Kubernetes | Azure Event Grid |
 |:--|:-:|:-:|
-| [Event Grid Topics](/rest/api/eventgrid/version2020-10-15-preview/topics) | ✔ | ✔ |
+| [Event Grid Topics](/rest/api/eventgrid/version2021-06-01-preview/topics) | ✔ | ✔ |
 | [CNCF Cloud Events schema](https://github.com/cloudevents/spec/blob/master/spec.md) | ✔ | ✔ |
 | Event Grid and custom schemas | ✘* | ✔ |
 | Reliable delivery | ✔ | ✔ |
@@ -36,7 +36,7 @@ Although Event Grid on Kubernetes and Azure Event Grid share many features and t
 | Azure Relay's Hybrid Connections as a destination | ✘ | ✔ |
 | [Advanced filtering](filter-events.md) | ✔*** | ✔ |
 | [Webhook AuthN/AuthZ with AAD](../secure-webhook-delivery.md) | ✘ | ✔ |
-| [Event delivery with resource identity](/rest/api/eventgrid/version2020-10-15-preview/eventsubscriptions/createorupdate#deliverywithresourceidentity) | ✘ | ✔ |
+| [Event delivery with resource identity](/rest/api/eventgrid/version2021-06-01-preview/event-subscriptions/create-or-update) | ✘ | ✔ |
 | Same set of data plane SDKs | ✔ | ✔ |
 | Same set of management SDKs | ✔ | ✔ |
 | Same Event Grid CLI | ✔ | ✔ |
@@ -48,4 +48,4 @@ Although Event Grid on Kubernetes and Azure Event Grid share many features and t
 \*** Event Grid on Kubernetes supports advanced filtering of events based on values in event data as Event Grid on Azure does, but there are a few features and operators that Event Grid on Kubernetes doesn't support. For more information, see [Advanced filtering](filter-events.md#filter-by-values-in-event-data).
 
 ## Next steps
-To learn more about Event Grid on Kubernetes, see [Event Grid on Kubernetes with Azure Arc (Preview) - overview](overview.md).
+To learn more about Event Grid on Kubernetes, see [Event Grid on Kubernetes with Azure Arc (Preview) - overview](overview.md).
diff --git a/articles/event-grid/kubernetes/overview.md b/articles/event-grid/kubernetes/overview.md
@@ -31,7 +31,7 @@ Event Grid on Kubernetes supports various event-driven integration scenarios. Ho
 
 "As an owner of a system deployed to a Kubernetes cluster, I want to communicate my system's state changes by publishing events and configuring routing of those events so that event handlers, under my control or otherwise, can process my system's events in a way they see fit."
 
-**Feature** that helps you realize above requirement: [Event Grid Topics](/rest/api/eventgrid/version2020-10-15-preview/topics).
+**Feature** that helps you realize above requirement: [Event Grid Topics](/rest/api/eventgrid/version2021-06-01-preview/topics).
 
 ### Event Grid on Kubernetes at a glance
 From the user perspective, Event Grid on Kubernetes is composed of the following resources in blue:
@@ -64,7 +64,7 @@ With Event Grid on Kubernetes, you can forward events to Azure for further proce
 Event handler destinations can be any HTTPS or HTTP endpoint to which Event Grid can reach through the network, public or private, and has access (not protected with some authentication mechanism). You define event delivery destinations when you create an event subscription. For more information, see [event handlers](event-handlers.md). 
 
 ## Features
-Event Grid on Kubernetes supports [Event Grid Topics](/rest/api/eventgrid/version2020-10-15-preview/topics), which is a feature also offered by [Azure Event Grid](../custom-topics.md). Event Grid topics help you realize the [primary integration use case](#use-case) where your requirements call for integrating your system with another workload that you own or otherwise is made accessible to your system.
+Event Grid on Kubernetes supports [Event Grid Topics](/rest/api/eventgrid/version2021-06-01-preview/topics), which is a feature also offered by [Azure Event Grid](../custom-topics.md). Event Grid topics help you realize the [primary integration use case](#use-case) where your requirements call for integrating your system with another workload that you own or otherwise is made accessible to your system.
 
 Some of the capabilities you get with Azure Event Grid on Kubernetes are:
 
@@ -92,4 +92,4 @@ Here are more resources that you can use:
 * [Data plane SDKs](../sdk-overview.md#data-plane-sdks).
 * [Publish events examples using the Data plane SDKs](https://devblogs.microsoft.com/azure-sdk/event-grid-ga/).
 * [Event Grid CLI](/cli/azure/eventgrid).
-* [Management SDKs](../sdk-overview.md#management-sdks).
+* [Management SDKs](../sdk-overview.md#management-sdks).
