Skip to content

Commit 2adb64b

Browse files
committed
Fix redirects
1 parent 538806f commit 2adb64b

File tree

8 files changed

+64
-9
lines changed

8 files changed

+64
-9
lines changed

articles/azure-maps/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -500,7 +500,7 @@ items:
500500
- name: Azure Maps code samples
501501
href: https://samples.azuremaps.com/
502502
- name: Support and help options
503-
href: ../iot-fundamentals/iot-support-help.md?toc=/azure/azure-maps/toc.json&bc=/azure/azure-maps/breadcrumb/toc.json
503+
href: ../iot/iot-support-help.md?toc=/azure/azure-maps/toc.json&bc=/azure/azure-maps/breadcrumb/toc.json
504504
- name: Azure Maps QPS Rate Limits
505505
href: azure-maps-qps-rate-limits.md
506506
- name: Azure IoT services

articles/event-hubs/event-hubs-federation-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Practically, that means your solution will maintain multiple Event Hubs, often
1818
in different regions and Event Hubs namespaces, and then replicate events between
1919
them. You might also exchange events with sources and targets like [Azure
2020
Service Bus](../service-bus-messaging/service-bus-messaging-overview.md), [Azure
21-
IoT Hub](../iot-fundamentals/iot-introduction.md), or [Apache
21+
IoT Hub](../iot/iot-introduction.md), or [Apache
2222
Kafka](https://kafka.apache.org).
2323

2424
Maintaining multiple active Event Hubs in different regions also allows clients

articles/iot-develop/.openpublishing.redirection.iot-develop.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -423,7 +423,7 @@
423423
{
424424
"source_path_from_root": "/articles/iot-pnp/howto-use-iot-explorer.md",
425425
"redirect_url": "/azure/iot/howto-use-iot-explorer",
426-
"redirect_document_id": true
426+
"redirect_document_id": false
427427
},
428428
{
429429
"source_path_from_root": "/articles/iot-pnp/overview-iot-plug-and-play-current-release.md",

articles/iot-hub/.openpublishing.redirection.iot-hub.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@
108108
{
109109
"source_path_from_root": "/articles/iot-hub/iot-hub-security-ground-up.md",
110110
"redirect_url": "/azure/iot/iot-security-architecture",
111-
"redirect_document_id": true
111+
"redirect_document_id": false
112112
},
113113
{
114114
"source_path_from_root": "/articles/iot-hub/iot-hub-arduino-huzzah-esp8266-get-started.md",

articles/iot/.openpublishing.redirection.iot.json

Lines changed: 56 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,67 @@
1212
}, {
1313
"source_path_from_root": "/articles/iot-fundamentals/security-recommendations.md",
1414
"redirect_url": "/azure/iot/iot-security-best-practices",
15-
"redirect_document_id": true
15+
"redirect_document_id": false
1616
},
1717
{
1818
"source_path_from_root": "/articles/iot-fundamentals/iot-security-deployment.md",
1919
"redirect_url": "/azure/iot/iot-security-best-practices",
2020
"redirect_document_id": false
21+
},
22+
{
23+
"source_path_from_root": "/articles/iot-fundamentals/howto-use-iot-explorer.md",
24+
"redirect_url": "/azure/iot/howto-use-iot-explorer",
25+
"redirect_document_id": true
26+
},
27+
{
28+
"source_path_from_root": "/articles/iot-fundamentals/index.yml",
29+
"redirect_url": "/azure/iot/",
30+
"redirect_document_id": true
31+
},
32+
{
33+
"source_path_from_root": "/articles/iot-fundamentals/iot-glossary.md",
34+
"redirect_url": "/azure/iot/iot-glossary",
35+
"redirect_document_id": true
36+
},
37+
{
38+
"source_path_from_root": "/articles/iot-fundamentals/iot-introduction.md",
39+
"redirect_url": "/azure/iot/iot-introduction",
40+
"redirect_document_id": true
41+
},
42+
{
43+
"source_path_from_root": "/articles/iot-fundamentals/iot-phone-app-how-to.md",
44+
"redirect_url": "/azure/iot/iot-phone-app-how-to",
45+
"redirect_document_id": true
46+
},
47+
{
48+
"source_path_from_root": "/articles/iot-fundamentals/iot-sdks.md",
49+
"redirect_url": "/azure/iot/iot-sdks",
50+
"redirect_document_id": true
51+
},
52+
{
53+
"source_path_from_root": "/articles/iot-fundamentals/iot-security-architecture.md",
54+
"redirect_url": "/azure/iot/iot-security-architecture",
55+
"redirect_document_id": true
56+
},
57+
{
58+
"source_path_from_root": "/articles/iot-fundamentals/iot-security-best-practices.md",
59+
"redirect_url": "/azure/iot/iot-security-best-practices",
60+
"redirect_document_id": true
61+
},
62+
{
63+
"source_path_from_root": "/articles/iot-fundamentals/iot-services-and-technologies.md",
64+
"redirect_url": "/azure/iot/iot-services-and-technologies",
65+
"redirect_document_id": true
66+
},
67+
{
68+
"source_path_from_root": "/articles/iot-fundamentals/iot-solution-options.md",
69+
"redirect_url": "/azure/iot/iot-solution-options",
70+
"redirect_document_id": true
71+
},
72+
{
73+
"source_path_from_root": "/articles/iot-fundamentals/iot-support-help.md",
74+
"redirect_url": "/azure/iot/iot-support-help",
75+
"redirect_document_id": true
2176
}
2277
]
2378
}

