Whilst performing routine server check this morning I noticed that most of my Server 2012 VM's require activation.
Most of the affected servers are currently in production so I am naturally concerned about this condition.
I have read several articles that state that AZURE VM licensing is covered as part of a per hour charge. However as several of our servers do not require activation I am naturally concerned about the ones that do.
One difference is that the servers that require activation were created from an image captured in one subscription, but were subsequently "migrated" from that subscription to another. This is the only pattern that I can see and whilst I am by no means confident that this is the reason, I can confirm that all the servers in the source subscription remain actived.
However, I have created a new VM from the same image used to create the problem servers:
1. In the source subscription the server is active
2. In an example migrated subscription the server is still activated
On that basis, if being migrated to a new subscription is part of the problem something else must be contributing to the issue.
Can anybody help?
Most of the affected servers are currently in production so I am naturally concerned about this condition.
I have read several articles that state that AZURE VM licensing is covered as part of a per hour charge. However as several of our servers do not require activation I am naturally concerned about the ones that do.
One difference is that the servers that require activation were created from an image captured in one subscription, but were subsequently "migrated" from that subscription to another. This is the only pattern that I can see and whilst I am by no means confident that this is the reason, I can confirm that all the servers in the source subscription remain actived.
However, I have created a new VM from the same image used to create the problem servers:
1. In the source subscription the server is active
2. In an example migrated subscription the server is still activated
On that basis, if being migrated to a new subscription is part of the problem something else must be contributing to the issue.
Can anybody help?