Merge pull request #172350 from JasonWHowell/disallowed-html-tags

Disallowed html tags

Author: PMEds28

articles/active-directory/saas-apps/fieldglass-tutorial.md

@@ -75,8 +75,8 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
    | Reply URL |
    |-----------|
-   | https://www.fieldglass.net/<company name> |
-   | https://<company name>.fgvms.com/<company name> |
+   | `https://www.fieldglass.net/<company name>` |
+   | `https://<company name>.fgvms.com/<company name>` |
    | 
 
 	> [!NOTE]

articles/databox-online/azure-stack-edge-gpu-connect-powershell-interface.md

@@ -104,7 +104,7 @@ You want to perform this configuration before you configure compute from the Azu
 
     `Set-HcsKubeClusterNetworkInfo -PodSubnet <subnet details> -ServiceSubnet <subnet details>`
 
-    Replace the <subnet details> with the subnet range that you want to use. 
+    Replace the \<subnet details\> with the subnet range that you want to use. 
 
 1. Once you have run this command, you can use the `Get-HcsKubeClusterNetworkInfo` command to verify that the pod and service subnets have changed.
 
@@ -480,9 +480,11 @@ To change the memory or processor limits for Kubernetes worker node, do the foll
     
 1. To change the values of memory and processors for the worker node, run the following command:
 
-    Set-AzureDataBoxEdgeRoleCompute -Name <Name value from the output of Get-AzureDataBoxEdgeRole> -Memory <Value in Bytes> -ProcessorCount <No. of cores>
+   ```powershell
+   Set-AzureDataBoxEdgeRoleCompute -Name <Name value from the output of Get-AzureDataBoxEdgeRole> -Memory <Value in Bytes> -ProcessorCount <No. of cores>
+   ```
 
-    Here is a sample output. 
+   Here is a sample output. 
 
     ```powershell
     [10.100.10.10]: PS>Set-AzureDataBoxEdgeRoleCompute -Name IotRole -MemoryInBytes 32GB -ProcessorCount 16

articles/defender-for-iot/organizations/how-to-deploy-certificates.md

@@ -189,9 +189,9 @@ This section describes how to convert existing certificates files to supported f
 
 |**Description** | **CLI command** |
 |--|--|
-| Convert .crt file to .pem file   | openssl x509 -inform PEM -in <full path>/<pem-file-name>.pem -out <fullpath>/<crt-file-name>.crt  | 
-| Convert .pem file to .crt file   | openssl x509 -inform PEM -in <full path>/<pem-file-name>.pem -out <fullpath>/<crt-file-name>.crt |  
-| Convert a PKCS#12 file (.pfx .p12) containing a private key and certificates to .pem   | openssl pkcs12 -in keyStore.pfx -out keyStore.pem -nodes. You can add -nocerts to only output the private key, or add -nokeys to only output the certificates.  |  
+| Convert .crt file to .pem file   | `openssl x509 -inform PEM -in <full path>/<pem-file-name>.pem -out <fullpath>/<crt-file-name>.crt`  | 
+| Convert .pem file to .crt file   | `openssl x509 -inform PEM -in <full path>/<pem-file-name>.pem -out <fullpath>/<crt-file-name>.crt` |  
+| Convert a PKCS#12 file (.pfx .p12) containing a private key and certificates to .pem   | `openssl pkcs12 -in keyStore.pfx -out keyStore.pem -nodes`. You can add -nocerts to only output the private key, or add -nokeys to only output the certificates.  |  
 
 ## Troubleshooting  
 

articles/defender-for-iot/organizations/references-work-with-defender-for-iot-apis.md

@@ -272,7 +272,7 @@ Array of JSON objects that represent devices.
 
 | Type | APIs | Example |
 |--|--|--|
-| GET | curl -k -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/api/v1/devices | curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:<span>//127<span>.0.0.1/api/v1/devices?authorized=true |
+| GET | `curl -k -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/api/v1/devices | curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https://127.0.0.1/api/v1/devices?authorized=true` |
 
 ### Retrieve device connection information - /api/v1/devices/connections
 
@@ -445,8 +445,8 @@ Array of JSON objects that represent device connections.
 > [!div class="mx-tdBreakAll"]
 > | Type | APIs | Example |
 > |--|--|--|
