Merge pull request #102758 from spelluru/ehubdotnet0129

.NET SDK release

Author: PMEds28

.openpublishing.redirection.json

@@ -13291,6 +13291,11 @@
       "redirect_url": "/azure/event-hubs/event-hubs-quickstart-powershell",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/event-hubs/event-hubs-managed-service-identity.md",
+      "redirect_url": "/azure/event-hubs/authenticate-managed-identity",
+      "redirect_document_id": false
+    },  
     {
       "source_path": "articles/event-hubs/event-hubs-node-get-started-receive.md",
       "redirect_url": "/azure/event-hubs/event-hubs-node-get-started-send",

articles/active-directory/managed-identities-azure-resources/TOC.yml

@@ -51,7 +51,7 @@
   - name: Azure App Service and Functions
     href: /azure/app-service/overview-managed-identity?context=azure/active-directory/managed-identities-azure-resources/context/msi-context
   - name: Azure Event Hubs
-    href: /azure/event-hubs/event-hubs-managed-service-identity?context=azure/active-directory/managed-identities-azure-resources/context/msi-context
+    href: /azure/event-hubs/authenticate-managed-identity.md?context=azure/active-directory/managed-identities-azure-resources/context/msi-context
   - name: Azure Container Instances
     href: /azure/container-instances/container-instances-managed-identity?context=azure/active-directory/managed-identities-azure-resources/context/msi-context
 - name: How-to guides

articles/active-directory/managed-identities-azure-resources/overview.md

@@ -132,7 +132,7 @@ Learn how to use a managed identity with other Azure services:
 * [Azure API Management](../../api-management/api-management-howto-use-managed-service-identity.md)
 * [Azure Container Instances](../../container-instances/container-instances-managed-identity.md)
 * [Azure Container Registry Tasks](../../container-registry/container-registry-tasks-authentication-managed-identity.md)
-* [Azure Event Hubs](../../event-hubs/event-hubs-managed-service-identity.md)
+* [Azure Event Hubs](../../event-hubs/authenticate-managed-identity.md)
 * [Azure Functions](/azure/app-service/overview-managed-identity)
 * [Azure Kubernetes Service](/azure/aks/use-managed-identity)
 * [Azure Logic Apps](/azure/logic-apps/create-managed-service-identity)

articles/azure-monitor/platform/diagnostics-extension-stream-event-hubs.md

@@ -197,7 +197,7 @@ In this example, the sink is applied to logs and is filtered only to error level
 ## Deploy and update a Cloud Services application and diagnostics config
 Visual Studio provides the easiest path to deploy the application and Event Hubs sink configuration. To view and edit the file, open the *.wadcfgx* file in Visual Studio, edit it, and save it. The path is **Cloud Service Project** > **Roles** > **(RoleName)** > **diagnostics.wadcfgx**.  
 
-At this point, all deployment and deployment update actions in Visual Studio, Visual Studio Team System, and all commands or scripts that are based on MSBuild and use the **/t:publish** target include the *.wadcfgx* in the packaging process. In addition, deployments and updates deploy the file to Azure by using the appropriate Azure Diagnostics agent extension on your VMs.
+At this point, all deployment and deployment update actions in Visual Studio, Visual Studio Team System, and all commands or scripts that are based on MSBuild and use the `/t:publish` target include the *.wadcfgx* in the packaging process. In addition, deployments and updates deploy the file to Azure by using the appropriate Azure Diagnostics agent extension on your VMs.
 
 After you deploy the application and Azure Diagnostics configuration, you will immediately see activity in the dashboard of the event hub. This indicates that you're ready to move on to viewing the hot-path data in the listener client or analysis tool of your choice.  
 
@@ -211,14 +211,72 @@ In the following figure, the Event Hubs dashboard shows healthy sending of diagn
 >
 
 ## View hot-path data
-As discussed previously, there are many use cases for listening to and processing Event Hubs data.
+As discussed previously, there are many use cases for listening to and processing Event Hubs data. One simple approach is to create a small test console application to listen to the event hub and print the output stream. 
 
-One simple approach is to create a small test console application to listen to the event hub and print the output stream. You can place the following code, which is explained in more detail
-in [Get started with Event Hubs](../../event-hubs/event-hubs-dotnet-standard-getstarted-send.md)), in a console application.  
+#### [.NET SDK latest (5.0.0 or later)](#tab/latest)
+You can place the following code, which is explained in more detail in [Get started with Event Hubs](../../event-hubs/get-started-dotnet-standard-send-v2.md)), in a console application.
 