articles/role-based-access-control/resource-provider-operations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8755,7 +8755,7 @@ Azure service: [IoT Central](../iot-central/index.yml)
87558755

87568756
### Microsoft.IoTSecurity
87578757

8758-
Azure service: [IoT security](../iot-fundamentals/iot-security-architecture.md)
8758+
Azure service: [IoT security](../iot/iot-security-architecture.md)
87598759

87608760
> [!div class="mx-tableFixed"]
87618761
> | Action | Description |

articles/service-bus-messaging/service-bus-federation-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Within namespaces, Azure Service Bus supports [creating topologies of chained qu
1111

1212
Many sophisticated solutions also require messages to be replicated across namespace boundaries in order to implement these and other patterns. Messages may have to flow between namespaces associated with multiple, different application tenants, or across multiple, different Azure regions.
1313

14-
Your solution will maintain multiple Service Bus namespaces in different regions and replicate messages between Queues and Topics, and/or that you will exchange messages with sources and targets like [Azure Event Hubs](../event-hubs/event-hubs-about.md), [Azure IoT Hub](../iot-fundamentals/iot-introduction.md), or [Apache Kafka](https://kafka.apache.org).
14+
Your solution will maintain multiple Service Bus namespaces in different regions and replicate messages between Queues and Topics, and/or that you will exchange messages with sources and targets like [Azure Event Hubs](../event-hubs/event-hubs-about.md), [Azure IoT Hub](../iot/iot-introduction.md), or [Apache Kafka](https://kafka.apache.org).
1515

1616
These scenarios are the focus of this article.
1717

articles/time-series-insights/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -196,7 +196,7 @@
196196
- name: Resources
197197
items:
198198
- name: Support and help options
199-
href: ../iot-fundamentals/iot-support-help.md?toc=/azure/time-series-insights/toc.json&bc=/azure/time-series-insights/breadcrumb/toc.json
199+
href: ../iot/iot-support-help.md?toc=/azure/time-series-insights/toc.json&bc=/azure/time-series-insights/breadcrumb/toc.json
200200
- name: Customer data requests
201201
href: time-series-insights-customer-data-requests.md
202202
- name: Developer resources
@@ -222,7 +222,7 @@
222222
- name: Azure support options
223223
href: https://azure.microsoft.com/support/options/
224224
- name: Azure IoT support and help options
225-
href: ../iot-fundamentals/iot-support-help.md
225+
href: ../iot/iot-support-help.md
226226
- name: Stack Overflow
227227
href: https://stackoverflow.com/questions/tagged/azure-timeseries-insights
228228
- name: MSDN forum

0 commit comments

Comments
 (0)