link the reserved resources such as VMs per resource ID to the services that request them. The current system is not user-friendly.
When choosing to reserve resources over a longer period and to benefit from a discount by committing to allocate resources over 1/3 years, the way that Azure does it is really not transparent and not user friendly.
First of all, it should be possible that a resource like AKS offers the option of creating a cluster for 1/3 years instead of requiring the user to create the underlying VMs first and have them "automatically" be assigned to the AKS, so long as the VMs are of the same type.
Also, what if another user that has access to the subscription creates resources that require the same type of VM? If there is no way to uniquely match the reserve resources, nothing prevents the VMs to be linked to another user and service for which the VMs were not originally intended for.
All of that would be prevented if the resources could be allocated while creating the service that requires those VMs...
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature