Azure Site Recovery Deployment Planner Version History
2.3
Updated December 3, 2018

Following fix has been added in 2.3
* Fixed - Recently, the ASR Deployment Planner was not able to generate a report with given target location and subscription. It was due to some change in the RateCard API interface which has broken the  API call in the ASR Deployment Planner.

2.2
Updated April 25, 2018

Following fixes are added
* For Hyper-V to Azure scenario, VMs with the shared VHDs and PassThrough  disk are now excluded profiling. Startprofiling operation will show the list of excluded VMs in the console.
* Added few more possible failure reasons for GetVMList operation failure.
* FIxed -  VM with more than 64 disk is not listed in incompatible VMs list for Hyper-V to Azure scenario.
*Fixed - Column name doesn't show up for the VM type configration info in the Compatible VMs sheet in the deployment planner report.
* Updated the IR and DR  compression factor for Hyper-V to Azure scenario.
* GetVMList command now creates the default directory or create the directory as specified in the outputfile parameter instead failing if the given directory is not present.
 *Added limited support for  SMB storage for Hyper-V to Azure scenario.

2.1
Updated: January 3. 2018

Following fixes are added:
* Minor update in the Excel report.
* Minor bug fixes in GetThroughput operation.
* Limit of number of VMs that can be profiled or to generate the report is now configurable.  The default limit is 1,000 VMs.
* Fixed- For VMware to Azure, Windows Server 2016 VM is going into the incompatible table.
* For VMware to Azure, updated compatibility messages for EFI Windows VMs.
* Updated the VMware to Azure and Hyper-V to Azure VM data churn limit per VM.
* Improved reliability of VM List file parsing.

2.0.1
Updated: December 7, 2017

Following bug fixes are made.
* Optimize the network bandwidth recommendation.

2.0
Updated: November 28, 2017

Following new features are added:
* Added support for Hyper-V to Azure scenario.
* Added cost calculator
* Added OS version check for VMware to Azure scenario to determine if the VM is compatible or incompatible for the protection. The tool uses the OS version string that is returned by the vCenter server for that VM. It is the guest operating system version that user has selected while creating the VM in VMware.
Known limitations:
* For Hyper-V to Azure, VM name contains following characters: , “” [] ` are not supported.  If profiled, report generation will fail or will have an incorrect result.
* For VMware to Azure, VM name contains comma is not supported. If profiled, report generation fails or will have an incorrect result.

1.3.1
Updated: July 19, 2017

Following new feature is added:
* Added support for large disks (> 1 TB) in report generation. Now you can use deployment planner to plan replication for virtual machines that have disk sizes greater than 1 TB (up to 4095 GB).
Read more about [Large disk support in Azure Site Recovery](https://azure.microsoft.com/en-us/blog/azure-site-recovery-large-disks/)

1.3
Updated: May 9, 2017

Following new feature is added:
* Added Managed Disk support in report generation. The number of virtual machines can be placed to a single storage account is calculated based on if the managed disk is selected for Failover/Test Failover.       

1.2
Updated: April 7, 2017

Added following fixes:
* Added boot type (BIOS or EFI) checks for each virtual machine to determine if the virtual machine is compatible or incompatible for the protection.
* Added OS type information for each virtual machine in the Compatible VMs and Incompatible VMs worksheets.
* The GetThroughput operation is now supported by the US Government and China Microsoft Azure regions.
* Added few more prerequisite checks for vCenter and ESXi Server.
* Incorrect report was getting generated when locale settings are set to non-English.

1.1
Updated: March 9, 2017

Fixed the following issues:
* The tool cannot profile VMs if the vCenter has two or more VMs with the same name or IP address across various ESXi hosts.
* Copy and search are disabled for the Compatible VMs and Incompatible VMs worksheets.

1.0
Updated: February 23, 2017

Azure Site Recovery Deployment Planner public preview 1.0 has the following known issues (to be addressed in upcoming updates):
* The tool works only for VMware-to-Azure scenarios, not for Hyper-V-to-Azure deployments. For Hyper-V-to-Azure scenarios, use the [Hyper-V capacity planner tool](./site-recovery-capacity-planning-for-hyper-v-replication.md).
* The GetThroughput operation is not supported by the US Government and China Microsoft Azure regions.
* The tool cannot profile VMs if the vCenter server has two or more VMs with the same name or IP address across various ESXi hosts. In this version, the tool skips profiling for duplicate VM names or IP addresses in the VMListFile. The workaround is to profile the VMs by using an ESXi host instead of the vCenter server. You must run one instance for each ESXi host.