Skip to content

Commit 5c5f119

Browse files
updating articles for Azure Gov
1 parent adb6a18 commit 5c5f119

31 files changed

+359
-254
lines changed

articles/migrate/common-questions-appliance.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure Migrate appliance FAQ
33
description: Get answers to common questions about the Azure Migrate appliance.
44
ms.topic: conceptual
5-
ms.date: 03/09/2020
5+
ms.date: 04/15/2020
66
---
77

88
# Azure Migrate appliance: Common questions
@@ -26,6 +26,15 @@ Here's more information about the Azure Migrate appliance:
2626

2727
[Learn more](migrate-appliance.md) about the appliance.
2828

29+
## How can I deploy the appliance?
30+
31+
The appliance can be deployed as follows:
32+
33+
- Using a template for VMware VMs and Hyper-V VMs (OVA template for VMware or VHD for Hyper-V).
34+
- If you don't want to use a template, or you're in Azure Government, you can deploy the appliance for VMware or Hyper-V using a PowerShell script.
35+
- For physical servers, you always deploy the appliance using a script.
36+
37+
2938
## How does the appliance connect to Azure?
3039

3140
The appliance can connect over the internet or by using Azure ExpressRoute with public/Microsoft peering.
@@ -40,11 +49,8 @@ When you use the downloaded template to create the appliance VM, you can add com
4049

4150
## What network connectivity is required?
4251

43-
See the following articles for information about network connectivity requirements for the Azure Migrate appliance:
4452