-> | GET | curl -k -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/api/v1/devices/connections | curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/api/v1/devices/connections |
-> | GET | curl -k -H "Authorization: <AUTH_TOKEN>" 'https://<IP_ADDRESS>/api/v1/devices/<deviceId>/connections?lastActiveInMinutes=&discoveredBefore=&discoveredAfter=' | curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" 'https:/<span>/127.0.0.1/api/v1/devices/2/connections?lastActiveInMinutes=20&discoveredBefore=1594550986000&discoveredAfter=1594550986000' |
+> | GET | `curl -k -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/api/v1/devices/connections` | `curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/api/v1/devices/connections` |
+> | GET | `curl -k -H "Authorization: <AUTH_TOKEN>" 'https://<IP_ADDRESS>/api/v1/devices/<deviceId>/connections?lastActiveInMinutes=&discoveredBefore=&discoveredAfter='` | `curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" 'https:/<span>/127.0.0.1/api/v1/devices/2/connections?lastActiveInMinutes=20&discoveredBefore=1594550986000&discoveredAfter=1594550986000'` |
 
 ### Retrieve information on CVEs - /api/v1/devices/cves
 
@@ -560,8 +560,8 @@ Array of JSON objects that represent CVEs identified on IP addresses.
 
 | Type | APIs | Example |
 |--|--|--|
-| GET | curl -k -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/api/v1/devices/cves | curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/api/v1/devices/cves |
-| GET | curl -k -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/api/v1/devices/<deviceIpAddress>/cves?top= | curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/api/v1/devices/10.10.10.15/cves?top=50 |
+| GET | `curl -k -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/api/v1/devices/cves` | `curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/api/v1/devices/cves` |
+| GET | `curl -k -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/api/v1/devices/<deviceIpAddress>/cves?top=` | `curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/api/v1/devices/10.10.10.15/cves?top=50` |
 
 ### Retrieve alert information - /api/v1/alerts
 
@@ -703,7 +703,7 @@ Note that /api/v2/ is needed for the following information:
 > [!div class="mx-tdBreakAll"]
 > | Type | APIs | Example |
 > |--|--|--|
-> | GET | curl -k -H "Authorization: <AUTH_TOKEN>" 'https://<IP_ADDRESS>/api/v1/alerts?state=&fromTime=&toTime=&type=' | curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" 'https:/<span>/127.0.0.1/api/v1/alerts?state=unhandled&fromTime=1594550986000&toTime=1594550986001&type=disconnections' |
+> | GET | `curl -k -H "Authorization: <AUTH_TOKEN>" 'https://<IP_ADDRESS>/api/v1/alerts?state=&fromTime=&toTime=&type='` | `curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" 'https:/<span>/127.0.0.1/api/v1/alerts?state=unhandled&fromTime=1594550986000&toTime=1594550986001&type=disconnections'` |
 
 ### Retrieve timeline events - /api/v1/events
 
@@ -2079,97 +2079,51 @@ Note that /api/v2/ is needed for the following information:
 
 ```rest
 [
-
     {
-    
         "engine": "Operational",
-        
         "handled": false,
-        
         "title": "Traffic Detected on sensor Interface",
-        
         "additionalInformation": null,
-        
         "sourceDevice": 0,
-        
         "zoneId": 1,
-        
         "siteId": 1,
-        
         "time": 1594808245000,
-        
         "sensorId": 1,
-        
         "message": "The sensor resumed detecting network traffic on ens224.",
-        
         "destinationDevice": 0,
-        
         "id": 1,
-        
         "severity": "Warning"
-    
     },
-    
     {
-    
         "engine": "Anomaly",
-        
         "handled": false,
-        
         "title": "Address Scan Detected",
-        
         "additionalInformation": null,
-        
         "sourceDevice": 4,
-        
         "zoneId": 1,
-        
         "siteId": 1,
-        
         "time": 1594808260000,
-        
         "sensorId": 1,
-        
         "message": "Address scan detected.\nScanning address: 10.10.10.22\nScanned subnet: 10.11.0.0/16\nScanned addresses: 10.11.1.1, 10.11.20.1, 10.11.20.10, 10.11.20.100, 10.11.20.2, 10.11.20.3, 10.11.20.4, 10.11.20.5, 10.11.20.6, 10.11.20.7...\nIt is recommended to notify the security officer of the incident.",
-        
         "destinationDevice": 0,
-        
         "id": 2,
-        
         "severity": "Critical"
-    
     },
-    
     {
-    
         "engine": "Operational",
-        
         "handled": false,
-        
         "title": "Suspicion of Unresponsive MODBUS Device",
-        
         "additionalInformation": null,
-        
         "sourceDevice": 194,
-        
         "zoneId": 1,
-        
         "siteId": 1,
-        
         "time": 1594808285000,
-        
         "sensorId": 1,
-        
         "message": "Outstation device 10.13.10.1 (Protocol Address 53) seems to be unresponsive to MODBUS requests.",
-        
         "destinationDevice": 0,
-        
         "id": 3,
-        
         "severity": "Minor"
-    
     }
-  
 ]
 ```
 
