Using the ACE to Estimate Azure Migration Costs – Part 1: Introduction & Installation

If you’re planning on migrating an on-premise workload into Microsoft Azure, but haven’t yet worked with Azure, you may want to know how much to expect your monthly bill will be.

Thankfully, there are several tools at your disposal in estimating costs, and assessing which systems are ready for Azure.

In a previous series, we looked at the Microsoft Assessment and Planning (MAP) Toolkit. In this series, we will look at the Microsoft Azure Cost Estimator tool.

 

Microsoft Azure Cost Estimator

The Azure Cost Estimator has been designed keeping in mind the need to provide the IT manager of next generation organizations the ability to quickly assess running cost of the existing on-premises workload on Azure.

 

About the tool

  • The tool provides real world machine hardware usage
  • It recommends appropriate Azure instance to match the scanned workload
  • It also generates 31-day cost estimates of running such an Azure instance

 

Features

  • The tool supports
    1. Microsoft technologies (Hyper-V, SCVMM)
    2. VMware technologies (vCenter, ESXi)
    3. Physical environments (Windows, Linux)
  • Support to A series, D-series and G-series Virtual Machines
  • Support to all regions apart from US
  • Price conversion in 24 currencies with the latest prices.
  • It is able to export to Excel/.csv that can be used for discussions with Systems Integration partner or a Microsoft representative
  • Create Cost Estimates and My Scenarios from the available Services
  • Cost Estimates can be generated using Scan tool results
  • Support for IP Range Feature in the Scan Your Environment Functionality
  • Import and Export functionality in “Scenarios”
  • Updated Sample Scenarios
  • New services added in tool – Azure App, IP Address, Mobile Engagement, Application Insights, VPN Gateway, Key Vault, DNS
  • No data is sent to Microsoft at any time. All report and profile information resides on the machine where the tool is installed

 

Value Proposition

  • Can be Installed and a profile scan completed within 15 minutes (can be deployed on a Windows client)
  • Enables a comparison with on-premises running costs (e.g. hardware, power, cooling, building, security, and systems management among others)

 

Installation

To start the installation you need to first download the installation files from the following location: http://www.microsoft.com/en-ca/download/details.aspx?id=43376. This will download the Microsoft Azure Cost Estimator Tool.msi file. Copy this file to the system you will install it on, and run the Microsoft Azure Cost Estimator Tool.msi.

On the Welcome screen, click Next.

MACE-Tool-Install-01-Welcome Using the ACE to Estimate Azure Migration Costs – Part 1: Introduction & Installation

MACE Tool – Install – Welcome

On the Information screen, read the information presented, then click Next.

MACE-Tool-Install-01-Welcome Using the ACE to Estimate Azure Migration Costs – Part 1: Introduction & Installation

MACE Tool – Install – Information

On the License Agreement screen, read the end-user license agreement, select the ‘I accept the terms in the License Agreement’ checkbox, then click Next.

MACE-Tool-Install-01-Welcome Using the ACE to Estimate Azure Migration Costs – Part 1: Introduction & Installation

MACE Tool – Install – License Agreement

On the Destination Folder screen, specify the destination for the installation, then click Next.

MACE-Tool-Install-01-Welcome Using the ACE to Estimate Azure Migration Costs – Part 1: Introduction & Installation

MACE Tool – Install – Destination Folder

On the Ready to Install screen, click Install.

MACE-Tool-Install-01-Welcome Using the ACE to Estimate Azure Migration Costs – Part 1: Introduction & Installation

MACE Tool – Install – Ready To Install

Once the installation is complete, click Finish.

MACE-Tool-Install-01-Welcome Using the ACE to Estimate Azure Migration Costs – Part 1: Introduction & Installation

MACE Tool – Install – Install Complete

With the tool installed, we now need to scan the environment; which we will cover in Part 2: Scan Your Environment.

 

%d bloggers like this: