MEG v0.71

FastTrack for Azure
The Migration Execution Guide
Developed by a team of FastTrack for Azure Program Managers and E

Success Unit.
Objectives
• Provide prescriptive guidance for the structure and running of a successful migration project. The guidance include d
migration tooling, project management, risk management and many other related templates.
• Provide consistent, well-considered migration execution guidance to the business, project management and technic
• Reduce the time required on Azure Migrate readiness by taking the complexity out of the different architectures, me
• Pre-empt support incidents, service outages and project delays by detailing a clear phase-by-phase migration journe
risks, and additional risk mitigation through request for change, and other templates with attributes that specifically a
Version Description
0.1 Initial draft

0.2 Limited pilot
0.3 Various updates
0.4 SQL migration to SQL on VM, MI, AzDB
0.5 Preview release
0.6 Preview release update
0.7 Preview release update
Review the available Microsoft programs and funding
Work through the below steps, or navigate directly to a topic of interest.
Step Item
1
Review the migration phases to get an understanding of the end-to-end procedure
2 Review workshop questions
3
Review the DACI matrix to understand the roles and responsibilities within a typical migration project
4
Assign resources to roles and responsibilities using the Team worksheet
5
Familiarize or refresh knowledge using recommended training resources and reference material
Reference the 'Tooling|...' worksheets for a visual
6 summary of the different discovery, assessment and
migration strategies.
7
Use the Checklist to ensure that key business, project management and technical recommendations are
8 Consider templates for your project:
Project Plan Template
Digital Estate Discovery Template
Workload Template
Wave Template
Runbook Template
Change Template
Risk Register Template

Track for Azure
ation Execution Guide
y a team of FastTrack for Azure Program Managers and Engineers working with the Microsoft SMC team, the Azure Advanced Cloud
.
g of a successful migration project. The guidance include digital estate discovery, defining the migration scope with common business d
nd many other related templates.
uidance to the business, project management and technical teams.
aking the complexity out of the different architectures, methodologies and prerequisite work.
elays by detailing a clear phase-by-phase migration journey with FastTrack for Azure best practices based on field experience, incident
nge, and other templates with attributes that specifically address common mistakes and oversights during migrations.
Content
Azure Migrate|Project Plan|Risk Register|Resource Management|Server Migration

…
…
Workshop Questionnaire | SQL checklist items and Tooling visualization
…
Project plan notes added | Promotion model added to runbook | Miscellaneous updates
Discover, Assess and Migrate tooling decision trees | Filter and Sort Workshop Questions by Topic | Miscelaneous updates
unding
rectly to a topic of interest.
Description
Migration Lifecycle
Sample questions to use during workshops with the business and technical teams in order to populate the migration temp
Resource Management
Resource Management
Training
Tooling
Best practice, field experience and incident root cause driven guidance.
Project Management
The purpose of the digital estate discovery is to present an inventory of applications and services to the business in order t
project.
Important dates should be captured and mapped to milestones in the project plan.
The purpose of the workload resource is to document and map the current technical attributes of the individual componen
migrated state.
The information in this resource is used as input when configuring replication and migration options.
It is also an important input to pre-and-post migration tasks that form the migration-day runbook.
The purpose of a wave plan is to document the workloads that will be grouped together in a single migration sprint.
Dependent services are typically included in the same Migration Wave.
In the portal you can select up to 10 VMs at once for migration. To migrate more machines, add them to groups in batches
The purpose of a migration-day runbook is to provide migration engineers with a proven list of tasks to perform during tes
The migration runbook in this guide is an example of what should be created for every machine, in all environments, for ea
The purpose of the request for change template is to provide migration specific details for consideration by the business, s
inclusion in their change management process.
It is also an additional checkpoint to help ensure that important migration decisions are made and relevant tasks carried o
clarify expectations and roles of approvers in advance and to establish a Cloud Change Authority.
The risk register is an important part of every migration project. The purpose of the example in this guide is to detail comm
any available mitigation, along with plans to migrate services that are subject to these risks.
f
common
Microsoft Programs and Funding
NOTE: Microsoft programs and funding are subject to change. Please discuss with your Microsoft representativ
Program
FastTrack for Azure

Solution Assessment Program
Azure Migration and Modernization Program

Azure Migration and Modernization Program | Azure for Partners
Azure Migration and Modernization Program (partner-led)
Azure Analytics and AI Accelerate Program

Microsoft Programs and Funding
nge. Please discuss with your Microsoft representative if you would like to participate in any of the programs.
Description
FastTrack for Azure is a technical enablement program for organizations with cloud projects that
enables the rapid, effective design, and deployment of Azure solutions in the cloud. It includes
tailored guidance from Azure engineers that leverages proven practices and architectural guides.
To ensure you use data driven insights to plan your digital transformation.
End-to-end migration assistance with the migration of workloads like, SQL, SAP, AVD and
application modernisation.
Microsoft Partners to assist with your program of work.
Partner investments and incentives can help drive the technical and workplace innovations you
need to advance your business and your customers’ digital transformation.
The Azure Analytics and AI Accelerate Program (AAAP) is a proven approach to help partners
accelerate customer demand and consumption of Analytics & AI Services. The program decreases
the time to solution and increases your ability to win!
Migration Framew
This resource includes guidance for all phases of the typical migration approach in the graphic below. The design of a n
with a cloud operating model and operations plan to manage migrated workloads. However, neither of these are with
areas.
LANDING ZONE
FTA Landing Zone Design

Review
Migration Framework
e graphic below. The design of a new, or validation of an existing landing zone for migrated workloads is recommended along
However, neither of these are within the scope of this resource. FastTrack for Azure offer separate resources to assist with these
CLOUD OPERATIONS
FTA Cloud Roles and