@@ -2178,7 +2132,7 @@ Note that /api/v2/ is needed for the following information:
 > [!div class="mx-tdBreakAll"]
 > | Type | APIs | Example |
 > |--|--|--|
-> | GET | curl -k -H "Authorization: <AUTH_TOKEN>" 'https://<>IP_ADDRESS>/external/v1/alerts?state=&zoneId=&fromTime=&toTime=&siteId=&sensor=' | curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" 'https:/<span>/127.0.0.1/external/v1/alerts?state=unhandled&zoneId=1&fromTime=0&toTime=1594551777000&siteId=1&sensor=1' |
+> | GET | `curl -k -H "Authorization: <AUTH_TOKEN>" 'https://<>IP_ADDRESS>/external/v1/alerts?state=&zoneId=&fromTime=&toTime=&siteId=&sensor='` | `curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" 'https:/<span>/127.0.0.1/external/v1/alerts?state=unhandled&zoneId=1&fromTime=0&toTime=1594551777000&siteId=1&sensor=1'` |
 
 ### QRadar alerts
 
@@ -2281,7 +2235,7 @@ Array of JSON objects that represent devices.
 
 | Type | APIs | Example |
 |--|--|--|
-| PUT | curl -k -X PUT -d '{"action": "<ACTION>"}' -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/external/v1/alerts/<UUID> | curl -k -X PUT -d '{"action": "handle"}' -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/external/v1/alerts/1-1594550943000 |
+| PUT | `curl -k -X PUT -d '{"action": "<ACTION>"}' -H "Authorization: <AUTH_TOKEN>" https://<IP_ADDRESS>/external/v1/alerts/<UUID>` | `curl -k -X PUT -d '{"action": "handle"}' -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/external/v1/alerts/1-1594550943000` |
 
 ### Alert exclusions (maintenance window) - /external/v1/maintenanceWindow
 
@@ -2302,13 +2256,9 @@ The APIs that you define here appear in the on-premises management console's **A
 - **engines**: Defines from which security engine to suppress alerts during the maintenance process:
 
    - ANOMALY
-
    - MALWARE
-
    - OPERATIONAL
-
    - POLICY_VIOLATION
-
    - PROTOCOL_VIOLATION
 
 - **sensorIds**: Defines from which Defender for IoT sensor to suppress alerts during the maintenance process. It's the same ID retrieved from /api/v1/appliances (GET).
@@ -2322,11 +2272,8 @@ The APIs that you define here appear in the on-premises management console's **A
 - **400 (Bad Request)**: Appears in the following cases:
 
    - The **ttl** parameter is not numeric or not positive.
-
    - The **subnets** parameter was defined using a wrong format.
-
    - The **ticketId** parameter is missing.
-
    - The **engine** parameter does not match the existing security engines.
 
 - **404 (Not Found)**: One of the sensors doesn't exist.
@@ -2357,9 +2304,7 @@ This method is useful when you want to set a longer duration than the currently
 - **400 (Bad Request)**: Appears in the following cases:
 
    - The **ttl** parameter is not numeric or not positive.
-
    - The **ticketId** parameter is missing.
-
    - The **ttl** parameter is missing.
 
 - **404 (Not Found)**: The ticket ID is not linked to an open maintenance window.
@@ -2439,10 +2384,10 @@ Array of JSON objects that represent maintenance window operations.
 
 | Type | APIs | Example |
 |--|--|--|