45-
- **VMware assessment**: [URL access](migrate-appliance.md#url-access) and [port access](migrate-support-matrix-vmware.md#port-access)
46-
- **VMware agentless migration**: [URL access](migrate-appliance.md#url-access) and [port access](migrate-support-matrix-vmware-migration.md#agentless-ports)
47-
- **Hyper-V assessment**: [URL access](migrate-appliance.md#url-access) and [port access](migrate-support-matrix-hyper-v.md#port-access)
53+
The appliance needs access to Azure URLs. [Review](migrate-appliance.md#url-access) the URL list.
4854

4955
## What data does the appliance collect?
5056

articles/migrate/common-questions-discovery-assessment.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Questions about discovery, assessment, and dependency analysis in Azure Migrate
33
description: Get answers to common questions about discovery, assessment, and dependency analysis in Azure Migrate.
44
ms.topic: conceptual
5-
ms.date: 02/17/2020
5+
ms.date: 04/15/2020
66

77
---
88

@@ -15,10 +15,17 @@ This article answers common questions about discovery, assessment, and dependenc
1515
- Questions about [server migration](common-questions-server-migration.md)
1616
- Get questions answered in the [Azure Migrate forum](https://aka.ms/AzureMigrateForum)
1717

18+
19+
## What geographies are supported for discovery and assessment with Azure Migrate?
20+
21+
Review the supported geographies for [public](migrate-support-matrix.md#supported-geographies-(public-cloud)) and [government clouds](migrate-support-matrix.md#supported-geographies-(azure-government)).
22+
23+
1824
## How many VMs can I discover with an appliance?
1925

2026
You can discover up to 10,000 VMware VMs, up to 5,000 Hyper-V VMs, and up to 250 physical servers by using a single appliance. If you have more machines, read about [scaling a Hyper-V assessment](scale-hyper-v-assessment.md), [scaling a VMware assessment](scale-vmware-assessment.md), or [scaling a physical server assessment](scale-physical-assessment.md).
2127

28+
2229
## The size of my VM changed. Can I run an assessment again?
2330

2431
The Azure Migrate appliance continuously collects information about the on-premises environment. An assessment is a point-in-time snapshot of on-premises VMs. If you change the settings on a VM that you want to assess, use the recalculate option to update the assessment with the latest changes.

articles/migrate/common-questions-server-migration.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,10 @@ This article answers common questions about the Azure Migrate: Server Migration
1414
- Questions about [discovery, assessment, and dependency visualization](common-questions-discovery-assessment.md)
1515
- Get questions answered in the [Azure Migrate forum](https://aka.ms/AzureMigrateForum)
1616

17+
## What geographies are supported for migration with Azure Migrate?
18+
19+
Review the supported geographies for [public](migrate-support-matrix.md#supported-geographies-(public-cloud)) and [government clouds](migrate-support-matrix.md#supported-geographies-(azure-government)).
20+
1721
## How does agentless VMware replication work?
1822

1923
The agentless replication method for VMware uses VMware snapshots and VMware Changed Block Tracking (CBT).

articles/migrate/concepts-assessment-calculation.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ This article provides an overview of assessments in the [Azure Migrate:Server As
1313

1414
An assessment with the Server Assessment tool measures the readiness, and estimates the impact, of migrating on-premises servers to Azure.
1515

16+
> [!NOTE]
17+
> In Azure Government, review the [supported target](migrate-support-matrix.md#supported-geographies-(azure-government)) assessment locations. Note that VM size recommendations in assessments will use the VM series specifically for Government Cloud regions.
18+
1619
## Types of assessments
1720

1821
Assessments you create with Server Assessment are a point-in-time snapshot of data. Server Assessment provides two types of assessments.
@@ -177,7 +180,7 @@ After the machine is marked as ready for Azure, Server Assessment makes sizing r
177180
If you use performance-basing sizing, Server Assessment making sizing recommendations as follows:
178181

179182
- Server Assessment considers the performance history of the machine to identify the VM size and disk type in Azure.
180-
- If servers have been imported using a CSV file, the values you specify are used. This method is especially helpful if you've over-allocated the on-premises machine, utilization is actually low, and you want to right-size the VM in Azure to save costs.
183+
- If servers have been imported using a CSV file, the values you specify are used. This method is especially helpful if you've over-allocated the on-premises machine, utilization is low, and you want to right-size the VM in Azure to save costs.
181184
- If you don't want to use the performance data, reset the sizing criteria to as-is on-premises, as described in the previous section.
182185

183186
#### Calculate storage sizing

articles/migrate/concepts-dependency-visualization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Dependency analysis in Azure Migrate Server Assessment
33
description: Describes how to use dependency analysis for assessment using Azure Migrate Server Assessment.
44
ms.topic: conceptual
5-
ms.date: 03/11/2020
5+
ms.date: 04/15/2020
66
---
77

88
# Dependency analysis

articles/migrate/deploy-appliance-script.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,10 +10,20 @@ ms.date: 03/23/2020
1010

1111
This article describes how to set up the [Azure Migrate appliance](deploy-appliance.md) using a PowerShell installer script.
1212

13-
The script provides:
14-
- An alternative to setting up the appliance using an OVA template, for assessment and agentless migration of VMware VMs.
15-
- An alternative to setting up the appliance using a VHD template, for assessment and migration of Hyper-V VMs.
16-
- For assessment of physical servers (or VMs that you want to migrate as physical servers), the script is the only method for setting up the appliance.
13+
14+
You can deploy the appliance using a couple of methods:
15+
16+
17+
- Using a template for VMware VMs (OVA) or Hyper-V VMs (VHD).
18+
- Using a script. This is the method described in this article. The script provides:
19+
- An alternative to setting up the appliance using an OVA template, for assessment and agentless migration of VMware VMs.
20+
- An alternative to setting up the appliance using a VHD template, for assessment and migration of Hyper-V VMs.
21+
- For assessment of physical servers (or VMs that you want to migrate as physical servers), the script is the only method for setting up the appliance.
22+
- A way to deploy the appliance in Azure Government.
23+
24+
25+
After creating the appliance, you verify that it can connect to Azure Migrate. You then configure the appliance for the first time, and register it with the Azure Migrate project.
26+
1727

1828
## Prerequisites
1929

articles/migrate/how-to-add-tool-first-time.md

Lines changed: 9 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,11 @@
11
---
22
title: Add an assessment/migration tool in Azure Migrate
33
description: Describes how to create an Azure Migrate project and add an assessment/migration tool.
4-
author: rayne-wiselman
5-
ms.service: azure-migrate
6-
ms.topic: article
7-
ms.date: 11/19/2019
8-
ms.author: raynew
4+
ms.topic: how-to
5+
ms.date: 04/16/2020
96
---
107

118

12-
139
# Add an assessment/migration tool for the first time
1410

1511
This article describes how to add an assessment or migration tool to an [Azure Migrate](migrate-overview.md) project for the first time.
@@ -20,7 +16,7 @@ Azure Migrate provides a central hub to track discovery, assessment and migratio
2016
Set up a new Azure Migrate project in an Azure subscription, and add a tool.
2117

2218
- An Azure Migrate project is used to store discovery, assessment, and migration metadata collected from the environment you're assessing or migrating.
23-
- In a project you can track discovered assets, and orchestrate assessment and migration.
19+
- In a project you can track discovered assets, and orchestrate assessment, and migration.
2420

2521
1. In the Azure portal > **All services**, search for **Azure Migrate**.
2622
2. Under **Services**, select **Azure Migrate**.
@@ -34,28 +30,14 @@ Set up a new Azure Migrate project in an Azure subscription, and add a tool.
3430

3531
1. In **Discover, assess and migrate servers**, click **Add tools**.
3632
2. In **Migrate project**, select your Azure subscription, and create a resource group if you don't have one.
37-
3. In **Project Details**, specify the project name, and geography in which you want to create the project.
33+
3. In **Project Details**, specify the project name, and geography in which you want to create the project. Review supported geographies for [public](migrate-support-matrix.md#supported-geographies-(public-cloud)) and [government clouds](migrate-support-matrix.md#supported-geographies-(azure-government)).
3834

3935
![Create an Azure Migrate project](./media/how-to-add-tool-first-time/migrate-project.png)
4036

41-
You can create an Azure Migrate project in any of these geographies.
42-
43-
**Geography** | **Storage location region**
44-
--- | ---
45-
Asia | Southeast Asia or East Asia
46-
Europe | North Europe or West Europe
47-
Japan | Japan East or Japan West
48-
United Kingdom | UK South or UK West
49-
United States | Central US or West US 2
50-
Canada | Canada Central
51-
India | India Central or India South
52-
Australia | Australia SouthEast
53-
54-
The geography specified for the project is only used to store the metadata gathered from on-premises VMs. You can select any target region for the actual migration.
55-
56-
If you want to specify a specific region within a geography for deploying the migrate project and its associated resources (Policy restrictions in your subscription may allow deploying of Azure resources only to a specific Azure region), you can use the below API to create a migrate project. Specify the Subscription ID, Resource group name, Migrate project name along with location(any of the Azure regions mentioned in the table where Azure Migrate is deployed.)
37+
- The geography specified for the project is only used to store the metadata gathered from on-premises VMs. You can select any target region for the actual migration.
38+
- If you need to deploy a project within a specific region in a geography, use the following API to create a project. Specify the subscription ID, resource group name, and project name, along with the location (review the geographies/regions for [public](migrate-support-matrix.md#supported-geographies-(public-cloud)) and [government clouds](migrate-support-matrix.md#supported-geographies-(azure-government)).
5739

58-
`PUT /subscriptions/<subid>/resourceGroups/<rg>/providers/Microsoft.Migrate/MigrateProjects/<mymigrateprojectname>?api-version=2018-09-01-preview "{location: 'centralus', properties: {}}"`
40+
`PUT /subscriptions/<subid>/resourceGroups/<rg>/providers/Microsoft.Migrate/MigrateProjects/<mymigrateprojectname>?api-version=2018-09-01-preview "{location: 'centralus', properties: {}}"`
5941

6042

6143
4. Click **Next**, and add an assessment or migration tool.
@@ -65,9 +47,9 @@ Set up a new Azure Migrate project in an Azure subscription, and add a tool.
6547
6648
5. In **Select assessment tool**, add an assessment tool. If you don't need an assessment tool, select **Skip adding an assessment tool for now** > **Next**.
6749
2. In **Select migration tool**, add a migration tool as required. If you don't need a migration tool right now, select **Skip adding a migration tool for now** > **Next**.
68-
3. In **Review + add tools**, review the settings and click **Add tools**.
50+
3. In **Review + add tools**, review the settings, and click **Add tools**.
6951

70-
After creating the project you can select additional tools for assessment and migration of servers and workloads, databases, and web apps.
52+
After creating the project, you can select additional tools for assessment and migration of servers and workloads, databases, and web apps.
7153

7254
## Create additional projects
7355

articles/migrate/how-to-set-up-appliance-hyper-v.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,16 @@ ms.date: 03/23/2020
88

99
# Set up an appliance for Hyper-V VMs
1010

11-
This article describes how to set up the Azure Migrate appliance for assessment of Hyper-V VMs with the [Azure Migrate:Server Assessment](migrate-services-overview.md#azure-migrate-server-assessment-tool) tool.
11+
Follow this article to set up the Azure Migrate appliance for assessment of Hyper-V VMs with the [Azure Migrate:Server Assessment](migrate-services-overview.md#azure-migrate-server-assessment-tool) tool.
1212

1313
The [Azure Migrate appliance](migrate-appliance.md) is a lightweight appliance used by Azure Migrate:Server Assessment/Migration to discover on-premises Hyper-V VMs, and send VM metadata/performance data to Azure.
1414

15-
You can set up the Azure Migrate appliance for Hyper-V VM assessment using a VHD template that you download, or using a PowerShell installation script. This article describes how to set up the appliance using the VHD template. If you want to set up the appliance using the script, follow the instructions in [this article](deploy-appliance-script.md).
15+
You can deploy the appliance using a couple of methods:
1616

17+
- Set up on a Hyper-V VM using a downloaded VHD. This is the method described in this article.
18+
- Set up on a Hyper-V VM or physical machine with a PowerShell installer script. [This method](migrate-appliance-script.md) should be used if you can't set up a VM using a VHD, or if you're in Azure Government.
19+
20+
After creating the appliance, you check that it can connect to Azure Migrate:Server Assessment, configure it for the first time, and register it with the Azure Migrate project.
1721

1822
## Appliance deployment (VHD)
1923

@@ -69,7 +73,7 @@ Import the downloaded file, and create the VM.
6973

7074
### Verify appliance access to Azure
7175

72-
Make sure that the appliance VM can connect to [Azure URLs](migrate-appliance.md#url-access).
76+
Make sure that the appliance VM can connect to Azure URLs for [public](migrate-appliance.md#public-cloud-urls) and [government](migrate-appliance.md#government-cloud-urls) clouds.
7377

7478
## Configure the appliance
7579

articles/migrate/how-to-set-up-appliance-physical.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,9 @@
11
---
22
title: Set up an Azure Migrate appliance for physical servers
33
description: Learn how to set up an Azure Migrate appliance for physical server assessment.
4-
author: rayne-wiselman
54
ms.service: azure-migrate
65
ms.topic: article
7-
ms.date: 11/19/2019
8-
ms.author: raynew
6+
ms.date: 04/15/2020
97
---
108

119

@@ -74,14 +72,14 @@ Run the script as follows:
7472
```
7573
The script will launch the appliance web application when it finishes successfully.
7674
77-
In case of any issues, you can access the script logs at C:\ProgramData\Microsoft Azure\Logs\AzureMigrateScenarioInstaller_<em>Timestamp</em>.log for troubleshooting.
75+
If you come across any issues, you can access the script logs at C:\ProgramData\Microsoft Azure\Logs\AzureMigrateScenarioInstaller_<em>Timestamp</em>.log for troubleshooting.
7876
7977
> [!NOTE]
8078
> Please do not execute the Azure Migrate installer script on an existing Azure Migrate appliance.
8179
8280
### Verify appliance access to Azure
8381
84-
Make sure that the appliance VM can connect to the required [Azure URLs](migrate-appliance.md#url-access).
82+
Make sure that the appliance VM can connect to Azure URLs for [public](migrate-appliance.md#public-cloud-urls) and [government](migrate-appliance.md#government-cloud-urls) clouds.
8583
8684
## Configure the appliance
8785
@@ -116,7 +114,7 @@ Set up the appliance for the first time.
116114
Connect from the appliance to physical servers, and start the discovery.
117115
118116
1. Click **Add Credentials** to specify the account credentials that the appliance will use to discover servers.
119-
2. Specify the **Operating System**, friendly name for the credentials, **Username** and **Password** and click **Add**.
117+
2. Specify the **Operating System**, a friendly name for the credentials, and the username and password. Then click **Add**.
120118
You can add one set of credentials each for Windows and Linux servers.
121119
4. Click **Add server**, and specify server details- FQDN/IP address and friendly name of credentials (one entry per row) to connect to the server.
122120
3. Click **Validate**. After validation, the list of servers that can be discovered is shown.

articles/migrate/how-to-set-up-appliance-vmware.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,22 @@
22
title: Set up an Azure Migrate appliance for VMware
33
description: Learn how to set up an Azure Migrate appliance to assess and migrate VMware VMs.
44
ms.topic: article
5-
ms.date: 03/23/2020
5+
ms.date: 04/16/2020
66
---
77

88

99
# Set up an appliance for VMware VMs
1010

11-
This article describes how to set up the Azure Migrate appliance for assessment with the [Azure Migrate:Server Assessment](migrate-services-overview.md#azure-migrate-server-assessment-tool) tool, and for agentless migration using the [Azure Migrate:Server Migration](migrate-services-overview.md#azure-migrate-server-migration-tool) tool.
11+
Follow this article to set up the Azure Migrate appliance for assessment with the [Azure Migrate:Server Assessment](migrate-services-overview.md#azure-migrate-server-assessment-tool) tool, and for agentless migration using the [Azure Migrate:Server Migration](migrate-services-overview.md#azure-migrate-server-migration-tool) tool.
1212

1313
The [Azure Migrate appliance](migrate-appliance.md) is a lightweight appliance used by Azure Migrate:Server Assessment and Server Migration to discover on-premises VMware VMs, send VM metadata/performance data to Azure, and for replication of VMware VMs during agentless migration.
1414

15-
You can set up the Azure Migrate appliance for VMware VM assessment using an OVA template that you download, or using a PowerShell installation script. This article describes how to set up the appliance using the OVA template. If you want to set up the appliance using the script, follow the instructions in [this article](deploy-appliance-script.md).
15+
You can deploy the appliance using a couple of methods:
16+
17+
- Set up on a VMware VM using a downloaded OVA template. This is the method described in this article.
18+
- Set up on a VMware VM or physical machine with a PowerShell installer script. [This method](migrate-appliance-script.md) should be used if you can't set up a VM using an OVA template, or if you're in Azure government.
19+
20+
After creating the appliance, you check that it can connect to Azure Migrate:Server Assessment, configure it for the first time, and register it with the Azure Migrate project.
1621

1722

1823
## Appliance deployment (OVA)
@@ -59,9 +64,9 @@ will be hosted.
5964
9. Review and confirm the settings, then click **Finish**.
6065

6166

62-
### Verify appliance access to Azure
67+
## Verify appliance access to Azure
6368

64-
Make sure that the appliance VM can connect to [Azure URLs](migrate-appliance.md#url-access).
69+
Make sure that the appliance VM can connect to Azure URLs for [public](migrate-appliance.md#public-cloud-urls) and [government](migrate-appliance.md#government-cloud-urls) clouds.
6570

6671

6772
## Configure the appliance

0 commit comments

Comments
 (0)