Basic Navigation

Migration Playbook is organized around work areas and entities.  A work area is dedicated to a specific set of tasks to be performed. Each work area provides a targeted collection of entities for working in that area. In some cases, the same entity appears in more than one area. The Application and Server entities, for example, appear in multiple work areas. Use the work-area menu to navigate between work areas.

Entities represent a specific type of data, such as a contacts, accounts, applications, application stacks, servers, migration waves, etc. Entities use a structured data format, which defines the collection of fields available to the entity. Each entity consists of a collection of individual records. For example, for the Contact entity, each record describes a single person, and each record includes a collection of fields such as first name, last name, and email address. Entities normally present two views: a list view, which is typically a table listing available records; and a form view, which shows all available data and settings for a single record. 

Read more about the Power Apps Unified Interface 

Basic Features

The following features have received positive feedback from other Migration Playbook users. 

Capabilities of the Solution

One of the most important elements for a successful migration to the cloud is well defined and executed business processes. Migration Playbook is aligned to Microsoft's Cloud Adoption Framework. The solution provides information support for strategy and planning activities.  During the execution phase, business processes available within the solution include; 1) Assess Applications,  2) Architect Workloads, 3) Manage Migration Wave, 4) V2V Migration, 5) Net New Migration.  Processes and business rules are easily customized or added to support the requirements of your migration initiatives.  

Read more about the Cloud Adoption Framework
 

Develop Cloud Adoption Strategy

The Cloud Adoption Framework is the One Microsoft approach to cloud adoption in Azure, consolidating and sharing best practices from Microsoft employees, partners, and customers. The framework gives customers a set of tools, guidance, and narratives that help shape technology, business, and people strategies for driving desired business outcomes during their adoption effort.

Migration Playbook provides the following capabilities to enhance the Cloud Adoption Framework, managing project deliverables and providing a focus for defining and measuring value. 





Assess Workloads

Assess workloads to align business and technical strategies, understand migration timeline constraints, validate expected value of migration, define technical modernization approaches, and align on migration methods. This process focuses on validating or challenging the assumptions made during the earlier planning phase by looking more closely at rationalization options and engaging with application management and support teams. This is also when reference patterns and dependencies are studied more closely to ensure workloads will achieve technical success post migration.

The choice of migration methods could involve a lift and shift or rehost to the cloud. Many of the assets supporting these workloads can be modernized to capitalize on the benefits of the cloud.  


 

Architect Workloads


 

Deploy Workloads

After workloads are assessed and target state cloud architectures defined, the existing functionality of those workloads is replicated (or improved) in the cloud.  Detailed processes for deployment, testing, and release to ongoing operations can vary based on the migration method used.

Migration Tasks are defined and planned hour by hour.  This includes detailed resources with contact information, communication processes, and backout/escalation plans. Critical during this process, is the effort to review the migrated workloads and hand them off to governance, operations management, and security teams for ongoing support of those workloads.

Post migration activities are also planned for the decommissioning or optimization of source infrastructure. 



Read more about Power Apps Business Process Features

Auditing

Tracking changes to records and fields is necessary to insure accuracy and proper governance.  Migration Playbook supports an auditing capability where entity and attribute data changes are recorded over time for use in analysis and reporting.  Using Microsoft Automate, record and attribute changes can trigger automated workflows or notifications. Auditing is supported on most Migration Playbook entities and is viewable for individual entities or across the organization.  

Read more about data change auditing 

Create Business Rules

Business rules provide logic and validation rules for Migration Playbook entities.  These rules can set fields values, show/hide fields, define mandatory fields, and provide validation rules.   Business rules provided within the tool are  triggered based on Business Process flow stages and entity record statuses.  The rules can easily be tailored to your requirements without writing code.

Read more about business rules  
 

Next

Register and sign in for access to additional content
Develop Cloud Adoption Strategy
Assess Workloads
Architect Workloads
Migrate Workloads