Operations Management
mmended along
assist with these
ERATIONS
Roles and
Management
The questions in this worksheet will help to populate the migration execution guide templates. A workshop (or series of
Id Question
Q001 Who is the business and technical owner(s) for each workload?
Q002 For each workload, are they revenue impacting for the business?
Q003 What are the number of users for each workload?
Q004 What is the cloud rationalization decision for each workload?
Q005 Are there any compliance requirements for the workloads?
Q006 Where is each workload located?
Q007 Do the workloads have geographic redundancy?
Q008 Are the workloads production or non-production systems?
Q009 What is the app type for each workload?
Q010 What is the business criticality that is assigned to each workload?

What is the expected workload lifecycle (where known)? Where is the
workload currently within this lifecycle? Are there plans to replace or
Q011 decommission the workload?
Are there any compelling business drivers for the migration of the
Q012 workloads?
Q013 What are the significant milestone dates to meet the business drivers?
Are you able to assign a migration priority to the workloads in your digital
Q014 estate?
Q015 Do you have a migration tooling preference?
Q016 What is the preferred promotion (to production) model for each workload?
Do you have on-premises, estimated cloud and migration cost details for
Q017 the workloads?
Q018 What is the current SLA for each workload?
Q019 Will the migration be into an existing landing zone?
What roles will be involved with this migration project? Will there be a
Q020 project manager, migration architect, UAT resources, etc?
Who is the testing team for the app, are they available, how do you book
Q021 them?
What are the support details? Is support for the workloads internal,
Q022 vendor or both?
Q023 Are there any agreed maintenance windows for the workloads?
Q024 What is the data classification that is associated with the workloads?
Is there a requirement for the capability to restore historic backups of the

Q025 system prior to migration?
Q026 What is the current and future plans for patching?
Q027 What is the current and future plans for Security Posture Management?
What is the current and future plans for Security Information and Event
Q028 Management?
Q029 What are the operating hours for the workloads by environment and host?
Q030 What is the required SLA for the workloads when migrated to the cloud?
Q031 What level of availability is required when the workloads are migrated to the cloud?
Q032 Should hybrid benefits be applied to Windows Server or supported Linux (RHEL/SUSE) machines that are being m
Q033 Will Azure Reserved Virtual Machine Instances be used to reduce costs?
Q034 Has a Total Cost of Ownership analysis been completed to estimate cost savings when migrating workloads to Az
Q035 How many servers are there in each workload?
Q036 Known issues/last successful reboot?
Q037 How do users and related services authenticate to the app?
Q038 Is any part of the workload considered to be a shared service?
Q039 Is the workload load balanced?
What is the client app, how does it connect, where is it hosted and does it
Q040 use DNS names?
For each workload, is external access required, or is the workload internal

Q041 facing only?
Q042 Are SSL certs used, what names, private/public?
Q043 What service accounts are used by the system?
Q044 What currently provides time synchronization service?
Q045 Are there any print service considerations for the application?
Q046 How is the app licensed?

Are there any batch jobs or scheduled tasks for the app or on the server?
Q047 How do they run, what do they run as?
How does DNS work for the workloads both internal and external? What is
Q048 the target state?
Q049 Is an SMTP relay used by the workloads?
Q050 What are the file services requirements?
Are there AV exclusions that need to be applied if it moves to a new

Q051 server?
Q052 What is the current backup and restore method?
Does the app use a database, what version, is it shared, what is the target
Q053 state, who owns and maintains the DB?
What are the database licensing requirements, will new licenses need to
Q054 be purchased?
Q055 How is DB authentication handled?
Q056 How can access to the workloads be arranged?
Is there an access management process that need to be followed for the

Q057 retrieval of existing and storing of new keys and passwords?
Q058 How are updates and new releases handled?
Q059 What is the support model for the app?
Q060 What is the current DR/BCP strategy, target state?
Q061 Are the workloads subject to change freeze?
Q062 Are the workloads subject to change control?

Q063 What OS version(s) are the workloads on?
Q064 What hardware or virtualization platform(s) are the workloads hosted on?
What roles are there in the workload architecture? Are they multi-tier
Q065 architectures?
Q066 What is the impact of changing an IP address on your workloads?

Workshop Questions
ecution guide templates. A workshop (or series of workshops) with all relevant stakeholders is recommended to gather the required info
Description Template Workshop
The business unit, business owner and technical owner that is responsible
for each workload. Digital Estate Business
Digital Estate Business
Will the app server be migrated, or will the app be re-installed on a new
host? Digital Estate Business
For example, legislated data retention for xx years. SOC-2, ISO 27001, etc. Digital Estate Business
Data centre and location. Digital Estate Business
Document the workload environment. Digital Estate Business
Is it a commercial-off-the-shelf (COTS), or custom app? Digital Estate Business
Mission critical, high, medium, low, etc. Digital Estate Business
Not defined, 5 years, etc. Digital Estate Business
Data centre exit, contract expiry, hardware or software end-of-life,

security concerns, competitive advantage, etc? Digital Estate Business

Azure Migrate, Azure Site Recovery, Backup and Restore, Movere, etc. Digital Estate Business
What level of testing is required for each workload before traffic is cut
over and it is considered to be production? Common models include
single-step, staged or flight (combines single-step and staged)? Digital Estate Business
This information is sometimes documented in the digital estate planning
phase to provide business justification and additional criteria for the
prioritization of workload migrations. Digital Estate Business
Consider using the FTA Landing Zone design/review checklist to validate theDigital
target Estate
environment.
Business
Refer to the roles and teams templates for suggested roles and
responsibilities. Roles Business
Wave Business
Internal and/or external support details for each workload. Workload Business
Workload Business
Refer to the data sheet for data classification examples. Workload Business
Workload Business
Workload Business
Workload Business
Workload Business
If a VM in the workload is not required 24x7, should shutdown be

configured for periods when it is not required? Workload Business
Ensure that a suitable availability option and disk type is selected to supportWorkload
the required SLA.
Business
Workload Business
If you have Windows Server machines that are covered with active
Software Assurance, Red Hat or SUSE software subscriptions, and you
want to apply the benefit to the machines you're migrating. Workload Business
Also consider Azure Savings Plans

https://azure.microsoft.com/en-us/pricing/offers/savings-plan-compute/. Workload Business
Digital Estate Technical
Are there any known issues prior to migration? Does the system start up
on reboot? Workload Technical
Check for NTLM, using an IP address to point to a DC directly, unsupported

protocols, etc. Workload Technical
Is the shared service used by other workloads? Workload Technical
Workload Technical
Check for client apps that use an IP address or NETBIOS name. Investigate
CNAMES that are used and if they can be changed easily Workload Technical
Workload Technical
Workload Technical
Will the service accounts work when the workload is migrated to the
cloud? Workload Technical
Is there a time server on-premises? Workload Technical
Workload Technical
Dongle, MAC address, IP address, etc will need to be planned for. Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Workload Technical
Web, Application, database, etc roles. Workload Technical
After migration servers will typically be assigned a different IP address.

How is the workload affected by an IP address change? Workload Technical
tions
ed to gather the required information.
Facilitator Attendee Roles Topic

Project Manager, Migration Engineer,
Migration Project Sponsor, Workload business owner, Workload
Architect Workload Technical Owner Details
Migration Project Sponsor, Workload business owner,
Architect Workload Technical Owner Business Case
Architect Workload Technical Owner Planning
Architect Workload Technical Owner Criticality
Architect Workload Technical Owner Tooling
Architect Workload Technical Owner Landing Zone
Migration Project Sponsor, Workload business owner, Project
Architect Workload Technical Owner Management
Project Manager, Migration Engineer, User
Migration Project Sponsor, Workload business owner, Acceptance
Architect Workload Technical Owner Testing
Architect Workload Technical Owner Support
Migration Project Sponsor, Workload business owner, Cost
Architect Workload Technical Owner Optimization

Project Sponsor, Workload business owner,
Migration Workload Technical Owner, Licensing Cost
Architect Specialist Optimization
Migration Workload business owner, Workload
Architect Technical Owner Business Case
Migration Workload business owner, Workload Workload
Architect Technical Owner Planning
Migration Workload business owner, Workload
Architect Technical Owner Support
Response
Roles and Re
Modify DACI as
required, then CLICK
HERE to assign project
resources
le
Ro
This shape represents a table slicer. Table slicers are not supported in this version of Excel.
If the shape was modified in an earlier version of Excel, or if the workbook was saved in Excel 2007 or earlier, the slice
Roles and Responsibilities
ati on
ati AT
op ery
AT
re
ti
U
t
en
M igra
tu
ov
tio se U
M on
on
ry
a n te c
ve
sc
M
ss
in
lC
e
n i e l ea
Di
klo sco
hi
klo igr
klo igr
se
klo ing
klo ool
klo est
na
c
igr tate
As
Ar
Sc
Di
igr lan
R
T
T
Pr on
W on
W ad
Or ad
W ad
W ad
W ad
W ad
d
s
tP
za
a
lE
Pl
klo
ati
ati
ec
ta
ga
av
le
or
or
or
or
or
or
or
oj
gi
Ro
W
M
M
Di
Migration Architect D D A D A A D A A A A A
Migration Engineer C I C C D D C D D C D C
Project Manager I I D I I I I I I D I D
Project Sponsor A A A A I I A I I I A I
User Acceptance Tester I I I I I I I I I C I C
Workload Architect I I C C C C C C C C C C
Workload Business Owner I I C I A A A A A A A A
Organizational Change Manager I I C I I I I I I C I C
Licensing Specialist I I C C I C C C I I I I
Cloud Operations Manager C C C I I I I C I I I I
Landing Zone Architect I I C C I I C C I I I I
rted in this version of Excel.
he workbook was saved in Excel 2007 or earlier, the slicer can't be used.
Or
I
I
I
I
I
I
C
C
C
A
D
ga
ni
za
tio
na
I
C
C
C
C
C
C
C
A
A
D
Tr lC
an ha
siti ng
e
I
I
I
I
I
I
I
C
A
A
D
W on M
or to an
klo Op ag
ad er em
Lic ati en
en on t
sin s
g
Resourc
CLICK HERE to
t
en
review role
tm
responsibilities
r
e
pa
m
e
l
De
Na
Ro
Michal Rosenstein Project Sponsor
Ebere Ibeabuchi Project Manager
Rita Tsakiris Migration Architect
Alexandra Voronova Migration Engineer
Vasily Butusov Workload Business Owner
Piet Smit User Acceptance Tester
Doan Linh Workload Owner
Abdul-Wahhab Maloof User Acceptance Tester
Stefan Milea Workload Business Owner
Gowri Kalluri User Acceptance Tester
Jadranko Lukic Workload Business Owner
Gabriella Göransson User Acceptance Tester
Koos Kriel Organizational Change Manager
Violet Martinez Landing Zone Architect
Sydney Mattos Licensing Specialist
Felix Henderson Cloud Operations Manager
This shape represents a table slicer. This shape represents a table slicer.
Table slicers are not supported in Table slicers are not supported in
this version of Excel. this version of Excel.
If the shape was modified in an If the shape was modified in an

earlier version of Excel, or if the earlier version of Excel, or if the
workbook was saved in Excel workbook was saved in Excel 2007
2007 or earlier, the slicer can't be or earlier, the slicer can't be used.
used.
Resource Assignment
(s)
t
en
y
ne
lit
ad
tm
on
Zo
bi
klo
ile
r
la
ati
l
pa
e
ai
ob
or
ai
m
c
em
De
Av
Lo
W
Ti
Exec All … [email protected] New York, US UTC-5
PMO All … [email protected] New York, US UTC-5
IT All … [email protected] New York, US UTC-5
IT All … [email protected] NSW, AU UTC+11
Finance Payroll system … [email protected] NSW, AU UTC+11
Finance Payroll system … [email protected] Gauteng, RSA UTC+2
HR Intranet … [email protected] London, UK UTC
HR Intranet … [email protected] London, UK UTC
Marketing Advertisement system … [email protected] London, UK UTC
Marketing Advertisement system … [email protected] London, UK UTC
HR Recruitment system … [email protected] Gauteng, RSA UTC+2
HR Recruitment system … gabriellagö[email protected] Gauteng, RSA UTC+2
IT All … [email protected] Gauteng, RSA UTC+2
Finance All … [email protected] NSW, AU UTC+11
e represents a table slicer. This shape represents a table This shape represents a table slicer. This shape represents a table
rs are not supported in slicer. Table slicers are not Table slicers are not supported in Table slicers are not support
n of Excel. supported in this version of Excel. this version of Excel. this version of Excel.
e was modified in an If the shape was modified in an If the shape was modified in an If the shape was modified in
sion of Excel, or if the earlier version of Excel, or if the earlier version of Excel, or if the earlier version of Excel, or if
was saved in Excel 2007 workbook was saved in Excel workbook was saved in Excel workbook was saved in Exce
the slicer can't be used. 2007 or earlier, the slicer can't be 2007 or earlier, the slicer can't be 2007 or earlier, the slicer can
used. used. used.
y
ne
lit
Zo
bi
la
e
ai
m
Av
Ti
OOF 15-23/01/2023
his shape represents a table slicer.

able slicers are not supported in
his version of Excel.
f the shape was modified in an

arlier version of Excel, or if the
workbook was saved in Excel
007 or earlier, the slicer can't be
sed.
Training Resources and Reference M
Resource
Azure Migrate Docs
Azure Migrate MSLearn
FTA Live|Migrations
FastTrack for Azure on Microsoft Learn
Azure Migrate : The hub for cloud migration and modernization
Migration guide: SQL Server to SQL Server on Azure Virtual Machines
Cloud migration - Cloud Adoption Framework | Microsoft Learn
Assessment and migration planning with Azure Migrate for servers - Cloud Adoption Framework | Microsoft Learn
Migration execution with Azure Migrate for servers - Cloud Adoption Framework | Microsoft Learn
(311) Assess, Get Recommendations & Migrate SQL Server to Azure using Azure Data Studio | Data Exposed - YouTube
Azure Data Studio - SQL Server | Microsoft Learn
Azure SQL migration extension for Azure Data Studio - Azure Data Studio | Microsoft Learn
Azure Database Migration Service documentation | Microsoft Learn
ence Material
Description
In-depth articles and tutorials on Azure Migrate.
Interactive, hands-on learning paths.
FastTrack for Azure training and QnA sessions.
Streamable FastTrack for Azure training sessions
YouTube introduction to Azure Migrate.
Step-by-step guidance.
Cloud migration in the Cloud Adoption Framework.
Best practices for assessment and migration planning with Azure Migrate
Best practices for migration execution with Azure Migrate
YouTube introduction to migrating SQL Server using Azure Data Studio
In-depth articles and tutorials on Azure Data Studio.
Azure SQL migration extension for Azure Data Studio article.
In-depth articles and tutorials on the Azure Database Migration Service.
The purpose of this page is to visualize the features of the Azure Migrate Appliance when used to discover, assess or m
DISCOVERY
Environment
VMware
Hyper-V
Physical
AWS
GCP
purpose of this page is to visualize the features of the Azure Migrate Appliance when used to discover, assess or migrate source environm
VMware
- Agentless Discovery and assessmen
VMware servers
- Agentless migration of VMware serv
Discover
Assess
Migrate
DISCOVERY
Reference
Discover servers running in a VMware environment with Azure Migrate Discovery and assessment
Discover servers on Hyper-V with Azure Migrate Discovery and assessment
Discover physical servers with Azure Migrate Discovery and assessment
Discover AWS instances with Azure Migrate Discovery and assessment
Discover servers on GCP instances with Azure Migrate Discovery and assessment
Azure Migrate Appliance
r migrate source environments that include VMware, Hyper-V, Physical or other Clouds. Reference information is also provided.
Hyper-V Physical or other Clouds

Discovery and assessment of - Agentless Discovery and assessment of Hyper- - Agentless Discovery and assessment of
vers V servers physical or other cloud VMs
migration of VMware servers - Cannot be used to migrate Hyper-V servers - Cannot be used to migrate physical or ot
cloud servers
ASSESSMENT
Environment Reference
VMware Assess VMware servers for migration to Azure VMs in Azure Migrate
Hyper-V Assess Hyper-V VMs for migration to Azure VMs with Azure Migrate
Physical Assess physical servers for migration to Azure with Azure Migrate
AWS Assess AWS instances for migration to Azure with Azure Migrate
GCP Assess GCP VM instances for migration to Azure with Azure Migrate
e information is also provided.
ysical or other Clouds

gentless Discovery and assessment of
ysical or other cloud VMs
annot be used to migrate physical or other
ud servers
MIGRATION
VMware Select a VMware migration option with Azure Migrate Server Migration
Hyper-V Migrate Hyper-V VMs to Azure with Azure Migrate Server Migration
Physical Migrate machines as physical server to Azure with Azure Migrate
AWS Discover, assess, and migrate Amazon Web Services (AWS) EC2 VMs to Azure
GCP Discover, assess, and migrate Google Cloud Platform (GCP) VM instances to Azure
The purpose of this page is to visualize the features of the Azure Site Recovery Provider and Microsoft Azure Recovery S
DISCOVERY
Environment
VMware
Hyper-V
Physical
AWS
GCP
Azure Site Recovery P
s page is to visualize the features of the Azure Site Recovery Provider and Microsoft Azure Recovery Services Agent when used to migrat
VMware
- Not used for migration of VMw
Migrate
DISCOVERY
Reference
ure Site Recovery Provider + Microsoft Azure Recovery Services Agent
Agent when used to migrate Hyper-V source environments. Reference information is also provided.
ware Hyper-V Physical or other Cloud

t used for migration of VMware servers - Agentless migration of Hyper-V servers - Not used for migration of phy
cloud servers
*Provider and agent is installed on the host servers
ASSESSMENT
VMware Assess VMware servers for migration to Azure VMs in Azure Migrate
Hyper-V Assess Hyper-V VMs for migration to Azure VMs with Azure Migrate
Physical Assess physical servers for migration to Azure with Azure Migrate
AWS Assess AWS instances for migration to Azure with Azure Migrate
GCP Assess GCP VM instances for migration to Azure with Azure Migrate
nt
Physical or other Cloud

- Not used for migration of physical or other
cloud servers
MIGRATION
Environment
VMware
Hyper-V
Physical
AWS
GCP
her Cloud
migration of physical or other
MIGRATION
Reference
Select a VMware migration option with Azure Migrate Server Migration
Migrate Hyper-V VMs to Azure with Azure Migrate Server Migration
Migrate machines as physical server to Azure with Azure Migrate
Discover, assess, and migrate Amazon Web Services (AWS) EC2 VMs to Azure
Discover, assess, and migrate Google Cloud Platform (GCP) VM instances to Azure
The purpose of this page is to visualize the features of the Azure Migrate Replication Appliance when used to migrate
DISCOVERY
Environment
VMware
Hyper-V
Physical
AWS
GCP
Azur
pose of this page is to visualize the features of the Azure Migrate Replication Appliance when used to migrate source environments tha
VMware
- Agent-based migration of V
Migrate
DISCOVERY
Reference
Azure Migrate Replication Appliance
source environments that include VMware, Physical or other Clouds. Reference information is also provided.
ware Hyper-V Physical or other Cloud

ent-based migration of VMware servers - Not used for migration of Hyper-V servers - Agent-based migration of ph
cloud servers
ASSESSMENT
Environment Reference Environment
VMware Assess VMware servers for migration to Azure VMs in Azure Migrate VMware
Hyper-V Assess Hyper-V VMs for migration to Azure VMs with Azure Migrate Hyper-V
Physical Assess physical servers for migration to Azure with Azure Migrate Physical
AWS Assess AWS instances for migration to Azure with Azure Migrate AWS
GCP Assess GCP VM instances for migration to Azure with Azure Migrate GCP
ysical or other Cloud
gent-based migration of physical or other
ud servers
MIGRATION
Reference
Migrate machines as physical server to Azure with Azure Migrate
Azure Migrate + Azure SQL Migration Exten
The purpose of this page is to visualize the features of Azure Migrate and Azure SQL Migration Extension for Azure Da
Migration
Targets
Azure Migrate to
DISCOVER and
ASSESS SQL
source
environments
Azure SQL
Migration
Extension for
Azure Data
Studio with
Database
Migration
Service (DMS) to
MIGRATE
databases
DISCOVERY ASS
Environment Reference Environment
SQL Server Discover SQL Server instances in an Azure Migrate project SQL Server
QL Migration Extension for Azure Data Studio with Database Migration Service (DMS)
tion Extension for Azure Data Studio with Database Migration Service (DMS) when used to migrate SQL Servers. Reference information i
er
cov
Dis
ess
Ass
Migrate
ASSESSMENT MIGRATION
Reference Environment
Create an Azure SQL assessment - Azure Migrate SQL Server
SQL Server
SQL Server
SQL Server
SQL Server
atabase Migration Service (DMS)
) when used to migrate SQL Servers. Reference information is also provided.
MIGRATION
Reference
Migrate databases by using the Azure SQL Migration extension for Azure Data Studio
Azure DMS tools matrix - migration phase
Migrate SQL Server databases to Azure
Rehost an on-premises application by migrating to Azure VMs and Azure SQL Managed Instance
Rehost an application by migrating it to Azure VMs and SQL Server Always On availability groups
Decis
The purpose of this page is to detail tooling decisions.
Discovery a
M
Decision Trees
Discovery and Assessment
Migrate
Discover Assess
Link A Link A
Link B Link B
Link C Link C
Link D Link D
Link E Link E
Link F
Link G
Migrate
Link A
Link B
Link C
Link D
Link E
Link F
FastTrack for Azure
Migration Checklist
Source
Phase Topic
Environment
1. Planning Cloud Adoption Plan All environments
1. Planning Migration Hyper-V Agentless
1. Planning Migration VMware
1. Planning Migration VMware Agent-based
1. Planning Project Management All environments


1. Planning Target: Azure SQL SQL Server

Database
(Database Migration
Service)
1. Planning Target: Azure SQL SQL Server

Managed Instance
(Database Migration
Service)
1. Planning Target: SQL Server on SQL Server

Azure VMs with/without
SQL Server Always On
Availability Groups
(Database Migration
Service)
1. Planning Tooling All environments


1. Planning Tooling Hyper-V
1. Planning Tooling Hyper-V
1. Planning Tooling: Azure Migrate All environments
1. Planning Tooling: Azure Migrate Hyper-V
1. Planning Tooling: Azure Migrate VMware Agentless

appliance

appliance
appliance
appliance
appliance
appliance
appliance
1. Planning Tooling: Azure Migrate Physical or other Cloud
appliance
appliance
appliance
1. Planning Tooling: Azure Migrate VMware
appliance
1. Planning Tooling: Azure Migrate VMware
appliance

appliance (Government)

Project
Replication appliance
1. Planning Tooling: Azure Migrate VMware Agent-based

1. Planning Tooling: Dependency All environments

Analysis
1. Planning Tooling: Discovery All environments
1. Planning Tooling: Discovery and All environments

Assessment
1. Planning Tooling: Discovery and Hyper-V Agentless
Assessment
1. Planning Tooling: Discovery and Hyper-V Agentless
Assessment
1. Planning Tooling: Discovery and Physical or other Cloud

Assessment
1. Planning Tooling: Network All environments
2. Digital Estate Migration Planning All environments

2. Digital Estate Workload Planning All environments
3. Discovery Tooling Hyper-V Agentless
3. Discovery Tooling Physical or other Cloud
3. Discovery Tooling VMware
3. Discovery Tooling: Azure Migrate SQL Server
4. Assessment Sizing All environments
4. Assessment Tooling SQL Server
4. Assessment Tooling: Azure Migrate SQL Server
4. Assessment Workload Planning All environments
4. Assessment Workload Planning All environments
4. Assessment Workload Planning AWS

4. Assessment Workload Planning GCP
4. Assessment Workload Preparation SQL Server
5. Pre-Migration Landing Zone All environments
5. Pre-Migration Wave Planning All environments
5. Pre-Migration Wave Planning All environments
5. Pre-Migration Workload Optimization All environments
5. Pre-Migration Workload Optimization Hyper-V
5. Pre-Migration Workload Optimization Physical or other Cloud
5. Pre-Migration Workload Optimization VMware
5. Pre-Migration Workload Planning All environments

5. Pre-Migration Workload Preparation All environments


5. Pre-Migration Workload Preparation SQL Server

6. Migration Migration All environments

6. Migration Migration All environments
6. Migration Network SQL Server

6. Migration Network SQL Server
6. Migration Replication AWS
6. Migration Replication GCP
6. Migration Replication Hyper-V
6. Migration Replication Physical or other Cloud
6. Migration Replication VMware
6. Migration Replication VMware Agentless
6. Migration Replication VMware Agentless

6. Migration Target: Azure SQL SQL Server
Database
(Database Migration
Service)
6. Migration Target: Azure SQL SQL Server

Managed Instance
(Database Migration
Service)
6. Migration Target: SQL Server on SQL Server

Azure VMs with/without
SQL Server Always On
Availability Groups
(Database Migration
Service)
6. Migration Test Migration All environments

6. Migration Tooling: Azure Migrate Hyper-V Agentless
6. Migration Tooling: Azure Migrate Physical or other Cloud
6. Migration Tooling: Azure Migrate VMware
6. Migration Tooling: Azure Migrate VMware Agent-based
7. Post-Migration Cleanup All environments

7. Post-Migration Cleanup VMware

7. Post-Migration Cleanup VMware Agent-based
7. Post-Migration Licensing All environments
7. Post-Migration Linux VMware Agent-based
7. Post-Migration Replication All environments

7. Post-Migration Target: Azure SQL SQL Server
Database
(Database Migration
Service)
7. Post-Migration Target: Azure SQL SQL Server

