Merge pull request #178977 from ElazarK/api-laws

added Microsoft APIs Terms of Use

Author: PMEds28

articles/defender-for-iot/device-builders/azure-rtos-security-module-api.md

@@ -9,7 +9,9 @@ ms.author: mlottner
 
 # Defender-IoT-micro-agent for Azure RTOS API (preview)
 
-This API is intended for use with the Defender-IoT-micro-agent for Azure RTOS only. For additional resources, see the [Defender-IoT-micro-agent for Azure RTOS GitHub resource](https://github.com/azure-rtos/azure-iot-preview/releases). 
+Defender for IoT APIs are governed by [Microsoft API License and Terms of use](/legal/microsoft-apis/terms-of-use).
+
+This API is intended for use with the Defender-IoT-micro-agent for Azure RTOS only. For additional resources, see the [Defender-IoT-micro-agent for Azure RTOS GitHub resource](https://github.com/azure-rtos/azure-iot-preview/releases).
 
 ## Enable Defender-IoT-micro-agent for Azure RTOS
 
@@ -47,7 +49,6 @@ Threads
 
 **nx_azure_iot_security_module_disable**
 
-
 ### Prototype
 
 ```c
@@ -76,7 +77,6 @@ This routine disables the Azure IoT Defender-IoT-micro-agent subsystem.
 
 Threads
 
-
 ## Next steps
 
 To learn more about how to get started with Azure RTOS Defender-IoT-micro-agent, see the following articles:

articles/defender-for-iot/organizations/references-horizon-api.md

@@ -5,20 +5,22 @@ ms.date: 1/5/2021
 ms.topic: article
 ---
 
-# Horizon API 
+# Horizon API
 
 This guide describes commonly used Horizon methods.
 
-### Getting more information
+## Getting more information
+
+Defender for IoT APIs are governed by [Microsoft API License and Terms of use](/legal/microsoft-apis/terms-of-use).
 
 For more information about working with Horizon and the Defender for IoT platform, see the following information:
 
 - For the Horizon Open Development Environment (ODE) SDK, contact your Defender for IoT representative.
+
 - For support and troubleshooting information, contact <[email protected]>.
 
 - To access the Defender for IoT user guide from the Defender for IoT console, select :::image type="icon" source="media/references-horizon-api/profile.png"::: and then select **Download User Guide**.
 
-
 ## `horizon::protocol::BaseParser`
 
 Abstract for all plugins. This consists of two methods:
@@ -30,7 +32,7 @@ Abstract for all plugins. This consists of two methods:
 
 The first function that is called for your plugin creates an instance of the parser for Horizon to recognize it and register it.
 
-### Parameters 
+### Parameters
 
 None.
 
@@ -40,15 +42,15 @@ shared_ptr to your parser instance.
 
 ## `std::vector<uint64_t> horizon::protocol::BaseParser::processDissectAs(const std::map<std::string, std::vector<std::string>> &) const`
 
-This function will get called for each plugin registered above. 
+This function will get called for each plugin registered above.
 
 In most cases, this will be empty. Throw an exception for Horizon to know something bad happened.
 
-### Parameters 
+### Parameters
 
 - A map containing the structure of dissect_as, as defined in the config.json of another plugin that wants to register over you.
 
-### Return value 
+### Return value
 
 An array of uint64_t, which is the registration processed into a kind of uint64_t. This means in the map, you'll have a list of ports, whose values will be the uin64_t.
 
@@ -65,7 +67,7 @@ Your plugin should be thread safe, as this function may be called from different
 - The SDK control unit responsible for storing the data and creating SDK-related objects, such as ILayer, and fields.
 - A helper for reading the data of the raw packet. It is already set with the byte order you defined in the config.json.
 
-### Return value 
+### Return value
 
 The result of the processing. This can be either *Success*, *Malformed*, or *Sanity*.
 
@@ -77,7 +79,7 @@ Marks the processing as sanitation failure, meaning the packet isn't recognized
 
 Constructor
 
-### Parameters 
+### Parameters
 
 - Defines the error code used by the Horizon for logging, as defined in the config.json.
 
@@ -89,7 +91,7 @@ Malformed result, indicated we already recognized the packet as our protocol, bu
 
 Constructor
 
-### Parameters  
+### Parameters
 
 - Error code, as defined in config.json.
 
@@ -105,7 +107,7 @@ Constructor. Created a basic successful result. This means we don't know the dir
 
 Constructor.
 
-### Parameters 
+### Parameters
 
 - The direction of packet, if identified. Values can be *REQUEST*, or *RESPONSE*.
 
@@ -122,15 +124,15 @@ Constructor.
 
 Constructor.
 
-### Parameters 
+### Parameters
 
--  Warnings. These events won’t be failed, but Horizon will be notified.
+- Warnings. These events won’t be failed, but Horizon will be notified.
 
 ## `HorizonID HORIZON_FIELD(const std::string_view &)`
 
 Converts a string-based reference to a field name (for example, function_code) to HorizonID.
 
-### Parameters 
+### Parameters
 
 - String to convert.
 
@@ -158,7 +160,7 @@ A reference to the manager.
 
 Creates a new numeric field of 64 bits on the layer with the requested ID.
 
-### Parameters 
+### Parameters
 
 - The layer you created earlier.
 - HorizonID created by the **HORIZON_FIELD** macro.
@@ -168,7 +170,7 @@ Creates a new numeric field of 64 bits on the layer with the requested ID.
 
 Creates a new string field of on the layer with the requested ID. The memory will be moved, so be careful. You won't be able to use this value again.
 
-### Parameters  
+### Parameters
 
 - The layer you created earlier.
 - HorizonID created by the **HORIZON_FIELD** macro.

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

@@ -1,12 +1,14 @@
 ---
 title: Work with Defender for IoT APIs
 description: Use an external REST API to access the data discovered by sensors and management consoles and perform actions with that data.
-ms.date: 10/17/2021
+ms.date: 11/08/2021
 ms.topic: reference
 ---
 
 # Defender for IoT sensor and management console APIs
 
+Defender for IoT APIs are governed by [Microsoft API License and Terms of use](/legal/microsoft-apis/terms-of-use).
+
 Use an external REST API to access the data discovered by sensors and management consoles and perform actions with that data.
 
 Connections are secured over SSL.