Merge pull request #108089 from craigcaseyMSFT/vcraic0316

fix broken links from CATS report

Author: megvanhuygen

articles/iot-hub/index.yml

@@ -94,4 +94,4 @@ sections:
           - title: Languages
             html: <p><a href="/dotnet/api/microsoft.azure.devices">.NET (Service)</a></p><p><a href="/dotnet/api/microsoft.azure.devices.client">.NET (Devices)</a></p><p><a href="https://docs.microsoft.com/azure/iot-hub/iot-c-sdk-ref/">C (Device SDK)</a></p><p><a href="/java/api/com.microsoft.azure.sdk.iot.service">Java (Service)</a></p><p><a href="/java/api/com.microsoft.azure.sdk.iot.device">Java (Devices)</a></p><p><a href="/javascript/api/azure-iothub/?view=azure-iot-typescript-latest">Node.js (Service)</a></p><p><a href="/javascript/api/azure-iot-device/?view=azure-iot-typescript-latest">Node.js (Devices)</a></p>
           - title: REST
-            html: <p><a href="/rest/api/iothub/device">REST (Device)</a></p><p><a href="/rest/api/iothub/service">REST (Service)</a></p><p><a href="/rest/api/iothub/iothubresource">REST (IoT Hub Resource)</a></p><p><a href="/rest/api/iothub/certificates">REST (Certificates)</a></p>
+            html: <p><a href="/rest/api/iothub/device">REST (Device)</a></p><p><a href="/rest/api/iothub/service/configuration">REST (Service)</a></p><p><a href="/rest/api/iothub/iothubresource">REST (IoT Hub Resource)</a></p><p><a href="/rest/api/iothub/certificates">REST (Certificates)</a></p>

articles/iot-hub/iot-hub-customer-data-requests.md

@@ -31,17 +31,17 @@ If you use the Azure Monitor integration feature of the Azure IoT Hub service to
 
 Tenant administrators can use the IoT devices blade of the Azure IoT Hub extension in the Azure portal to delete a device, which deletes the data associated with that device.
 
-It is also possible to perform delete operations for devices using REST APIs. For more information, see [Service - Delete Device](/rest/api/iothub/service/deletedevice).
+It is also possible to perform delete operations for devices using REST APIs. For more information, see [Service - Delete Device](/rest/api/iothub/service/registrymanager/deletedevice).
 
 ## Exporting customer data
 
 Tenant administrators can utilize copy and paste within the IoT devices pane of the Azure IoT Hub extension in the Azure portal to export data associated with a device.
 
-It is also possible to perform export operations for devices using REST APIs. For more information, see [Service - Get Device](/rest/api/iothub/service/getdevice).
+It is also possible to perform export operations for devices using REST APIs. For more information, see [Service - Get Device](/rest/api/iothub/service/registrymanager/getdevice).
 
 > [!NOTE]
 > When you use Microsoft's enterprise services, Microsoft generates some information, known as system-generated logs. Some Azure IoT Hub system-generated logs are not accessible or exportable by tenant administrators. These logs constitute factual actions conducted within the service and diagnostic data related to individual devices.
 
 ## Links to additional documentation
 
