Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 4a91f74

Browse files
committedSep 28, 2021
Remove mentions of solution accelerators
1 parent f5c7a6b commit 4a91f74

26 files changed

+76
-203
lines changed
 

‎articles/azure-maps/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -396,8 +396,6 @@
396396
href: /microsoft-iot-central/
397397
- name: IoT Edge
398398
href: ../iot-edge/index.yml
399-
- name: IoT solution accelerators
400-
href: ../iot-accelerators/index.yml
401399
- name: IoT Plug and Play
402400
href: ../iot-develop/index.yml
403401
- name: Azure Maps

‎articles/index.yml

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -965,13 +965,6 @@ productDirectory:
965965
- iot
966966
url: iot-hub/index.yml
967967
# Card
968-
- title: Azure IoT solution accelerators
969-
summary: Create fully customizable solutions with templates for common IoT scenarios
970-
imageSrc: ./media/index/iot-solution-accelerators.svg
971-
azureCategories:
972-
- iot
973-
url: iot-accelerators/index.yml
974-
# Card
975968
- title: Azure Maps
976969
summary: Simple and secure location APIs provide geospatial context to data
977970
imageSrc: https://static.docs.com/ui/media/product/azure/maps.svg

‎articles/iot-accelerators/.openpublishing.redirection.iot-accelerators.json

Lines changed: 67 additions & 122 deletions
Large diffs are not rendered by default.

‎articles/iot-central/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -282,8 +282,6 @@
282282
href: ../iot-dps/index.yml
283283
- name: IoT Edge
284284
href: ../iot-edge/index.yml
285-
- name: IoT solution accelerators
286-
href: ../iot-accelerators/index.yml
287285
- name: IoT Plug and Play
288286
href: ../iot-develop/index.yml
289287
- name: Azure Maps

‎articles/iot-dps/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -186,8 +186,6 @@
186186
href: /microsoft-iot-central/
187187
- name: IoT Edge
188188
href: ../iot-edge/index.yml
189-
- name: IoT solution accelerators
190-
href: ../iot-accelerators/index.yml
191189
- name: IoT Plug and Play
192190
href: ../iot-develop/index.yml
193191
- name: Azure Maps

‎articles/iot-edge/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -305,8 +305,6 @@
305305
href: /microsoft-iot-central/
306306
- name: IoT Edge
307307
href: ./index.yml
308-
- name: IoT solution accelerators
309-
href: ../iot-accelerators/index.yml
310308
- name: IoT Plug and Play
311309
href: ../iot-develop/index.yml
312310
- name: Azure Maps

‎articles/iot-edge/about-iot-edge.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ The Azure IoT Edge runtime runs on a large set of IoT devices that enables using
6262

6363
It's difficult to manage the software life cycle for millions of IoT devices that are often different makes and models or geographically scattered. Workloads are created and configured for a particular type of device, deployed to all of your devices, and monitored to catch any misbehaving devices. These activities can’t be done on a per device basis and must be done at scale.
6464

65-
Azure IoT Edge integrates seamlessly with Azure IoT solution accelerators to provide one control plane for your solution’s needs. Cloud services allow you to:
65+
Azure IoT Edge integrates seamlessly with Azure IoT Central to provide one control plane for your solution’s needs. Cloud services allow you to:
6666

6767
* Create and configure a workload to be run on a specific type of device.
6868
* Send a workload to a set of devices.

‎articles/iot-fundamentals/index.yml

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -199,19 +199,6 @@ conceptualContent:
199199
footerLink:
200200
url: ../azure-maps/index.yml
201201
text: See more
202-
# Card
203-
- title: Customize a pre-built IoT solution
204-
links:
205-
- url: ../iot-accelerators/about-iot-accelerators.md
206-
itemType: overview
207-
text: What are Azure IoT solution accelerators?
208-
- url: ../iot-accelerators/quickstart-connected-factory-deploy.md
209-
itemType: quickstart
210-
text: Try a connected factory solution
211-
# footerLink
212-
footerLink:
213-
url: ../iot-accelerators/index.yml
214-
text: See more
215202