Database
(Database Migration
Service)
7. Post-Migration Testing All environments
7. Post-Migration Testing All environments
7. Post-Migration User Acceptance Testing All environments
7. Post-Migration Workload Optimization All environments


7. Post-Migration Workload Optimization SQL Server
7. Post-Migration Workload Preparation SQL Server

1. Planning Business Case VMware

This shape represents a table This shape represents a table slicer. Table slicers are
slicer. Table slicers are not
supported in this version of If the shape was modified in an earlier version of Ex
Excel. slicer can't be used.
stTrack for Azure If the shape was modified in
ation Checklist an earlier version of Excel,
or if the workbook was
saved in Excel 2007 or
earlier, the slicer can't be
used.
Item
Ensure that the migration project is aligned with the cloud adoption plan.
Confirm that Hyper-V host and guest VM migration requirements are met.
Decide between agentless and agent-based migration strategies.
Confirm that VMware host and guest VM requirements are met for agent-based
migration.
The migration project should have a separate dedicated project plan.
Resources should be assigned to key project roles and responsibilities.
Document planned leave for SME's and UAT testing teams.

The project should have a risk register.
Consider using Azure Devops or GitHub projects to manage the migration project.
Create a detailed migration and rollback plan to Azure SQL Database.
Create a detailed migration and rollback plan to Azure SQL Managed Instance.
Create a detailed migration and rollback plan to SQL Server on Azure VMs
Migrate using Azure Migrate rather than Azure Site Recovery.

Plan for existing backups to be migrated.
Plan for password and key storage post migration
Plan for SME/app owner access to new monitoring, backup, budget, observability
portals.
Confirm logins for SSL Cert , domain name management and external DNS portals
are available.
Validate Application Licencing Model.
Confirm plan for OS, Application and Security patching post migration.
Validate AV exclusions that will need to be applied post migration.

When installing/configuring the MARS agent on Hyper-V hosts with Server Core
the installation will fail if not run from the working directory of the executable
(DRConfigurator.exe).
If the hosts are running Windows Server 2012 R2 and the MARS provider fails to
install, try to install the MARS agent manually and then retry the provider.
Be mindful that Azure Policies with a deny effect may cause issues when creating
an Azure Migrate project, and/or when migrating VMs.
Plan to create additional Azure Migrate projects if you need to migrate to
multiple regions.
Plan target subscriptions for the migration scope and configure access in the
TARGET SUBSCRIPTION(S) accordingly.
Be mindful that 'TokenCache Errors' on Hyper-V 2012R2 - often related to ADAL
vs MSAL on modern OS'. Surfaces when changing tools or Azure Migrate project.
Confirm that VMware host and guest VM requirements are met for agentless
migration.
Ensure that DNS name resolution works between the Azure Migrate appliance
and Azure, Azure Migrate appliance and the host machines (ESX, Hyper-V) and
guest migration source machines.
Confirm that all prerequisites and support requirements for the Azure Migrate
appliance are met.
Allow internet access on the Azure Migrate appliance and ensure access to
required URLs are provisioned.
Use the scripted methodology to deploy Azure Migrate appliance when OVA or
VHD methods are not possible.
Allow Azure Migrate appliance auto-updates.
Routinely check the Azure Migrate appliance version.
Exclude the %ProgramData%\Microsoft Azure folder from antivirus scanning.
Deploy the Azure Migrate appliance for physical servers or virtual servers in other
clouds using a PowerShell installer script.
If using the PowerShell installer script downloaded from the Azure Migrate
project, verify by checking the hash values.
Confirm that Physical and or other cloud server requirements are met.
Deploy Azure Migrate appliance as a new virtual server running on vCenter Server
using an OVA template
Deploy additional Azure Migrate appliances if more than 10 vCenter servers need
to be connected to, and/or more than 10,000 servers need to be discovered.
Deploy the Azure Migrate appliance for Government using a PowerShell installer
script.
Ensure an account with appropriate permissions is available to create an Azure

Migrate "Project" in the Azure Portal.
Review Azure Migrate Replication appliance requirements are met.
Confirm that Azure Migrate Replication appliance requirements are met for
VMware agent-based migrations.
Decide between agentless and agent-based or manual dependency analysis

strategies.
Ensure that security approvals and admin access is available as required to run
the tooling on your existing environment.
Decide how servers will be discovered and assessed.
Deploy Azure Migrate appliance as a virtual server running on a Hyper-V host

using a VHD template
Deploy additional Azure Migrate appliances if more than 300 Hyper-V host
servers need to be connected to, and/or more than 5,000 servers need to be
discovered.
Deploy additional Azure Migrate appliances if more than 1,000 physical servers
need to be discovered.
If a private network (e.g. Azure ExpressRoute private peering or a site-to-site VPN
connection) is mandatory for use to discover, assess, and migrate servers with
Azure Migrate use Azure Private Link.
If a private network is not mandatory for use to discover, assess, and migrate
servers with Azure Migrate use ExpressRoute Microsoft peering or an internet
connection.
If you selected private endpoint as the connectivity method for the Azure Migrate
project, grant the Recovery Services vault access to the cache storage account.
To replicate using ExpressRoute with private peering, create a private endpoint

for the cache storage account.
If you selected private endpoint as the connectivity method for the Azure Migrate
project, verify DNS name resolution.
The migration scope should be defined as part of a digital estate discovery with
included workloads for the migration project.
Determine the digital estate planning approach - Workload based Top Down
Assessment Approach -App aligned-5Rs IaaS/PaaS/SaaS) vs Asset-driven
Approach (IaaS)
The business drivers should be documented and communicated along with any
key dates e.g. datacentre exit dates.
Document each workload with relevant technical, business and support
information.
Confirm discovery support compatibility for the digital estate and add any
unsupported assets into a risk register.
Confirm discovery support compatibility on-premises or in other clouds like AWS,
GCP, Xen etc. for the digital estate and add any unsupported assets into a risk
register.
Confirm discovery support compatibility in a VMware environment for the digital
estate and add any unsupported assets into a risk register. Use tools like Azure
Migrate
Use Azure Migrate to discover SQL Servers.
Decide on the sizing criteria that is most suitable to your business requirements.
Choose between Performance-based and As-is-on-premises or do an assessment
of each type and choose the best approach.
Recalculate assessments to include the most recent data in decisions.
Do not use Performance-based assessments with a confidence rating below 5

stars for making production decisions.
Consider doing a detailed database assessment of all discovered databases using
tooling such as a SQL Server Data Tools project.
Compare migration targets and select the most appropriate platform for each
database.
Compare SQL migration tools and select the most appropriate migration tooling
strategy.
Consider DMA, Cloud Atlas or Cloudamize alternatives to Azure Migrate for

assessments.
Use Azure Migrate to create and run an Azure SQL assessment.
Use Azure Migrate to assess readiness and cost estimates for migrating apps,
infrastructure, and workloads to Microsoft Azure.
Let the Azure migrate dependency tracker and performance data captures run
across a week end, across a month end, quarter end, etc, as per the business
cycles to capture sufficient data.
Ensure that the AWS VMs you want to migrate are running a supported OS
version.
Ensure that AWS VMs comply with the supported configurations for migration to
Azure.
Verify that the AWS VMs that you replicate to Azure comply with Azure VM
requirements.
Ensure that the GCP VMs you want to migrate are running a supported OS
version.
Ensure that GCP VMs comply with the supported configurations for migration to
Azure.
Verify that the GCP VMs that you replicate to Azure comply with Azure VM
requirements.
Capture performance baselines on source system.
Ensure there is a suitable Landing Zone available to host the migrated workloads.
Plan migration waves and document with relevant information.
Evaluate network readiness for planned migration activities.
Remediate workloads prior to migration.
Before migration enable RDP on the on-premises VM. Make sure that TCP, and
UDP rules are added for the Public profile, and that RDP is allowed in Windows
Firewall > Allowed Apps, for all profiles.
For site-to-site VPN access, enable RDP and allow RDP in Windows Firewall ->
Allowed apps and features for Domain and Private networks.
Intra-Subnet Traffic: Be mindful that security rules in a Network Security Group
associated to a subnet can affect connectivity between VMs within the subnet.
Perform pre-migration activities. Document the availability of hybrid benefits for

each workload as the information is required for the migration step.
Legacy workloads e.g. Windows Server 2008-2012R2, SQL Server 2012.

Confirm Microsoft server software support for Azure VMs.
Define a promotion model for each assessed workload.
Design workload architecture before migration for each workload. The workload
architecture will determine placement in the cloud, any prerequisite work that
may be required e.g. allowing firewall ports, network communication,
deployment of load balancers, placement in availability sets/zones, proximity
groups, etc.
Prioritise workloads based on quick wins.
To replicate VMs with CMK, you'll need to create a disk encryption set under the
target Resource Group. A disk encryption set object maps Managed Disks to a Key
Vault that contains the CMK to use for SSE.
For each workload, choose and document the desired disk encryption option.
For each workload, choose an availability option and document it in the workload
plan.
Manually configure the SAN policy as Online All for machines running operating
systems earlier than Windows Server 2008 R2
Install Hyper-V Guest Integration manually on machines running Windows Server
2003.
Install the Windows Azure Guest Agent manually for machines running operating
systems earlier than Windows Server 2008 R2.
Do not migrate domain controllers unless migrating into an isolated environment
in Azure requiring its own domain controllers (or testing applications in a sandbox
environment).
Do not migrate/move the last domain controller before migrating all domain-
dependent workloads.
Verify that the desired VM Sku is available in the target region prior to migration.
Also confirm that Azure Policy is not blocking the VM Sku, and that the target
subscription has sufficient available quota.
Monitor resource consumption including disk capacity and utilization on
replicating machines, appliances and host systems.
Check Windows Application and System event logs for any errors.
Create a detailed migration rollback plan.
Test migration plan and record timings.

Test rollback plan and record timings.
If existing databases have Transparent Data Encryption (TDE) enabled, ensure
that the protector will be migrated and protected within Azure.
Check SQL Server Error Log for any ongoing errors.

Check SQL Server Error Log for any errors at last startup.
Check SQL Server Agent for any failing jobs.
Tidy up SQL Server Agent jobs that are no required (and therefore don't need to
be migrated).
Check that ALL system and user databases have successfully been backed up
recently. Best place to check for this is within msdb.dbo.backupset.
Check within user databases if there are any unused indexes. Consider dropping
or disabling these to reduce the overall size of the database.
Check that a successful full database consistency check has been performed on all
user and system databases recently (DBCC CHECKDB WITH DATA_PURITY).
Check if the data purity bit has been flipped on user databases. If not, run DBCC
CHECKDB WITH DATA_PURITY.
In preparation for the migration, proactively migrate all relevant SQL Agent jobs
and supporting configuration (such as logins and proxies) and create these jobs
on the destination server. To prevent these jobs inadvertently executing, DISABLE
these jobs until the migration has been completed.
Ensure user databases have 'page_verify' set to CHECKSUM.
Check data and log file sizes for databases.
Check data and log file auto-growth settings and set to an appropriate value.
Check Virtual Log Files (VLFs) within the transaction log are appropriately sized.
Where applicable, setup maintenance tasks on target platform (such as index

rebuild, update statistics, consistency checks and backups).
Clean up test migrations using the Azure Migrate: Server Migration.
Notify the business and those affected by the migration maintenance window.
if using SQL Clusters and the migration is to new VMs and Windows Firewall is in
use, ensure Windows Firewall rules are open to allow failover clustering to
communicate between the VMs.
if using SQL Clusters, ensure Network Security Groups have allow rules for
failover cluster communication ports.
Consider all network devices (for example, NAT Gateways) between the source
VM and the replication appliance, and from there to Azure. Pay particular
attention to any limits in connection count, connection timouts on idle, and
bandwidth.
Consider all network devices (for example, NAT Gateways) between the source
VM and the replication appliance, and from there to Azure. Pay particular
attention to any limits in connection count, connection timouts on idle, and
bandwidth.
Review common replication bottlenecks through testing and validation.
Decide if replication bandwidth throttling is required. Increasing and decreasing

the replication bandwidth based on a time of day, day of week, etc basis is a
recommended consideration.
Decide if blackout windows are required to define intervals during which
replication is not allowed.
Consider using the Azure SQL Migration extension for Azure Data Studio with
DMS for migrating to Azure SQL Database as the target from SQL Server.
DMS for migrating to Azure SQL Managed Instance as the target from SQL Server.
DMS for migrating to SQL Server on Azure VMs with or without SQL Server Always
On Availability Groups as the target from SQL Server.
Plan to perform workload UAT during a test migration for each workload.
Deploy VMs in a suitable Hyper-V environment (e.g. non-production or unused
Hyper-V hosts) and perform test migrations of non-business workloads to Azure
to validate the toolset and procedure prior to test migrations of business
workloads.
Deploy physical machines or VMs and perform test migrations of non-business

workloads to Azure to validate the toolset and procedure prior to test migrations
of business workloads.
Deploy VMs in a suitable VMware environment (e.g. non-production) and
perform agentless test migrations of non-business workloads to Azure to validate
the toolset and procedure prior to test migrations of business workloads.
Deploy VMs in a suitable VMware environment (e.g. non-production) and

perform agent-based test migrations of non-business workloads to Azure to
validate the toolset and procedure prior to test migrations of business workloads.
Move app traffic over to the app running on the migrated Azure VM instance.
Remove the on-premises VMs from your local VM inventory.
Update any internal documentation to show the new location and IP address of
the Azure VMs.
Manually uninstall VMware tools after migration.
Manually uninstall the Mobility service from the Azure VM after migration.
Verify and troubleshoot any Windows activation issues on the Azure VM.
Install the Azure VM agent on Linux VMs after migration.
Factor stop replication duration into change management and cost

considerations.
Configure maintenance window for an Azure SQL database or elastic pool.
Configure maintenance window for an Azure SQL Managed Instance.
Confirm SME's have access to monitoring and observability resources.
Validate connectivity to the new Azure VM using RDP, SSH, Azure Bastion.
Plan to perform final workload UAT following the production migration for each
workload.
Decommission retired assets.
Perform post-migration activities.
Perform any post-migration app tweaks, such as updating database connection

strings, and web server configurations.
Configure Business continuity and disaster recovery for the Azure VM.
Ensure that the Azure VM is covered by Defender for Cloud.

Restrict network traffic as required with Network Security Groups.
Enable the serial console on Azure VMs to help with troubleshooting.
Configure an auto shutdown schedule for VMs that meet the business
requirements.
Confirm that workload monitoring is configured and complies with observability
requirements, configure any required alerts.
Confirm that migrated VMs are enrolled to Update management and is able to
receive security and feature updates.
Consider updating database compatibility for migrated databases to a tested and
supported level.
If SQL Agent jobs were migrated and left in a disabled state in the pre-migration
phase, enable them as required.
Ensure that server logins are successfully mapped to users within databases.
Update statistics across user databases.
If the target platform is SQL Server or SQL Managed Instance and if Service Broker
was enabled on source, check that it is enabled now on target. If not, enable.
If migrating to SQL Server on Azure VMs, check if 'TRUSTWORTHY' was enabled

for databases on source, then check if enabled on target. If not, enable.
Ensure that monitoring is collecting the desired information on the new SQL
platform.
Check the performance of the new system, and 'right size' based on actual
workload.
Setup automation to scale up/down and/or pause/start resources.
Consider enabling reserved capacity for migrated workloads.
Consider using the new business case capability in Azure Migrate to help build
business proposals to understand how Azure can bring the most value.
This shape represents a table slicer. Table slicers are not supported in this version of Excel.
If the shape was modified in an earlier version of Excel, or if the workbook was saved in Excel 2007 or earlier, the
slicer can't be used.
! High volume
of support
cases.
Description
The Azure Site Recovery Provider and MARS agent are installed on Hyper-V hosts running Windows
Server 2022, Windows Server 2019, Windows Server 2016, or Windows Server 2012 R2 with .Net
Framework 4.7 or later. Refer to the URL for guest VM support.
The decision determines whether the Azure Migrate appliance or the Azure Migrate Replication
appliance will be used.
VMware vCenter Server v5.5, 6.0, 6.5, or 6.7, and VMware vSphere ESXI host v5.5, 6.0, 6.5, 6.7 or 7.0 are
supported. Refer to the URL for guest VM support.
The sample DACI matrix should be updated to reflect the specific allocation of roles and responsibilities
for the migration project.
Refer to this when planning migration waves.
Refer to the sample risk register with common migration phase risks.
Azure Migrate: Migration is the primary tool for Migrations to Azure. Azure Site Recovery supports
Disaster Recovery scenarios
Ensure existing and historical on premises backups can be restored and retained in line with legal
requirements.
Consider using reserved backup storage for long term backup retention.
Decide if a 3rd party backup tool will be used, or if backups will be migrated to Azure Backup.
Will the customer use a third party solution or a key vault.

Who needs access post migration.
Ensure access to the current password and key management store is available to the migration team.
So they can manage the applications and have visibility of their health.
Ensure someone in the business is able to log in and manage these resources prior to migration.
Document any new SSL certs that will need to be purchased.
Confirm how the application license will be activated post migration. Note that some apps may rely on a
dongle, static MAC or IP address.
Ensure patches will be applied to migrated servers.
Ensure schedules, black out windows or alerts are configured for migrated servers.
Ensure AV exclusions are migrated or re-applied in Azure for migrated workloads.
Consider excluding the affected scope from the policies to resolve the issue.
An Azure Migrate project will be required for each target region.
The lack of permissions to create a VM, write to a managed disk and join to a VNET on TARGET
SUBSCRIPTION(s) is a frequent root cause on support cases.
Reboot Hyper-V to mitigate Token cache errors. May need to unregister/reregister provider with
project/recovery services vault.
VMware vCenter Server v5.5, 6.0, 6.5, or 6.7, and VMware vSphere ESXI host v5.5, 6.0, 6.5, 6.7 or 7.0 are
supported. Refer to the URL for guest VM support
Azure Migrate Discovery and Assessment tool (appliance) is a primary tool to discover (and then assess)
migrated estate.
Irrespective of Private or Public endpoint, certain URLs/FQDNs must be allowed outbound
When OVA Template/VHD method is not available for any reason, appliance can be deployed using
script method
Enable auto update for the appliance
Check appliance version
A/V exclusion best practices
Setup appliance using script.

Verify installer signature.
Azure Migrate Migration tool (based on ASR) is used.
Setup appliance using OVA Template method
Scale Discovery and assessment appliance
Discovery and assessment appliance for Azure Government
Owner or Contributor + User Access Administrator permissions to the subscription is required. Note:
Contributor WITHOUT UAA is a frequent root cause on support cases.
The replication appliance is required when you set up agent-based migration of either VMware VMs or
physical servers. Replication appliance is a form of the Azure Site Recovery (ASR) tool that can be used
for migration purposes.
The replication appliance is required when you set up agent-based migration of either VMware VMs or
physical servers. Replication appliance is a form of the Azure Site Recovery (ASR) tool that can be used
for migration purposes.
It is possible to do a manual dependency analysis based on documentation, application owner
interviews and/or using monitoring tools. A proven service like Azure Migrate is however recommended.
Azure Migrate appliance is recommended, but it is also possible to use a CSV file.
Setup appliance using VHD method
Azure migrate discovery and migration traffic is received over public endpoint by default which can be
altered using private endpoint/link services. Configuration should be chosen and implemented while
setting up Azure Migrate Project
Azure migrate discovery and migration traffic is received over public endpoint by default which can be
altered using private endpoint/link services. Configuration should be chosen and implemented while
setting up Azure Migrate Project
Refer to the Azure Migrate project properties in the Azure portal for a list of resources that would need
DNS name resolution.
Digital estate planning takes several forms depending on the desired outcomes and size of the existing
estate. Refer to the cloud adoption framework for different approaches.
Workloads should be documented with key properties and specifications, their existing architecture
design as well as the intended future architecture design.
Discovery support for Hyper-V environment
Discovery support for physical servers/other clouds
Discovery support for VMware environment
Discovery and assessment for SQL Server instances and databases is available across VMware, Microsoft
Hyper-V and Physical environments. MAP Toolkit and Cloudamize are alternatives.
Business requirements like and cost savings versus the trade-off with risk should be considered.
Assessments are point-in-time snapshots, they aren't automatically updated with the latest data.
Upgrading the Project Setting "Target Platform" will allow you to rebuild the solution and verify whether
the captured schema would be compatible with the new target platform.
Typical options include: SQL Server to Azure SQL Database, SQL Server to Azure SQL Managed Instance,
SQL Server to SQL Server on Azure VMs. Refer to the cloud adoption framework guidance for typical
criteria.
Azure Migrate is an option for lift-and-shift SQL Server to SQL Server on Azure VM scenarios. Azure
Database Migration Service however provides more options.
Azure Database Migration Service is a typical option for migrating SQL Server to Azure SQL Database,
SQL Managed Instance or SQL Server on Azure VM.
Azure Migrate can be used to get Azure SQL deployment recommendations, target sizing, and monthly
estimates.
Assess application dependencies, understand the readiness of SQL Servers migrating to Azure SQL, get
Microsoft recommendations, the optimal Azure SQL deployment option and right SKU that can fit the
performance needs for the workloads. Get monthly estimates running the databases on Azure SQL.
Assess migratable estate for readiness/estimates. Assessment is created in the portal using the
discovered data using Azure migrate appliance
The FTA landing zone checklist can be used to review a landing zone design.
Migration waves should be planned around the grouping of dependent services e.g. application tiers, the
criticality of services, the environment (non-production, production), the availability of acceptance
testers, the size of replication data, the available network bandwidth, the potential impact on the
hosting platform and its supporting services e.g. storage, etc.
Total storage directly affects bandwidth requirements during initial replication. However, storage drift
continues from the point of replication until release. Calculate the bandwidth needed to reach the
anticipated migration velocity.
Existing issues, minor host upgrades, minor guest OS upgrades, SLA modifications, reboot all machines
etc.
This is often the root cause in failover cluster instance migrations to SQL Server on Azure VMs.
Estimate costs.
Perform right-sizing for virtual machines (VMs) and storage.
Use Azure Hybrid Benefit.
Use Azure Reserved VM Instances, Reserved storage, Reserved backup storage.
Compare Azure Savings plans and burstable instances.
Estimate cloud spending across subscriptions.
Target legacy workloads to access Microsoft extended security updates.

Microsoft maintains a list of server software that is officially supported on Azure VMs.
Single-step: Staging process doubles as the promotion process. After all assets are staged, end-user
traffic is rerouted and staging becomes production. In such a case, promotion is part of the migration
process.
Staged: In a staged promotion model, the workload is considered migrated after it's staged, but it isn't
yet promoted. Before promotion, the migrated workload undergoes a series of performance tests,
business tests, and optimization changes. It's then promoted at a future date with a business test plan.
Flight: In a flight model, the assets in the workload are treated like production after landing in staging.
After a condensed period of automated testing, production traffic is routed to the workload. However,
it's a subset of the traffic. That traffic serves as the first flight of production and testing. Assuming the
workload works from a feature and performance perspective, more traffic is migrated. After all
production traffic has been moved onto the new assets, the workload is considered fully promoted.
In addition to the generic landing zone design and implementation that needs to precede a workload
migration, specific architecture planning is also required for each workload. Workloads may have
different requirements wrt network, availability services, management and security.
Use the assessment reports to identify low-hanging fruit, including servers and databases that are fully
ready, and require minimal effort to migrate to Azure.
Encryption-at-rest with platform-managed key

Encryption-at-rest with customer-managed key
Double encryption with platform-managed and customer-managed keys
Availability Set
Availability Zone
No infrastructure redundancy required option
It is recommended that additional domain controllers be built and replicated to using AD DS services
rather than migrated.
Configure alerting.
Prepare a rollback plan for the workload in case of workload issues during or after migration. Note: Once
you've performed a final migration to Azure and the on-premises source machine was shut down, you
can't perform a rollback from Azure to your on-premises environment using Azure Migrate. Any rollback
plan after final migration would need to be based on features external to Azure Migrate e.g. backups
and restore.
When migrating to SQL Server: https://learn.microsoft.com/en-us/sql/relational-databases/security/

encryption/move-a-tde-protected-database-to-another-sql-server?view=sql-server-ver16
When migrating to SQL MI: https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/tde-
certificate-migrate?view=azuresql&tabs=azure-powershell
https://github.com/microsoft/tigertoolbox/tree/master/BPCheck
The SQL Server Product Group have a script that can check for unused indexes (and many more best
practices). https://github.com/microsoft/tigertoolbox/tree/master/BPCheck
For SQL 2016 or above, you can use DATABASEPROPERTYEX to view the 'LastGoodCheckDbTime'
https://learn.microsoft.com/en-us/sql/t-sql/functions/databasepropertyex-transact-sql?view=sql-
server-2017.
For SQL 2014 and earlier, use DBCC DBINFO.
You only need to run a Data Purity assessment once successfully, as this will flip the purity bit
Lots of methods to migrate these objects. Consider the community PowerShell module
https://dbatools.io/
With modern CPUs, the performance impact of using checksum is inconsequential with significant
benefits to the consistency of the database.
https://learn.microsoft.com/en-us/sql/relational-databases/policy-based-management/set-the-page-
verify-database-option-to-checksum?view=sql-server-ver16
Are they appropriately sized? If they have a lot of unused space, consider shrinking the files to reduce
disk space requirements on the target platform.
Check that database data files ALL auto-growth settings are the same size within each filegroup.
Check that database data files ALL have the same auto-growth settings.
http://adventuresinsql.com/2009/12/a-busyaccidental-dbas-guide-to-managing-vlfs/
Consider a standard meeting invite that includes the migration plan and a conference bridge to discuss
any open items during the migration.
Failure to complete replication, due to insufficient bandwidth on NAT gateways for internet bound
access, has been a root cause of incidents.
Failure to complete replication, due to insufficient bandwidth on NAT gateways for internet bound
access, has been a root cause of incidents.
The replication speed of initial migration has many factors to consider. Usually the appliance is in Hyper-
V as a VM and its disks reside in a data store.
Possible bottlenecks:
1. Replication bandwidth between appliance and Azure / Storage account. Monitor connection e.g.
ExpressRoute. Test speed between appliance and cache storage account using azcopy bench.
2. Monitor appliance performance for CPU/RAM/Network (inbound and outbound) as well as disk IOPS.
3. Replication bandwidth between the Hyper-V host and appliance.
4. Source VM disk IOPS.
5. Combination of the above.
Trigger an initial replication to monitor and benchmark all of the above.
The replication speed of initial migration in a Migrate Appliance infrastructure, has many factors to
consider.
1. Replication bandwidth between appliance and Azure / storage account. Monitor connection e.g.
3. Replication bandwidth between the physical or other cloud VM and appliance.
4. Source physical or other cloud VM disk IOPS.
The replication speed of initial migration in a Migrate Appliance infrastructure, has many factors to
consider. Usually the appliance is in vCenter as a VM and its disks reside in a data store.
1. Replication bandwidth between appliance and Azure / storage account. Monitor connection e.g.
3. Replication bandwidth between the ESXi host and appliance.
4. Source VM disk IOPS.
You can increase or decrease the replication bandwidth using the NetQosPolicy.
Customers may prefer to schedule replication during non-business hours or off-peak periods. Replication
issues during periods when there are resource contention is a frequent root cause for support incidents.
DMS supports Schema and offline data migration scenarios. Consider Cloudamize, Attunity and Striim for
online migration scenarios.
DMS supports Schema, offline and online data migration scenarios.
DMS supports Schema and offline data migration scenarios. Consider Azure SQL Migration extension,
Cloudamize, Attunity and Striim for online migration scenarios.
Use a non-production vnet and subnet to host and validate the VMs as part of the test migration.
The procedure and migration tooling should be initially tested with no (or low, potentially only
bandwidth consumption) business impact.
Including application as-built and architecture documentation.
The Azure VM agent manages VM interaction with the Azure Fabric Controller. It's required for some
Azure services, such as Azure Backup, Site Recovery, and Azure Security. When migrating VMware VMs
with agent-based migration, the Mobility Service installer installs Azure VM agent on Windows
machines. On Linux VMs, it is recommend to install the agent after migration.
As a best practice, always complete the migration after a VM has migrated successfully to Azure to
ensure that extra charges for storage transactions on the intermediate managed disks (seed disks) are
not incurred. Be mindful that in some cases, stop replication takes time. It is because whenever
replication is stopped, the ongoing replication cycle is completed (only when the VM is in delta sync)
before deleting the artifacts. The time taken to stop replication has a high volume of support incidents.
Conduct handover training so the teams can self manage alerts and thresholds.
Test that alerts, api or helpdesk integration is working.
Set up service health alerts for these teams to notify them of any service deprecations.
Set up Azure advisor alerts.
Use Azure Cost Management + Billing

Monitor resource utilization
Implement resource group budgets
Benchmark and resize cloud assets
Optimize storage
Automate VM optimization
Use Azure Logic Apps and runbooks with Budgets API
Implement serverless technologies
Azure Backup
Azure Site Recovery
Refer to the workload template for auto shutdown business decisions.
Confirmation that migrated workload is successfully monitored and required alerts are configured.
Recommended to pre-script in TSQL.

https://learn.microsoft.com/en-us/sql/relational-databases/databases/view-or-change-the-
compatibility-level-of-a-database?view=sql-server-ver16#TsqlProcedure
You can do this via the GUI in SSMS or ADS, but it is recommended to script this process to avoid error
https://learn.microsoft.com/en-us/sql/ssms/agent/disable-or-enable-a-job?view=sql-server-ver16
If you have pre-created logins and then restored user databases, it's important that the logins and users
are mapped correctly.
https://learn.microsoft.com/en-us/sql/sql-server/failover-clusters/troubleshoot-orphaned-users-sql-
server?view=sql-server-ver16
This is an optional step post migration. New versions of SQL Server & Azure SQL improve the 'update
stats' algorithms, so by updating them post migration, you are ensuring that the database has fresh
statistics and reducing the risk of plan regressions.
https://learn.microsoft.com/en-us/sql/t-sql/statements/update-statistics-transact-sql?view=sql-server-
ver16
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/sql-server-service-broker?view=sql-server-ver
Note this is applicable to SQL Server only.

https://learn.microsoft.com/en-us/sql/relational-databases/security/trustworthy-database-property?
view=sql-server-ver16
https://learn.microsoft.com/en-us/azure/azure-monitor/insights/azure-sql
End-to-end application monitoring will give the best visibility. For SQL specific monitoring, it is
recommended to utilise https://learn.microsoft.com/en-us/azure/azure-monitor/insights/azure-sql.
An advantage the cloud provides is to quickly 'try' differenent configurations and then measure the
performance of the application
It's very important to build resiliancy into this process. For example, there scale up/down process should
monitor if the action was successful, and either attempt n times or notify an operator. It is
recommended scaling occurs on a schedule, not triggered by the performance of the system.
Here is an example of how to build: https://github.com/azureautomation/azure-sql-database-scale-
using-scheduled-autoscaling
For Azure SQL & SQL MI: https://learn.microsoft.com/en-us/azure/azure-sql/database/reserved-

