licence for MS project not propogating from template to VMs invirtual pool

Alex Grossi 1 Reputation point


We wanted to use MS Project Standalone 2016 for construction Azure lab class. We installed MS Project 2016 and activated using our edu MAK key on the template. No issue with activation and usage detected on the template.

Upon inviting myself to use virtual machine from the virtual pool of that template, there was an issue with activation. The MAK key does not seem to propagate from template to VMs unlike other softwares.

Azure Lab Services
Azure Lab Services
An Azure service that is used to set up labs for classrooms, trials, development and testing, and other scenarios.
278 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. kobulloc-MSFT 23,336 Reputation points Microsoft Employee

    Some software creates a license key based on your computer's hardware (like your motherboard) as an extra layer of security, including Windows 10 and Office.

    Each Office activation that uses MAK counts toward the activation limit. After Office is activated, no re-activation is required unless the hardware changes significantly.

    This causes the issue with activation that you see when you create a new VM as the current hardware does not match the hardware of the VM it was activated on (and use caution here, as each activation counts towards the limit).

    There is a cloud license for Microsoft Project available that should work (per user rather than per activation), and I would talk to sales to confirm that this will work for what you need:

    0 comments No comments