Merge pull request #115302 from JimacoMS3/update-java-telemetry-quickstart

Changes to java telemetry quickstart for  EH client upgrade

Author: Jak-MS

articles/iot-hub/iot-hub-devguide-messages-read-builtin.md

@@ -59,7 +59,7 @@ The SDKs you can use to connect to the built-in Event Hub-compatible endpoint th
 | Language | SDK | Example |
 | -------- | --- | ------ |
 | .NET | https://github.com/Azure/azure-event-hubs-dotnet | [Quickstart](quickstart-send-telemetry-dotnet.md) |
- Java | https://github.com/Azure/azure-event-hubs-java | [Quickstart](quickstart-send-telemetry-java.md) |
+ Java | https://mvnrepository.com/artifact/com.azure/azure-messaging-eventhubs | [Quickstart](quickstart-send-telemetry-java.md) |
 | Node.js | https://www.npmjs.com/package/@azure/event-hubs | [Quickstart](quickstart-send-telemetry-node.md) |
 | Python | https://pypi.org/project/azure-eventhub/ | https://github.com/Azure-Samples/azure-iot-samples-python/tree/master/iot-hub/Quickstarts/read-d2c-messages |
 

articles/iot-hub/media/quickstart-send-telemetry-java/iot-hub-read-device-to-cloud.png

@@ -9,7 +9,7 @@ services: iot-hub
 ms.devlang: java
 ms.topic: quickstart
 ms.custom: [mvc, seo-java-august2019, seo-java-september2019, mqtt]
-ms.date: 06/21/2019
+ms.date: 05/26/2020
 # As a developer new to IoT Hub, I need to see how IoT Hub sends telemetry from a device to an IoT hub and how to read that telemetry data from the hub using a back-end application. 
 ---
 
@@ -125,7 +125,7 @@ The simulated device application connects to a device-specific endpoint on your
 
     The following screenshot shows the output as the simulated device application sends telemetry to your IoT hub:
 
-    ![Output from telemetry sent by the device to your IoT hub](media/quickstart-send-telemetry-java/iot-hub-simulated-device.png)
+    ![Output from telemetry sent by the device to your IoT hub](media/quickstart-send-telemetry-java/simulated-device.png)
 
 ## Read the telemetry from your hub
 
@@ -137,9 +137,9 @@ The back-end application connects to the service-side **Events** endpoint on you
 
     | Variable | Value |
     | -------- | ----------- |
-    | `eventHubsCompatibleEndpoint` | Replace the value of the variable with the Event Hubs-compatible endpoint you made a note of earlier. |
-    | `eventHubsCompatiblePath`     | Replace the value of the variable with the Event Hubs-compatible path you made a note of earlier. |
-    | `iotHubSasKey`                | Replace the value of the variable with the service primary key you made a note of earlier. |
+    | `EVENT_HUBS_COMPATIBLE_ENDPOINT` | Replace the value of the variable with the Event Hubs-compatible endpoint you made a note of earlier. |
+    | `EVENT_HUBS_COMPATIBLE_PATH`     | Replace the value of the variable with the Event Hubs-compatible path you made a note of earlier. |
+    | `IOT_HUB_SAS_KEY`                | Replace the value of the variable with the service primary key you made a note of earlier. |
 
 3. In the local terminal window, run the following commands to install the required libraries and build the back-end application:
 
@@ -155,7 +155,7 @@ The back-end application connects to the service-side **Events** endpoint on you
 
     The following screenshot shows the output as the back-end application receives telemetry sent by the simulated device to the hub:
 
-    ![Output as back-end application receives telemetry sent to your IoT hub](media/quickstart-send-telemetry-java/iot-hub-read-device-to-cloud.png)
+    ![Output as back-end application receives telemetry sent to your IoT hub](media/quickstart-send-telemetry-java/read-device-to-cloud.png)
 
 ## Clean up resources