Updated steps to generate partner info, minor fix

Author: sunasing

articles/industry/agriculture/ingest-historical-telemetry-data-in-azure-farmbeats.md

@@ -32,37 +32,48 @@ Follow these steps:
 > [!NOTE]
 > You must be an administrator to do the following steps.
 
-1. Download the [zip file](https://aka.ms/farmbeatspartnerscriptv2), and extract it to your local drive. There will be one file inside the zip file.
+1. Sign in to https://portal.azure.com/.
 
-2. Sign in to https://portal.azure.com/ and go to **Azure Active Directory** > **App Registrations**.
+2. **If you are on FarmBeats version 1.2.7 or later, skip steps a, b and c, and go to step 3.** You can check FarmBeats version by selecting the **Settings** icon on the top-right corner of the FarmBeats UI.
 
-3. Select the **App Registration** that was created as part of your FarmBeats deployment. It will have the same name as your FarmBeats Datahub.
+      a.  Go to **Azure Active Directory** > **App Registrations**
 
-4. Select **Expose an API** > Select **Add a client application** and enter **04b07795-8ddb-461a-bbee-02f9e1bf7b46** and check **Authorize Scope**. This will give access to the Azure CLI (Cloud Shell) to perform the following steps:
+      b. Select the **App Registration** that was created as part of your FarmBeats deployment. It will have the same name as your FarmBeats datahub.
 
-5. Open Cloud Shell. This option is available on the toolbar in the upper-right corner of the Azure portal.
+      c. Select **Expose an API** > select **Add a client application** and enter **04b07795-8ddb-461a-bbee-02f9e1bf7b46** and check **Authorize Scope**. This will give access to the Azure CLI (Cloud Shell) to perform the below steps:
+
+3. Open Cloud Shell. This option is available on the toolbar in the upper-right corner of the Azure portal.
 
     ![Azure portal toolbar](./media/get-drone-imagery-from-drone-partner/navigation-bar-1.png)
 
-6. Ensure the environment is set to **PowerShell**. By default, it's set to Bash.
+4. Ensure the environment is set to **PowerShell**. By default, it's set to Bash.
 
     ![PowerShell toolbar setting](./media/get-sensor-data-from-sensor-partner/power-shell-new-1.png)
 
-7. Upload the file from step 1 in your Cloud Shell instance.
+5. Go to your home directory.
+
+    ```azurepowershell-interactive 
+    cd  
+    ```
 
-    ![Upload toolbar button](./media/get-sensor-data-from-sensor-partner/power-shell-two-1.png)
+6. Run the following command. This will download a script to your home directory.
 
-8. Go to the directory where the file was uploaded. By default, files get uploaded to the home directory under the username.
+    ```azurepowershell-interactive 
 
-9. Run the following script. The script asks for the Tenant ID, which can be obtained from **Azure Active Directory** > **Overview page**.
+    wget –q https://aka.ms/farmbeatspartnerscriptv3 -O ./generatePartnerCredentials.ps1
 
-    ```azurepowershell-interactive
+    ```
+
+7. Run the following script. The script asks for the Tenant ID, which can be obtained from **Azure Active Directory** > **Overview** page.
+
+    ```azurepowershell-interactive 
 
     ./generatePartnerCredentials.ps1   
 
     ```
 
-10. Follow the onscreen instructions to capture the values for **API Endpoint**, **Tenant ID**, **Client ID**, **Client Secret**, and **EventHub Connection String**.
+8. Follow the onscreen instructions to capture the values for **API Endpoint**, **Tenant ID**, **Client ID**, **Client Secret**, and **EventHub Connection String**.
+
 
 ## Create device or sensor metadata
 
@@ -346,11 +357,11 @@ Convert the historical sensor data format to a canonical format that Azure FarmB
       "sensordata": [
         {
           "timestamp": "< timestamp in ISO 8601 format >",
-          "<sensor measure name (as defined in the Sensor Model)>": "<value>"
+          "<sensor measure name (as defined in the Sensor Model)>": <value>
         },
         {
           "timestamp": "<timestamp in ISO 8601 format>",
-          "<sensor measure name (as defined in the Sensor Model)>": "<values>"
+          "<sensor measure name (as defined in the Sensor Model)>": <value>
         }
       ]
     }
@@ -424,11 +435,11 @@ Here's an example of a telemetry message:
       "sensordata": [
         {
           "timestamp": "< timestamp in ISO 8601 format >",
-          "<sensor measure name (as defined in the Sensor Model)>": "<value>"
+          "<sensor measure name (as defined in the Sensor Model)>": <value>
         },
         {
           "timestamp": "<timestamp in ISO 8601 format>",
-          "<sensor measure name (as defined in the Sensor Model)>": "<value>"
+          "<sensor measure name (as defined in the Sensor Model)>": <value>
         }
       ]
     }