Merge pull request #228475 from spelluru/freshness0224

Service Bus overview - refresh

Author: Court72

articles/event-grid/includes/event-sources-system-topics.md

@@ -5,7 +5,7 @@
  author: spelluru
  ms.service: event-grid
  ms.topic: include
- ms.date: 03/15/2022
+ ms.date: 02/27/2023
  ms.author: spelluru
  ms.custom: include file
 ---
@@ -17,6 +17,7 @@
 - [Azure Cache for Redis](../event-schema-azure-cache.md)
 - [Azure Communication Services](../event-schema-communication-services.md) 
 - [Azure Container Registry](../event-schema-container-registry.md)
+- [Azure Data Box](../event-schema-data-box.md)
 - [Azure Event Hubs](../event-schema-event-hubs.md)
 - [Azure Health Data Services](../event-schema-azure-health-data-services.md)
 - [Azure IoT Hub](../event-schema-iot-hub.md)

articles/event-grid/index.yml

@@ -13,7 +13,7 @@ metadata:
   ms.collection: collection
   author: spelluru #Required; your GitHub user alias, with correct capitalization.
   ms.author: spelluru #Required; microsoft alias of author; optional team alias.
-  ms.date: 01/11/2022 #Required; mm/dd/yyyy format.
+  ms.date: 02/27/2023 #Required; mm/dd/yyyy format.
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
 
@@ -54,6 +54,10 @@ landingContent:
             url: custom-event-quickstart-portal.md
           - text: Send events from a private container registry
             url: ../container-registry/container-registry-event-grid-quickstart.md?toc=/azure/event-grid/toc.json
+          - text: Handle SMS and delivery report events
+            url: ../communication-services/quickstarts/sms/handle-sms-events.md?toc=/azure/event-grid/toc.json
+          - text: Route Azure Cache for Redis events to web endpoint
+            url: ../azure-cache-for-redis/cache-event-grid-quickstart-portal.md
   # Card
   - title: Tutorials
     linkLists:
@@ -108,7 +112,7 @@ landingContent:
             url: /azure/architecture/reference-architectures/enterprise-integration/queues-events
 
   # Card
-  - title: Customizations
+  - title: Custom topics
     linkLists:
       - linkListType: quickstart
         links:
@@ -125,6 +129,32 @@ landingContent:
           - text: Map custom fields to Event Grid schema
             url: input-mappings.md
 
+  # Card
+  - title: Partner topics
+    linkLists:
+      - linkListType: concept
+        links:
+          - text: Partner Events overview (Customers)
+            url: partner-events-overview.md
+          - text: Partner Events overview (Partners)
+            url: partner-events-overview-for-partners.md
+          - text: Auth0 as an event source
+            url: auth0-overview.md
+          - text: Graph API as an event source
+            url: partner-events-graph-api.md
+      - linkListType: how-to-guide
+        links:
+          - text: Onboard as a partner
+            url: onboard-partner.md
+          - text: Subscribe to partner events
+            url: subscribe-to-partner-events.md
+          - text: Subscribe to SAP events
+            url: subscribe-to-sap-events.md
+          - text: Subscribe to Tribal Group events
+            url: subscribe-to-tribal-group-events.md
+          - text: Subscribe to Microsoft Graph API events
+            url: subscribe-to-graph-api-events.md
+
   # Card
   - title: Event Grid on Kubernetes
     linkLists:

articles/event-grid/system-topics.md

@@ -2,14 +2,14 @@
 title: System topics in Azure Event Grid
 description: Describes system topics in Azure Event Grid. 
 ms.topic: conceptual
-ms.date: 01/05/2022
+ms.date: 02/27/2023
 ---
 
 # System topics in Azure Event Grid
-A system topic in Event Grid represents one or more events published by Azure services such as Azure Storage and Azure Event Hubs. For example, a system topic may represent **all blob events** or only **blob created** and **blob deleted** events published for a **specific storage account**. In this example, when a blob is uploaded to the storage account, the Azure Storage service publishes a **blob created** event to the system topic in Event Grid, which then forwards the event to topic's [subscribers](event-handlers.md) that receive and process the event. 
+A system topic in Event Grid represents one or more **events published by Azure services** such as Azure Storage and Azure Event Hubs. For example, a system topic may represent **all blob events** or only **blob created** and **blob deleted** events published for a **specific storage account**. In this example, when a blob is uploaded to the storage account, the Azure Storage service publishes a **blob created** event to the system topic in Event Grid, which then forwards the event to topic's [subscribers](event-handlers.md) that receive and process the event. 
 
 > [!NOTE] 
