Skip to content

Commit e7f5be8

Browse files
authored
Modified with updated steps to generate creds
1 parent d905508 commit e7f5be8

File tree

1 file changed

+14
-9
lines changed

1 file changed

+14
-9
lines changed

articles/industry/agriculture/get-sensor-data-from-sensor-partner.md

Lines changed: 14 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -35,35 +35,40 @@ After you start the streaming of sensor data, you can begin the process of getti
3535
You can generate the above information by following these steps: (Please note these steps are required to be done on Azure so you will need access to the Azure subscription where FarmBeats is deployed)
3636

3737
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.
38-
2. Sign in to https://portal.azure.com/ and go to Azure Active Directory -> App Registrations
3938

40-
3. Click on the App Registration that was created as part of your FarmBeats deployment. It will have the same name as your FarmBeats data hub.
39+
2. Sign in to https://portal.azure.com/.
4140

42-
4. Click on “Expose an API” -> Click “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.
41+
3. **If you are on FarmBeats version 1.2.7 or later, please skip steps 3a, 3b and 3c, and go to step 4.**. You can check FarmBeats version by clicking on the Settings icon on the top-right side of the FarmBeats UI.
4342

44-
5. Open Cloud Shell. This option is available on the toolbar in the upper-right corner of the Azure portal.
43+
3a. Go to Azure Active Directory -> App Registrations
44+
45+
3b. Click on the App Registration that was created as part of your FarmBeats deployment. It will have the same name as your FarmBeats data hub.
46+
47+
3c. Click on “Expose an API” -> Click “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.
48+
49+
4. Open Cloud Shell. This option is available on the toolbar in the upper-right corner of the Azure portal.
4550

4651
![Azure portal toolbar](./media/get-drone-imagery-from-drone-partner/navigation-bar-1.png)
4752

48-
6. Make sure the environment is set to **PowerShell**. By default, it's set to Bash.
53+
5. Make sure the environment is set to **PowerShell**. By default, it's set to Bash.
4954

5055
![PowerShell toolbar setting](./media/get-sensor-data-from-sensor-partner/power-shell-new-1.png)
5156

52-
7. Upload the file from step 1 in your Cloud Shell instance.
57+
6. Upload the file from step 1 in your Cloud Shell instance.
5358

5459
![Upload toolbar button](./media/get-sensor-data-from-sensor-partner/power-shell-two-1.png)
5560

56-
8. Go to the directory where the file was uploaded. By default, files get uploaded to the home directory under the username.
61+
7. Go to the directory where the file was uploaded. By default, files get uploaded to the home directory under the username.
5762

58-
9. Run the following script. The script asks for the Tenant ID which can be obtained from Azure Active Directory -> Overview page.
63+
8. Run the following script. The script asks for the Tenant ID which can be obtained from Azure Active Directory -> Overview page.
5964

6065
```azurepowershell-interactive 
6166
6267
./generatePartnerCredentials.ps1
6368
6469
```
6570
66-
10. Follow the onscreen instructions to capture the values for **API Endpoint**, **Tenant ID**, **Client ID**, **Client Secret**, and **EventHub Connection String**.
71+
9. Follow the onscreen instructions to capture the values for **API Endpoint**, **Tenant ID**, **Client ID**, **Client Secret**, and **EventHub Connection String**.
6772
6873
### Integrate device data by using the generated credentials
6974

0 commit comments

Comments
 (0)