Azure Pack

Do you have an idea or suggestion based on your experience with Azure Pack ? We would love to hear it! Please take a few minutes to submit your ideas about providing Azure technologies and services on-premises, or vote up an idea submitted by another customer. All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure Pack. Remember that this site is only for feature suggestions and ideas!

For further reading on Azure Pack, please see our TechNet Documentation and our Wiki (links to articles and blogs). If you have technical questions or need help with Azure Pack, please try our Discussion Forum.

It is very important for tenants to have control over backup and recovery of the VMs they created in their Windows Azure Pack VM Clouds. It should be possible to backup VMs while online and recover while offline.

We are reviewing a feature for disaster recovery for VMs. If you have particular ideas about the feature, please share with us here. Note that disaster recovery and backup/recovery are different features.

Today, we can add several address spaces inside a virtual network on the portal, but when setting a particular VM, we can only choose the virtual network, not the subnet (which is present when viewing into the VMM console)

Currently a VM has to be taken offline to add, remove, grow or shrink a VHDX. If the operating supports it this should be an online experience.
Future online capabilities should also be online in Windows Azure Pack

Templates are great when you have a limited number, but can get cumbersome in large environments. Allow vm and os provisioning via other methods such as pxe, sccm, iso, etc to help streamline template management. - especially useful when trying to leverage dsc/puppet/chef for management.

When a tenant selects to add a ISO or a disk, all the items are shown from the read only lib unsorted. The possibility add sorting and prefilter (for instance based on tags) would enhance the tenant experience and hide unwanted files.

Parameter validation options are very limited and could be expanded with (external) script hooks.
Example:
An Enterprise utilizes Azure Pack internally. All VM roles must join the same Active Directory domain. During VM role deployment a computer name is provided by the user. There is no way to check against Active Directory if this computer name is already in use. Worst case scenario, the user enters a name of a server already in use and highjacks the trust relationship with the new VM role breaking service of the “old” server. Many other scenarios could be thought of. It would be nice for more validation options to be available in the view definition. Integration with SMA would be preferred for optimum flexibility.

Parameter validation options are very limited and could be expanded with (external) script hooks.
Example:
An Enterprise utilizes Azure Pack internally. All VM roles must join the same Active Directory domain. During VM role deployment a computer name is provided by the user. There is no way to check against Active Directory if this computer name is already in use. Worst case scenario, the user enters a name of a server already in use and highjacks the trust relationship with the new VM role breaking service of the “old” server. Many other scenarios could be thought of. It would be…