capacity-overview?view=azuresql
For SQL Server on Azure VMs, utilise VM reservation and Hybrid Use Benefit where applicable
Understand the ROI for migrating servers, SQL Server and ASP.NET web apps running in a VMware
environment to Azure. Including:
On-premises vs Azure TCO and YoY cashflow.
Resource utilization-based insights to identify servers and workloads that are ideal for cloud and right-
sized recommendations in Azure.
Quick wins for migration and modernization including end of support Windows OS and SQL versions.
Long term cost savings by moving from a capital expenditure model to an Operating expenditure model
This shape represents a table slicer. Table slicers
are not supported in this version of Excel.
ier, the
If the shape was modified in an earlier version of
Excel, or if the workbook was saved in Excel 2007
or earlier, the slicer can't be used.
Incident Root
Severity Status
Cause Alert
Medium Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified

High Not verified
Medium Not verified

High Not verified
Low Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified

High Not verified
High Not verified
Medium Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified

High Not verified
High Not verified
High Not verified
Medium Not verified
Medium Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified
Medium Not verified
High Not verified
High Not verified

High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified
High Not verified
Medium Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified

Medium Not verified
Medium Not verified
Medium Not verified
High Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified
Medium Not verified
Medium Not verified
Medium Not verified
High Not verified
High Not verified
Low Not verified
High Not verified
Medium Not verified
Medium Not verified
High Not verified
High Not verified
High Not verified

High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified
High Not verified
Medium Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified

High Not verified
Medium Not verified
Medium Not verified
Low Not verified
High Not verified
Medium Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified
Medium Not verified

High Not verified
High Not verified

High Not verified
High Not verified
Medium Not verified

Medium Not verified
Medium Not verified
Medium Not verified
Medium Not verified
Low Not verified
Medium Not verified
Medium Not verified
Medium Not verified
High Not verified
Medium Not verified
Medium Not verified
Medium Not verified
Medium Not verified
Low Not verified

Medium Not verified
High Not verified

High Not verified
Medium Not verified
High Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified
Low Not verified

Medium Not verified
Medium Not verified
Medium Not verified
High Not verified

High Not verified
High Not verified
High Not verified
High Not verified
High Not verified

Low Not verified
Low Not verified
Medium Not verified

Medium Not verified
High Not verified
Medium Not verified
High Not verified

Medium Not verified
Medium Not verified
Low Not verified
High Not verified
High Not verified
High Not verified

High Not verified
High Not verified
High Not verified
High Not verified

High Not verified
High Not verified
High Not verified
High Not verified
High Not verified
Medium Not verified
Medium Not verified
Medium Not verified

Low Not verified
High Not verified
High Not verified
Medium Not verified
Medium Not verified
Low Not verified
Medium Not verified
Medium Not verified

r. Table slicers
f Excel. TIP Select 'all
environments' for
rlier version of generic content VMware
along with the
ed in Excel 2007 specific source
environment(s)
Guest VM --> Agent Agentless

Server Migration
Azure
Migrate Azure
Appliance / Host --> Replication Migrate
appliance
appliance
Comment
Hyper-V Physical
Agentless Agentless Agent
Microsoft Azure Site Recovery Azure

Azure Migrate
Migrate provider and Microsoft Azure
appliance Recovery Service agent on Hyper-V Replication
Hosts or cluster nodes appliance
Url
Cloud adoption plan
Support for Hyper-V migration in Azure Migrate
Support for VMware migration in Azure Migrate
Project Plan Template

DACI matrix
DACI matrix
Risk Register
Migration Templates
SQL Server to Azure SQL Database: Migration guide
SQL Server to Azure SQL Managed Instance: Migration guide
SQL Server to SQL Server on Azure Virtual Machines: Migration guide

Azure Migrate vs. Azure Site Recovery
8. Workload'!A1
8. Workload'!A1
8. Workload'!A1
8. Workload'!A1
8. Workload'!A1
8. Workload'!A1
8. Workload'!A1
Can I use the same Azure Migrate project to migrate to multiple regions?
Can I use the same Azure Migrate project to migrate to multiple subscriptions?
Remove servers and disable protection

Azure Migrate appliance
Azure Migrate appliance
How to setup appliance using scripts for VMware/Hyper (When OVA/VHD option not available)
Azure Migrate appliance - Auto-update
Azure Migrate appliance - Version
Azure Migrate appliance - Antivirus
Tutorial to setup Physical server/other cloud discovery

Azure Migrate appliance - Physical
Support for physical server migration in Azure Migrate
Tutorial to Setup an appliance for VMware
Azure Migrate appliance - Scale out VMware
Deploy appliance script government
Create and manage projects
Azure Migrate replication appliance
Azure Migrate replication appliance
Dependency analysis in Azure Migrate Discovery and assessment
Provide server credentials to discover software inventory, dependencies, web apps, and SQL Server instances and databas
Discover and Assess servers using an imported CSV file
Tutorial to Set up appliance for Hyper-V
Azure Migrate appliance scale out - Hyper-V
Azure Migrate appliance scale out- Physical
Use Azure Migrate with private endpoints
Azure Migrate Connectivity
Migrate servers to Azure by using Private Link
Migrate servers to Azure by using Private Link
Troubleshoot network connectivity issues
Digital Estate Discovery Template

Approaches to digital estate planning
Why are we moving to the cloud?
Workload Template
Hyper-V discovery support
Physical server/other cloud discovery support
VMware discovery support
Discover SQL Server instances in an existing Azure Migrate project
Assessment best practices in Azure Migrate Discovery and assessment tool
Download SQL Server Data Tools (SSDT)
Azure Database Migration Guides
Compare SQL data migration tools
Azure DMS tools matrix - business justification

Create an Azure SQL assessment
Creating Azure Migrate assessments
SQL Server to Azure SQL Managed Instance: Performance baseline

Azure Landing Zone
Migration Wave Template
Evaluate network readiness for planned migration activities
Remediating assets prior to migration
Support for Hyper-V migration in Azure Migrate
Network security group - how it works
Best practices before migration to Azure
What are extended security updates?

Microsoft server software support for Azure VMs
Promotion model types
Design workload architectures before migration
Build a migration plan with Azure Migrate
Enable customer-managed keys with SSE
Overview of managed disk encryption options
Availability options for Azure Virtual Machines
Prepare machines for migration with Azure Migrate
Common questions about Azure Migrate Server Migration

Is there a Rollback option for Azure Migrate?
Move a TDE-protected database to another SQL Server

Viewing the SQL Server Error Log
Viewing the SQL Server Error Log
SQL Server Agent
SQL Server Agent
backupset (Transact-SQL)
Indexes - SQL Server
DBCC CHECKDB (Transact-SQL)
DBCC CHECKDB (Transact-SQL)
SQL Server Agent
Set the PAGE_VERIFY Database Option to CHECKSUM
Display data & log space info for a database
Considerations for the autogrow and autoshrink
Transaction Log Architecture and Management Guide
Maintenance Plans
Configure a load balancer & availability group listener

Configure a load balancer & availability group listener
NAT gateways - Amazon Virtual Private Cloud
azcopy bench
azcopy bench
Agentless replication of VMware virtual machines concepts
Blackout window
Migrate databases by using the Azure SQL Migration extension for Azure Data Studio
Migrate databases by using the Azure SQL Migration

extension for Azure Data Studio
Migrate databases by using the Azure SQL Migration

extension for Azure Data Studio
Business testing guidance during migration
Tutorial Migrate Hyper-V VMs
Tutorial Migrate physical server to Azure
Tutorial Migrate VMware VMs using agentless method
Tutorial Migrate VMware VMs using agent-based method
Troubleshoot Windows virtual machine activation problems in Azure
Migrate VMware VMs with agent-based Azure Migrate Server Migration

Configure maintenance window - Azure SQL Database
Configure maintenance window - Azure SQL Database
Azure Bastion
Decommission retired assets
Decommission retired assets

Best practices after migration to Azure
Azure Backup
Microsoft Defender for Cloud

Azure network security groups
8. Workload'!A1
Monitoring Azure virtual machines
Azure Automation Update Management
ALTER DATABASE compatibility level (Transact-SQL)
SQL Server Agent
Create a Database User

Statistics
SQL Server Service Broker
TRUSTWORTHY Database Property
Monitor your SQL deployments with SQL Insights (preview)
Scale resources - Azure SQL Database
Save compute costs with reserved capacity
Build a Business case with Azure Migrate

AWS GCP
Agent Agent
Azure
Azure Migrate
Migrate Replication
appliance
More information
Resource Assignment
Resource Assignment
Cloud Adoption Framework Tools and Templates

Azure Private Endpoint DNS configuration
Gather inventory data for a digital estate - Cloud Adoption Framework

Azure Database Migration Service tools matrix
SSDT Database Project Settings
Migrate SQL Server databases to Azure
Azure DMS tools matrix - premigration phase

Compare SQL data migration tools
Support matrix for VMware/Physical Server

Support matrix for VMware/Physical Server
Collect baseline: Performance best practices & guidelines - SQL Server on Azure VMs
FTA Landing Zone Review
Replication and the migration process
Migrate failover cluster instance - SQL Server on Azure VMs

Migrate TDE certificate - managed instance
Create a Login - SQL Server
Shrink a database - SQL Server
Failover Cluster communication ports

Failover Cluster communication ports
replication bandwidth throttle script


Build a migration plan with Azure Migrate
Tests migrate replicating virtual machines

Connect using Remote Desktop to an Azure VM running Windows
Benchmark and resize cloud assets
Azure Site Recovery

Azure Reserved Virtual Machine Instances
Migration Project Plan
Visualize and track your migration projects using this template. To start, enter the tasks you're working on in the Milestone description section and then enter details for each task. The data will automatically update and it’s easy to insert new tasks or use the scrollbar to scroll through the timeline.
• Use Progress to add how much of the project you finished by adding a percentage number.
• Add the day you started your project in the Project Start Date.
• Finish your calculations by filling in the number of days you need to complete your project in the Total Days to deliver field.
Migration Project Title
Company name Contoso Total Days to deliver: 114 Legend: Complete On Track Low Risk Med Risk High Risk Unassigned Step
Migration Architect Rita Tsakiris Days Delivered so far: #NAME?
Project Start Date: 3/11/2023 Percent project delivered: #NAME? March April May June
TIP Scroll bar
Scrolling View Offset (Auto): 0 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9
Days Complete
Days of Work
Days Delayed
Overlap Days
Lag Days
Dependenc Start Date
Mon
Mon
Mon
Mon
Mon
Wed
Wed
Wed
Wed
Wed
Mon
Wed
Mon
Wed
Mon
Wed
Mon
Wed
Mon
Wed
Mon
Wed
Mon
Wed
Mon
Wed
Milestone description Category Id Assigned to Dependency Progress % Start Date End Date
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Thu
Sun
Thu
Sun
Thu
Sun
Thu
Thu
Tue
Tue
Tue
Tue
Tue
Tue
Tue
Tue
Tue
Tue
Tue
Tue
Tue
Thu
Thu
Thu
Thu
Thu
Thu
Thu
Thu
Sun
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Sat
Fri
Fri
Fri
Fri
Fri
Fri
Fri
Fri
Fri
Fri
Fri
Fri
Fri
y Type Override
Step 18 #NAME? 0.0 3/11/2023 3/11/2023 #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Project Start
Project Start
Goal 19 1 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Project Start Step
Project Start Step
Step 20 End Date #NAME? 0.0 #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
PLANNING
PLANNING
On Track 21 Rita Tsakiris 1 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Align the migration project with the cloud adoption plan
Align the migration project with the cloud adoption
Complete 22 Ebere Ibeabuchi 1 2 plan End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Assign resources to project
Low Risk 23 Ebere Ibeabuchi 3 2 End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Create a risk register
PLANNING
Liaise with service management team to create migration change Low Risk 24 Ebere Ibeabuchi 1 6 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
request forms
PLANNING
Low Risk 25 Ebere Ibeabuchi 1 6 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Create a project repository with all templates
Low Risk 26 Rita Tsakiris 2 End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Conduct a business workhop
Liaise with service management team to create
Low Risk 27 Rita Tsakiris 3 migration change request forms End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Conduct a technical workhop
PLANNING
DIGITAL ESTATE DISCOVERY
On Track 29 Rita Tsakiris 5 2 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Perform a digital estate discovery and populate template
Perform a digital estate discovery and populate
Milestone 30 Rita Tsakiris 2 template End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Liaise with business to complete digital discovery and migration scope
Liaise with business to complete digital discovery and
Low Risk 31 1 migration scope End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
…
TOOLING
TOOLING
On Track 33 Rita Tsakiris 1 1 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Define migration tooling and get business signoff on approach
Define migration tooling and get business signoff on
Med Risk 34 Alexandra Voronova 2 3 approach End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Create Azure Migrate project in Contoso production subscription
Create Azure Migrate project in Contoso production
High Risk 35 Alexandra Voronova 2 subscription End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Install Azure Migrate appliance in Apollo data centre
Install Azure Migrate appliance in Apollo data centre
Goal 36 2 End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
…
TOOLING
DISCOVERY
DISCOVERY
Confirm discovery support compatibility in a VMware environment for Low Risk 38 Alexandra Voronova 1 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
the digital estate
Confirm discovery support compatibility in a VMware
Low Risk 39 Alexandra Voronova 1 1 environment for the digital estate End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Discover servers in Apollo datacentre using Azure Migrate
Discover servers in Apollo datacentre using Azure
Goal 40 1 1 Migrate End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
…
DISCOVERY
ASSESSMENT
ASSESSMENT
Med Risk 42 Alexandra Voronova 15 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Perform AS-IS assessment using Azure Migrate
ASSESSMENT
Med Risk 43 Alexandra Voronova 5 10 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Perform PERFORMANCE-BASED assessment using Azure Migrate
Perform PERFORMANCE-BASED assessment using
Milestone 44 1 Azure Migrate End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
…
ASSESSMENT
WAVE 01|PRE-MIGRATION
Low Risk 46 Rita Tsakiris 15 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Wave 01 Planning
Wave 01 Planning
High Risk 47 Alexandra Voronova 5 End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Evaluate network readiness for planned migration activities.
Evaluate network readiness for planned migration
Milestone 48 1 activities. End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
…
WAVE 01|MIGRATION
WAVE 01|MIGRATION
Med Risk 50 Alexandra Voronova 15 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Perform test migration of selected workloads
Perform test migration of selected workloads
Milestone 51 Alexandra Voronova 1 End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Migration of selected workloads
Migration of selected workloads
Med Risk 52 Alexandra Voronova 1 End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
Test migration cleanup
Test migration cleanup
53 1 End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
…
WAVE 01|MIGRATION
WAVE 01|POST-MIGRATION
WAVE 01|POST-MIGRATION
Move app traffic over to the app running on the migrated Azure VM High Risk 55 Alexandra Voronova 15 Start Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
instance.
Move app traffic over to the app running on the
56 5 migrated Azure VM instance. End Date #NAME? ### #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
…
Project Duration Step - DO NOT TOUCH WAVE 01|POST-MIGRATION
INSERT TASKS/ROWS ABOVE THIS
To add more data, Insert new rows ABOVE this STEP (PROJECT END) and Project Duration Step - DO NOT TOUCH
fill the progress & dates formulas Goal 58 1 INSERT TASKS/ROWS ABOVE THIS Start Date #NAME? ### #NAME? #NAME? #NAME? ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
The purpose of the digital estate discovery is to This shape represents a tab
present an inventory of applications and services to slicer. Table slicers are not
the business in order to determine the scope and supported in this version o
nature of a migration project. Excel.
Important dates should be captured and mapped
to milestones in the project plan. If the shape was modified
Digital Estate an earlier version of Excel
Discovery or if the workbook was
used.
Discovery Data
Date Centre Workload SLA Description Redundancy
Lunar Orbit
Friday, December 1, 2023 Apollo Control 99.99% … Geographic
Sundial
calendar
Friday, December 1, 2023 Luna II management 99.95% … Local
Airship
navigation
Friday, December 1, 2023 Apollo system 99.90% … No redundancy
Carburettor air
and fuel Backup and
Friday, December 1, 2023 Luna II supply 99.50% … Restore
Complaints
Friday, December 1, 2023 Apollo management 95.00% … Geographic
Lunar Orbit
Friday, December 1, 2023 Luna II Control 99.90% … Local
Friday, December 1, 2023 Apollo Infobahn 99.90% … No redundancy

