Merge pull request #288275 from kgremban/oct11-sfi

ROPC: iot and device-update

Author: prmerger-automator[bot]

articles/iot-hub-device-update/device-update-control-access.md

@@ -52,6 +52,9 @@ To integrate an application or service with Microsoft Entra ID, first [register
 * Mobile or desktop application, add **Mobile and desktop applications** platform with `https://login.microsoftonline.com/common/oauth2/nativeclient` for the Redirect URI.
 * Website with implicit sign-on, add **Web** platform and select **Access tokens (used for implicit flows)**.
 
+>[!NOTE]
+>Microsoft recommends that you use the most secure authentication flow available. Implicit flow authentication requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
+
 ### Configure permissions
 
 Next, add permissions for calling Device Update to your app:

articles/iot/iot-mqtt-connect-to-iot-hub.md

@@ -82,6 +82,8 @@ from azure.iot.device.aio import IoTHubDeviceClient
 device_client = IoTHubDeviceClient.create_from_connection_string(deviceConnectionString, websockets=True)
 ```
 
+[!INCLUDE [iot-authentication-device-connection-string](../../includes/iot-authentication-device-connection-string.md)]
+
 ### Default keep-alive timeout
 
 In order to ensure a client/IoT Hub connection stays alive, both the service and the client regularly send a *keep-alive* ping to each other. The client using IoT SDK sends a keep-alive at the interval defined in the following table: