Skip to content

Commit c52be21

Browse files
committed
December freshness (5/11)
1 parent 6cbf917 commit c52be21

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

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

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Azure IoT Hub is a multi-tenant service that exposes its functionality to variou
2929

3030
The following list describes the endpoints:
3131

32-
* **Resource provider**. The IoT Hub resource provider exposes an [Azure Resource Manager](../azure-resource-manager/management/overview.md) interface. This interface enables Azure subscription owners to create and delete IoT hubs, and to update IoT hub properties. IoT Hub properties govern [hub-level security policies](iot-hub-dev-guide-sas.md#access-control-and-permissions), as opposed to device-level access control, and functional options for cloud-to-device and device-to-cloud messaging. The IoT Hub resource provider also enables you to [export device identities](iot-hub-devguide-identity-registry.md#import-and-export-device-identities).
32+
* **Resource provider**. The IoT Hub resource provider exposes an [Azure Resource Manager](../azure-resource-manager/management/overview.md) interface. This interface enables Azure subscription owners to create and delete IoT hubs, and to update IoT hub properties. IoT Hub properties govern [hub-level shared access policies](iot-hub-dev-guide-sas.md#access-control-and-permissions), as opposed to device-level access control, and functional options for cloud-to-device and device-to-cloud messaging. The IoT Hub resource provider also enables you to [export device identities](iot-hub-devguide-identity-registry.md#import-and-export-device-identities).
3333

3434
* **Device identity management**. Each IoT hub exposes a set of HTTPS REST endpoints to manage device identities (create, retrieve, update, and delete). [Device identities](iot-hub-devguide-identity-registry.md) are used for device authentication and access control.
3535

@@ -45,9 +45,9 @@ The following list describes the endpoints:
4545

4646
* *Initiate file uploads*. A device uses this endpoint to receive an Azure Storage SAS URI from IoT Hub to [upload a file](iot-hub-devguide-file-upload.md).
4747

48-
* *Retrieve and update device twin properties*. A device uses this endpoint to access its [device twin](iot-hub-devguide-device-twins.md)'s properties. HTTPS is not supported.
48+
* *Retrieve and update device twin properties*. A device uses this endpoint to access its [device twin](iot-hub-devguide-device-twins.md)'s properties. HTTPS isn't supported.
4949

50-
* *Receive direct method requests*. A device uses this endpoint to listen for [direct method](iot-hub-devguide-direct-methods.md)'s requests. HTTPS is not supported.
50+
* *Receive direct method requests*. A device uses this endpoint to listen for [direct method](iot-hub-devguide-direct-methods.md) requests. HTTPS isn't supported.
5151

5252
[!INCLUDE [iot-hub-include-x509-ca-signed-support-note](../../includes/iot-hub-include-x509-ca-signed-support-note.md)]
5353

@@ -61,15 +61,15 @@ The following list describes the endpoints:
6161

6262
* *Direct method invocation*. This endpoint allows a back-end service to invoke a [direct method](iot-hub-devguide-direct-methods.md) on a device.
6363

64-
The [Azure IoT SDKs](iot-hub-devguide-sdks.md) article describes the various ways to access these endpoints.
64+
The [Azure IoT Hub SDKs](iot-hub-devguide-sdks.md) article describes the various ways to access these endpoints.
6565

6666
All IoT Hub endpoints use the [TLS](https://tools.ietf.org/html/rfc5246) protocol, and no endpoint is ever exposed on unencrypted/unsecured channels.
6767

6868
## Custom endpoints
6969

70-
You can link existing Azure services in your Azure subscriptions to your IoT hub to act as endpoints for message routing. These endpoints act as service endpoints and are used as sinks for message routes. Devices cannot write directly to the additional endpoints. Learn more about [message routing](../iot-hub/iot-hub-devguide-messages-d2c.md).
70+
You can link existing Azure services in your Azure subscriptions to your IoT hub to act as endpoints for message routing. These endpoints act as service endpoints and are used as sinks for message routes. Devices can't write directly to these endpoints. For more information about message routing, see [Use IoT Hub message routing to send device-to-cloud messages to different endpoints](../iot-hub/iot-hub-devguide-messages-d2c.md).
7171

72-
IoT Hub currently supports the following Azure services as additional endpoints:
72+
IoT Hub currently supports the following Azure services as custom endpoints:
7373

7474
* Storage containers
7575
* Event Hubs
@@ -85,15 +85,15 @@ For the limits on the number of endpoints you can add, see [Quotas and throttlin
8585

8686
## Field gateways
8787

88-
In an IoT solution, a *field gateway* sits between your devices and your IoT Hub endpoints. It is typically located close to your devices. Your devices communicate directly with the field gateway by using a protocol supported by the devices. The field gateway connects to an IoT Hub endpoint using a protocol that is supported by IoT Hub. A field gateway might be a dedicated hardware device or a low-power computer running custom gateway software.
88+
In an IoT solution, a *field gateway* sits between your devices and your IoT Hub endpoints. It's typically located close to your devices. Your devices communicate directly with the field gateway by using a protocol supported by the devices. The field gateway connects to an IoT Hub endpoint using a protocol that is supported by IoT Hub. A field gateway might be a dedicated hardware device or a low-power computer running custom gateway software.
8989

9090
You can use [Azure IoT Edge](../iot-edge/index.yml) to implement a field gateway. IoT Edge offers functionality such as multiplexing communications from multiple devices onto the same IoT Hub connection.
9191

9292
## Next steps
9393

9494
Other reference topics in this IoT Hub developer guide include:
9595

96-
* [IoT Hub query language for device twins, jobs, and message routing](iot-hub-devguide-query-language.md)
97-
* [Quotas and throttling](iot-hub-devguide-quotas-throttling.md)
98-
* [IoT Hub MQTT support](iot-hub-mqtt-support.md)
99-
* [Understand your IoT hub IP address](iot-hub-understand-ip-address.md)
96+
* [IoT Hub query language for device and module twins, jobs, and message routing](iot-hub-devguide-query-language.md)
97+
* [IoT Hub quotas and throttling](iot-hub-devguide-quotas-throttling.md)
98+
* [Communicate with your IoT hub using the MQTT protocol](iot-hub-mqtt-support.md)
99+
* [IoT Hub IP addresses](iot-hub-understand-ip-address.md)

0 commit comments

Comments
 (0)