Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into pauljewell-qs-next-steps

Author: pauljewellmsft

articles/active-directory/hybrid/migrate-from-federation-to-cloud-authentication.md

@@ -10,7 +10,7 @@ ms.date: 08/26/2022
 
 ms.author: jricketts
 author: janicericketts
-manager: amycolannino
+manager: martinco
 
 ms.collection: M365-identity-device-management
 ---

articles/container-registry/container-registry-private-link.md

@@ -19,7 +19,7 @@ This article shows how to configure a private endpoint for your registry using t
 [!INCLUDE [container-registry-scanning-limitation](../../includes/container-registry-scanning-limitation.md)]
 
 > [!NOTE]
-> Starting October 2021, new container registries allow a maximum of 200 private endpoints. Registries created earlier allow a maximum of 10 private endpoints. Use the az acr show-usage command to see the limit for your registry. Please open a support ticket if this limit needs to be increased to 200 private endpoints.
+> Starting from October 2021, new container registries allow a maximum of 200 private endpoints. Registries created earlier allow a maximum of 10 private endpoints. Use the [az acr show-usage](/cli/azure/acr#az-acr-show-usage) command to see the limit for your registry. Please open a support ticket if the maximum limit of private endpoints increases to 200.
 
 ## Prerequisites
 

articles/cosmos-db/nosql/migrate-dotnet-v3.md

@@ -219,7 +219,7 @@ Some settings in `ConnectionPolicy` have been renamed or replaced by `CosmosClie
 |`MediaRequestTimeout`|Removed. Attachments are no longer supported.|
 |`SetCurrentLocation`|`CosmosClientOptions.ApplicationRegion` can be used to achieve the same effect.|
 |`PreferredLocations`|`CosmosClientOptions.ApplicationPreferredRegions` can be used to achieve the same effect.|
-|`UserAgentSuffix`| | `CosmosClientBuilder.ApplicationName` can be used to achieve the same effect.|
+|`UserAgentSuffix`|`CosmosClientBuilder.ApplicationName` can be used to achieve the same effect.|
 
 ### Indexing policy
 

articles/defender-for-cloud/continuous-export.md

@@ -172,7 +172,7 @@ To view the event schemas of the exported data types, visit the [Log Analytics t
 
 ## Export data to an Azure Event hub or Log Analytics workspace in another tenant
 
-You can export data to an Azure Event hub or Log Analytics workspace in a different tenant, without using [Azure Lighthouse](/azure/lighthouse/overview.md). When collecting data into a tenant, you can analyze the data from one central location. 
+You can export data to an Azure Event hub or Log Analytics workspace in a different tenant, without using [Azure Lighthouse](../lighthouse/overview.md). When collecting data into a tenant, you can analyze the data from one central location. 
 
 To export data to an Azure Event hub or Log Analytics workspace in a different tenant:
 

articles/defender-for-cloud/defender-for-databases-enable-cosmos-protections.md

@@ -87,7 +87,7 @@ You can enable Microsoft Defender for Cloud on a specific Azure Cosmos DB accoun
 
 ### [ARM template](#tab/arm-template)
 
-Use an Azure Resource Manager template to deploy an Azure Cosmos DB account with Microsoft Defender for Azure Cosmos DB enabled. For more information, see [Create an Azure Cosmos DB account with Microsoft Defender for Azure Cosmos DB enabled](https://azure.microsoft.com/resources/templates/microsoft-defender-cosmosdb-create-account/).
+Use an Azure Resource Manager template to deploy an Azure Cosmos DB account with Microsoft Defender for Azure Cosmos DB enabled. For more information, see [Create an Azure Cosmos DB account with Microsoft Defender for Azure Cosmos DB enabled](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.documentdb/microsoft-defender-cosmosdb-create-account).
 
 ---
 

articles/iot-central/core/concepts-iot-edge.md

@@ -218,8 +218,6 @@ Downstream devices connect to a module in the gateway that provides IoT Central
 
 The IoT Edge device is provisioned in IoT Central along with the downstream devices connected to the IoT Edge device. Currently, IoT Central doesn't have runtime support for a gateway to provide an identity and to provision downstream devices. If you bring your own identity translation module, IoT Central can support this pattern.
 
-The [Azure IoT Central gateway module for Azure Video Analyzer](https://github.com/iot-for-all/iotc-ava-gateway/blob/main/README.md) on GitHub uses this pattern.
-
 ### Downstream device relationships with a gateway and modules
 
 If the downstream devices connect to an IoT Edge gateway device through the *IoT Edge hub* module, the IoT Edge device is a transparent gateway:

articles/iot-central/core/howto-transform-data.md

@@ -506,7 +506,7 @@ To configure the device bridge to transform the exported device data:
 
 1. Select **Go →** to open the **App Service Editor** page. Make the following changes:
 
-    1. Open the *wwwroot/IoTCIntegration/index.js* file. Replace all the code in this file with the code in [index.js](https://raw.githubusercontent.com/iot-for-all/iot-central-compute/main/Azure_function/index.js).
+    1. Open the *wwwroot/IoTCIntegration/index.js* file. Replace all the code in this file with the code in [index.js](https://raw.githubusercontent.com/Azure/iot-central-compute/main/Azure_function/index.js).
 
     1. In the new *index.js*, update the `openWeatherAppId` variable file with Open Weather API key you obtained previously.
 
@@ -529,7 +529,7 @@ To configure the device bridge to transform the exported device data:
         message.properties.add('computed', true);
         ```
 
-        For reference, you can view a completed example of the [engine.js](https://raw.githubusercontent.com/iot-for-all/iot-central-compute/main/Azure_function/lib/engine.js) file.
+        For reference, you can view a completed example of the [engine.js](https://raw.githubusercontent.com/Azure/iot-central-compute/main/Azure_function/lib/engine.js) file.
 
 1. In the **App Service Editor**, select **Console** in the left navigation. Run the following commands to install the required packages:
 
@@ -554,7 +554,7 @@ To configure the device bridge to transform the exported device data:
 
 This section describes how to set up the Azure IoT Central application.
 
-First, save the [device model](https://raw.githubusercontent.com/iot-for-all/iot-central-compute/main/model.json) file to your local machine.
+First, save the [device model](https://raw.githubusercontent.com/Azure/iot-central-compute/main/model.json) file to your local machine.
 
 To add a device template to your IoT Central application, navigate to your IoT Central application and then:
 
@@ -593,7 +593,7 @@ To run a sample device that tests the scenario:
 1. Clone the GitHub repository that contains the sample code, run the following command:
 
     ```bash
-    git clone https://github.com/iot-for-all/iot-central-compute
+    git clone https://github.com/Azure/iot-central-compute
     ```
 
 1. To connect the sample device to your IoT Central application, edit the connection settings in the *iot-central-compute/device/device.js* file. Replace the scope ID and group SAS key with the values you made a note of previously:

articles/iot-central/core/overview-iot-central-solution-builder.md

@@ -108,7 +108,7 @@ Scenarios that process IoT data outside of IoT Central to extract business value
 
   For example, use the IoT Central continuous data export feature to continuously ingest your IoT data into an Azure Synapse store. Then use Azure Data Factory to bring data from external systems into the Azure Synapse store. Use the Azure Synapse store with Power BI to generate your business reports.
 
-To learn more, see [Transform data for IoT Central](howto-transform-data.md). For a complete, end-to-end sample, see the [IoT Central Compute](https://github.com/iot-for-all/iot-central-compute) GitHub repository.
+To learn more, see [Transform data for IoT Central](howto-transform-data.md). For a complete, end-to-end sample, see the [IoT Central Compute](https://github.com/Azure/iot-central-compute) GitHub repository.
 
 ## Integrate with other services
 
@@ -120,7 +120,7 @@ You can use the data export and rules capabilities in IoT Central to integrate w
 - [Extend Azure IoT Central with custom rules using Stream Analytics, Azure Functions, and SendGrid](howto-create-custom-rules.md)
 - [Extend Azure IoT Central with custom analytics using Azure Databricks](howto-create-custom-analytics.md)
 
-You can use IoT Edge devices connected to your IoT Central application to integrate with [Azure Video Analyzer](../../azure-video-analyzer/video-analyzer-docs/overview.md). To learn more, see the [Azure IoT Central gateway module for Azure Video Analyzer](https://github.com/iot-for-all/iotc-ava-gateway/blob/main/README.md) on GitHub.
+You can use IoT Edge devices connected to your IoT Central application to integrate with [Azure Video Analyzer](../../azure-video-analyzer/video-analyzer-docs/overview.md).
 
 ## Integrate with companion applications
 

articles/iot-hub/iot-hub-devguide-sdks.md

@@ -1,20 +1,20 @@
 ---
 title: Azure IoT Hub SDKs | Microsoft Docs
-description: Links to the Azure IoT Hub SDKs which you can use to build device apps and back-end apps.
+description: Links to the Azure IoT Hub SDKs that you can use to build device apps and back-end apps.
 author: kgremban
 ms.author: kgremban
 ms.service: iot-hub
 services: iot-hub
 ms.topic: conceptual
-ms.date: 06/01/2021
+ms.date: 11/18/2022
 ms.custom: [mqtt, 'Role: IoT Device', 'Role: Cloud Development']
 ---
 
 # Azure IoT Hub SDKs
 
 There are three categories of software development kits (SDKs) for working with IoT Hub:
 
-* [**IoT Hub device SDKs**](#azure-iot-hub-device-sdks) enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can use these SDKs to build device apps that use [Azure IoT Plug and Play](../iot-develop/overview-iot-plug-and-play.md) conventions and models to advertise their capabilities to IoT Plug and Play-enabled applications. You can also use module client to author [modules](../iot-edge/iot-edge-modules.md) for [Azure IoT Edge runtime](../iot-edge/about-iot-edge.md).
+* [**IoT Hub device SDKs**](#azure-iot-hub-device-sdks) enable you to build apps that run on your IoT devices using the device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, jobs, methods, or twin updates from your IoT hub. You can use these SDKs to build device apps that use [Azure IoT Plug and Play](../iot-develop/overview-iot-plug-and-play.md) conventions and models to advertise their capabilities to IoT Plug and Play-enabled applications. You can also use the module client to author [modules](../iot-edge/iot-edge-modules.md) for [Azure IoT Edge runtime](../iot-edge/about-iot-edge.md).
 
 * [**IoT Hub service SDKs**](#azure-iot-hub-service-sdks) enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
 
@@ -39,11 +39,11 @@ The SDKs are available in **multiple languages** providing the flexibility to ch
 | **C** | [packages](https://github.com/Azure/azure-iot-sdk-c/blob/master/readme.md#getting-the-sdk) | [GitHub](https://github.com/Azure/azure-iot-sdk-c) | [Quickstart](../iot-develop/quickstart-send-telemetry-iot-hub.md?pivots=programming-language-ansi-c) | [Samples](https://github.com/Azure/azure-iot-sdk-c/tree/master/iothub_client/samples) | [Reference](https://github.com/Azure/azure-iot-sdk-c/) |
 
 > [!WARNING]
-> The **C SDK** listed above is **not** suitable for embedded applications due to its memory management and threading model. For embedded devices, refer to the [Embedded device SDKs](#embedded-device-sdks).
+> The **C device SDK** listed in the previous table is **not** suitable for embedded applications due to its memory management and threading model. For embedded devices, refer to the [Embedded device SDKs](#embedded-device-sdks).
 
 ### Embedded device SDKs
 
-These SDKs were designed and created to run on devices with limited compute and memory resources and are implemented using the C language.
+These SDKs are designed and created to run on devices with limited compute and memory resources and are implemented using the C language.
 
 The embedded device SDKs are available for **multiple operating systems** providing the flexibility to choose which best suits your team and scenario.
 
@@ -53,7 +53,7 @@ The embedded device SDKs are available for **multiple operating systems** provid
 | **FreeRTOS** | FreeRTOS Middleware | [GitHub](https://github.com/Azure/azure-iot-middleware-freertos) | [Samples](https://github.com/Azure-Samples/iot-middleware-freertos-samples) | [Reference](https://azure.github.io/azure-iot-middleware-freertos) |
 | **Bare Metal** | Azure SDK for Embedded C | [GitHub](https://github.com/Azure/azure-sdk-for-c/tree/master/sdk/docs/iot) | [Samples](https://github.com/Azure/azure-sdk-for-c/blob/master/sdk/samples/iot/README.md) | [Reference](https://azure.github.io/azure-sdk-for-c) |
 
-Learn more about the IoT Hub device SDKS in the [IoT Device Development Documentation](../iot-develop/about-iot-sdks.md).
+Learn more about the IoT Hub device SDKS in the [IoT device development documentation](../iot-develop/about-iot-sdks.md).
 
 ## Azure IoT Hub service SDKs
 
@@ -68,7 +68,7 @@ The Azure IoT service SDKs contain code to facilitate building applications that
 
 ## Azure IoT Hub management SDKs
 
-The Iot Hub management SDKs help you build backend applications that manage the IoT hubs in your Azure subscription.
+The IoT Hub management SDKs help you build backend applications that manage the IoT hubs in your Azure subscription.
 
 | Platform | Package | Code repository | Reference |
 | -----|-----|-----|-----|
@@ -79,7 +79,7 @@ The Iot Hub management SDKs help you build backend applications that manage the
 
 ## SDK and hardware compatibility
 
-For more information about device SDK compatibility with specific hardware devices, see the [Azure Certified for IoT device catalog](https://devicecatalog.azure.com/) or individual repository.
+For more information about device SDK compatibility with specific hardware devices, see the [Azure Certified Device catalog](https://devicecatalog.azure.com/) or individual repository.
 
 [!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-partial.md)]
 
@@ -91,7 +91,7 @@ Azure IoT SDKs are also available for the following services:
 
 * [Device Update for IoT Hub SDKs](../iot-hub-device-update/understand-device-update.md): To help you deploy over-the-air (OTA) updates for IoT devices.
 
-* [IoT Plug and Play SDKs](../iot-develop/libraries-sdks.md): To help you build IoT Plug and Play solutions.
+* [Microsoft SDKs for IoT Plug and Play](../iot-develop/libraries-sdks.md): To help you build IoT Plug and Play solutions.
 
 ## Next steps
 

includes/iot-hub-basic-partial.md

@@ -11,4 +11,4 @@
 ---
 
 >[!NOTE]
->Some of the features mentioned in this article, like cloud-to-device messaging, device twins, and device management, are only available in the standard tier of IoT Hub. For more information about the basic and standard IoT Hub tiers, see [How to choose the right IoT Hub tier](../articles/iot-hub/iot-hub-scaling.md).
+>Some of the features mentioned in this article, like cloud-to-device messaging, device twins, and device management, are only available in the standard tier of IoT Hub. For more information about the basic and standard/free IoT Hub tiers, see [Choose the right IoT Hub tier for your solution](../articles/iot-hub/iot-hub-scaling.md).