Skip to content

Commit fa20bcc

Browse files
committed
Minor edits
1 parent f5189ea commit fa20bcc

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/migrate/resources-faq.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@ author: v-ksreedevan
55
ms.author: v-ksreedevan
66
ms.manager: abhemraj
77
ms.topic: conceptual
8-
ms.date: 04/15/2020
8+
ms.date: 09/27/2022
99
---
1010

1111
# Azure Migrate: Common questions
1212

13-
This article answers common questions about Azure Migrate. If you have questions after you read this article, you can post them in the [Azure Migrate forum](https://aka.ms/AzureMigrateForum). You also can review these articles:
13+
This article answers common questions about Azure Migrate. If you've questions after you read this article, you can post them in the [Azure Migrate forum](https://aka.ms/AzureMigrateForum). You also can review these articles:
1414

1515
- Questions about the [Azure Migrate appliance](common-questions-appliance.md)
1616
- Questions about [discovery, assessment, and dependency visualization](common-questions-discovery-assessment.md)
@@ -39,7 +39,7 @@ The Azure Migrate: Server Migration tool uses some back-end Site Recovery functi
3939

4040
## I have a project with the previous classic experience of Azure Migrate. How do I start using the new version?
4141

42-
Classic Azure Migrate is retiring in Feb 2024. After Feb 2024, classic version of Azure Migrate will no longer be supported and the inventory metadata in the classic project will be deleted. You can't upgrade projects or components in the previous version to the new version. You need to [create a new Azure Migrate project](create-manage-projects.md), and [add assessment and migration tools](./create-manage-projects.md) to it. Use the tutorials to understand how to use the assessment and migration tools available. If you had a Log Analytics workspace attached to a classic project, you can attach it to a project of current version after you delete the classic project.
42+
Classic Azure Migrate is retiring in Feb 2024. After Feb 2024, classic version of Azure Migrate will no longer be supported, and the inventory metadata in the classic project will be deleted. You can't upgrade projects or components in the previous version to the new version. You need to [create a new Azure Migrate project](create-manage-projects.md), and [add assessment and migration tools](./create-manage-projects.md) to it. Use the tutorials to understand how to use the assessment and migration tools available. If you had a Log Analytics workspace attached to a classic project, you can attach it to a project of current version after you delete the classic project.
4343

4444
## What's the difference between Azure Migrate: Discovery and assessment and the MAP Toolkit?
4545

@@ -68,16 +68,16 @@ Review the supported geographies for [public](migrate-support-matrix.md#public-c
6868
When you create a project, you select a geography of your choice. The project and related resources are created in one of the regions in the geography, as allocated by the Azure Migrate service.
6969
See the metadata storage locations for each geography [here](https://learn.microsoft.com/en-us/azure/migrate/migrate-support-matrix#public-cloud).
7070

71-
Azure Migrate does not move or store customer data outside of the region allocated, guaranteeing data residency and resiliency in the same geography.
71+
Azure Migrate doesn't move or store customer data outside of the region allocated, guaranteeing data residency and resiliency in the same geography.
7272

7373
## Does Azure Migrate offer Backup and Disaster Recovery?
7474

75-
Azure Migrate is classified as customer managed Disaster Recovery, which means Azure Migrate does not offer to recover data from an alternate region and offer it to customers when the project region is not available.
75+
Azure Migrate is classified as customer managed Disaster Recovery, which means Azure Migrate doesn't offer to recover data from an alternate region and offer it to customers when the project region isn't available.
7676

77-
While using different capabilities, it is recommended that you export the software inventory, dependency analysis, and assessment report for an offline backup.
77+
While using different capabilities, it's recommended that you export the software inventory, dependency analysis, and assessment report for an offline backup.
7878

7979
In the event of a regional failure or outage in the Azure region that your project is created in:
80-
• You may not be able to access your Azure Migrate projects, assessments, and other reports for the duration of the outage. However, you can use the offline copies that you have exported.
80+
• You may not be able to access your Azure Migrate projects, assessments, and other reports for the duration of the outage. However, you can use the offline copies that you've exported.
8181
• Any in-progress replication and/or migration will be paused and you might have to restart it post the outage.
8282

8383
## How do I get started?

0 commit comments

Comments
 (0)