Azure · xiangyan99 · Jan 13, 2025 · Jan 10, 2025
@@ -224,7 +224,7 @@ This version and all future versions will require Python 3.8+.
 
   **Breaking Changes**
   - `azure.eventgrid.models` namespace along with all the models in it are now removed.:
-      - JSON documentation on the events is available here: https://docs.microsoft.com/azure/event-grid/system-topics
+      - JSON documentation on the events is available here: https://learn.microsoft.com/azure/event-grid/system-topics
       - `azure.eventgrid.SystemEventNames` provides the list of available events name for easy switching.
   - `azure.eventgrid.event_grid_client.EventGridClient` is now removed in favor of `azure.eventgrid.EventGridPublisherClient`.
   - `azure.eventgrid.event_grid_client.EventGridClientConfiguration` is now removed.

@@ -20,7 +20,7 @@ This is a GA release of Azure Event Grid's `EventGridPublisherClient` and `Event
 * Python 3.8 or later is required to use this package.
 * You must have an [Azure subscription][azure_subscription] and at least one of the following:
     * an Event Grid Namespace resource. To create an Event Grid Namespace resource follow [this tutorial](https://learn.microsoft.com/azure/event-grid/create-view-manage-namespaces).
-    * an Event Grid Basic resource. To create an Event Grid Basic resource via the Azure portal follow this [step-by-step tutorial](https://docs.microsoft.com/azure/event-grid/custom-event-quickstart-portal). To create an Event Grid Basic resource via the [Azure CLI](https://docs.microsoft.com/cli/azure) follow this [tutorial](https://docs.microsoft.com/azure/event-grid/custom-event-quickstart)
+    * an Event Grid Basic resource. To create an Event Grid Basic resource via the Azure portal follow this [step-by-step tutorial](https://learn.microsoft.com/azure/event-grid/custom-event-quickstart-portal). To create an Event Grid Basic resource via the [Azure CLI](https://learn.microsoft.com/cli/azure) follow this [tutorial](https://learn.microsoft.com/azure/event-grid/custom-event-quickstart)
 
 ### Event Grid Resources
 
@@ -115,7 +115,7 @@ You can find the topic endpoint within the Event Grid Topic resource on the Azur
 To use an Access key as the `credential` parameter,
 pass the key as a string into an instance of [AzureKeyCredential][azure-key-credential].
 
-> **Note:** The Access Key may be found in the azure portal in the "Access Keys" menu of the Event Grid Topic resource.  They may also be obtained via the azure CLI, or the `azure-mgmt-eventgrid` library. A guide for getting access keys can be found [here](https://docs.microsoft.com/azure/event-grid/get-access-keys).
+> **Note:** The Access Key may be found in the azure portal in the "Access Keys" menu of the Event Grid Topic resource.  They may also be obtained via the azure CLI, or the `azure-mgmt-eventgrid` library. A guide for getting access keys can be found [here](https://learn.microsoft.com/azure/event-grid/get-access-keys).
 
 <!-- SNIPPET:sample_authentication.client_auth_with_key_cred -->
 
@@ -155,21 +155,21 @@ An **[event subscription](https://learn.microsoft.com/azure/event-grid/concepts-
 ### Event Grid Basic
 
 #### Topic
-A **[topic](https://docs.microsoft.com/azure/event-grid/concepts#topics)** is a channel within the Event Grid service to send events. The event schema that a topic accepts is decided at topic creation time. If events of a schema type are sent to a topic that requires a different schema type, errors will be raised.
+A **[topic](https://learn.microsoft.com/azure/event-grid/concepts#topics)** is a channel within the Event Grid service to send events. The event schema that a topic accepts is decided at topic creation time. If events of a schema type are sent to a topic that requires a different schema type, errors will be raised.
 
 #### Domain
-An event **[domain](https://docs.microsoft.com/azure/event-grid/event-domains)** is a management tool for large numbers of Event Grid topics related to the same application. They allow you to publish events to thousands of topics. Domains also give you authorization and authentication control over each topic. For more information, visit [Event domain overview](https://docs.microsoft.com/azure/event-grid/event-domains).
+An event **[domain](https://learn.microsoft.com/azure/event-grid/event-domains)** is a management tool for large numbers of Event Grid topics related to the same application. They allow you to publish events to thousands of topics. Domains also give you authorization and authentication control over each topic. For more information, visit [Event domain overview](https://learn.microsoft.com/azure/event-grid/event-domains).
 
 #### Event schemas
-An **[event](https://docs.microsoft.com/azure/event-grid/concepts#events)** is the smallest amount of information that fully describes something that happened in the system. When a custom topic or domain is created, you must specify the schema that will be used when publishing events.
+An **[event](https://learn.microsoft.com/azure/event-grid/concepts#events)** is the smallest amount of information that fully describes something that happened in the system. When a custom topic or domain is created, you must specify the schema that will be used when publishing events.
 
 Event Grid supports multiple schemas for encoding events.
 
 #### System Topics
-A **[system topic](https://docs.microsoft.com/azure/event-grid/system-topics)** in Event Grid represents one or more events published by Azure services such as Azure Storage or Azure Event Hubs. For example, a system topic may represent all blob events or only blob creation and blob deletion events published for a specific storage account.
+A **[system topic](https://learn.microsoft.com/azure/event-grid/system-topics)** in Event Grid represents one or more events published by Azure services such as Azure Storage or Azure Event Hubs. For example, a system topic may represent all blob events or only blob creation and blob deletion events published for a specific storage account.
 
 The names of the various event types for the system events published to Azure Event Grid are available in `azure.eventgrid.SystemEventNames`.
-For complete list of recognizable system topics, visit [System Topics](https://docs.microsoft.com/azure/event-grid/system-topics).
+For complete list of recognizable system topics, visit [System Topics](https://learn.microsoft.com/azure/event-grid/system-topics).
 
  For more information about the key concepts on Event Grid, see [Concepts in Azure Event Grid][publisher-service-doc].
 
@@ -196,7 +196,7 @@ Please have a look at the [samples](https://github.com/Azure/azure-sdk-for-pytho
 
 ## Event Grid on Kubernetes with Azure Arc
 
-Event Grid on Kubernetes with Azure Arc is an offering that allows you to run Event Grid on your own Kubernetes cluster. This capability is enabled by the use of Azure Arc enabled Kubernetes. Through Azure Arc enabled Kubernetes, a supported Kubernetes cluster connects to Azure. Once connected, you are able to install Event Grid on it. Learn more about it [here](https://docs.microsoft.com/azure/event-grid/kubernetes/overview).
+Event Grid on Kubernetes with Azure Arc is an offering that allows you to run Event Grid on your own Kubernetes cluster. This capability is enabled by the use of Azure Arc enabled Kubernetes. Through Azure Arc enabled Kubernetes, a supported Kubernetes cluster connects to Azure. Once connected, you are able to install Event Grid on it. Learn more about it [here](https://learn.microsoft.com/azure/event-grid/kubernetes/overview).
 
 ## Examples
 
@@ -434,7 +434,7 @@ More samples can be found [here][python-eg-samples].
 
 ### Additional documentation
 
-For more extensive documentation on Azure Event Grid, see the [Event Grid documentation][python-eg-product-docs] on docs.microsoft.com.
+For more extensive documentation on Azure Event Grid, see the [Event Grid documentation][python-eg-product-docs] on learn.microsoft.com.
 
 ## Contributing
 This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit [cla.microsoft.com][cla].
@@ -448,9 +448,9 @@ This project has adopted the [Microsoft Open Source Code of Conduct][code_of_con
 [azure_cli_link]: https://pypi.org/project/azure-cli/
 [python-eg-src]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/eventgrid/azure-eventgrid
 [python-eg-pypi]: https://pypi.org/project/azure-eventgrid
-[python-eg-product-docs]: https://docs.microsoft.com/azure/event-grid/overview
+[python-eg-product-docs]: https://learn.microsoft.com/azure/event-grid/overview
 [python-eg-ref-docs]: https://azuresdkdocs.blob.core.windows.net/$web/python/azure-eventgrid/latest/index.html
-[publisher-service-doc]: https://docs.microsoft.com/azure/event-grid/concepts
+[publisher-service-doc]: https://learn.microsoft.com/azure/event-grid/concepts
 [python-eg-samples]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/eventgrid/azure-eventgrid/samples
 [python-eg-changelog]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/eventgrid/azure-eventgrid/CHANGELOG.md
 [pip]: https://pypi.org/project/pip/

@@ -13,7 +13,7 @@ class SystemEventNames(str, Enum, metaclass=CaseInsensitiveEnumMeta):
     """
     This enum represents the names of the various event types for the system events published to
     Azure Event Grid. To check the list of recognizable system topics,
-    visit https://docs.microsoft.com/azure/event-grid/system-topics.
+    visit https://learn.microsoft.com/azure/event-grid/system-topics.
     """
 
     # These names at the top are 'corrected' aliases of duplicate values that appear below, which are

@@ -115,7 +115,7 @@ def _eventgrid_data_typecheck(event):
     if isinstance(data, bytes):
         raise TypeError(
             "Data in EventGridEvent cannot be bytes. Please refer to"
-            "https://docs.microsoft.com/en-us/azure/event-grid/event-schema"
+            "https://learn.microsoft.com/azure/event-grid/event-schema"
         )
 
 

@@ -203,7 +203,7 @@ def send(self, events: SendType, *, channel_name: Optional[str] = None, **kwargs
         :keyword channel_name: Optional. Used to specify the name of event channel when publishing to partner.
         :paramtype channel_name: str or None
          namespaces with partner topic. For more details, visit
-         https://docs.microsoft.com/azure/event-grid/partner-events-overview
+         https://learn.microsoft.com/azure/event-grid/partner-events-overview
         :rtype: None
         """
         if not isinstance(events, list):

@@ -199,7 +199,7 @@ async def send(self, events: SendType, *, channel_name: Optional[str] = None, **
         :keyword channel_name: Optional. Used to specify the name of event channel when publishing to partner
         :paramtype channel_name: str or None
          namespaces with partner topic. For more details, visit
-         https://docs.microsoft.com/azure/event-grid/partner-events-overview
+         https://learn.microsoft.com/azure/event-grid/partner-events-overview
         :rtype: None
         """
         if not isinstance(events, list):

@@ -72,7 +72,7 @@ To publish events, dict representation of the models could also be used as follo
 
 [python-eg-sample-consume-custom-payload]: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/eventgrid/azure-eventgrid/samples/basic/sync_samples/sample_consume_custom_payload.py
 
-[publisher-service-doc]: https://docs.microsoft.com/azure/event-grid/concepts
+[publisher-service-doc]: https://learn.microsoft.com/azure/event-grid/concepts
 
 
 [python-eg-namespace-authenticate]:https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/eventgrid/azure-eventgrid/samples/namespace/sync_samples/sample_namespace_authentication.py