216203
tools:
217204
title: Azure IoT SDKs

‎articles/iot-fundamentals/iot-glossary.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -363,10 +363,6 @@ IoT Plug and Play [devices](#iot-plug-and-play-device) are expected to follow a
363363

364364
An IoT Plug and Play device is typically a small-scale, standalone computing device that collects data or controls other devices, and that runs software or firmware that implements a [device model](#device-model). For example, an IoT Plug and Play device might be an environmental monitoring device, or a controller for a smart-agriculture irrigation system. An IoT Plug and Play device might be implemented directly or as an IoT Edge module. You can write a cloud-hosted IoT solution to command, control, and receive data from IoT Plug and Play devices.
365365

366-
### IoT solution accelerators
367-
368-
Azure IoT solution accelerators package together multiple Azure services into solutions. These solutions enable you to get started quickly with end-to-end implementations of common IoT scenarios. For more information, see [What are Azure IoT solution accelerators?](../iot-accelerators/about-iot-accelerators.md)
369-
370366
## J
371367

372368
### Job

‎articles/iot-fundamentals/iot-security-architecture.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,5 @@ ms.author: robinsh
1313
[!INCLUDE [iot-security-architecture](../../includes/iot-security-architecture.md)]
1414

1515
## See also
16-
To learn more about securing a solution created by an IoT solution accelerator, see [Secure your IoT deployment](iot-security-deployment.md).
1716

1817
Read about IoT Hub security in [Control access to IoT Hub](../iot-hub/iot-hub-devguide-security.md) in the IoT Hub developer guide.

‎articles/iot-fundamentals/iot-security-best-practices.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,4 @@ ms.author: robinsh
1414

1515
## See also
1616

17-
To learn more about securing a solution created by an IoT solution accelerator, see [Secure your IoT deployment](iot-security-deployment.md).
18-
1917
Read about IoT Hub security in [Control access to IoT Hub](../iot-hub/iot-hub-devguide-security.md) in the IoT Hub developer guide.

‎articles/iot-fundamentals/iot-security-deployment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: Secure your Azure Internet of Things (IoT) deployment | Microsoft Docs
33
description: This article details how to secure your Azure IoT deployment. It links to implementation level details for configuring and deploying each component.
44
author: dominicbetts
55
manager: timlt
6-
ms.service: iot-accelerators
7-
services: iot-accelerators
6+
ms.service: iot-fundamentals
7+
services: iot-fundamentals
88
ms.topic: conceptual
99
ms.date: 03/08/2019
1010
ms.author: dobett

‎articles/iot-fundamentals/iot-services-and-technologies.md

Lines changed: 3 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -28,38 +28,25 @@ Choose devices from the [Azure Certified for IoT device catalog](https://devicec
2828

2929
As a fully managed application platform, IoT Central has a simple, predictable pricing model.
3030

31-
## Azure IoT solution accelerators
32-
33-
The [Azure IoT solution accelerators](https://www.azureiotsolutions.com) are a collection of customizable enterprise-grade solutions. You can deploy these solutions as they are, or develop a custom IoT solution using the open-source Java or .NET source code.
34-
35-
Azure IoT solution accelerators provide a high level of control over your IoT solution. The solution accelerators include prebuilt solutions for common IoT scenarios that you can deploy to your Azure subscription in minutes. The scenarios include:
36-
37-
* Connected factory
38-
* Device simulation
39-
40-
The open-source code base for all the solution accelerators is available on GitHub. Download the code to customize a solution accelerator to meet your specific IoT requirements.
41-
42-
The solution accelerators use Azure services such as Azure IoT Hub and Azure Storage that you must manage in your Azure subscription.
43-
4431
## Custom solutions
4532

46-
To build an IoT solution from scratch, or extend a solution created using IoT Central or a solution accelerator, use one or more of the following Azure IoT technologies and services:
33+
To build an IoT solution from scratch, or extend a solution created using IoT Central, use one or more of the following Azure IoT technologies and services:
4734

4835
### Devices
4936

5037
Develop your IoT devices using one of the [Azure IoT Starter Kits](https://devicecatalog.azure.com/kits) or choose a device to use from the [Azure Certified for IoT device catalog](https://devicecatalog.azure.com). Implement your embedded code using the open-source [device SDKs](../iot-hub/iot-hub-devguide-sdks.md). The device SDKs support multiple operating systems, such as Linux, Windows, and real-time operating systems. There are SDKs for multiple programming languages, such as [C](https://github.com/Azure/azure-iot-sdk-c), [Node.js](https://github.com/Azure/azure-iot-sdk-node), [Java](https://github.com/Azure/azure-iot-sdk-java), [.NET](https://github.com/Azure/azure-iot-sdk-csharp), and [Python](https://github.com/Azure/azure-iot-sdk-python).
5138

5239
You can further simplify how you create the embedded code for your devices by following the [IoT Plug and Play](../iot-develop/overview-iot-plug-and-play.md) conventions. IoT Plug and Play enables solution developers to integrate devices with their solutions without writing any embedded code. At the core of IoT Plug and Play, is a _device capability model_ schema that describes device capabilities. Use the device capability model to generate your embedded device code and configure a cloud-based solution such as an IoT Central application.
5340

54-
[Azure IoT Edge](../iot-edge/about-iot-edge.md) lets you offload parts of your IoT workload from your Azure cloud services to your devices. IoT Edge can reduce latency in your solution, reduce the amount of data your devices exchange with the cloud, and enable off-line scenarios. You can manage IoT Edge devices from IoT Central and some solution accelerators.
41+
[Azure IoT Edge](../iot-edge/about-iot-edge.md) lets you offload parts of your IoT workload from your Azure cloud services to your devices. IoT Edge can reduce latency in your solution, reduce the amount of data your devices exchange with the cloud, and enable off-line scenarios. You can manage IoT Edge devices from IoT Central.
5542

5643
[Azure Sphere](/azure-sphere/product-overview/what-is-azure-sphere) is a secured, high-level application platform with built-in communication and security features for internet-connected devices. It includes a secured microcontroller unit, a custom Linux-based operating system, and a cloud-based security service that provides continuous, renewable security.
5744

5845
### Cloud connectivity
5946

6047
The [Azure IoT Hub](../iot-hub/about-iot-hub.md) service enables reliable and secure bidirectional communications between millions of IoT devices and a cloud-based solution. [Azure IoT Hub Device Provisioning Service](../iot-dps/about-iot-dps.md) is a helper service for IoT Hub. The service provides zero-touch, just-in-time provisioning of devices to the right IoT hub without requiring human intervention. These capabilities enable customers to provision millions of devices in a secure and scalable manner.
6148

62-
IoT Hub is a core component of the solution accelerators and you can use it to meet IoT implementation challenges such as:
49+
IoT Hub is a core component and you can use it to meet IoT implementation challenges such as:
6350

6451
* High-volume device connectivity and management.
6552
* High-volume telemetry ingestion.

‎articles/iot-fundamentals/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,6 @@
4242
href: /microsoft-iot-central/
4343
- name: IoT Edge
4444
href: ./index.yml
45-
- name: IoT solution accelerators
46-
href: ../iot-accelerators/index.yml
4745
- name: IoT Plug and Play
4846
href: ../iot-develop/index.yml
4947
- name: Azure Maps

‎articles/iot-hub-device-update/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -108,8 +108,6 @@ items:
108108
href: /microsoft-iot-central/
109109
- name: IoT Edge
110110
href: ../iot-edge/index.yml
111-
- name: IoT solution accelerators
112-
href: ../iot-accelerators/index.yml
113111
- name: IoT Plug and Play
114112
href: ../iot-develop/index.yml
115113
- name: Azure Maps

‎articles/iot-hub/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -480,8 +480,6 @@
480480
href: ../iot-edge/index.yml
481481
- name: IoT Plug and Play
482482
href: ../iot-develop/index.yml
483-
- name: IoT solution accelerators
484-
href: ../iot-accelerators/index.yml
485483
- name: Azure Maps
486484
href: ../azure-maps/index.yml
487485
- name: Time Series Insights

‎articles/iot-hub/iot-hub-configuration-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Automatic device management in Azure IoT Hub automates many repetitive and compl
1515

1616
* **IoT hardware manufacturer/integrator:** Manufacturers of IoT hardware, integrators assembling hardware from various manufacturers, or suppliers providing hardware for an IoT deployment manufactured or integrated by other suppliers. Involved in development and integration of firmware, embedded operating systems, and embedded software.
1717

18-
* **IoT solution developer:** The development of an IoT solution is typically done by a solution developer. This developer may be part of an in-house team or a system integrator specializing in this activity. The IoT solution developer can develop various components of the IoT solution from scratch, integrate various standard or open-source components, or customize an [IoT solution accelerator](../iot-accelerators/index.yml).
18+
* **IoT solution developer:** The development of an IoT solution is typically done by a solution developer. This developer may be part of an in-house team or a system integrator specializing in this activity. The IoT solution developer can develop various components of the IoT solution from scratch, integrate various standard, or open-source components.
1919

2020
* **IoT solution operator:** After the IoT solution is deployed, it requires long-term operations, monitoring, upgrades, and maintenance. These tasks can be done by an in-house team that consists of information technology specialists, hardware operations and maintenance teams, and domain specialists who monitor the correct behavior of the overall IoT infrastructure.
2121

‎articles/iot-hub/iot-hub-csharp-csharp-c2d.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -218,6 +218,4 @@ In this section, you modify the **SendCloudToDevice** app to request feedback, a
218218

219219
In this how-to, you learned how to send and receive cloud-to-device messages.
220220

221-
To see examples of complete end-to-end solutions that use IoT Hub, see [Azure IoT Remote Monitoring solution accelerator](/azure/iot-suite/).
222-
223221
To learn more about developing solutions with IoT Hub, see the [IoT Hub developer guide](iot-hub-devguide.md).

‎articles/iot-hub/iot-hub-ios-swift-c2d.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -173,6 +173,4 @@ You are now ready to use the two applications to send and receive cloud-to-devic
173173

174174
In this tutorial, you learned how to send and receive cloud-to-device messages.
175175

176-
To see examples of complete end-to-end solutions that use IoT Hub, see the [Azure IoT Solution Accelerators](https://azure.microsoft.com/documentation/suites/iot-suite/) documentation.
177-
178176
To learn more about developing solutions with IoT Hub, see the [IoT Hub developer guide](iot-hub-devguide.md).

‎articles/iot-hub/iot-hub-java-java-c2d.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -217,6 +217,4 @@ You are now ready to run the applications.
217217

218218
In this tutorial, you learned how to send and receive cloud-to-device messages.
219219

220-
To see examples of complete end-to-end solutions that use IoT Hub, see [Azure IoT Solution Accelerators](https://azure.microsoft.com/documentation/suites/iot-suite/).
221-
222220
To learn more about developing solutions with IoT Hub, see the [IoT Hub developer guide](iot-hub-devguide.md).

‎articles/iot-hub/iot-hub-node-node-c2d.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -196,6 +196,4 @@ You are now ready to run the applications.
196196
197197
In this tutorial, you learned how to send and receive cloud-to-device messages.
198198
199-
To see examples of complete end-to-end solutions that use IoT Hub, see [Azure IoT Remote Monitoring solution accelerator](https://azure.microsoft.com/documentation/suites/iot-suite/).
200-
201199
To learn more about developing solutions with IoT Hub, see the [IoT Hub developer guide](iot-hub-devguide.md).

‎articles/iot-hub/iot-hub-python-python-c2d.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -232,6 +232,4 @@ You are now ready to run the applications.
232232

233233
In this tutorial, you learned how to send and receive cloud-to-device messages.
234234

235-
To see examples of complete end-to-end solutions that use IoT Hub, see [Azure IoT Remote Monitoring solution accelerator](https://azure.microsoft.com/documentation/suites/iot-suite/).
236-
237235
To learn more about developing solutions with IoT Hub, see the [IoT Hub developer guide](iot-hub-devguide.md).

‎articles/iot-hub/iot-hub-query-avro-data.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -165,8 +165,6 @@ In this section, you query Avro data and export it to a CSV file in Azure Blob s
165165
166166
In this tutorial, you learned how to query Avro data to efficiently route messages from Azure IoT Hub to Azure services.
167167
168-
For examples of complete end-to-end solutions that use IoT Hub, see the [Azure IoT Solution Accelerators Documentation](../iot-accelerators/index.yml).
169-
170168
To learn more about developing solutions with IoT Hub, see the [IoT Hub developer guide](iot-hub-devguide.md).
171169
172170
To learn more about message routing in IoT Hub, see [Send and receive messages with IoT Hub](iot-hub-devguide-messaging.md).

‎bread/toc.yml

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -255,9 +255,6 @@
255255
- name: Azure Digital Twins
256256
tocHref: /azure/digital-twins/
257257
topicHref: /azure/digital-twins/
258-
- name: IoT Solution Accelerators
259-
tocHref: /azure/iot-accelerators/
260-
topicHref: /azure/iot-accelerators/
261258
- name: IoT Hub Device Provisioning Service
262259
tocHref: /azure/iot-dps/
263260
topicHref: /azure/iot-dps/
@@ -634,9 +631,6 @@
634631
# - name: IoT Hub Device Provisioning Service
635632
# tocHref: /azure/iot-dps/
636633
# topicHref: /azure/iot-dps/
637-
# - name: IoT solution accelerators
638-
# tocHref: /azure/iot-accelerators/
639-
# topicHref: /azure/iot-accelerators/
640634
# - name: IoT Central
641635
# tocHref: /azure/iot-central/
642636
# topicHref: /azure/iot-central/

‎includes/iot-secure-your-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Securing the Azure IoT deployment can be divided into the following three securi
2424

2525
## Secure device provisioning and authentication
2626

27-
The IoT solution accelerators secure IoT devices using the following two methods:
27+
IoT solutions secure IoT devices using the following two methods:
2828

2929
* By providing a unique identity key (security tokens) for each device, which can be used by the device to communicate with the IoT Hub.
3030

‎includes/iot-security-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This security-in-depth strategy can be developed and executed with active partic
1818

1919
* **IoT hardware manufacturer/integrator**: Typically, these players are the manufacturers of IoT hardware being deployed, integrators assembling hardware from various manufacturers, or suppliers providing hardware for an IoT deployment manufactured or integrated by other suppliers.
2020

21-
* **IoT solution developer**: The development of an IoT solution is typically done by a solution developer. This developer may part of an in-house team or a system integrator (SI) specializing in this activity. The IoT solution developer can develop various components of the IoT solution from scratch, integrate various off-the-shelf or open-source components, or adopt solution accelerators with minor adaptation.
21+
* **IoT solution developer**: The development of an IoT solution is typically done by a solution developer. This developer may part of an in-house team or a system integrator (SI) specializing in this activity. The IoT solution developer can develop various components of the IoT solution from scratch, or integrate various off-the-shelf or open-source components.
2222

2323
* **IoT solution deployer**: After an IoT solution is developed, it needs to be deployed in the field. This process involves deployment of hardware, interconnection of devices, and deployment of solutions in hardware devices or the cloud.
2424

0 commit comments

Comments
 (0)
Please sign in to comment.