Merge pull request #279729 from Saglodha/patch-1

Create event-hubs-emulator-whats-new.md

Author: v-ccolin

articles/event-hubs/TOC.yml

@@ -112,7 +112,11 @@
     - name: Application groups
       href: resource-governance-overview.md  
     - name: Local emulator
-      href: overview-emulator.md
+      items:
+      - name: Overview of Event Hubs emulator
+        href: overview-emulator.md
+      - name: What's new with Event Hubs emulator
+        href: event-hubs-emulator-whats-new.md
     - name: Tiers 
       items: 
       - name: Premium tier

articles/event-hubs/event-hubs-emulator-whats-new.md

@@ -0,0 +1,55 @@
+---
+title: What's new with Event Hubs emulator
+titleSuffix: Azure Event Hubs
+description: View the updates for the latest version and previous versions of the Azure Event Hubs emulator.
+author: Sannidhya
+ms.author: saglodha
+ms.topic: article
+ms.date: 07/01/2024
+---
+
+
+# What's new with Event Hubs emulator
+
+This article provides a detailed overview of the enhancements introduced in the latest version of the Azure Event Hubs emulator, along with information about previous versions.
+
+> [!NOTE]
+> The emulator is intended solely for development and test purpose. Any kind of production use is strictly discouraged. We don't provide any official support for the emulator.
+>
+> Kindly report any problems or suggestions in the emulator's [GitHub installer repository](https://github.com/Azure/azure-event-hubs-emulator-installer/issues).
+
+## Latest version ``1.2.4`` 
+
+> *Released July 1st, 2024*
+
+This release provides enhanced connectivity fixes for Emulator. Details are below:
+ 
+  - When the emulator container and interacting application are running natively on local machine, use following connection string:
+
+  `"Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;"`
+
+  - Applications (Containerized/Non-containerized) on the different machine and same local network can interact with Emulator using the IPv4 address of the machine. Use following connection string:
+
+  `"Endpoint=sb://192.168.y.z;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;"`
+
+  - Application containers on the same bridge network can interact with Emulator using its alias or IP. Following connection string assumes the name of Emulator has default value i.e."eventhubs-emulator":
+
+  `Endpoint=sb://eventhubs-emulator;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;"`
+
+  - Application containers on the different bridge network can interact with Emulator using the "host.docker.internal" as host. Use following connection string:
+
+  `"Endpoint=sb://host.docker.internal;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;"`
+
+- Fixes emulator not accepting connections for initial few seconds after launch.
+- Namespace name and type are now optional parameters in user supplied JSON configuration. 
+
+## Previous releases
+
+### ``1.2.3`` (21st May,2024)
+
+- Initial Launch
+
+## Next steps
+
+- [Learn more about the Azure Event Hubs emulator](overview-emulator.md)
+- [Get started using the Azure Event Hubs emulator for development](test-locally-with-event-hub-emulator.md)