Merge pull request #107591 from uhabiba04/master

updating to meet the doc standards and resolving code block issues

Author: PRMerger14

articles/industry/agriculture/manage-users-in-azure-farmbeats.md

@@ -14,14 +14,16 @@ Azure FarmBeats includes user management for people who are part of your Azure A
 
 ## Prerequisites
 
-- An Azure FarmBeats installation is required. For more information, see [Install Azure FarmBeats](install-azure-farmbeats.md).
+- Azure FarmBeats installation is required. For more information, see [Install Azure FarmBeats](install-azure-farmbeats.md).
 - The email IDs of the users you want to add or remove from your Azure FarmBeats instance.
 
 ## Manage Azure FarmBeats users
 
 Azure FarmBeats uses Azure AD for authentication, access control, and roles. You can add users in the Azure AD tenant as users in Azure FarmBeats.
 
 > [!NOTE]
+> If a user is not an Azure AD tenant user, , follow the instructions in the **Add Azure AD users** section to complete the setup.
+
 > If a user you're trying to add as an Azure FarmBeats user isn't present in the Azure AD tenant, complete the setup by following the instructions in the "Add Azure AD users" section.
 
 Azure FarmBeats supports two types of user roles:
@@ -59,7 +61,7 @@ To remove users from the Azure FarmBeats system:
 ## Add Azure AD users
 
 > [!NOTE]
-> Azure FarmBeats users need to exist in the Azure AD tenant before you can assign them to applications and roles. If a user that you want to add to Azure FarmBeats doesn't already exist in the Azure AD tenant, follow the instructions in this section. If the user exists in the Azure AD tenant, you can skip these instructions.
+> Azure FarmBeats users need to exist in the Azure AD tenant before you assign them to applications and roles. If a user doesn't exist in the Azure AD tenant, follow the instructions in this section. Skip the instructions, if a user already exists in the Azure AD tenant.
 
 To add users to Azure AD, do the following:
 

articles/industry/agriculture/sensor-partner-integration-in-azure-farmbeats.md

@@ -11,7 +11,7 @@ ms.author: v-umha
 
 This article provides information about the Azure FarmBeats **Translator** component, which enables sensor partner integration.
 
-Using this component, partners can integrate with FarmBeats using FarmBeats Data hub APIs and send customer device data and telemetry to FarmBeats Data hub. Once the data is available in FarmBeats, it is visualized using the FarmBeats Accelerator and can be used for data fusion and for building machine learning/artificial intelligence models.
+Using this component, partners can integrate with FarmBeats using FarmBeats Datahub APIs and send customer device data and telemetry to FarmBeats Datahub. Once the data is available in FarmBeats, it is visualized using the FarmBeats Accelerator and can be used for data fusion and for building machine learning/artificial intelligence models.
 
 ## Before you start
 
