Skip to content

Commit 799a150

Browse files
Merge pull request #301357 from SoniaLopezBravo/replace-references-iot-hub-ha-dr
Update instances of iot-hub-ha-dr
2 parents ff35ebf + 4ed19bc commit 799a150

8 files changed

+8
-8
lines changed

articles/iot-dps/iot-dps-ha-dr.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.subservice: azure-iot-hub-dps
1313

1414
# IoT Hub Device Provisioning Service high availability and disaster recovery
1515

16-
Device Provisioning Service (DPS) is a helper service for IoT Hub that enables zero-touch device provisioning at-scale. DPS is an important part of your IoT solution. This article describes the High Availability (HA) and Disaster Recovery (DR) capabilities that DPS provides. To learn more about how to achieve HA-DR across your entire IoT solution, see [Disaster recovery and high availability for Azure applications](/azure/architecture/reliability/disaster-recovery). To learn about HA-DR in IoT Hub, see [IoT Hub high availability and disaster recovery](../iot-hub/iot-hub-ha-dr.md).
16+
Device Provisioning Service (DPS) is a helper service for IoT Hub that enables zero-touch device provisioning at-scale. DPS is an important part of your IoT solution. This article describes the High Availability (HA) and Disaster Recovery (DR) capabilities that DPS provides. To learn more about how to achieve HA-DR across your entire IoT solution, see [Disaster recovery and high availability for Azure applications](/azure/architecture/reliability/disaster-recovery). To learn more, see [Reliability in Azure IoT Hub](/azure/reliability/reliability-iot-hub).
1717

1818
## High availability
1919

articles/iot-hub/iot-hub-understand-ip-address.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ You can use these IP address prefixes to control connectivity between IoT Hub an
3131

