Hello @Horak David
There isn't a Microsoft memory-allocation guide based simply on purchasing a specific number of VMs. Memory sizing is determined by the workloads running inside those VMs, not by the VM count or licensing/package quantity.
For example, if these are Hyper-V VMs, you should consider:
- Guest OS and application memory requirements
- Number of VMs expected to run concurrently
- Memory required by the Hyper-V host
- Whether you're using static or Dynamic Memory
- Startup, minimum, and maximum RAM settings
- Expected workload peaks and available physical RAM
Microsoft recommends providing enough physical memory for the expected guest VM requirements plus sufficient memory for the host operating system. Hyper-V Dynamic Memory can also adjust VM memory according to workload demand.
So, for example, 50 VMs configured with 8 GB each would represent 400 GB of configured guest memory, before considering host requirements and your Dynamic Memory/overcommit strategy. That doesn't automatically mean the host needs exactly 400 GB, the actual design depends heavily on workload behavior.
Could you clarify what you mean by the "50 VM package" and which Microsoft product or reseller offering you purchased? Also provide the host specifications and what workloads/OS will run in the VMs. That will make it possible to point you to the correct sizing guidance.
Please "Accept the Answer" if this information helped you.