@@ -45,7 +45,7 @@ FarmBeats uses Microsoft Azure Active Directory authentication. Azure App Serv
 
 For more information, see [Azure Active Directory](https://docs.microsoft.com/azure/app-service/overview-authentication-authorization).
 
-FarmBeats Data hub uses bearer authentication, which needs the following credentials:
+FarmBeats Datahub uses bearer authentication, which needs the following credentials:
    - Client ID
    - Client secret
    - Tenant ID
@@ -80,14 +80,14 @@ access_token = token_response.get('accessToken') 
 
 **HTTP request headers**
 
-Here are the most common request headers that need to be specified when you make an API call to FarmBeats Data hub.
+Here are the most common request headers that need to be specified when you make an API call to FarmBeats Datahub.
 
 
 **Header** | **Description and example**
 --- | ---
-Content-Type | The request format (Content-Type: application/<format>). For FarmBeats Data hub APIs, the format is JSON. Content-Type: application/json
+Content-Type | The request format (Content-Type: application/<format>). For FarmBeats Datahub APIs, the format is JSON. Content-Type: application/json
 Authorization | Specifies the access token required to make an API call. Authorization: Bearer <Access-Token>
-Accept | The response format. For FarmBeats Data hub APIs, the format is JSON. Accept: application/json
+Accept | The response format. For FarmBeats Datahub APIs, the format is JSON. Accept: application/json
 
 **API requests**
 
@@ -114,7 +114,7 @@ JSON is a common language-independent data format that provides a simple text re
 
 ## Metadata specifications
 
-FarmBeats Data hub has the following APIs that enable device partners to create and manage device or sensor metadata.
+FarmBeats Datahub has the following APIs that enable device partners to create and manage device or sensor metadata.
 
 - /**DeviceModel**: DeviceModel corresponds to the metadata of the device, such as the manufacturer and the type of device, which is either gateway or node.
 - /**Device**: Device corresponds to a physical device present on the farm.
@@ -225,11 +225,11 @@ The canonical message format is as follows:
       "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>"
         }
       ]
     }
@@ -299,7 +299,7 @@ After customers have purchased and deployed devices or sensors, they can access
 
 ## Unlink FarmBeats
 
-Device partners can enable customers to unlink an existing FarmBeats integration. Unlinking FarmBeats shouldn't delete any device or sensor metadata that was created in FarmBeats Data hub. Unlinking does the following:
+Device partners can enable customers to unlink an existing FarmBeats integration. Unlinking FarmBeats shouldn't delete any device or sensor metadata that was created in FarmBeats Datahub. Unlinking does the following:
 
    - Stops telemetry flow.
    - Deletes and erases the integration credentials on the device partner.

articles/industry/agriculture/troubleshoot-azure-farmbeats.md

@@ -11,7 +11,7 @@ ms.author: v-umha
 
 This article provides solutions to common Azure FarmBeats issues.
 
-For additional help, contact us at [email protected]. Be sure to include the **deployer.log** file in your email.
+For additional help, contact us at [email protected]. Ensure to include the **deployer.log** file in your email.
 
 To download the **deployer.log** file, do the following:
 
@@ -46,7 +46,7 @@ To understand how to download logs, go to the ["Collect logs manually"](#collect
 
 **Corrective action**:
 
-1. Ensure you have done the partner registration correctly - you can check this by going to your datahub swagger, navigate to /Partner API, Do a Get and check if the partner is registered. If not, please follow the [steps here](get-sensor-data-from-sensor-partner.md#enable-device-integration-with-farmbeats) to add partner.
+1. Ensure you have done the partner registration correctly - you can check this by going to your datahub swagger, navigate to /Partner API, Do a Get and check if the partner is registered. If not, follow the [steps here](get-sensor-data-from-sensor-partner.md#enable-device-integration-with-farmbeats) to add partner.
 2. Ensure that you have used the correct Telemetry message format:
 
 ```json
@@ -60,11 +60,11 @@ To understand how to download logs, go to the ["Collect logs manually"](#collect
       "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>"
         }
       ]
     }
@@ -114,14 +114,14 @@ While you're deleting a device, you might encounter one of the following common
 2. Delete the specific device.  
 
     > [!NOTE]
-    > You can't delete a device if sensors are associated with it. For more information about how to delete associated sensors, see the "Delete sensor" section in [Get sensor data from sensor partners](get-sensor-data-from-sensor-partner.md).
+    > You can't delete a device if sensors are associated with it. For more information about how to delete associated sensors, see the **Delete sensor** section in [Get sensor data from sensor partners](get-sensor-data-from-sensor-partner.md).
 
 
 ## Issues with jobs
 
 ### FarmBeats internal error
 
-**Message**: "FarmBeats internal error, see troubleshooting guide for more details."
+**Message**: "FarmBeats internal error, see troubleshooting guide for more details".
 
 **Corrective action**:
 This issue might result from a temporary failure in the data pipeline. Create the job again. If the error persists, add the error message in a post on the FarmBeats forum, or contact [email protected].
@@ -134,13 +134,13 @@ This issue might result from a temporary failure in the data pipeline. Create th
 
 **Message**: "No matching users found."
 
-**Corrective action**: Check the email ID for which you're trying to add a role assignment. The email ID must be an exact match of the ID that's registered for that user in the Active Directory. If the error persists, add the error message in a post on the FarmBeats forum, or contact [email protected].
+**Corrective action**: Check the email ID for which you're trying to add a role assignment. The email ID must be an exact match of the ID, which is registered for that user in the Active Directory. If the error persists, add the error message in a post on the FarmBeats forum, or contact [email protected].
 
 ### Unable to log in to Accelerator
 
-**Message**: "Error: You are not authorized to call the service. Contact the admin for authorization."
+**Message**: "Error: You are not authorized to call the service. Contact the administrator for authorization."
 
-**Corrective action**: Ask the admin to authorize you to access the FarmBeats deployment. This can be done by doing a POST of the RoleAssignment APIs or through the Access Control in the **Settings** pane in Accelerator.  
+**Corrective action**: Ask the administrator to authorize you to access the FarmBeats deployment. This can be done by doing a POST of the RoleAssignment APIs or through the Access Control in the **Settings** pane in Accelerator.  
 
 If you've already been granted access and are facing this error, try again by refreshing the page. If the error persists, add the error message in a post on the FarmBeats forum, or contact [email protected].
 
@@ -159,6 +159,7 @@ If the error persists, add the error message in a post on the FarmBeats forum, o
 **Issue**: FarmBeats Accelerator isn't showing the latest version, even after you've upgraded FarmBeatsDeployment.
 
 **Corrective action**: This error occurs because of service worker persistence in the browser. Do the following:
+
 1. Close all browser tabs that have Accelerator open, and close the browser window.
 2. Start a new instance of the browser, and reload the Accelerator URI. This action loads the new version of Accelerator.
 
@@ -171,6 +172,7 @@ If the error persists, add the error message in a post on the FarmBeats forum, o
 **Corrective action**:
 
 Do one of the following:
+
 - Rerun the installer for upgrading Datahub with the correct username and password.
 - Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check to see whether the job is successful.
 
@@ -194,6 +196,7 @@ This issue can occur if any maintenance activities are being done on the Sentine
 1. If any job or pipeline fails because maintenance is being performed, resubmit the job after some time. 
 
    For information about any planned or unplanned Sentinel maintenance activities, go to the [Copernicus Open Access Hub News](https://scihub.copernicus.eu/news/) site.  
+
 2. Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check to see whether the job is successful.
 
 ### Sentinel: Maximum number of connections reached
@@ -204,6 +207,7 @@ This issue can occur if any maintenance activities are being done on the Sentine
 
 **Corrective action**:
 Try either of the following:
+
 * Create a new Sentinel account, and then rerun the installer to upgrade Datahub by using a new Sentinel username and password.  
 * Rerun the failed job or run a satellite indices job for a date range of 5 to 7 days, and then check to see whether the job is successful.
 
@@ -215,13 +219,15 @@ Try either of the following:
 1. If any job or pipeline fails because maintenance is being performed, resubmit the job after some time. 
 
    For information about any planned or unplanned Sentinel maintenance activities, go to the [Copernicus Open Access Hub News](https://scihub.copernicus.eu/news/) site.  
+
 2. Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check to see whether the job is successful.
 
 ## Collect logs manually
 
 [Install and deploy Azure Storage Explorer]( https://docs.microsoft.com/azure/vs-azure-tools-storage-manage-with-storage-explorer?tabs=windows).
 
 ### Collect Azure Data Factory job logs in Datahub
+
 1. Sign in to the [Azure portal](https://portal.azure.com).
 2. In the **Search** box, search for the FarmBeats Datahub resource group.
 
@@ -297,11 +303,11 @@ Try either of the following:
 
 ### Azure Active Directory (Azure AD)-related issues
 
-**Error message**: "Could not update required settings to Azure AD App d41axx40-xx21-4fbd-8xxf-97xxx9e2xxc0: Insufficient privileges to complete the operation. Ensure that above settings are configured properly for the Azure AD App."
+**Error message**: "Could not update required settings to Azure AD App d41axx40-xx21-4fbd-8xxf-97xxx9e2xxc0: Insufficient privileges to complete the operation. Ensure that the above settings are configured properly for the Azure AD App."
 
 **Meaning**: The Azure AD app registration configuration wasn't completed properly.  
 
-**Corrective action**: Ask the IT admin (the person with tenant read access) to use our [script](https://github.com/Azure-Samples/active-directory-dotnet-webapp-openidconnect/tree/master/AppCreationScripts) for creating the Azure AD app registration. This script automatically takes care of the configuration steps as well.
+**Corrective action**: Ask the IT administrator (the person with tenant read access) to use our [script](https://github.com/Azure-Samples/active-directory-dotnet-webapp-openidconnect/tree/master/AppCreationScripts) for creating the Azure AD app registration. This script automatically takes care of the configuration steps as well.
 
 **Error message**: "Could not create new Active Directory Application '\<application name\>' in this tenant: Another object with the same value for property identifier URIs already exists."