Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AME changes #62

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

AME changes #62

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c40cc3
AME changes
Karthigasree Sep 7, 2023
d208596
Edits
Karthigasree Sep 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 21 additions & 21 deletions documentation/azure-migrate-export.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,15 +91,15 @@ SQL assessment is a three-step process:
2. The remaining SQL Instances that cannot be migrated to Azure SQL MI due to migration blockers (details of which are available in opportunity report) are then assessed for migration to SQL server in Azure VM (sizing the instance for Azure VM, using the recommended migration approach). Details of such SQL Server instances can be found in “SQL_IaaS_Instance_Rehost_Perf” tab in Assessment Core Report.
Only Premium disks are recommended for Azure VMs that run SQL Instances on them.
3. The remaining servers whose SQL instances are not ready for the above two migration/ modernization approaches are then assessed for readiness for SQL Server on Azure VM – using a Lift and Shift approach ie migrating an entire server not just individual SQL Server Instances running in them. Details of such SQL Server can be found in “SQL_IaaS_Server_Rehost_Perf” tab in Assessment Core report. [Learn more](https://learn.microsoft.com/en-us/azure/migrate/concepts-azure-sql-assessment-calculation) about the SQL Server assessment logic.
### Web app Assessment
### Web app assessment
Web app assessment is a two-step process:
1. All the in-scope discovered .NET Web apps running on IIS Web Servers on Windows Server are first assessed for migration to Azure App Service. Details of the Web app that are ready for Azure App service can be found in “WebApp_PaaS” tab in Assessment Core Report.
1. All the in-scope discovered .NET Web apps running on IIS Web Servers on Windows Server are first assessed for migration to Azure App Service. Details of the Web app that are ready for Azure App service can be found in **WebApp_PaaS** tab in Assessment Core Report.
2. The remaining servers whose web app/web apps cannot be migrated to Azure App Service due to migration blockers (details of which are available in opportunity report) are then assessed for Azure VM. Details of such server can be found in “WebApp_IaaS_Server_Rehost_Perf” tab in Assessment Core Report. [Learn more](https://learn.microsoft.com/en-us/azure/migrate/concepts-azure-webapps-assessment-calculation) about the App Service assessment logic.
### Assessment of Servers containing SQL Services
### Assessment of servers containing SQL Services
All in-scope discovered machines containing SQL Services such as SQL Server Integration services, SQL Server Reporting Services and SQL Server Analysis Services are assessed for migration to Azure VM – using a Lift and Shift approach. Details of such machines can be found in “VM_SS_IaaS_Server_Rehost_Perf” tab in Assessment Core Report.
### VM Assessment
### VM assessment
The in-scope discovered Windows and Linux servers that do not have SQL Server, Web app, or SQL Services present on them are assessed for migration to Azure VM. Details of such machines can be found in “VM_IaaS_Server_Rehost_Perf” tab in Assessment Core Report. [Learn more](https://learn.microsoft.com/en-us/azure/migrate/concepts-assessment-calculation) about the Azure VM assessment logic.
### AVS Assessment
### AVS assessment
The in-scope discovered machines that are running on VMware are assessed AVS assessment. AVS is an alternate approach to PaaS preferred migration where customer can choose to rehost their VMware environment on Azure VMware Services. Details of such machines can be found in “AVS_Summary” and “AVS_IaaS_Rehost_Perf” tab in Assessment Opportunity Core Report. [Learn more](https://learn.microsoft.com/en-us/azure/migrate/concepts-azure-vmware-solution-assessment-calculation) about the AVS assessment logic.
### Azure Site Recovery and Backup
Azure Site Recovery and backup cost is only computed for the following workloads:
Expand All @@ -122,13 +122,13 @@ Follow the below steps:
1. Download the Azure Migrate Export utility package and extract the contents on the package. [Learn More](#how-to-get-azure-migrate-export-utility-package) about how to get Azure Migrate Export Utility Package.
2. Run Azure Migrate Export application.
3. To generate the Discovery and assessment reports with customization, select **Workflow Option** as Both.
4. In **Source Appliance**, select the source of servers. By default, all three sources, namely VMware, Hyper-V, and Physical are selected.
5. Enter the project identifier details such as Tenant ID, Subscription ID, Resource Group name, Discovery Site name and assessment project name. [Learn More](#how-to-find-project-discovery-and-assessment-parameters) on where to find the Project Identifier.
4. In **Azure Migrate source appliance**, select the source of servers. By default, all three sources, namely VMware, Hyper-V, and Physical are selected.
5. Enter the project identifier details such as Tenant ID, Subscription ID, Resource Group name, Discovery Site name, and assessment project name. [Learn More](#how-to-find-project-discovery-and-assessment-parameters) on where to find the Project Identifier.
6. Select the **Target location** where you want to modernize your resources, the **Assessment duration** for which you want to run assessment, and select **Submit**.
7. Users will now be prompted to authenticate Azure access.
8. Once the user is authenticated in Azure, the discovery and assessment modules both run in sequence to generate discovery Report, Assessment Core Report, Assessment Opportunity Report and Assessment Clash Report. [Learn More](#discovery-and-assessment-report-analysis) about highlights of the report.
> [!Note]
> Assessment typically runs in 1-2 hours but may take more time to run depending on the size of environment.
> An assessment typically runs in 1-2 hours but may take more time to run depending on the size of environment.
9. Users can choose to customize assessment report for removing required duplicates in assessment. [Learn More](#how-to-customize-assessment-core-report) about how to customize assessment reports.
10. Run the “Azure_Migrate_Export.pbit” PowerBI template provided in the Utility package.
11. Provide the path of utility package where all the reports are generated and click Load. [Learn More](#how-to--find-basepath) about base Path.
Expand All @@ -141,23 +141,23 @@ Follow the below steps:
### To run AME with customization, users need to first generate the discovery report, apply customization, and then run assessment. Follow these steps:
1. Download the Azure Migrate Export utility package and extract the contents on the package. [Learn More](#how-to-get-azure-migrate-export-utility-package) about how to get Azure Migrate Export Utility Package.
2. Run Azure Migrate Export application.
3. On the console, Select Workflow Option as Discovery.
4. In **Source Appliance**, select the source of servers. By default, all three sources, namely VMware, Hyper-V, and Physical are selected.
5. Enter the project identifier details such as Tenant ID, Subscription ID, Resource Group name, and Discovery Site name. [Learn More](#how-to-find-project-discovery-and-assessment-parameters) on where to find the Project Identifier.
6. Select the Target location where you want to move your resources and select **Submit**.
7. Users will now be prompted to authenticate for Azure access.
8. Once the user is authenticated in Azure, the discovery runs to generate the “Discovery_VMs” report which provides details of all servers discovered in your environment from the selected source type.
3. Enter the project identifier details such as Tenant ID, Subscription name, Resource Group name, and Azure Migrate project name. [Learn More](#how-to-find-project-discovery-and-assessment-parameters) on where to find the Project Identifier. Select **Next**.
3. In the **Configuration** tab, do the following:
1. In **Azure Migrate source appliance**, select the source of servers. By default, all three sources, namely VMware, Hyper-V, and Physical are selected.
1. In **Workflow**, select **Discovery** from the **Custom** drop-down. Select **Submit**.
7. Users will now be prompted to authenticate Azure access.
3. On the console, select **Workflow** option as **Discovery**. Select **Next**.\
the discovery runs to generate the “Discovery_VMs” report which provides details of all servers discovered in your environment from the selected source type.
9. Apply the required customizations on the Discovery report and save the file. [Learn More](#how-to-customize-discovery-report) on how to customize discovery file.
10. On the console, select Workflow option as Assessment.
11. Enter the project identifiers such as Tenant ID, Subscription ID, Resource Group name, and Assessment project name. [Learn More](#how-to-find-project-discovery-and-assessment-parameters) on where to find the project identifiers.
12. Select the Assessment duration for which you want to run assessment and click **Submit**.
13. Users will now be prompted to authenticate Azure access.
14. Once the user is authenticated in Azure, the assessment runs to generate Core Report, Opportunity Report and Clash Report. [Learn More](#discovery-and-assessment-report-analysis) about highlights of the report.
10. On the console, select **Assess**.
6. Select the **Target region** where you want to move your resources, **Currency**, **Assessment duration** for which you want to run assessment, and **Migration strategy**. Select **Submit**.
7. Users will now be prompted to authenticate for Azure access.
14. Once the user is authenticated in Azure, the assessment runs to generate Core Report, Opportunity Report, and Clash Report. [Learn More](#discovery-and-assessment-report-analysis) about highlights of the report.
> [!Note]
> An assessment typically runs in 1-2 hours but may take more time depending on the size of environment.
15. Users can choose to customize assessment reports for removing required duplicates in assessment. [Learn More](#how-to-customize-assessment-core-report) about how to customize assessment reports.
16. Run the “Azure_Migrate_Export.pbit” PowerBI template provided in the Utility package.
17. Provide the path of utility package where all the reports are generated and click Load. [Learn More](#how-to--find-basepath) about the base Path.
16. Run the *Azure_Migration_and_Modernization* PowerBI template provided in the Utility package.
17. Provide the path of utility package where all the reports are generated and click Load. [Learn More](#how-to--find-basepath) about the base path.
18. Once the data is loaded, Users can now choose to change static data in PowerBI report to customize as per requirement. [Learn More](#how-to-customize-powerbi-report) about how to customize PowerBI Report.
19. After finalizing the slides, publish the PowerBI report on your workspace.
![Screenshot of PowerBI workspace.](./.media/workspace-report.png)
Expand Down
15 changes: 8 additions & 7 deletions documentation/concepts-reports.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,9 @@ Azure Migrate Export (AME) generates the following excel reports to provide disc
## Discovered VMs
File Path: ```\AzMigExport\All_Discovered-VMs-Report\Discovered_VMs.xlsx```

Discovered VMs report contains details of all VMs and servers that are discovered in customer’s environment from the selected source type or appliance. The report also outlines the type of workload a VM is running.
The Discovered VMs report contains details of all VMs and servers that are discovered in customer’s environment from the selected source type or appliance. The report also outlines the type of workload a VM is running.
Kindly refer to below dictionary for more details:

**Column Name** | **Details**
--- | ---
Machine | Name of the discovered machine.
Expand All @@ -40,10 +41,10 @@ Firstdiscoverytime | Date and time when collection of discovery data began by Az
EnvironmentType | This column is for user inputs. <br></br> Users can categorize the servers into dev and prod environments by entering information into this column so that adequate pricing considerations are applied at the time of assessment. Servers where environment type cells are blank are considered as production servers by default. <br></br> Permitted User input values: “Dev” and “Prod”. [Learn More](how-to-customize-discovery-report) about how to customize discovery report.
Target | Region Target regions selected by user while running discovery on AME.

## Assessment Core Report
## Assessment Core report
File Path: ```\AzMigExport\Core-Report\AzureMigrate_Assessment_Core_Report.xlsx```.

Assessment Core report contains all the information about servers and workloads and the targets that are ready to be migrated to Azure with minimal changes. The focus here is on a PaaS first approach such that if the customer’s SQL Server instances or .NET Web Apps running on IIS web servers are ready for Azure SQL Managed Instance and Azure App Service respectively, they will be considered for those targets unless scoped out of the consideration set before running Assessment module in AME. SQL Server instance and .NET Apps that are not ready for PaaS, as well as remaining workloads and servers, including those running other SQL Services such as SQL Server Analysis Services, are sized for Azure VM. In addition to SKUs and ready to be migrated workloads, core report covers estimated prices considering various options considering offers such as Pay-as-you-go, reservations, and Azure Hybrid Benefit for Windows and SQL. These are run on in-scope servers.
The Assessment Core report contains all the information about servers and workloads and the targets that are ready to be migrated to Azure with minimal changes. The focus here is on a PaaS first approach such that if the customer’s SQL Server instances or .NET Web Apps running on IIS web servers are ready for Azure SQL Managed Instance and Azure App Service respectively, they will be considered for those targets unless scoped out of the consideration set before running Assessment module in AME. SQL Server instance and .NET Apps that are not ready for PaaS, as well as remaining workloads and servers, including those running other SQL Services such as SQL Server Analysis Services, are sized for Azure VM. In addition to SKUs and ready to be migrated workloads, core report covers estimated prices considering various options considering offers such as Pay-as-you-go, reservations, and Azure Hybrid Benefit for Windows and SQL. These are run on in-scope servers.

The definition of reports that are part of Assessment Core report are as follows:

Expand All @@ -64,7 +65,7 @@ VM_IaaS_Server_Rehost_As-is | The in-scope VMs that doesn’t have SQL Server, W
SQL_All_Servers | The report contains details of perf-based assessment of all in-scope SQL Servers, its recommended target, readiness warnings (if any), performance properties of SQL Instance, and various estimated cost considering offers such as Pay-as-you-go, reservations, and Azure Hybrid Benefit for both Dev and Prod environment.
AllVM_IaaS_Server_Rehost_Perf | The report contains details of perf-based assessment of all in-scope VMs, its readiness warnings (if any), recommended Azure VM Configuration, performance properties of VM, and estimated cost on Azure for both Dev and Prod environment.

## Assessment Opportunity Report
## Assessment Opportunity report
File Path: ``` \AzMigExport\Opportunity-Report\AzureMigrate_Assessment_Opportunity_Report.xlsx```.
The opportunity report helps one identify additional modernization opportunities for SQL Server instances and .NET Web apps, by indicating what blockers or issues customers must address to be able to fully modernize SQL Server and .NET workloads.
Additionally, Opportunity report also covers details of alternate migration paths for VMware based servers, by indicating cost, readiness and SKUs for Azure VMware Solution (AVS). These are run on in-scope servers.
Expand All @@ -80,20 +81,20 @@ SQL Issues & Warnings | The report contains details of in-scope SQL Server insta
Webapp Opportunity | The report contains details of in-scope Web app that cannot be migrated to Azure App Service. The report highlights details of issues and warnings that needs to be remediated to make Web app ready for Azure App Service.
VM Opportunity_Perf | The report contains details of in-scope VMs that cannot be migrated to Azure. The report highlights details of issues and warnings that needs to be remediated to make VM ready for Azure VM.

## Assessment Clash Report
## Assessment Clash report
File Path: ```\AzMigExport\Clash-Report\AzureMigrate_Assessment_Clash_Report.xlsx```.

The Clash report helps to identify duplicates within the Core report. With this report, users can customize the Assessment Core report by deleting unwanted servers in an assessment. This helps a user generate precise estimated cost of customer’s workloads in Azure.

The Clash report highlights count and details of assessments conducted for a machine that is sized for assessments.

### Interpreting Clash Report
### Interpreting Clash report

![Screenshot of clash report.](./.media/clash-report.png)

In the example above, the machine CRMSQLVM14 has two entries in SQL_IaaS_Instance_Rehost_Perf tab and one entry in SQL_MI_PaaS tab, and one entry in SQL_IaaS_Server_Rehost_Perf tab. This report can be used as a tally to understand a summary of all the in-scope machines and the user can customize the Assessment Core report to get the required cost estimate output from PowerBI. [Learn More](#how-to-customize-assessment-core-report) on how to customize the Assessment Core Report.

## Understanding PowerBI Report
## Understanding PowerBI report
The details of each slide in data populated PowerBI report is as follows:
**Slide** | **Details**
--- | ---
Expand Down
6 changes: 3 additions & 3 deletions documentation/tutorial-run-with-customization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,14 +21,14 @@ This article describes the procedure to run Azure Migrate Export with customizat
To run AME with customization, users need to first generate the discovery report, apply customization, and then run assessment. Follow these steps:
1. Download the Azure Migrate Export utility package and extract the contents on the package. [Learn More](#how-to-get-azure-migrate-export-utility-package) about how to get Azure Migrate Export Utility Package.
2. Run Azure Migrate Export application.
3. On the console, Select Workflow Option as Discovery.
4. In **Source Appliance**, select the source of servers. By default, all three sources, namely VMware, Hyper-V, and Physical are selected.
3. On the console, select **Workflow** option as **Discovery**.
4. In **Azure Migrate source appliance**, select the source of servers. By default, all three sources, namely VMware, Hyper-V, and Physical are selected.
5. Enter the project identifier details such as Tenant ID, Subscription ID, Resource Group name, and Discovery Site name. [Learn More](#how-to-find-project-discovery-and-assessment-parameters) on where to find the Project Identifier.
6. Select the Target location where you want to move your resources and select **Submit**.
7. Users will now be prompted to authenticate for Azure access.
8. Once the user is authenticated in Azure, the discovery runs to generate the “Discovery_VMs” report which provides details of all servers discovered in your environment from the selected source type.
9. Apply the required customizations on the Discovery report and save the file. [Learn More](#how-to-customize-discovery-report) on how to customize discovery file.
10. On the console, select Workflow option as Assessment.
10. On the console, select **Workflow** option as **Assessment**.
11. Enter the project identifiers such as Tenant ID, Subscription ID, Resource Group name, and Assessment project name. [Learn More](#how-to-find-project-discovery-and-assessment-parameters) on where to find the project identifiers.
12. Select the Assessment duration for which you want to run assessment and click **Submit**.
13. Users will now be prompted to authenticate Azure access.
Expand Down
Loading