Loading Assessments

You can load assessments into cloudstep using the Import/Export tool in the Analysis menu.  Choose a previously exported assessment spreadsheet from Azure Migrate.

You have some choices as to how you process the file:

  • Create new infrastructure based on assessments
  • Update existing infrastructure but do not create new entries
  • Load assessments but don't update infrastructure

Once you've added the spreadsheet you can click the Upload Azure Migrate Server Assessments.  You should see the following:

All going well the assessments should load and you'll see entries of type AzureMigrateMachine and AzureMigrateDisk in the list.  Where Virtuals were created you'll see a link to the "Record" it created.

Seeing Assessments in your model

If you told cloudstep create or update infrastructure entries when loading your assessments you'll see a tab in the Financials section of the explorer labelled "Azure Migrate Assessments".  This shows all assessments loaded that referrence this infrastructure.  there might be several since you could run several assessments with different properties.  cloudstep will use the most recently created assessment when considering pricing information.

Breaking this down you'll see the settings for the server as learned from the assessment along with Azure Migrate's decisions about how to deploy the virtual machine and storage.  A summary of the storage numbers are shown on the right hand side.  You'll be able to see this on the Virtual infrastructure and on any _azr entries that are replacements of this server in the cloud.

Seeing all the Azure Migrate Assessments

The infrastructure explorer will focus on specific assessment information but if you want to browse all of your assessments then choose Azure Migrate > Server Assessments from the Model menu.  You'll see assessments laid out the same as they are for an individual piece of infrastructure but all of them are present.  You can filter by the name of a machine..

Incorporating Azure Migrate Cost Assessments into your model

cloudstep Azure Migrate integration can override the cloudstep cost modeling mechanisms and trust the Azure Migrate assessments performed.  When a match can't be found for some reason, the Storage and VM costs will default to trying to work out a suitable cost based on how the cost is configured.  This is useful if you don't have a set of assessments initially but add them later.

When an Azure Migrate Machine or Disk assessment is available these will be used and shown in the "Associated Costs" tab in the Financials section of the infrastructure explorer.  These are typically applied to _azr infrastructure elements.

Above you can see storage and VM costs applied to an infrastructure element.  The Azure Migrate Assessment information is shown along with a summary of the costs.  This is the same data in the Azure Migrate Assessments tab but it represents costs applied in your model.  If the cost has used the default cloudstep mechanism it will show its working differently.

VM Costs

cloudstep has a matching algorithm for choosing azure VM types built in.  When you load assessments into cloudstep you can tell it to use Azure's assessment mechanism instead of the cloudstep chooser.  You do this by modifying one drop down in your Azure cost objects as follows:

Remember that when there are multiple assessments in the model, cloudstep will use the most recently exported one, not the cheapest or any other selection criteria.

Storage Costs

Storage costs work similarly to the VM costs.  You can tell cloudstep which chooser to use for identifying storage costs, either its own in-built one which uses a $/GB cost and a growth rate.  It works out the current storage cost based on this.  It is a useful mechanism for building a quick assessment of storage costs.  Azure Migrate has more sophsisticated mechanisms for assessing storage costs based on bracketed offerings in Azure.  Assessments of the storage take into account the nature of the underlying on-premises disks and the costs are reflected accordingly. 

If an assessment of disks cannot be found then the default $/GB/m will be used in its place.


About this Page

Last Updated: 2021-01-27 10:32:20.967778+00:00

More Specific Information
Nothing More