Skip to content

Commit 16bf60e

Browse files
authored
Merge pull request #172804 from dominicbetts/central-monthly-perf
Content performance updates.
2 parents 1a13ac4 + c9ef2f9 commit 16bf60e

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

articles/iot-central/core/howto-migrate.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,11 @@ title: Migrate a V2 Azure IoT Central application to V3 | Microsoft Docs
33
description: Learn how to migrate your V2 Azure IoT Central application to V3
44
author: troyhopwood
55
ms.author: troyhop
6-
ms.date: 01/18/2021
6+
ms.date: 09/17/2021
77
ms.topic: conceptual
88
ms.service: iot-central
99
services: iot-central
10+
ms.custom: contperf-fy22q1
1011

1112
# Administrator
1213
---
@@ -15,6 +16,8 @@ services: iot-central
1516

1617
Currently, when you create a new IoT Central application, it's a V3 application. If you previously created an application, then depending on when you created it, it may be V2. This article describes how to migrate a V2 to a V3 application to be sure you're using the latest IoT Central features.
1718

19+
To learn more, see the [Retirement announcement](/answers/questions/529295/retirement-announcement-upgrade-to-iot-central-v3.html).
20+
1821
To learn how to identify the version of an IoT Central application, see [How do I get information about my application?](howto-faq.yml#how-do-i-get-information-about-my-application-).
1922

2023
The steps to migrate an application from V2 to V3 are:
@@ -25,9 +28,7 @@ The steps to migrate an application from V2 to V3 are:
2528

2629
## Create a new V3 application
2730

28-
Use the migration wizard to create a new V3 application.
29-
30-
IoT Central doesn't support migrating to an existing V3 application. To automatically move existing devices, use the migration wizard to create your V3 application.
31+
IoT Central doesn't let you migrate to an existing V3 application. To move existing devices from a V2 to V3 application, use the migration wizard to create your V3 application.
3132

3233
The migration wizard:
3334

@@ -65,7 +66,7 @@ You must be an administrator to migrate an application to V3.
6566
After your new V3 application is created, make any configuration changes before you move your devices from the V2 application to the V3 application.
6667

6768
> [!TIP]
68-
> Take a moment to [familiarize yourself with V3](overview-iot-central-tour.md#navigate-your-application) as it has some differences from the the previous version.
69+
> Take a moment to [familiarize yourself with V3](overview-iot-central-tour.md#navigate-your-application) as it has some differences from V2.
6970
7071
Here are some recommended configuration steps to consider:
7172

@@ -106,4 +107,4 @@ After you've validated that everything works as expected in your new V3 applicat
106107

107108
## Next steps
108109

109-
Now that you've learned how to migrate your application, the suggested next step is to review the [Azure IoT Central UI](overview-iot-central-tour.md) to see what's changed in V3.
110+
Now that you've learned how to migrate your application, the suggested next step is to review the [Azure IoT Central UI](overview-iot-central-tour.md) to see what's changed in V3.

0 commit comments

Comments
 (0)