-| POST | curl -k -X POST -d '{"ticketId": "<TICKET_ID>",ttl": <TIME_TO_LIVE>,"engines": [<ENGINE1, ENGINE2...ENGINEn>],"sensorIds": [<SENSOR_ID1, SENSOR_ID2...SENSOR_IDn>],"subnets": [<SUBNET1, SUBNET2....SUBNETn>]}' -H "Authorization: <AUTH_TOKEN>" https:/<span>/127.0.0.1/external/v1/maintenanceWindow | curl -k -X POST -d '{"ticketId": "a5fe99c-d914-4bda-9332-307384fe40bf","ttl": "20","engines": ["ANOMALY"],"sensorIds": ["5","3"],"subnets": ["10.0.0.3"]}' -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/external/v1/maintenanceWindow |
-| PUT | curl -k -X PUT -d '{"ticketId": "<TICKET_ID>",ttl": "<TIME_TO_LIVE>"}' -H "Authorization: <AUTH_TOKEN>" https:/<span>/127.0.0.1/external/v1/maintenanceWindow | curl -k -X PUT -d '{"ticketId": "a5fe99c-d914-4bda-9332-307384fe40bf","ttl": "20"}' -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/external/v1/maintenanceWindow |
-| DELETE | curl -k -X DELETE -d '{"ticketId": "<TICKET_ID>"}' -H "Authorization: <AUTH_TOKEN>" https:/<span>/127.0.0.1/external/v1/maintenanceWindow | curl -k -X DELETE -d '{"ticketId": "a5fe99c-d914-4bda-9332-307384fe40bf"}' -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/external/v1/maintenanceWindow |
-| GET | curl -k -H "Authorization: <AUTH_TOKEN>" 'https://<IP_ADDRESS>/external/v1/maintenanceWindow?fromDate=&toDate=&ticketId=&tokenName=' | curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" 'https:/<span>/127.0.0.1/external/v1/maintenanceWindow?fromDate=2020-01-01&toDate=2020-07-14&ticketId=a5fe99c-d914-4bda-9332-307384fe40bf&tokenName=a' |
+| POST | `curl -k -X POST -d '{"ticketId": "<TICKET_ID>",ttl": <TIME_TO_LIVE>,"engines": [<ENGINE1, ENGINE2...ENGINEn>],"sensorIds": [<SENSOR_ID1, SENSOR_ID2...SENSOR_IDn>],"subnets": [<SUBNET1, SUBNET2....SUBNETn>]}' -H "Authorization: <AUTH_TOKEN>" https:/<span>/127.0.0.1/external/v1/maintenanceWindow` | `curl -k -X POST -d '{"ticketId": "a5fe99c-d914-4bda-9332-307384fe40bf","ttl": "20","engines": ["ANOMALY"],"sensorIds": ["5","3"],"subnets": ["10.0.0.3"]}' -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/external/v1/maintenanceWindow` |
+| PUT | `curl -k -X PUT -d '{"ticketId": "<TICKET_ID>",ttl": "<TIME_TO_LIVE>"}' -H "Authorization: <AUTH_TOKEN>" https:/<span>/127.0.0.1/external/v1/maintenanceWindow` | `curl -k -X PUT -d '{"ticketId": "a5fe99c-d914-4bda-9332-307384fe40bf","ttl": "20"}' -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/external/v1/maintenanceWindow` |
+| DELETE | `curl -k -X DELETE -d '{"ticketId": "<TICKET_ID>"}' -H "Authorization: <AUTH_TOKEN>" https:/<span>/127.0.0.1/external/v1/maintenanceWindow` | `curl -k -X DELETE -d '{"ticketId": "a5fe99c-d914-4bda-9332-307384fe40bf"}' -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" https:/<span>/127.0.0.1/external/v1/maintenanceWindow` |
+| GET | `curl -k -H "Authorization: <AUTH_TOKEN>" 'https://<IP_ADDRESS>/external/v1/maintenanceWindow?fromDate=&toDate=&ticketId=&tokenName='` | `curl -k -H "Authorization: 1234b734a9244d54ab8d40aedddcabcd" 'https:/<span>/127.0.0.1/external/v1/maintenanceWindow?fromDate=2020-01-01&toDate=2020-07-14&ticketId=a5fe99c-d914-4bda-9332-307384fe40bf&tokenName=a'` |
 
 ### Authenticate user credentials - /external/authentication/validation
 
@@ -2505,7 +2450,7 @@ response:
 
 | Type | APIs | Example |
 |--|--|--|
-| POST | curl -k -d '{"username":"<USER_NAME>","password":"PASSWORD"}' 'https://<IP_ADDRESS>/external/authentication/validation' | curl -k -d '{"username":"myUser","password":"1234@abcd"}' 'https:/<span>/127.0.0.1/external/authentication/validation' |
+| POST | `curl -k -d '{"username":"<USER_NAME>","password":"PASSWORD"}' 'https://<IP_ADDRESS>/external/authentication/validation'` | `curl -k -d '{"username":"myUser","password":"1234@abcd"}' 'https:/<span>/127.0.0.1/external/authentication/validation'` |
 
 ### Change password - /external/authentication/set_password
 