-Note that the console application must include the [Event Processor Host NuGet package](https://www.nuget.org/packages/Microsoft.Azure.ServiceBus.EventProcessorHost/).  
+```csharp
+using System;
+using System.Text;
+using System.Threading.Tasks;
+using Azure.Storage.Blobs;
+using Azure.Messaging.EventHubs;
+using Azure.Messaging.EventHubs.Processor;
+namespace Receiver1204
+{
+    class Program
+    {
+        private static readonly string ehubNamespaceConnectionString = "EVENT HUBS NAMESPACE CONNECTION STRING";
+        private static readonly string eventHubName = "EVENT HUB NAME";
+        private static readonly string blobStorageConnectionString = "AZURE STORAGE CONNECTION STRING";
+        private static readonly string blobContainerName = "BLOB CONTAINER NAME";
 
-Remember to replace the values in angle brackets in the **Main** function with values for your resources.   
+        static async Task Main()
+        {
+            // Read from the default consumer group: $Default
+            string consumerGroup = EventHubConsumerClient.DefaultConsumerGroupName;
+
+            // Create a blob container client that the event processor will use 
+            BlobContainerClient storageClient = new BlobContainerClient(blobStorageConnectionString, blobContainerName);
+
+            // Create an event processor client to process events in the event hub
+            EventProcessorClientOptions options = new EventProcessorClientOptions { }
+            EventProcessorClient processor = new EventProcessorClient(storageClient, consumerGroup, ehubNamespaceConnectionString, eventHubName);
+
+            // Register handlers for processing events and handling errors
+            processor.ProcessEventAsync += ProcessEventHandler;
+            processor.ProcessErrorAsync += ProcessErrorHandler;
+
+            // Start the processing
+            await processor.StartProcessingAsync();
+
+            // Wait for 10 seconds for the events to be processed
+            await Task.Delay(TimeSpan.FromSeconds(10));
+
+            // Stop the processing
+            await processor.StopProcessingAsync();
+        }
+
+        static Task ProcessEventHandler(ProcessEventArgs eventArgs)
+        {
+            Console.WriteLine("\tRecevied event: {0}", Encoding.UTF8.GetString(eventArgs.Data.Body.ToArray()));
+            return Task.CompletedTask;
+        }
+
+        static Task ProcessErrorHandler(ProcessErrorEventArgs eventArgs)
+        {
+            Console.WriteLine($"\tPartition '{ eventArgs.PartitionId}': an unhandled exception was encountered. This was not expected to happen.");
+            Console.WriteLine(eventArgs.Exception.Message);
+            return Task.CompletedTask;
+        }
+    }
+}
+```
+
+#### [.NET SDK legacy (4.1.0 or earlier)](#tab/legacy)
+
+You can place the following code, which is explained in more detail in [Get started with Event Hubs](../../event-hubs/event-hubs-dotnet-standard-getstarted-send.md)), in a console application. Note that the console application must include the [Event Processor Host Nuget package](https://www.nuget.org/packages/Microsoft.Azure.ServiceBus.EventProcessorHost/). Remember to replace the values in angle brackets in the **Main** function with values for your resources.   
 
 ```csharp
 //Console application code for EventHub test client
@@ -300,14 +358,15 @@ namespace EventHubListener
     }
 }
 ```
+---
 
 ## Troubleshoot Event Hubs sinks
 * The event hub does not show incoming or outgoing event activity as expected.
 
     Check that your event hub is successfully provisioned. All connection info in the **PrivateConfig** section of *.wadcfgx* must match the values of your resource as seen in the portal. Make sure that you have a SAS policy defined ("SendRule" in the example) in the portal and that *Send* permission is granted.  
 * After an update, the event hub no longer shows incoming or outgoing event activity.
 
-    First, make sure that the event hub and configuration info is correct as explained previously. Sometimes the **PrivateConfig** is reset in a deployment update. The recommended fix is to make all changes to *.wadcfgx* in the project and then push a complete application update. If this is not possible, make sure that the diagnostics update pushes a complete **PrivateConfig** that includes the SAS key.  
+    First, make sure that the event hub and configuration info are correct as explained previously. Sometimes the **PrivateConfig** is reset in a deployment update. The recommended fix is to make all changes to *.wadcfgx* in the project and then push a complete application update. If this is not possible, make sure that the diagnostics update pushes a complete **PrivateConfig** that includes the SAS key.  
 * I tried the suggestions, and the event hub is still not working.
 
     Try looking in the Azure Storage table that contains logs and errors for Azure Diagnostics itself: **WADDiagnosticInfrastructureLogsTable**. One option is to use a tool such as [Azure Storage Explorer](https://www.storageexplorer.com) to connect to this storage account, view this table, and add a query for TimeStamp in the last 24 hours. You can use the tool to export a .csv file and open it in an application such as Microsoft Excel. Excel makes it easy to search for calling-card strings, such as **EventHubs**, to see what error is reported.  
@@ -383,7 +442,7 @@ The complementary *ServiceConfiguration.Cloud.cscfg* for this example looks like
 </ServiceConfiguration>
 ```
 
-Equivalent JSON settings for virtual machines is as follows:
+Equivalent JSON settings for virtual machines are as follows:
 
 Public Settings:
 ```JSON

articles/event-hubs/TOC.yml

@@ -26,29 +26,27 @@
       href: event-hubs-resource-manager-namespace-event-hub.md
   - name: Send and receive events
     items:
-    - name: .NET Core
-      href: event-hubs-dotnet-standard-getstarted-send.md
-    - name: Java
+    - name: .NET Core (Azure.Messaging.EventHubs)
+      href: get-started-dotnet-standard-send-v2.md
+    - name: Java (azure-eventhubs)
       href: event-hubs-java-get-started-send.md
-    - name: Python
+    - name: Python (azure-eventhub version 5)
       href: get-started-python-send-v2.md
-    - name: Node.js
+    - name: Node.js (azure/event-hubs version 5)
       href: get-started-node-send-v2.md
     - name: Go
       href: event-hubs-go-get-started-send.md
     - name: C (send only)
       href: event-hubs-c-getstarted-send.md
     - name: Apache Storm (receive only)
       href: event-hubs-storm-getstarted-receive.md   
-    - name: .NET Framework
-      href: event-hubs-dotnet-framework-getstarted-send.md
   - name: Capture events
     items:
     - name: Use the Azure portal to enable Event Hubs Capture
       href: event-hubs-capture-enable-through-portal.md
     - name: Use a Resource Manager template to enable Event Hubs Capture
       href: event-hubs-resource-manager-namespace-event-hub-enable-capture.md
-    - name: Capture Event Hubs data using Python
+    - name: Capture Event Hubs data using Python  (azure-eventhub version 5)
       href: get-started-capture-python-v2.md
   - name: Stream into Event Hubs for Apache Kafka
     href: event-hubs-quickstart-kafka-enabled-event-hubs.md
@@ -71,8 +69,10 @@
   items:
   - name: Event Hubs terminology
     href: event-hubs-features.md
-  - name: Event processor host
+  - name: Event processor host (legacy SDK)
     href: event-hubs-event-processor-host.md
+  - name: Event processor (latest SDK)
+    href: event-processor-balance-partition-load.md    
   - name: Availability and consistency
     href: event-hubs-availability-and-consistency.md
   - name: Scalability
@@ -116,20 +116,26 @@
       href: event-hubs-exchange-events-different-protocols.md
     - name: Programming guides
       items:
-      - name: Python
+      - name: .NET (Azure.Messaging.EventHubs)
+        href: https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/eventhub/Azure.Messaging.EventHubs/README.md      
+      - name: Python (azure-eventhub version 5)
         href: https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/eventhub/azure-eventhub/README.md
-      - name: JavaScript
+      - name: JavaScript (azure/event-hubs version 5)
         href: https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/eventhubs/azure-messaging-eventhubs/README.md
-      - name: .NET programming guide
+      - name: .NET (Microsoft.Azure.EventHubs)
         href: event-hubs-programming-guide.md
-    - name: Read captured data using Python (legacy)
+    - name: Read captured data using Python (azure-eventhub version 1)
       href: event-hubs-capture-python.md
-    - name: Send and receive events (legacy)
+    - name: Send and receive events (old versions/packages)
       items:
-      - name: Python (legacy)
+      - name: .NET Core (Microsoft.Azure.EventHubs)
+        href: event-hubs-dotnet-standard-getstarted-send.md
+      - name: Python (azure-eventhub version 1)
         href: event-hubs-python-get-started-send.md
-      - name: Node.js (legacy)    
+      - name: Node.js (azure/event-hubs version 2)    
         href: event-hubs-node-get-started-send.md
+      - name: .NET Framework (Microsoft.Azure.EventHubs)
+        href: event-hubs-dotnet-framework-getstarted-send.md
   - name: Process data
     items:
     - name: Process data using Azure Stream Analytics 
@@ -186,34 +192,52 @@
       href: resource-manager-exceptions.md
 - name: Reference
   items:
-  - name: Java
-    items:
-    - name: com.microsoft.azure.eventhubs
-      href: /java/api/com.microsoft.azure.eventhubs
-    - name: com.microsoft.azure.eventprocessorhost
-      href: /java/api/com.microsoft.azure.eventprocessorhost
   - name: .NET
     items:
-    - name: Microsoft.Azure.EventHubs
-      href: /dotnet/api/microsoft.azure.eventhubs
-    - name: Microsoft.Azure.EventHubs.Processor
-      href: /dotnet/api/microsoft.azure.eventhubs.processor
-    - name: Microsoft.ServiceBus.Messaging
-      href: /dotnet/api/microsoft.servicebus.messaging
-    - name: Microsoft.ServiceBus.Messaging.EventProcessorHost
-      href: /dotnet/api/microsoft.servicebus.messaging.eventprocessorhost
-    - name: Microsoft.Azure.Management.EventHub
+    - name: Client library
+      items:
+      - name: Migrate from Microsoft.Azure.Event Hubs to Azure.Messaging.EventHubs
+        href: https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/eventhub/Azure.Messaging.EventHubs/MIGRATIONGUIDE.md    
+      - name: Azure.Messaging.EventHubs (latest)
+        href: /dotnet/api/azure.messaging.eventhubs?view=azure-dotnet-preview
+      - name: Microsoft.Azure.EventHubs (legacy)
+        href: /dotnet/api/microsoft.azure.eventhubs
+      - name: Microsoft.ServiceBus.Messaging (legacy)
+        href: /dotnet/api/microsoft.servicebus.messaging
+    - name: Management library
       href: /dotnet/api/microsoft.azure.management.eventhub
-  - name: Node.js
-    items: 
-    - name: Migrate from version 2 to version 5
-      href: https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/eventhub/event-hubs/migrationguide.md
-    - name: API reference
-      href: /javascript/api/overview/azure/event-hub?view=azure-node-latest
+  - name: Java
+    items:
+    - name: Client library
+      items:
+      - name: azure-eventhubs
+        href: /java/api/overview/azure/eventhubs/client?view=azure-java-stable
+    - name: Management library
+      href: /java/api/com.microsoft.azure.management.eventhub?view=azure-java-stable
   - name: Python
     items:
-    - name: Migrate from version 1 to version 5
+    - name: Migrate from azure-eventhub version 1 to version 5
       href: https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/eventhub/azure-eventhub/migration_guide.md
+    - name: Client library
+      items:
+      - name: azure-eventhub version 5
+        href: /python/api/azure-eventhub/?view=azure-python-preview
+      - name: azure-eventhub version 1
+        href: /python/api/azure-eventhub/?view=azure-python
+    - name: Management library
+      href: /python/api/overview/azure/event-hub?view=azure-python
+  - name: Node.js
+    items: 
+    - name: Migrate from azure/eventhubs version 2 to version 5
+      href: https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/eventhub/event-hubs/migrationguide.md
+    - name: Client library
+      items:
+      - name: azure/eventhubs version 5
+        href: /javascript/api/@azure/event-hubs/?view=azure-node-preview
+      - name: azure/eventhubs version 2
+        href: /javascript/api/@azure/event-hubs/?view=azure-node-latest
+    - name: Management library
+      href: /javascript/api/@azure/arm-eventhub/?view=azure-node-latest
   - name: REST
     href: /rest/api/eventhub
   - name: Resource Manager template