Share via

License for a software bonded with Server based is compatible to move to Azure cloud?

Lenin durai J 20 Reputation points
2025-12-19T06:46:30.4033333+00:00

Dear All, we have a requirement to host a software license on a virtual machine in the Azure cloud. The license is server-based. The application team has shared feedback regarding a previous on-premises VMware environment scenario, where a vMotion event within a cluster caused the license to become invalid due to a change in the underlying host. Will a similar situation occur in Azure? What precautions should be taken? Additionally, could you provide evidence or official Microsoft documentation that explains this scenario? how to mitigate?

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
Answer accepted by question author
  1. Ankit Yadav 7,945 Reputation points Microsoft External Staff Moderator
    2025-12-19T09:17:03.59+00:00

    Hello @Lenin durai J ,

    Please find the answer to your question below:-

    Will a similar situation occur in Azure?

    Yes, but the trigger is different. Azure does not perform live migrations like VMware vMotion in the same way. However, the underlying physical host for your VM can change during events like:

    • Resizing your VM to a different series (e.g., changing from a Dv4 to an Ev4 series).
    • Service Healing: If the underlying Azure host experiences a hardware failure, the Azure platform may automatically move your VM to a healthy host.
    • Performing Redeploy on the VM.

    These events can change the hardware identifiers (like SMBIOS System UUID) that your server-based license uses to fingerprint the host, potentially causing license invalidation.

    What precautions should be taken?

    1. Use Azure Dedicated Host (ADH): For maximum hardware stability, deploy your VM to an Azure Dedicated Host. This gives you exclusive access to a physical server, preventing host changes due to other customers' activity. Note: Your VM can still be moved if the dedicated host itself fails (service healing).
    2. Minimize Unnecessary VMSize Changes: When resizing a VM for performance, try to stay within the same VM series (e.g., D4s_v3 to D8s_v3) to reduce the risk of a hardware fingerprint change.
    3. For non-Microsoft licenses (like softwares that are not covered by Microsoft Hybrid policies):- You need to check with you Software Vendor. You check with them if they can they provide a cloud-friendly licensing model (e.g., tied to VM hostname, a license key, or Azure subscription ID) instead of a hardware fingerprint?
    4. Have a Re-activation Plan: Assume a host change may occur. Work with your non-Microsoft vendor to understand what's best to automatically re-activate the license and test their license re-activation process to ensure you can recover quickly.

    References:

    Hope this clears up your questions about the software licenses. If you have any more, feel free to comment below and I'll be happy to assist you further.

    1 person found this answer helpful.
    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.