Feedback by UserVoice

I suggest you ...

Solve Office Activation Issues on Azure VMs

Office installed on Azure VMs are losing their activation after a VM shutdown. This makes it impossible to create test VMs or use Office on a developer VM to develop/test/deploy(buildserver output) on Azure. Activation based on hardware assets such as harddrive and network MAC/IP combinations is outdated in 2014 and invalidates your VM images.

65 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Maarten van Stam (MVP) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Mike Williams commented  ·   ·  Flag as inappropriate

        This is causing me grief with Office 2013, is there are news on when we might see a way round this?

      • Yuki K commented  ·   ·  Flag as inappropriate

        I've also been running into this issue. Unless we can get around this roadblock, it's difficult to rely upon Azure as the basis of our particular test infrastructure. Perhaps a new licensing model is needed, specifically for use in the cloud.

      • Scott Harrison commented  ·   ·  Flag as inappropriate

        This is a huge issue for me right now also. I'm glad I'm not the only one facing it. I work on an Office add-in and we have multiple Azure VMs setup with different OS\Office combinations for automated testing of our product. However, every time we start up a new VM, we have to re-activate Office. This seems like an easy issue to address and should be a slam dunk decision for Microsoft to pursue if they truly want developers to adopt Azure VMs for their test infrastructure.

      Feedback and Knowledge Base