-> - Only Azure services can publish events to system topics. Therefore, you don't get an endpoint or access keys that you can use to publish events like you do for [custom topics](custom-topics.md) or [event domains](event-domains.md).
+> Only Azure services can publish events to system topics. Therefore, you don't get an endpoint or access keys that you can use to publish events like you do for [custom topics](custom-topics.md) or [event domains](event-domains.md).
 
 ## Azure services that support system topics
 Here's the current list of Azure services that support creation of system topics on them.
@@ -18,17 +18,17 @@ Here's the current list of Azure services that support creation of system topics
 
 
 ## System topics as Azure resources
-In the past, a system topic was implicit and wasn't exposed for simplicity. System topics are now visible as Azure resources and provide the following capabilities:
+System topics are visible as Azure resources and provide the following capabilities:
 
 - [View system topics in the Azure portal](create-view-manage-system-topics.md#view-all-system-topics)
 - Export Resource Manager templates for system topics and event subscriptions in the Azure portal
 - [Set up diagnostic logs for system topics](enable-diagnostic-logs-topic.md#enable-diagnostic-logs-for-event-grid-system-topics)
-- Set up alerts on publish and delivery failures 
+- [Set up alerts](set-alerts.md) on publish and delivery failures 
 
 > [!NOTE]
-> - Only one Azure Event Grid system topic is allowed per source (like Subscription, Resource Group, etc.).
-> - Resource Group is required for Subscription level Event Grid system topic and cannot be changed until deleted/moved to another subscription.  
-> - Azure Event Grid creates a system topic resource in the same Azure subscription that has the event source. For example, if you create a system topic for a storage account *ContosoStorage* in an Azure subscription *ContosoSubscription*, Event Grid creates the system topic in the *ContosoSubscription*. It's not possible to create a system topic in an Azure subscription that's different from the event source's Azure subscription.
+> - Only one Azure Event Grid system topic is allowed per source (like subscription, resource group, etc.).
+> - A resource group is required for subscription-level system topic and can't be changed until deleted or moved to another subscription.  
+> - Event Grid creates a system topic resource in the same Azure subscription that has the event source. For example, if you create a system topic for a storage account `ContosoStorage` in an Azure subscription `ContosoSubscription`, Event Grid creates the system topic in the `ContosoSubscription`. It's not possible to create a system topic in an Azure subscription that's different from the event source's Azure subscription.
 
 ## Lifecycle of system topics
 You can create a system topic in two ways: 
@@ -38,12 +38,15 @@ You can create a system topic in two ways:
 
     When you use the Azure portal, you're always using this method. When you create an event subscription using the [**Events** page of an Azure resource](blob-event-quickstart-portal.md#subscribe-to-the-blob-storage), the system topic is created first and then the subscription for the topic is created. You can explicitly create a system topic first by using the [**Event Grid System Topics** page](create-view-manage-system-topics.md#create-a-system-topic) and then create a subscription for that topic. 
 
-When you use [CLI](create-view-manage-system-topics-cli.md), [REST](/rest/api/eventgrid/controlplane-version2022-06-15/event-subscriptions/create-or-update), or [Azure Resource Manager template](create-view-manage-system-topics-arm.md), you can choose either of the above methods. We recommend that you create a system topic first and then create a subscription on the topic, as it's the latest way of creating system topics.
+When you use [CLI](create-view-manage-system-topics-cli.md), [REST](/rest/api/eventgrid/controlplane-version2022-06-15/event-subscriptions/create-or-update), or [Azure Resource Manager template](create-view-manage-system-topics-arm.md), you can choose either of the above methods. 
+
+> [!IMPORTANT]
+> We recommend that you create a system topic first and then create a subscription on the topic, as it's the latest way of creating system topics.
 
 ### Failure to create system topics
 The system topic creation fails if you have set up Azure policies in such a way that the Event Grid service can't create it. For example, you may have a policy that allows creation of only certain types of resources (for example: Azure Storage, Azure Event Hubs, and so on.) in the subscription. 
 
-In such cases, event flow functionality is preserved. However, metrics and diagnostic functionalities of system topics will be unavailable.
+In such cases, event flow functionality is preserved. However, metrics and diagnostic functionalities of system topics are unavailable.
 
 If you require this functionality, allow creation of resources of the system topic type, and create the missing system topic as described in the [Lifecycle of system topics](#lifecycle-of-system-topics) section.