@@ -2579,7 +2524,7 @@ response:
 
 | Type | APIs | Example |
 |--|--|--|
-| POST | curl -k -d '{"username": "<USER_NAME>","password": "<CURRENT_PASSWORD>","new_password": "<NEW_PASSWORD>"}' -H 'Content-Type: application/json'  https://<IP_ADDRESS>/external/authentication/set_password | curl -k -d '{"username": "myUser","password": "1234@abcd","new_password": "abcd@1234"}' -H 'Content-Type: application/json'  https:/<span>/127.0.0.1/external/authentication/set_password |
+| POST | `curl -k -d '{"username": "<USER_NAME>","password": "<CURRENT_PASSWORD>","new_password": "<NEW_PASSWORD>"}' -H 'Content-Type: application/json'  https://<IP_ADDRESS>/external/authentication/set_password` | `curl -k -d '{"username": "myUser","password": "1234@abcd","new_password": "abcd@1234"}' -H 'Content-Type: application/json'  https:/<span>/127.0.0.1/external/authentication/set_password` |
 
 ### User password update by system admin - /external/authentication/set_password_by_admin
 
@@ -2660,7 +2605,7 @@ response:
 > [!div class="mx-tdBreakAll"]
 > | Type | APIs | Example |
 > |--|--|--|
-> | POST | curl -k -d '{"admin_username":"<ADMIN_USERNAME>","admin_password":"<ADMIN_PASSWORD>","username": "<USER_NAME>","new_password": "<NEW_PASSWORD>"}' -H 'Content-Type: application/json'  https://<IP_ADDRESS>/external/authentication/set_password_by_admin | curl -k -d '{"admin_user":"adminUser","admin_password": "1234@abcd","username": "myUser","new_password": "abcd@1234"}' -H 'Content-Type: application/json'  https:/<span>/127.0.0.1/external/authentication/set_password_by_admin |
+> | POST | `curl -k -d '{"admin_username":"<ADMIN_USERNAME>","admin_password":"<ADMIN_PASSWORD>","username": "<USER_NAME>","new_password": "<NEW_PASSWORD>"}' -H 'Content-Type: application/json'  https://<IP_ADDRESS>/external/authentication/set_password_by_admin` | `curl -k -d '{"admin_user":"adminUser","admin_password": "1234@abcd","username": "myUser","new_password": "abcd@1234"}' -H 'Content-Type: application/json'  https:/<span>/127.0.0.1/external/authentication/set_password_by_admin` |
 
 ## Next steps
 

articles/industry/agriculture/rest-api-in-azure-farmbeats.md

@@ -65,15 +65,15 @@ Here are the most common request headers that you must specify when you make an
 
 **Header** | **Description and example**
 --- | ---
-Content-Type  | The request format (Content-Type: application/<format>). For Azure 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>
+Content-Type  | The request format (Content-Type: application/\<format\>). For Azure 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 Azure FarmBeats Datahub APIs, the format is JSON. Accept: application/json
 
 ### API requests
 
 To make a REST API request, you combine the HTTP (GET, POST, PUT, or DELETE) method, the URL to the API service, the URI to a resource to query, submit data to, update, or delete, and then add one or more HTTP request headers.
 
-The URL to the API service is your Datahub URL, for example, https://\<yourdatahub-website-name>.azurewebsites.net.
+The URL to the API service is your Datahub URL, for example, `https://<yourdatahub-website-name>.azurewebsites.net`.
 
 Optionally, you can include query parameters on GET calls to filter, limit the size of, and sort the data in the responses.
 
@@ -153,7 +153,7 @@ Azure FarmBeats APIs can be accessed by a user or an app registration in Azure A
     - Go back to **Overview**, and select the link next to **Manage Application in local directory**.
     - Go to **Properties** to capture the **Object ID**.
 
-4. Go to your Datahub Swagger (https://<yourdatahub>.azurewebsites.net/swagger/index.html) and do the following:
+4. Go to your Datahub Swagger (`https://<yourdatahub>.azurewebsites.net/swagger/index.html`) and do the following:
     - Go to the **RoleAssignment API**.
     - Perform a POST to create a **RoleAssignment** object for the **Object ID** you just created.