Merge pull request #88122 from dagiro/master

cats51

Author: v-shils

articles/hdinsight/apache-kafka-spark-structured-streaming-cosmosdb.md

@@ -29,7 +29,7 @@ Spark structured streaming is a stream processing engine built on Spark SQL. It
 
 Apache Kafka on HDInsight does not provide access to the Kafka brokers over the public internet. Anything that talks to Kafka must be in the same Azure virtual network as the nodes in the Kafka cluster. For this example, both the Kafka and Spark clusters are located in an Azure virtual network. The following diagram shows how communication flows between the clusters:
 
-![Diagram of Spark and Kafka clusters in an Azure virtual network](./media/hdinsight-apache-spark-with-kafka/spark-kafka-vnet.png)
+![Diagram of Spark and Kafka clusters in an Azure virtual network](./media/apache-kafka-spark-structured-streaming-cosmosdb/apache-spark-kafka-vnet.png)
 
 > [!NOTE]  
 > The Kafka service is limited to communication within the virtual network. Other services on the cluster, such as SSH and Ambari, can be accessed over the internet. For more information on the public ports available with HDInsight, see [Ports and URIs used by HDInsight](hdinsight-hadoop-port-settings-for-services.md).

articles/hdinsight/connect-on-premises-network.md

@@ -63,7 +63,7 @@ These steps use the [Azure portal](https://portal.azure.com) to create an Azure
 
 2. From the left menu, navigate to **+ Create a resource** > **Compute** > **Ubuntu Server 18.04 LTS**.
 
-    ![Create an Ubuntu virtual machine](./media/connect-on-premises-network/create-ubuntu-vm.png)
+    ![Create an Ubuntu virtual machine](./media/connect-on-premises-network/create-ubuntu-virtual-machine.png)
 
 3. From the __Basics__ tab, enter the following information:  
 
@@ -80,7 +80,7 @@ These steps use the [Azure portal](https://portal.azure.com) to create an Azure
     |Password or SSH public key | The available field is determined by your choice for **Authentication type**.  Enter the appropriate value.|
     |Public inbound ports|Select **Allow selected ports**. Then select **SSH (22)** from the **Select inbound ports** drop-down list.|
 
-    ![Virtual machine basic configuration](./media/connect-on-premises-network/vm-basics.png)
+    ![Virtual machine basic configuration](./media/connect-on-premises-network/virtual-machine-basics.png)
 
     Leave other entries at the default values and then select the **Networking** tab.
 
@@ -105,7 +105,7 @@ Once the virtual machine has been created, you will receive a **Deployment succe
 
 2. Note the values for **PUBLIC IP ADDRESS/DNS NAME LABEL** and **PRIVATE IP ADDRESS** for later use.
 
-   ![Public and private IP addresses](./media/connect-on-premises-network/vm-ip-addresses.png)
+   ![Public and private IP addresses](./media/connect-on-premises-network/virtual-machine-ip-addresses.png)
 
 ### Install and configure Bind (DNS software)
 

articles/hdinsight/domain-joined/apache-domain-joined-configure-using-azure-adds.md

@@ -69,7 +69,7 @@ Once the managed identity is created and given the correct role, the AAD-DS admi
 
 After you enable Azure AD-DS, a local Domain Name Service (DNS) server runs on the AD Virtual Machines (VMs). Configure your Azure AD-DS Virtual Network (VNET) to use these custom DNS servers. To locate the right IP addresses, select **Properties** under the **Manage** category and look at the IP Addresses listed beneath **IP Address on Virtual Network**.
 
-![Locate IP Addresses for Local DNS Servers](./media/apache-domain-joined-configure-using-azure-adds/hdinsight-aadds-dns.png)
+![Locate IP Addresses for Local DNS Servers](./media/apache-domain-joined-configure-using-azure-adds/hdinsight-aadds-dns1.png)
 
 Change the configuration of the DNS servers in the Azure AD-DS VNET to use these custom IPs by selecting **DNS Servers** under the **Settings** category. Then click the radio button next to **Custom**, enter the first IP Address in the text box below, and click **Save**. Add additional IP Addresses using the same steps.