Vacuum tube
order Backup and
Friday, December 1, 2023 Luna II processing 99.50% … Restore
Sundial
calendar
Friday, December 1, 2023 Apollo management 99.90% … Geographic
Buggy whip
time
Friday, December 1, 2023 Luna II management 99.50% … Local
Pulse phone
distribution
Friday, December 1, 2023 Apollo system 99.90% … No redundancy
Backup and
Friday, December 1, 2023 Luna II Dialtone Vibes 99.50% … Restore
Fax is life
Friday, December 1, 2023 Apollo server 99.90% … Geographic
Quaternary
glaciation
Friday, December 1, 2023 Luna II scheduling 99.50% … Geographic
ICALPTDAHJ
Friday, December 1, 2023 Apollo Search Engine 99.95% … Geographic
This shape represents a table This shape represents a table This shape represents a table This shape represents a tabl
slicer. Table slicers are not slicer. Table slicers are not slicer. Table slicers are not slicer. Table slicers are not
supported in this version of supported in this version of supported in this version of supported in this version of
Excel. Excel. Excel. Excel.
If the shape was modified in If the shape was modified in If the shape was modified in If the shape was modified in
an earlier version of Excel, an earlier version of Excel, an earlier version of Excel, an earlier version of Excel,
or if the workbook was or if the workbook was or if the workbook was or if the workbook was
saved in Excel 2007 or saved in Excel 2007 or saved in Excel 2007 or saved in Excel 2007 or
earlier, the slicer can't be earlier, the slicer can't be earlier, the slicer can't be earlier, the slicer can't be
used. used. used. used.
Revenue Business Technical

Compliance Impacting Users Business Unit Owner Owner Environment
Data retention
(7 years) Yes 100 Rocket Unit … … Production
Backup
retention Human
(5 years) No 10 Resources … … Production
Log retention
(2 years) Yes 500 Transport … … Production
SOC-2 Yes 10 Transport … … Production
ISO 27001 Yes 10 Client Services … … Production
None Yes 10 Rocket Unit … … Production
None Yes 10 Transport … … Production
None Yes 10 Manufacturing … … Production
Human
None No 10 Resources … … Development
Human
None Yes 10 Resources … … Production
None Yes 10 Communications … … Production

None Yes 10 Geo Unit … … Production
None No 1 OOTheCEO … … Production

This shape represents a table This shape represents a table This shape represents a table This shape represents a
slicer. Table slicers are not slicer. Table slicers are not slicer. Table slicers are not table slicer. Table slicers are
supported in this version of supported in this version of supported in this version of not supported in this version
Excel. Excel. Excel. of Excel.
If the shape was modified in If the shape was modified in If the shape was modified in If the shape was modified in
an earlier version of Excel, an earlier version of Excel, an earlier version of Excel, an earlier version of Excel,
or if the workbook was or if the workbook was or if the workbook was or if the workbook was
saved in Excel 2007 or saved in Excel 2007 or saved in Excel 2007 or saved in Excel 2007 or
earlier, the slicer can't be earlier, the slicer can't be earlier, the slicer can't be earlier, the slicer can't be
used. used. used. used.
i Significant dates e
i Common cloud exit datacentre b
migration and <date>
modernization
drivers
Business End-of-life
Servers App Type Criticality Lifecycle Date Business Drivers
Commercial
Off-The-Shelf Mission Data centre
5 (COTS) Critical Not defined Not defined contract expiration.
Hardware end-of-
2 Custom Low 5 Years Thursday, January 1, 2026 life.
Commercial
Off-The-Shelf Mission End-of-support
5 (COTS) Critical Long-term Saturday, January 1, 2050 operating systems
End-of-support
4 Custom High < 1 Year Wednesday, November 1, 2023 software
Commercial
Off-The-Shelf Mission Under-provisioned
10 (COTS) Critical Long-term Saturday, January 1, 2050 servers
Over-provisioned
2 Custom Medium Long-term Saturday, January 1, 2050 servers
Commercial
Off-The-Shelf Mission Cybersecurity
4 (COTS) Critical Long-term Saturday, January 1, 2050 threats
Cash flow
challenges,
5 Custom Low 1-3 Years Sunday, November 1, 2026 CAPEX to OPEX
Commercial
Off-The-Shelf Mission Budget and
2 (COTS) Critical Long-term Saturday, January 1, 2050 resource constrains
Rapidly scale web
apps and
5 Custom High 5 Years Thursday, January 1, 2026 infrastructure
Commercial
Off-The-Shelf Mission Application
4 (COTS) Critical Long-term Saturday, January 1, 2050 innovation
Cost-optimizing
10 Custom Medium < 1 Year applications
Commercial
Off-The-Shelf Mission Faster time to
2 (COTS) Critical Long-term Saturday, January 1, 2050 market
Enabling hybrid
4 Custom Low 5 Years Thursday, January 1, 2026 work
Access Microsoft
Extended Security
Updates for Legacy
2 Custom High Not defined Not defined Workload
This shape represents a This shape represents a table This shape represents a table
table slicer. Table slicers are slicer. Table slicers are not slicer. Table slicers are not
not supported in this version supported in this version of supported in this version of
of Excel. Excel. Excel.
If the shape was modified in If the shape was modified in If the shape was modified in
an earlier version of Excel, an earlier version of Excel, an earlier version of Excel,
or if the workbook was or if the workbook was or if the workbook was
saved in Excel 2007 or saved in Excel 2007 or saved in Excel 2007 or
earlier, the slicer can't be earlier, the slicer can't be earlier, the slicer can't be
used. used. used.
i Significant dates e.g.

exit datacentre by
<date>
Migration Decisions Financial

Milestone On-premises
Date Priority Rationalization Tooling Promotion Cost
Friday, March 15, 2024 High Rehost Azure Migrate Single-step …
Friday, March 15, 2024 High Rehost Azure Migrate Staged …
Friday, March 15, 2024 High Rehost Azure Migrate Flight …
Friday, March 15, 2024 High Refactor … Single-step …
Friday, March 15, 2024 Medium Rearchitect … Staged …
Friday, March 15, 2024 Medium Rebuild … Flight …
Friday, March 15, 2024 High Rearchitect … Single-step …
Friday, March 15, 2024 Medium Retire … Staged …
Friday, March 15, 2024 Medium Refactor … Flight …
Friday, March 15, 2024 Low Rehost … Single-step …
Friday, March 15, 2024 Low Rehost Azure Migrate Staged …

Friday, March 15, 2024 High Rearchitect … Flight …
Friday, March 15, 2024 High Rebuild … Single-step …
Friday, March 15, 2024 High Refactor … Staged …
Friday, March 15, 2024 High Rehost Azure Migrate Staged …

Financial Approvals
Cloud Migration Business Technical Migration Approval Scheduled Start
Cost Cost Owner Owner Architect Date Migration Date
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024

… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … … Monday, January 1, 2024
… … … … … Monday, January 1, 2024

The purpose of the workload resource is This shape represents a table
to document and map the current slicer. Table slicers are not
technical attributes of the individual supported in this version of
components of a workload to the future Excel.
attributes of the migrated state.
The information in this resource is used as If the shape was modified in

Workload input when configuring replication and an earlier version of Excel, or
Template migration options. if the workbook was saved in
Excel 2007 or earlier, the
It is also an important input to pre-and- slicer can't be used.
post tasks that form the migration-day
runbook.
Analysis Migration Migration Risk

Date Date Workload Risk Mitigation
Perform UAT
and use a flight
Lunar Orbit promotion
Friday, December 1, 2023 Monday, January 1, 2024 Control High model
Perform UAT
and use a flight
Lunar Orbit
Friday, December 1, 2023 Monday, January 1, 2024 Control High Not applicable
Lunar Orbit
Friday, December 1, 2023 Monday, January 1, 2024 Control High Not applicable
Lunar Orbit
Friday, December 1, 2023 Monday, January 1, 2024 Control Medium Not applicable
Perform UAT
and use a flight
Friday, December 1, 2023 Monday, January 1, 2024 Control Medium model
Perform UAT
and use a flight
Lunar Orbit
Lunar Orbit
Lunar Orbit
Friday, December 1, 2023 Monday, January 1, 2024 Control Low Not applicable
Low
High
High
High
High
ents a table This shape represents a table This shape represents a This shape represents a table
rs are not slicer. Table slicers are not table slicer. Table slicers are slicer. Table slicers are not
version of supported in this version of not supported in this version supported in this version of
Excel. of Excel. Excel.
modified in If the shape was modified in If the shape was modified in If the shape was modified in
of Excel, or an earlier version of Excel, an earlier version of Excel, an earlier version of Excel, or
was saved in or if the workbook was or if the workbook was if the workbook was saved in
lier, the saved in Excel 2007 or saved in Excel 2007 or Excel 2007 or earlier, the
d. earlier, the slicer can't be earlier, the slicer can't be slicer can't be used.
used. used.
Known
Environment Machine Issues Type Platform Firmware
Production prd-w-loc-01 None VM VMware N/A
Services do not start

Production prd-w-loc-02 automatically on reboot. VM VMware N/A
Services startup need to be

Test tst-w-loc-01 sequenced. VM VMware N/A
Memory leak in application.
Server is restarted every 3
UAT uat-w-loc-01 weeks. VM VMware N/A
Current open support case

with application vendor to
Development dev-w-loc-01 address batch update bug. VM VMware N/A
Production prd-wcn-loc-01 None VM VMWare N/A
Production prd-wcn-loc-02 None VM VMWare N/A
Test tst-wcn-loc-01 None VM VMWare N/A

UAT uat-wcn-loc-01 None VM VMWare N/A
Development dev-wcn-loc-01 None VM VMWare N/A

resents a table This shape represents a table This shape represents a table This shape represents a table
cers are not slicer. Table slicers are not slicer. Table slicers are not slicer. Table slicers are not
is version of supported in this version of supported in this version of supported in this version of
Excel. Excel. Excel.
s modified in If the shape was modified in If the shape was modified in If the shape was modified in
on of Excel, or an earlier version of Excel, an earlier version of Excel, or an earlier version of Excel,
k was saved in or if the workbook was if the workbook was saved in or if the workbook was saved
earlier, the saved in Excel 2007 or Excel 2007 or earlier, the in Excel 2007 or earlier, the
used. earlier, the slicer can't be slicer can't be used. slicer can't be used.
used.
Operating
System Role Traffic Shared Service Authentication Location
Windows
Server 2016 Apollo Data
Standard Application Node Internal-Facing No NTLM Centre
Yes, this server is

also used by the
Windows Sundial Calendar
Server 2016 Management Apollo Data
Standard Application Node Internal-Facing workload Oauth Centre
Windows
Server 2016
Standard Application Node Internet-facing No Kerberos Luna II
Windows
Server 2016
Standard Application Node Internal-Facing No Kerberos Luna II
Windows
Server 2016
Standard Application Node Internet-facing No Kerberos Luna II
Windows
Server 2016 Database Cluster Apollo Data
Standard Node Internal-Facing No Kerberos Centre
Windows
Server 2016 Database Cluster Apollo Data
Standard Node Internal-Facing No Kerberos Centre
Windows
Server 2016 Database Cluster
Standard Node Internal-Facing No Kerberos Luna II
Windows
Windows
represents a table This shape represents a table This shape represents a table
e slicers are not slicer. Table slicers are not slicer. Table slicers are not
n this version of supported in this version of supported in this version of
Excel. Excel.
was modified in If the shape was modified in If the shape was modified in
ersion of Excel, an earlier version of Excel, or an earlier version of Excel,
rkbook was saved if the workbook was saved in or if the workbook was saved
07 or earlier, the Excel 2007 or earlier, the in Excel 2007 or earlier, the
be used. slicer can't be used. slicer can't be used.
Data System Password Routine Outage Change

Support Classification Access Access Window(s) Management
Last Friday of the Standard

Geo Services Server Team month 6pm - 7am Request for
(Internal) Non-business Service Request Password Vault Saturday Change process

Central IT Server Team month 6pm - 7am Request for
(Internal) Public Service Request Password Vault Saturday Change process
Last Friday of the

Vendor Server Team month 6pm - 7am
(External) General Service Request Password Vault Saturday Not applicable
Last Friday of the
Vendor Server Team month 6pm - 7am
(External) Confidential Service Request Password Vault Saturday Not applicable
Last Friday of the

Vendor Highly Server Team month 6pm - 7am

Vendor Highly Server Team month 6pm - 7am Request for
(External) Confidential Service Request Password Vault Saturday Change process

Vendor Highly Server Team month 6pm - 7am Request for
(External) Confidential Service Request Password Vault Saturday Change process
Last Friday of the

Last Friday of the
Last Friday of the

Update and
Change New Release App Hardware Summary of Operating Capacity:
Freeze Cycles Vendor Vendor Dependencies Hours Cores
Monthly
updates to
coordinates
database.
Quarterly OS Database cluster:
updates. prd-wc-loc-01
Annual LOC Application
1 December to firmware server: prd-w-loc-
15 January updates. … … 02 24x7 …
Monthly
updates to
coordinates
database.
Quarterly OS Database cluster:
updates. prd-wc-loc-01
Annual LOC Application
Last week of firmware server prd-w-loc-
every month updates. … … 01 24x7 …
Monthly
updates to
coordinates
database.
Quarterly OS
updates. Database cluster:
Annual tst-wc-loc-01
firmware File Server: tst-
Not applicable updates. … … wfs-01 8x5 …
Monthly
updates to
coordinates
database.
Quarterly OS
updates.
Annual
firmware Database cluster:
Not applicable updates. … … uat-wc-loc-01 8x5 …
Monthly
updates to
coordinates
database.
Quarterly OS
updates.
Annual
firmware Database cluster:
Not applicable updates. … … dev-wc-loc-01 8x5 …
Monthly
updates to
coordinates
database.
Quarterly OS
updates. Application server:
Annual prd-w-loc-01
1 December to firmware Application server:
15 January updates. … … prd-w-loc-02 24x7 …
Monthly
updates to
coordinates
database.
Quarterly OS
updates. Application server:
Annual prd-w-loc-01
1 December to firmware Application server:
15 January updates. … … prd-w-loc-02 24x7 …
Monthly
updates to
coordinates
database.
Quarterly OS
updates.
Annual
firmware Application server:
Not applicable updates. … … tst-w-loc-01 8x5 …
Monthly
updates to
coordinates
database.
Quarterly OS
updates.
Annual
Not applicable updates. … … uat-w-loc-01 8x5 …
Monthly
updates to
coordinates
database.
Quarterly OS
updates.
Annual
Not applicable updates. … … dev-w-loc-01 8x5 …
Capacity: Capacity: Load Firewall Antivirus Service
Memory Disk Balancing Rules Exclusions Certificates Accounts
… … F5 … None Private Domain
… … None … None None Local
HTTPS inbound
… … Citrix (TCP 443) None Public Localsystem
… … None … None None Domain
HTTPS inbound Domain, Local and

… … Citrix (TCP 443) None Public Localsystem
Always On
availability
… … group None None Domain
Always On
availability
… … group None None Domain
Windows
… … Failover Cluster None None Domain
Windows
Windows
SOURCE: ON-PREMISES/OTHER CLOUD
Batch Services
Time App / Scheduled SMTP Print Client
Services Licensing Tasks Relay Services App
Yes, LocApp
Stratum 1 Time hosted on Citrix
Server Dongle None None None farm prd-c01
Scheduled Tasks Yes, on-premises Yes, on- Yes, LocApp