-Full documentation for Azure IoT Hub Service APIs is located at [IoT Hub Service APIs](https://docs.microsoft.com/rest/api/iothub/service).
+Full documentation for Azure IoT Hub Service APIs is located at [IoT Hub Service APIs](https://docs.microsoft.com/rest/api/iothub/service/configuration).

articles/iot-hub/iot-hub-devguide-direct-methods.md

@@ -45,7 +45,7 @@ Now, invoke a direct method from a back-end app.
 
 Direct method invocations on a device are HTTPS calls that are made up of the following items:
 
-* The *request URI* specific to the device along with the [API version](/rest/api/iothub/service/invokedevicemethod):
+* The *request URI* specific to the device along with the [API version](/rest/api/iothub/service/devicemethod/invokedevicemethod):
 
     ```http
     https://fully-qualified-iothubname.azure-devices.net/twins/{deviceId}/methods?api-version=2018-06-30
@@ -173,9 +173,9 @@ The AMQP message arrives on the receive link that represents the method request.
 
 The device creates a sending link to return the method response on address `amqps://{hostname}:5671/devices/{deviceId}/methods/deviceBound`.
 
-The method’s response is returned on the sending link and is structured as follows:
+The method's response is returned on the sending link and is structured as follows:
 
-* The correlation ID property, which contains the request ID passed in the method’s request message.
+* The correlation ID property, which contains the request ID passed in the method's request message.
 
 * An application property named `IoThub-status`, which contains the user supplied method status.
 

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

@@ -222,7 +222,7 @@ You configure [routing rules](iot-hub-devguide-messages-read-custom.md) in your
 SASL PLAIN is a protocol that the AMQP protocol uses to transfer security tokens.
 
 ## Service REST API
-You can use the [Service REST API](https://docs.microsoft.com/rest/api/iothub/service) from the solution back end to manage your devices. The API enables you to retrieve and update [device twin](#device-twin) properties, invoke [direct methods](#direct-method), and schedule [jobs](#job). Typically, you should use one of the higher-level [service SDKs](#azure-iot-service-sdks) as shown in the IoT Hub tutorials.
+You can use the [Service REST API](https://docs.microsoft.com/rest/api/iothub/service/configuration) from the solution back end to manage your devices. The API enables you to retrieve and update [device twin](#device-twin) properties, invoke [direct methods](#direct-method), and schedule [jobs](#job). Typically, you should use one of the higher-level [service SDKs](#azure-iot-service-sdks) as shown in the IoT Hub tutorials.
 
 ## Shared access signature
 Shared Access Signatures (SAS) are an authentication mechanism based on SHA-256 secure hashes or URIs. SAS authentication has two components: a _Shared Access Policy_ and a _Shared Access Signature_ (often called a token). A device uses SAS to authenticate with an IoT hub. [Back-end apps](#back-end-app) also use SAS to authenticate with the service-facing endpoints on an IoT hub. Typically, you include the SAS token in the [connection string](#connection-string) that an app uses to establish a connection to an IoT hub.

articles/iot-hub/iot-hub-devguide-identity-registry.md

@@ -74,7 +74,7 @@ Use asynchronous operations on the [IoT Hub resource provider endpoint](iot-hub-
 
 For more information about the import and export APIs, see [IoT Hub resource provider REST APIs](/rest/api/iothub/iothubresource). To learn more about running import and export jobs, see [Bulk management of IoT Hub device identities](iot-hub-bulk-identity-mgmt.md).
 
-Device identities can also be exported and imported from an IoT Hub via the Service API via either the [REST API](/rest/api/iothub/service/createimportexportjob) or one of the IoT Hub [Service SDKs](/azure/iot-hub/iot-hub-devguide-sdks#azure-iot-hub-service-sdks).
+Device identities can also be exported and imported from an IoT Hub via the Service API via either the [REST API](/rest/api/iothub/service/jobclient/createimportexportjob) or one of the IoT Hub [Service SDKs](/azure/iot-hub/iot-hub-devguide-sdks#azure-iot-hub-service-sdks).
 
 ## Device provisioning
 

articles/iot-hub/iot-hub-devguide-query-language.md

@@ -228,7 +228,7 @@ The query object exposes multiple **Next** values, depending on the deserializat
 ### Limitations
 
 > [!IMPORTANT]
-> Query results can have a few minutes of delay with respect to the latest values in device twins. If querying individual device twins by ID, use the [get twin REST API](https://docs.microsoft.com/rest/api/iothub/service/gettwin). This API always returns the latest values and has higher throttling limits. You can issue the REST API directly or use the equivalent functionality in one of the [Azure IoT Hub Service SDKs](iot-hub-devguide-sdks.md#azure-iot-hub-service-sdks).
+> Query results can have a few minutes of delay with respect to the latest values in device twins. If querying individual device twins by ID, use the [get twin REST API](https://docs.microsoft.com/rest/api/iothub/service/twin/getdevicetwin). This API always returns the latest values and has higher throttling limits. You can issue the REST API directly or use the equivalent functionality in one of the [Azure IoT Hub Service SDKs](iot-hub-devguide-sdks.md#azure-iot-hub-service-sdks).
 
 Currently, comparisons are supported only between primitive types (no objects), for instance `... WHERE properties.desired.config = properties.reported.config` is supported only if those properties have primitive values.
 
@@ -435,7 +435,7 @@ To understand what each symbol in the expressions syntax stands for, refer to th
 | binary_operator | Any binary operator listed in the [Operators](#operators) section. |
 | function_name| Any function listed in the [Functions](#functions) section. |
 | decimal_literal |A float expressed in decimal notation. |
-| hexadecimal_literal |A number expressed by the string ‘0x’ followed by a string of hexadecimal digits. |
+| hexadecimal_literal |A number expressed by the string '0x' followed by a string of hexadecimal digits. |
 | string_literal |String literals are Unicode strings represented by a sequence of zero or more Unicode characters or escape sequences. String literals are enclosed in single quotes or double quotes. Allowed escapes: `\'`, `\"`, `\\`, `\uXXXX` for Unicode characters defined by 4 hexadecimal digits. |
 
 ### Operators
@@ -463,7 +463,7 @@ In routes conditions, the following math functions are supported:
 | ABS(x) | Returns the absolute (positive) value of the specified numeric expression. |
 | EXP(x) | Returns the exponential value of the specified numeric expression (e^x). |
 | POWER(x,y) | Returns the value of the specified expression to the specified power (x^y).|
-| SQUARE(x)	| Returns the square of the specified numeric value. |
+| SQUARE(x)    | Returns the square of the specified numeric value. |
 | CEILING(x) | Returns the smallest integer value greater than, or equal to, the specified numeric expression. |
 | FLOOR(x) | Returns the largest integer less than or equal to the specified numeric expression. |
 | SIGN(x) | Returns the positive (+1), zero (0), or negative (-1) sign of the specified numeric expression.|

articles/iot-hub/iot-hub-scaling.md

@@ -66,37 +66,37 @@ The difference in supported capabilities between the basic and standard tiers of
 
 | API | Basic tier | Free/Standard tier |
 | --- | ---------- | ------------- |
-| [Delete device](https://docs.microsoft.com/rest/api/iothub/service/deletedevice) | Yes | Yes |
-| [Get device](https://docs.microsoft.com/rest/api/iothub/service/getdevice) | Yes | Yes |
-| [Delete module](https://docs.microsoft.com/rest/api/iothub/service/deletemodule) | Yes | Yes |
-| [Get module](https://docs.microsoft.com/rest/api/iothub/service/getmodule) | Yes | Yes |
-| [Get registry statistics](https://docs.microsoft.com/rest/api/iothub/service/getdeviceregistrystatistics) | Yes | Yes |
-| [Get services statistics](https://docs.microsoft.com/rest/api/iothub/service/getservicestatistics) | Yes | Yes |
-| [Create or update device](https://docs.microsoft.com/rest/api/iothub/service/createorupdatedevice) | Yes | Yes |
-| [Create or update module](https://docs.microsoft.com/rest/api/iothub/service/createorupdatemodule) | Yes | Yes |
-| [Query IoT Hub](https://docs.microsoft.com/rest/api/iothub/service/queryiothub) | Yes | Yes |
+| [Delete device](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/deletedevice) | Yes | Yes |
+| [Get device](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/getdevice) | Yes | Yes |
+| [Delete module](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/deletemodule) | Yes | Yes |
+| [Get module](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/getmodule) | Yes | Yes |
+| [Get registry statistics](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/getdevicestatistics) | Yes | Yes |
+| [Get services statistics](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/getservicestatistics) | Yes | Yes |
+| [Create or update device](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/createorupdatedevice) | Yes | Yes |
+| [Create or update module](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/createorupdatemodule) | Yes | Yes |
+| [Query IoT Hub](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/queryiothub) | Yes | Yes |
 | [Create file upload SAS URI](https://docs.microsoft.com/rest/api/iothub/device/createfileuploadsasuri) | Yes | Yes |
 | [Receive device bound notification](https://docs.microsoft.com/rest/api/iothub/device/receivedeviceboundnotification) | Yes | Yes |
 | [Send device event](https://docs.microsoft.com/rest/api/iothub/device/senddeviceevent) | Yes | Yes |
 | Send module event | AMQP and MQTT only | AMQP and MQTT only |
 | [Update file upload status](https://docs.microsoft.com/rest/api/iothub/device/updatefileuploadstatus) | Yes | Yes |
-| [Bulk device operation](https://docs.microsoft.com/rest/api/iothub/service/bulkcreateorupdatedevices) | Yes, except for IoT Edge capabilities | Yes |
-| [Cancel import export job](https://docs.microsoft.com/rest/api/iothub/service/cancelimportexportjob) | Yes | Yes |
-| [Create import export job](https://docs.microsoft.com/rest/api/iothub/service/createimportexportjob) | Yes | Yes |
-| [Get import export job](https://docs.microsoft.com/rest/api/iothub/service/getimportexportjob) | Yes | Yes |
-| [Get import export jobs](https://docs.microsoft.com/rest/api/iothub/service/getimportexportjobs) | Yes | Yes |
-| [Purge command queue](https://docs.microsoft.com/rest/api/iothub/service/purgecommandqueue) |   | Yes |
-| [Get device twin](https://docs.microsoft.com/rest/api/iothub/service/gettwin) |   | Yes |
-| [Get module twin](https://docs.microsoft.com/rest/api/iothub/service/getmoduletwin) |   | Yes |
-| [Invoke device method](https://docs.microsoft.com/rest/api/iothub/service/invokedevicemethod) |   | Yes |
-| [Update device twin](https://docs.microsoft.com/rest/api/iothub/service/updatetwin) |   | Yes |
-| [Update module twin](https://docs.microsoft.com/rest/api/iothub/service/updatemoduletwin) |   | Yes |
+| [Bulk device operation](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/bulkdevicecrud) | Yes, except for IoT Edge capabilities | Yes |
+| [Cancel import export job](https://docs.microsoft.com/rest/api/iothub/service/jobclient/cancelimportexportjob) | Yes | Yes |
+| [Create import export job](https://docs.microsoft.com/rest/api/iothub/service/jobclient/createimportexportjob) | Yes | Yes |
+| [Get import export job](https://docs.microsoft.com/rest/api/iothub/service/jobclient/getimportexportjob) | Yes | Yes |
+| [Get import export jobs](https://docs.microsoft.com/rest/api/iothub/service/jobclient/getimportexportjobs) | Yes | Yes |
+| [Purge command queue](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/purgecommandqueue) |   | Yes |
+| [Get device twin](https://docs.microsoft.com/rest/api/iothub/service/twin/getdevicetwin) |   | Yes |
+| [Get module twin](https://docs.microsoft.com/rest/api/iothub/service/twin/getmoduletwin) |   | Yes |
+| [Invoke device method](https://docs.microsoft.com/rest/api/iothub/service/devicemethod/invokedevicemethod) |   | Yes |
+| [Update device twin](https://docs.microsoft.com/rest/api/iothub/service/twin/updatedevicetwin) |   | Yes |
+| [Update module twin](https://docs.microsoft.com/rest/api/iothub/service/twin/updatemoduletwin) |   | Yes |
 | [Abandon device bound notification](https://docs.microsoft.com/rest/api/iothub/device/abandondeviceboundnotification) |   | Yes |
 | [Complete device bound notification](https://docs.microsoft.com/rest/api/iothub/device/completedeviceboundnotification) |   | Yes |
-| [Cancel job](https://docs.microsoft.com/rest/api/iothub/service/canceljob) |   | Yes |
-| [Create job](https://docs.microsoft.com/rest/api/iothub/service/createjob) |   | Yes |
-| [Get job](https://docs.microsoft.com/rest/api/iothub/service/getjob) |   | Yes |
-| [Query jobs](https://docs.microsoft.com/rest/api/iothub/service/queryjobs) |   | Yes |
+| [Cancel job](https://docs.microsoft.com/rest/api/iothub/service/jobclient/canceljob) |   | Yes |
+| [Create job](https://docs.microsoft.com/rest/api/iothub/service/jobclient/createjob) |   | Yes |
+| [Get job](https://docs.microsoft.com/rest/api/iothub/service/jobclient/getjob) |   | Yes |
+| [Query jobs](https://docs.microsoft.com/rest/api/iothub/service/jobclient/queryjobs) |   | Yes |
 
 ## Message throughput
 

articles/iot-hub/iot-hub-troubleshoot-error-403004-devicemaximumqueuedepthexceeded.md

@@ -31,4 +31,4 @@ The supported pattern for cloud-to-device messages with HTTPS is intermittently
 
 Alternatively, enhance device side logic to complete, reject, or abandon queued messages quickly, shorten the time to live, or consider sending fewer messages. See [C2D message time to live](./iot-hub-devguide-messages-c2d.md#message-expiration-time-to-live).
 
-Lastly, consider using the [Purge Queue API](https://docs.microsoft.com/rest/api/iothub/service/purgecommandqueue) to periodically clean up pending messages before the limit is reached.
+Lastly, consider using the [Purge Queue API](https://docs.microsoft.com/rest/api/iothub/service/registrymanager/purgecommandqueue) to periodically clean up pending messages before the limit is reached.

articles/iot-hub/virtual-network-support.md

@@ -281,7 +281,7 @@ This functionality requires connectivity from IoT Hub to the storage account. To
 
 3. Navigate to the **Firewalls and virtual networks** tab in your storage account and enable **Allow access from selected networks** option. Under the **Exceptions** list, check the box for **Allow trusted Microsoft services to access this storage account**. Click the **Save** button.
 
-You can now use the Azure IoT REST API's for [creating import export jobs](https://docs.microsoft.com/rest/api/iothub/jobclient/getimportexportjobs) for information on how to use the bulk import/export functionality. Note that you will need to provide the `storageAuthenticationType="identityBased"` in your request body and use `inputBlobContainerUri="https://..."` and `outputBlobContainerUri="https://..."` as the input and output URL's of your storage account, respectively.
+You can now use the Azure IoT REST API's for [creating import export jobs](https://docs.microsoft.com/rest/api/iothub/service/jobclient/getimportexportjobs) for information on how to use the bulk import/export functionality. Note that you will need to provide the `storageAuthenticationType="identityBased"` in your request body and use `inputBlobContainerUri="https://..."` and `outputBlobContainerUri="https://..."` as the input and output URL's of your storage account, respectively.
 
 
 Azure IoT Hub SDK's also support this functionality in the service client's registry manager. The following code snippet shows how to initiate an import job or export job in using the C# SDK.