3232
* For constrained IoT systems without domain name resolution (DNS), IoT Hub IP address ranges are published periodically via service tags before changes take effect. It’s therefore important that you develop processes to regularly retrieve and use the latest service tags. This process can be automated via the [service tags discovery API](../virtual-network/service-tags-overview.md#service-tags-on-premises) or by reviewing [service tags in downloadable JSON format](../virtual-network/service-tags-overview.md#discover-service-tags-by-using-downloadable-json-files).
3333

34-
* Use the _AzureIoTHub.[region name]_ tag to identify IP prefixes used by IoT Hub endpoints in a specific region. To account for datacenter disaster recovery or [regional failover](iot-hub-ha-dr.md), ensure connectivity to IP prefixes of your IoT hub's geo-pair region is also enabled.
34+
* Use the _AzureIoTHub.[region name]_ tag to identify IP prefixes used by IoT Hub endpoints in a specific region. To account for datacenter disaster recovery or regional failover, ensure connectivity to IP prefixes of your IoT hub's geo-pair region is also enabled. For more information, see [Reliability in Azure IoT Hub](/azure/reliability/reliability-iot-hub).
3535

3636
* Setting up firewall rules in IoT Hub might block off connectivity needed to run Azure CLI and PowerShell commands against your IoT hub. To avoid blocking connectivity, you can add ALLOW rules for your clients' IP address prefixes to re-enable CLI or PowerShell clients to communicate with your IoT hub.
3737

articles/iot-hub/migrate-hub-arm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The steps in this article are useful if you want to:
2222
* Export IoT hub state information to have as a backup.
2323
* Increase the number of [partitions](iot-hub-scaling.md#partitions) for an IoT hub.
2424
* Set up a hub for a development, rather than production, environment.
25-
* Enable a custom implementation of multi-hub high availability. For more information, see the [How to achieve cross region HA section of IoT Hub high availability and disaster recovery](iot-hub-ha-dr.md#achieve-cross-region-ha).
25+
* Enable a custom implementation of multi-hub high availability. For more information, see [Reliability in Azure IoT Hub](/azure/reliability/reliability-iot-hub).
2626

2727
To migrate a hub, you need a subscription with administrative access to the original hub. You can put the new hub in a new resource group and region, in the same subscription as the original hub, or even in a new subscription. You just can't use the same name because the hub name has to be globally unique.
2828

articles/iot/concepts-manage-device-reconnections.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ A high number of connection attempts per second can cause a condition similar to
3333

3434
### Hub failure or reconfiguration could disconnect many devices
3535

36-
After an IoT hub experiences a failure, or after you reconfigure service settings on an IoT hub, devices might be disconnected. For proper failover, disconnected devices require reprovisioning. To learn more about failover options, see [IoT Hub high availability and disaster recovery](../iot-hub/iot-hub-ha-dr.md).
36+
After an IoT hub experiences a failure, or after you reconfigure service settings on an IoT hub, devices might be disconnected. For proper failover, disconnected devices require reprovisioning. To learn more about failover options, see [Reliability in Azure IoT Hub](/azure/reliability/reliability-iot-hub).
3737

3838
### Reprovisioning many devices could increase costs
3939

articles/iot/iot-overview-scalability-high-availability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ For information on high availability across availability zones and regions for A
9797

9898
To learn more about the high availability and disaster recovery capabilities of the cloud-based IoT services in your solution, see the following articles:
9999

100-
- [Azure IoT Hub high availability and disaster recovery](../iot-hub/iot-hub-ha-dr.md)
100+
- [Reliability in Azure IoT Hub](/azure/reliability/reliability-iot-hub)
101101
- [IoT Hub Device Provisioning Service high availability and disaster recovery](../iot-dps/iot-dps-ha-dr.md)
102102
- [Azure Digital Twins high availability and disaster recovery](../digital-twins/concepts-high-availability-disaster-recovery.md)
103103
- [Azure IoT Central high availability and disaster recovery](../iot-central/core/concepts-architecture.md#high-availability-and-disaster-recovery)

articles/reliability/availability-zones-service-support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Some Azure services are *nonregional*, which means that you don't deploy the ser
6363
| [Azure Functions](./reliability-functions.md#availability-zone-support) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
6464
| [Azure HDInsight](./reliability-hdinsight.md#availability-zone-support) | | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false":::|
6565
| [Azure HPC Cache](../hpc-cache/hpc-cache-overview.md) | | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: |
66-
| [Azure IoT Hub](../iot-hub/iot-hub-ha-dr.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
66+
| [Azure IoT Hub](reliability-iot-hub.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
6767
| [Azure IoT Hub Device Provisioning Service](../iot-dps/about-iot-dps.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
6868
| [Azure Key Vault](/azure/key-vault/general/disaster-recovery-guidance) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | |
6969
| [Azure Kubernetes Service (AKS)](reliability-aks.md#availability-zone-support) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: |

articles/reliability/overview-reliability-guidance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ This section provides links to reliability guidance for many Azure services. Eac
8383
|Azure Health Data Services: De-identification service (preview)|[Reliability in Azure Health Data Services: De-Identification service](reliability-health-data-services-deidentification.md)||
8484
|Azure Health Data Services: Workspace services (FHIR®, DICOM®, MedTech) | | [Business continuity and disaster recovery considerations](/azure/healthcare-apis/business-continuity-disaster-recovery?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) |
8585
|Azure HDInsight| [Reliability in Azure HDInsight](reliability-hdinsight.md)||
86-
|Azure IoT Hub|| [IoT Hub high availability and disaster recovery](../iot-hub/iot-hub-ha-dr.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json#disable-disaster-recovery) |
86+
|Azure IoT Hub|| [Reliability in Azure IoT Hub](reliability-iot-hub.md). |
8787
|Azure Key Vault|| [Azure Key Vault availability and redundancy](/azure/key-vault/general/disaster-recovery-guidance?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) |
8888
|Azure Kubernetes Service (AKS)| [Reliability in Azure Kubernetes Service (AKS)](reliability-aks.md)||
8989
|Azure Load Balancer| [Reliability in Azure Load Balancer](reliability-load-balancer.md )||

includes/time-series-insights-business-recovery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Make sure you enable the relevant Azure features to provide global, cross-region
3131

3232
Some Azure IoT services also include built-in business disaster recovery features:
3333

34-
- [Azure IoT Hub high-availability disaster recovery](../articles/iot-hub/iot-hub-ha-dr.md), which includes intra-region redundancy
34+
- [Reliability in Azure IoT Hub](/azure/reliability/reliability-iot-hub), which includes intra-region redundancy
3535
- [Azure Event Hubs policies](../articles/event-hubs/event-hubs-geo-dr.md)
3636
- [Azure Storage redundancy](../articles/storage/common/storage-redundancy.md)
3737

0 commit comments

Comments
 (0)