Stratum 1 Time Static IP run as Domain authenticated premises print hosted on Citrix
Server Address account SMTP relay server farm prd-c01
Yes, LocApp
Stratum 1 Time MAC hosted on Citrix
Server Address None None None farm tst-c01
Yes, LocApp
Server License key None None None farm uat-c01
Yes, LocApp
Server License key None None None farm dev-c01
Stratum 1 Time
Server License key None None None Not applicable
Stratum 1 Time
Stratum 1 Time
Stratum 1 Time
Stratum 1 Time
ER CLOUD
Client App Workload IP Address File Database

DNS DNS Change Services Database Authentication
AD integrated
DNS, between
AD integrated App and Yes, prd-wc-loc-
DNS Database roles No impact Local only 01 Windows
AD integrated
DNS, between
AD integrated App and Yes, prd-wc-loc-
DNS Database roles No impact Local only 01 Windows
AD integrated
DNS, between
App and Remote File Yes, tst-wc-loc-
No Database roles Breaks App Server 01 SQL
AD integrated
DNS, between
App and Yes, uat-wc-loc- Mixed SQL and
No Database roles Breaks App Local only 01 Windows
AD integrated
DNS, between
App and Yes, dev-wc-loc- Mixed SQL and
No Database roles Breaks App Local only 01 Windows
AD integrated
DNS, between
Not applicable Database roles Breaks App Local only 02 Windows
AD integrated
DNS, between
AD integrated
DNS, between
AD integrated
DNS, between
AD integrated
DNS, between
Source
Environment
Disaster CSPM Update Technical Target Load
Recovery Backup & SIEM Management Architecture Balancing
Microsoft
Endpoint
Configuration Azure Internal
None SCDPM 2022 None Manager 2207 <link> Load Balancer
Microsoft
Endpoint
Configuration
None SCDPM 2023 None Manager 2208 <link> None
Microsoft
Endpoint Azure
Configuration Application
None SCDPM 2024 None Manager 2209 <link> Gateway
Microsoft
Endpoint
Configuration
None SCDPM 2025 None Manager 2210 <link> None
Microsoft
Endpoint
Configuration Azure Front
None SCDPM 2026 None Manager 2211 <link> Door
Microsoft
Endpoint Always On
Configuration availability
None SCDPM 2027 None Manager 2212 <link> group
Microsoft
Endpoint Always On
Microsoft
Endpoint Always On
Microsoft
Endpoint Always On
Microsoft
Endpoint Always On
Target Firewall Target Amtivirus Target Target Service Target Time Target App
Rules Exclusions Certificates Accounts Services Licensing
Default
(time.windows.c
om and host Convert to
… Private Retain time) license key
Default
(time.windows.c
om and host Convert to new
… None Retain time) IP address
Default
Create new (time.windows.c
HTTPS inbound domain service om and host Convert to
(TCP 443) Public accounts time) license key
Default
(time.windows.c
om and host Reuse license
… None Retain time) key
Default
(time.windows.c
HTTPS inbound om and host Reuse license
(TCP 443) Public Retain time) key
None, traffic is Default

not passing (time.windows.c
through Azure om and host Reuse license
Firewall None None Retain time) key
None, traffic is
not passing
through Azure
Firewall
None, traffic is
not passing
through Azure
Firewall
None, traffic is
not passing
through Azure
Firewall
None, traffic is
not passing
through Azure
Firewall
Target Batch
Services or Target SMTP Target Print Target Client Target Client Target
Scheduled Tasks Relay Services App App DNS Workload DNS
Migrate client
app to AVD Migrate to
None None None hosted app Azure DNS Retain
Migrate client
Convert to Migrate to app to AVD Migrate to
Retain SendGrid Universal Print hosted app Azure DNS Retain
Migrate client
app to AVD
None None None hosted app None Retain
Migrate client
app to AVD
Migrate client
app to AVD
None None None Not applicable Not applicable Retain
None Not applicable Not applicable Retain


TARGET: CLOUD
Target Backup
IP Address Target File Target Database Target Disaster and backup
Change Plan Services Target Database Authentication Recovery continuity plan
Azure Backup,
prd-wc-loc-01 is retain SCDPM
migrated in the Azure Site for historic data
Not required Local only same wave Windows Recovery restore
Azure Backup,
prd-wc-loc-01 is retain SCDPM
migrated in the Azure Site for historic data
Update line-of-
business
application to Azure Backup,
use DNS alias Migrate to tst-wc-loc-01 is no requirement
instead of IP Azure Storage migrated in the Azure Site for historic
address. Account same wave Windows Recovery restore
Update line-of-
business
application to Azure Backup,
use DNS alias uat-wc-loc-01 is no requirement
instead of IP migrated in the Azure Site for historic
address. Local only same wave Windows Recovery restore
Azure Backup,
dev-wc-loc-01 is no requirement
migrated in the Azure Site for historic
Always On
availability Azure Backup,
group to no requirement
secondary for historic
Not required Local only Not applicable Windows region restore
Always On
availability Azure Backup,
group to no requirement
secondary for historic
Not required Local only Not applicable Windows region restore
Azure Backup,
no requirement
Restore from for historic
Not required Local only Not applicable Windows Azure Backup restore
Azure Backup,
no requirement
Azure Backup,
no requirement
Target CSPM & Target Update Selected Azure Availability Scheduled Auto
SIEM Management Sizing Option VM Size Option Shutdown
Defender for
Cloud &
Microsoft Azure Update Performance- Standard_D64_v
Sentinel Management based 4 Availability Set No
Defender for
Cloud &
Microsoft Azure Update Performance- Standard_D64_v
Sentinel Management based 4 Availability Set No
Defender for
Cloud &
Microsoft Azure Update Performance- Standard_D64_v Single-node Yes, only 8x5
Sentinel Management based 4 Availability Set online required
Defender for
Cloud &
Microsoft Azure Update On-premises Standard_D32_v Single-node Yes, only 8x5
Sentinel Management capacity 4 Availability Set online required
Defender for
Cloud &
Microsoft Azure Update On-premises Standard_D32_v Yes, only 8x5
Sentinel Management capacity 4 Availability Zone online required
Defender for
Cloud &
Microsoft Azure Update On-premises Standard_D32_v
Sentinel Management capacity 5 Availability Zone No
Defender for
Cloud &
Microsoft Azure Update On-premises Standard_D32_v
Sentinel Management capacity 6 Availability Zone No
Defender for
Cloud &
Defender for
Cloud &
Defender for
Cloud &
Cloud
Azure Reserved Technical
Hybrid Benefit VM Instances Disk Encryption Disks Replicated Target Disk Type Architecture
Encryption-at-
rest with
platform-
Yes … managed key All Standard SSD <link>
Encryption-at-
rest with
customer-
Yes … managed key All Standard SSD <link>
Double
encryption with
platform-
managed and
customer-
No … managed keys All Standard SSD <link>
Encryption-at-
rest with
platform-
No … managed key C|D|E|M|O Premium <link>
Encryption-at-
rest with
customer-
Yes … managed key C|D|E|M|O Premium <link>
Encryption-at-
rest with
customer-
Yes … managed key C|D|E|M|O Standard SSD <link>
Encryption-at-
rest with
customer-
Encryption-at-
rest with
customer-
Encryption-at-
rest with
customer-
Yes … managed key All Ultra <link>
Encryption-at-
rest with
customer-
Yes … managed key All Ultra <link>
The purpose of a wave plan is to document the workloads that
will be grouped together in a single migration sprint.
Dependent services are typically included in the same Migration
Wave.
In the portal you can select up to 10 VMs at once for migration.

Wave Plan To migrate more machines, add them to groups in batches of
Template 10.
Definition Migration Wave

Date Start Date Number Workload
Friday, December 1, 2023 Monday, January 1, 2024 Lunar Orbit Control
ads that This shape represents a table This shape represents a table This shape represents a table
slicer. Table slicers are not slicer. Table slicers are not slicer. Table slicers are not
supported in this version of supported in this version of supported in this version of
Migration Excel. Excel. Excel.
migration. If the shape was modified in If the shape was modified in If the shape was modified in
ches of an earlier version of Excel, or an earlier version of Excel, an earlier version of Excel,
if the workbook was saved in or if the workbook was or if the workbook was saved
Excel 2007 or earlier, the saved in Excel 2007 or in Excel 2007 or earlier, the
slicer can't be used. earlier, the slicer can't be slicer can't be used.
used.
Source
Machine Operating System Migration Engineer Environment Environment
Windows Server 2016

dev-w-loc-01 Standard Alexandra Voronova Development Hyper-V
Windows Server 2016

tst-w-loc-01 Standard Alexandra Voronova Test VMware Agentless
Windows Server 2016

uat-w-loc-01 Standard Alexandra Voronova UAT VMware Agentless
Windows Server 2016

prd-w-loc-01 Standard Alexandra Voronova Production Physical or other Cloud
Windows Server 2016

prd-w-loc-02 Standard Alexandra Voronova Production Hyper-V
hape represents a table This shape represents a table This shape represents a table This shape represents a table
Table slicers are not slicer. Table slicers are not slicer. Table slicers are not slicer. Table slicers are not
rted in this version of supported in this version of supported in this version of supported in this version of
Excel. Excel. Excel.
shape was modified in If the shape was modified in If the shape was modified in If the shape was modified in
lier version of Excel, an earlier version of Excel, an earlier version of Excel, an earlier version of Excel,
he workbook was saved or if the workbook was or if the workbook was or if the workbook was
el 2007 or earlier, the saved in Excel 2007 or saved in Excel 2007 or saved in Excel 2007 or
can't be used. earlier, the slicer can't be earlier, the slicer can't be earlier, the slicer can't be
used. used. used.
i The region for the project
cannot be changed after the
first replication is initiated.
Please select the region
carefully.
Target
Target Target Final
Migration Migration Target Target Final Final Resource Availability
Methodology Group Subscription Region VNET Subnet Group Option
Single-node
ASR Provider + <subscription <resource Availability
MARS agent 1 name> <region> <vnet> <subnet> group> Set
Single-node
Azure Migrate <subscription <resource Availability
appliance 2 name> <region> <vnet> <subnet> group> Set
Azure Migrate No
appliance <subscription <resource infrastructure
(Government) 2 name> <region> <vnet> <subnet> group> redundancy
Azure Migrate
Replication <subscription <resource Availability
appliance 3 name> <region> <vnet> <subnet> group> Zone
ASR Provider + <subscription <resource Availability

MARS agent 3 name> <region> <vnet> <subnet> group> Zone
presents a table
licers are not
this version of
was modified in
sion of Excel,
kbook was
el 2007 or
cer can't be
Initial
Disk Initial Replication Replication Delta Replication
Disk Encryption Type Start Date Status Start Date
Encryption-at-
rest with
platform-
managed key Standard SSD Monday, January 1, 2024 Passed Monday, January 1, 2024
Encryption-at-
rest with
customer-
managed key Standard SSD Monday, January 1, 2024 Failed Monday, January 1, 2024
Double
encryption with
platform-
managed and
customer-
managed keys Standard SSD Monday, January 1, 2024 Passed Monday, January 1, 2024
Encryption-at-
rest with
platform-
managed key Premium Monday, January 1, 2024 Failed Monday, January 1, 2024
Encryption-at-
rest with
customer-
managed key Premium Monday, January 1, 2024 Passed Monday, January 1, 2024
Test Test Test Resource Test Migration Test Migration Test Migration
VNET Subnet Group Start Date UAT Status UAT Owner
<vnet> <subnet> <resource group> Monday, January 8, 2024 Passed Gowri Kalluri
<vnet> <subnet> <resource group> Monday, January 15, 2024 Failed Gowri Kalluri
<vnet> <subnet> <resource group> Monday, January 22, 2024 Passed Gowri Kalluri
<vnet> <subnet> <resource group> Monday, January 29, 2024 Failed Gowri Kalluri
<vnet> <subnet> <resource group> Monday, February 5, 2024 Passed Gowri Kalluri
Final Migration Final Migration Final Migration Replication Digital Estate
Start Date UAT Status UAT Owner Completed Planning
Monday, January 15, 2024 Passed Gowri Kalluri No 8. Digital Estate'!A1
Monday, January 22, 2024 Failed Gowri Kalluri No 8. Digital Estate'!A1
Monday, January 29, 2024 Passed Gowri Kalluri No 8. Digital Estate'!A1
Monday, February 5, 2024 Failed Gowri Kalluri No 8. Digital Estate'!A1
Monday, February 12, 2024 Passed Gowri Kalluri No 8. Digital Estate'!A1

Migration Day
Workload Details Runbook
8. Workload'!A1 8. Runbook'!A1
The purpose of a migration-day runbook is to provide migration engineers with a proven list of tasks to perform duri
The migration runbook below is an example of what should be created for every machine, in all environments, for ea
PRODUCTION MACHINE:
Promotion Plan
Model:
Notes:
Task Id
Pre-001
Pre-002
Pre-003
Pre-004
Pre-005
Pre-006
Pre-007
Pre-008
Pre-009
Pre-010
Pre-011
Pre-012
Pre-013
Pre-014
Pre-015
Pre-016
Pre-017
Task Id
Mig-001
Mig-002
Mig-003
Mig-004
Mig-005
Mig-006
Mig-007
Mig-008
Mig-009
Mig-010
Mig-011
Mig-012
Mig-013
Mig-014
Mig-015
Mig-016
Mig-017
Task Id
Post-001
Post-002
Post-003
Post-004
Post-005
Post-006
Post-007
Post-008
Post-009
Post-010
Post-011
Post-012
Post-013
Post-014
Post-015
Post-016
Migration-D
The purpose of a migration-day runbook is to provide migration engineers with a proven list of tasks to perform during test and produ
Audience:
The migration runbook below is an example of what should Engineers,
be created Project
for every Managers
machine, in all environments, for each workload.
PRODUCTION MACHINE: WORKLOAD [LUN

Promotion Plan
Flight
Treated like production directly after migration.

2 hours of automated testing.
30% of production traffic will be routed to the workload for 2 days in FLIGHT 1.
Production UAT within 2 days.
70% of traffic is routed after 2 days and UAT pass.
Pre-Migration Tasks
Provide access to on-premises server (<server>) to the migration team.
Validate <server> health and application functionality prior to any changes.
Raise a change request for <server> and communicate outage as part of change request.
Manually configure the SAN policy as Online All for machine as OS is earlier than Windows Server 2008 R2.
Request firewall ports to be opened in Azure.
Verify VMware server requirements.
Verify VM requirements for migration.
Verify Azure settings. On-premises VMs you replicate to Azure must comply with Azure VM requirements.
Confirm <server> has been discovered in Azure Migrate.
Review <server> Azure Migrate assessment.
Remediate issues identified in the Azure Migrate assessment.
Reboot the server to confirm it boots up without error.
Enable replication:
Azure Migrate appliance: <>
vCenter Server: <>
Process Server <replication appliance>
Guest Credentials: <VM Admin account>
Virtual Machines: <server>
Import migration settings from an Azure Migrate assessment: Yes (VM sizing and disk type)
Availability options: <Availability Zone|Set|No>
Target settings: <subscription><region><resource group>
Virtual Network: <VNET/Subnet>
Cache storage account: <default>
Disk encryption type: <>
Azure Hybrid Benefit: <Yes><No>
Disks: <disks to be replicated>
Tags: <>
Confirm successful replication status.
Run a test migration.
Validate <server> health and application functionality.
Clean up test migration.
Migration Tasks
Change the TTL on your DNS to be short so changes will replicate quicky post migration.
Pause monitoring alerts or notify the relevant teams to ignore alerts during migration.
Notify testing teams, managed service providers and business SME's.
Migrate <server>
Shut down virtual machines and perform a planned migration with no data loss, select Yes > OK.
Update DNS for the new Azure VM.
Validate VM size, OS, allocated disks, drive letters and network configuration of the new VM in Azure.
Validate Network Security Group (NSG) configuration.
Verify and troubleshoot any Windows activation issues on the Azure VM.
Update database connection strings on <server>.
Move on-premises traffic to the migrated Azure VM instance by pointing the DNS record to the new IP address.
Connect clients to the application hosted by the new Azure VM and validate <server> health and application functionality.
Validate <server> health and application functionality.
Request approval from business owner to decommission the on-premises application on <server>.
GO/NOGO decision for <server>.
NOGO: Rollback the changes using the rollback plan and update the migration project governance team.
GO: Communicate the change to users and update the migration project governance team.
Stop replication. Validate that <server> has been removed from the replicating servers count in Azure Migrate.
Post-Migration Tasks
Disable on-premises monitoring, backup and update management for <server>.
Apply AV exclusions to new server.
Validate new resource tags with business owners.
Remove the on-premises <server> from the asset management inventory.
Update application as-built and architecture documentation to reflect the changes.
Manually uninstall the Mobility service from the new Azure VM.
Manually uninstall VMware tools from the new Azure VM.
Clean up any old hardware devices from the VM that are no longer required or in a failed state.
Configure Azure Backup for the new Azure VM.
Install Azure Monitor Agent and create Service Health alerts for the new Azure VM.
Configure the new Azure VM for Azure Site Recovery replication to the secondary region.
Ensure the new Azure VM is covered by Defender for Cloud and that endpoint protection has been enabled.
Validate connectivity to the new Azure VM using RDP, SSH, Azure Bastion.
Ensure the new Azure VM is configured for Update Management.
Once validated and finalized request signoff from the respective stake holders and transition to the business-as-usual supp
Notify the CMDB team to update configuration item records and confirm the on-premises <server> for decommission.
book
ation windows.
CONTROL] SERVER [prd-w-loc-01]
Promotion model types - Cloud Adoption Framework
Change Window
Duration
Approved Owner (hours) Start DateTime End DateTime Server
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
0
… … 1 9/23/2022 0:00 9/23/2022 1:00 …

… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
Change Window
Approved Owner Duration Start DateTime End DateTime Server
0
0
0
… … 1 9/23/2022 0:00 9/23/2022 1:00 …

… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …

… … 0 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
Change Window
Approved Owner Duration Start DateTime End DateTime Server
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
0
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
0
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
… … 1 9/23/2022 0:00 9/23/2022 1:00 …
Notes
<UAT procedure>
<CR>
procedure
<Ports>
requirements
requirements
requirements
discovery
review assessment
<step-by-step details>
replicate
validate
test migration
<UAT procedure>
test migration
Notes
migrate
<NSG details>
activation
<db connection details>
<DNS details>
<UAT procedure>
<decommission
approval>
<rollback plan>
stop replication
Notes
<tags>
Migrati
The purpose of the request for change template is to provide migration specific details for consideration by the
It is also an additional checkpoint to help ensure that important migration decisions are made and relevant tas
Change Authority.
Approve architecture changes before migration
Item
Requestor Name:
Request Date:
Urgency:
Project Name:
Description:
Reason for Change:
Resource Requirements:
Business Drivers for Change:
Requested Change Start Date and Time:

Estimated Change End Date and Time:
Estimated Duration:
Estimated Risk:
Business Disruption Anticipated:
Business Communication Plan:
Workload Name:
Workload Business Owner:
User Acceptance Test:
User Acceptance Tester Name:
Migration Wave Number:

Migration Wave Plan
Migration Workload Plan:
Promotion Model:
Migration Type:
Has a Test Migration been done?
What was the outcome of the Test Migration?
When was Replication first enabled?
What is the estimated end date for Replication?
Has the network bandwidth been considered and validated with the network
team?
Will Replication cleanup be done as part of this change?
Will Hybrid Benefits be used for this migrated machine?
Will Azure Reserved VM Instances be used for this migrated machine?
Document the Azure Reserved Instance Details
Has an SR been raised to remove the existing asset from the asset management
register?
Has an SR been raised to remove the existing asset from the CMDB?
Has an SR been raised to decommission the existing asset monitoring?
Has an SR been raised to decommission the existing asset backup?
Has an SR been raised to decommission the existing asset SIEM configuration?
Has an SR been raised to remove the existing asset from geo-replicated DR?
Has the existing technical architecture and as-built documentation been updated?
Has an SR been raised to onboard the new VM to Azure Monitor?
Has an SR been raised to onboard the new VM to Azure backup?
Has an SR been raised to onboard the new VM to Microsoft Defender for Cloud?
Has an SR been raised to onboard the new VM to Microsoft Sentinel?
Has an SR been raised to onboard the new VM to Azure Site Recovery and start
Replication to another region?
Will scheduled auto shutdown be configured for this service?
Will traffic be cut over to the new service?
Has an end user communication been drafted?
Has a Test Plan been created?
Has a Rollback Plan been created?
Has a Transition to CCoE plan been created?
Should there be an allowance for Troubleshooting/Remediation time?

Allowed Remediation Time:
Approver:
Approved:
Approval Date:
Migration Request for Change
specific details for consideration by the business, service management and migration teams for inclusion in their change management
on decisions are made and relevant tasks carried out. It is recommended to seek approval early, clarify expectations and roles of approv
Value
<Requestor Name>
<datetime>
[Urgent|Expedited|Standard]
<Project Name>
<Project Description>
<Change Reason>
<Resources involved with this change>
<Business Drivers>
<datetime>
<datetime>
<days|hours>
[High|Medium|Low]
[Yes|No]
[Yes|No]
<Workload name>
<Workload owner name and contact information>
[Yes|No]
<UAT Tester Name>
<Wave nn>
[Yes | No]
[Yes | No]
[Single-step|Staged|Flight]
[Test|Final]
[Yes|No]
[Successful|Success with remediation|Failed]
<datetime>
<datetime>
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
<details>
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes |No]
[Yes |No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[Yes|No]
[60 | 90 | 120 | 180 | 240] minutes
<Approver Name>
[Yes | No]
<datetime>
nclusion in their change management process.
clarify expectations and roles of approvers in advance and to establish a Cloud
Notes
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
8. Wave'!A1
8. Workload'!A1
Promotion model types
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
Azure Hybrid Benefit for Windows Server
<detail>
Understand Azure Reserved VM Instances discount
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
Applies only where services are not required to be online 24x7.
<detail>
<detail>
<detail>
<detail>
<detail>
<detail>
The risk register is an important part of every migration project. The
purpose of this example is to detail common risks that need to be
evaluated along with any available mitigation, along with plans to
migrate services that are subject to these risks.
Risk Register
i Common risks
and issues
Id Workload Risk
Service not in support matrix of the selected
risk-001 Airship Navigation System migration tooling.
risk-002 Carburettor Air and Fuel Supply Service is past end-of-life.
risk-003 Complaints Management Service with no business owner.

risk-004 Lunar Orbit Control Service with no technical support owner.
risk-005 The White Dot Generator Service with no vendor support.
risk-006 Vacuum Tuben Service with no documentation.

risk-007 Sundial Calendar Management Service with no UAT procedure.
risk-008 Buggy Whip Time Management Service with no pre-production environment.

No access to data centre where services are hosted,
risk-009 Pulse Phone Distribution System and limited ability to deploy appliances.
No access to services due to service provider/partner
risk-010 All contractual lockout.
Service with software that is not supported on Azure.
Refer to
https://docs.microsoft.com/en-US/troubleshoot/azur
e/virtual-machines/server-software-support for more
risk-011 Dialtone Vibes information.
OS run by servers do not support agentless
risk-012 Astronavigationtrix dependency analysis.
On-premises servers that are to be migrated to Azure

are already configured for Azure Site Recovery, and
hence cannot be replicated with the selected
Quaternary Glaciation migration tooling option i.e. agent-based and Azure
risk-013 Scheduling Migrate Replication appliance.
Project resources are not available due to BAU

risk-014 All activities.
Project delays as a result of Architect review board
time to approve Landing zone and/or application
risk-015 All architectures.
Project delays as a result of a lack of coordination of
risk-016 All tasks and steps.
Project delays due to a lack of buy-in and ownership
risk-017 All from Application owners.
Project delays as a result of a lack of decision making
risk-018 All accountability.
Workload needs to be migrated to a different target

region from where the Azure Migrate project was
Quaternary Glaciation created in (and the other in scope workloads need to
risk-019 Scheduling be migrated to).
project. The This shape represents a table slicer. This shape represents a table slicer. This shape represents a table
eed to be Table slicers are not supported in Table slicers are not supported in slicer. Table slicers are not
th plans to
this version of Excel. this version of Excel. supported in this version of
Excel.
earlier version of Excel, or if the earlier version of Excel, or if the If the shape was modified in
workbook was saved in Excel 2007 workbook was saved in Excel 2007 an earlier version of Excel,
or earlier, the slicer can't be used. or earlier, the slicer can't be used. or if the workbook was
used.
Status Date Identified Category Date Resolved Severity

Tuesday, August 16, 2022 Friday, September 16, 2022
Technical
Technical
Tuesday, August 16, 2022 …
Business
Tuesday, August 16, 2022 Business …
Business

Business
Tuesday, August 16, 2022 Business Friday, September 16, 2022

Business
Business
Business
Technical
Technical
Technical

Project
Project
Project
Business
Business
Friday, October 7, 2022 Friday, October 7, 2022
Technical
This shape represents a table This shape represents a table slicer. This shape represents a table slicer.
slicer. Table slicers are not Table slicers are not supported in Table slicers are not supported in
supported in this version of this version of Excel. this version of Excel.
Excel.
If the shape was modified in earlier version of Excel, or if the earlier version of Excel, or if the
an earlier version of Excel, workbook was saved in Excel 2007 workbook was saved in Excel 2007
or if the workbook was or earlier, the slicer can't be used. or earlier, the slicer can't be used.
used.
Business Owner Technical Owner Support Business Criticality
… … Internal Mission Critical
… … External <vendor> Mission Critical
… … External <vendor> High

… … External <vendor> Medium

… … External <vendor> Medium
… … External <vendor> Low
… … Internal High
… … Internal Medium
… … Internal Mission Critical

s shape represents a table slicer. This shape represents a table slicer.
ble slicers are not supported in Table slicers are not supported in
version of Excel. this version of Excel.
he shape was modified in an If the shape was modified in an

lier version of Excel, or if the earlier version of Excel, or if the
rkbook was saved in Excel 2007 workbook was saved in Excel
earlier, the slicer can't be used. 2007 or earlier, the slicer can't be
used.
Mitigation
Airship ticket sales are at an all time low.
Look into fuel injection technology.

The system is about to be replaced with the Zero Complaints
service framework.
Go around again.
Keep it on.
Transistor-based replacement is a WIP.

Tempus machina will displace this system.
Recover from backup.
Access via service provider can be arranged.
Access via service provider can be arranged.
RRAS will be replaced with VPN.

Perform a manual dependency analysis using network packet
captures, or install the MMA and dependency agents.
Agentless migration using the Azure Migrate appliance is

compatible with Azure Site Recovery.
Extend project timelines with approval.

…
Date
Action Plan Approver Approved
Fresh install in the cloud. … Monday, January 2, 2023
Modernise service in a separate project. … Monday, January 2, 2023
Assign a business owner. … Monday, January 2, 2023

Assign a technical owner. … Monday, January 2, 2023
Upgrade before migration and engage a Service Provider to
provide vendor support. … Monday, January 2, 2023
Investigate service, including use of Azure Migrate dependency
analysis. Document architecture and create a user acceptance test
plan. … Monday, January 2, 2023
Modernise … Monday, January 2, 2023
Obtain business approval to migrate without pre-production
prerequisite then take application offline and capture a resource
consistent snapshot to serve as a rollback plan. … Monday, January 2, 2023
Engage service provider to carry out the appliance and agent
installation. … Monday, January 2, 2023
Engage service provider to carry out the appliance and agent
installation. … Monday, January 2, 2023
Keep RRAS on-premises until it is fully replaced by the new VPN.

Prioritise the VPN project to meet business milestones. … Monday, January 2, 2023
Allow additional time to perform the dependency analysis and
then migrate along with dependencies. … Monday, January 2, 2023
Migrate using the agentless migration method with the Azure

Migrate appliance. … Monday, January 2, 2023
Employ a partner or ensure that project resources are dedicated

to the project and hand-off their BAU responsibilities. … Monday, January 2, 2023
Ensure that review time SLA's are set prior to the project plan
being finalised and review time is built into project plan … Monday, January 2, 2023
Assign a project manager … Monday, January 2, 2023

Clearly documented and communicated Cloud transformation
strategy from Executive sponsor … Monday, January 2, 2023
Establish a steering committee that will be responsible for driving
project success … Monday, January 2, 2023
Create an Azure Migrate project and related infrastructure in the

target region. … Monday, January 2, 2023
More information
…
…
…
…
…
…
Can I use the same Azure Migrate project to migrate to multiple regions?

MEG v0.71

Uploaded by

Copyright:

Available Formats

MEG v0.71

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MEG v0.71

Uploaded by

Copyright:

Available Formats

FastTrack for Azure

The Migration Execution Guide

Developed by a team of FastTrack for Azure Program Managers and E

0.1 Initial draft

Review the available Microsoft programs and funding

Work through the below steps, or navigate directly to a topic of interest.

Digital Estate Discovery Template

Risk Register Template

uidance to the business, project management and technical teams.

Azure Migrate|Project Plan|Risk Register|Resource Management|Server Migration

rectly to a topic of interest.

FastTrack for Azure

Azure Migration and Modernization Program

Azure Migration and Modernization Program (partner-led)

Azure Analytics and AI Accelerate Program

FTA Landing Zone Design

FTA Cloud Roles and

Q003 What are the number of users for each workload?

Q004 What is the cloud rationalization decision for each workload?

Q005 Are there any compliance requirements for the workloads?

Q006 Where is each workload located?

Q007 Do the workloads have geographic redundancy?

Q008 Are the workloads production or non-production systems?

Q009 What is the app type for each workload?

Q010 What is the business criticality that is assigned to each workload?

Q018 What is the current SLA for each workload?

Q019 Will the migration be into an existing landing zone?

Is there a requirement for the capability to restore historic backups of the

Q026 What is the current and future plans for patching?

Q035 How many servers are there in each workload?

Q036 Known issues/last successful reboot?

Q037 How do users and related services authenticate to the app?

Q038 Is any part of the workload considered to be a shared service?

Q039 Is the workload load balanced?

For each workload, is external access required, or is the workload internal

Q042 Are SSL certs used, what names, private/public?

Q043 What service accounts are used by the system?

Q044 What currently provides time synchronization service?

Q046 How is the app licensed?

Q049 Is an SMTP relay used by the workloads?

Q050 What are the file services requirements?

Are there AV exclusions that need to be applied if it moves to a new

Q052 What is the current backup and restore method?

Q055 How is DB authentication handled?

Q056 How can access to the workloads be arranged?

Is there an access management process that need to be followed for the

Q058 How are updates and new releases handled?

Q059 What is the support model for the app?

Q060 What is the current DR/BCP strategy, target state?

Q061 Are the workloads subject to change freeze?

Q062 Are the workloads subject to change control?

Q066 What is the impact of changing an IP address on your workloads?

Description Template Workshop

Digital Estate Business

Digital Estate Business

Data centre and location. Digital Estate Business

Digital Estate Business

Document the workload environment. Digital Estate Business

Is it a commercial-off-the-shelf (COTS), or custom app? Digital Estate Business

Mission critical, high, medium, low, etc. Digital Estate Business