We should be able to release user license when the user is no longer with the company. This could be done by checking if the user is active in Active Directory. With on prem deployment, we could do this using udadmin on the license server.

I have spoken to multiple people who have mentioned this is the only thing holding them back from going cloud. They have too high of turnover for user licensing to make sense. They would either need concurrent licensing or the functionality mentioned above.

Expand the Current Tenant customisation options which allows XenApp/XenDesktop and License Servers to be split per customer to include Netscaler license SKUs. Being able to allocate a Netscaler to a Customer would be very useful in a multi tenant Service Provider environment

LUI throws up a little warning on the site to say a license server hasn't checked in for a few days - how about sending an email when this happens? We don't check the site very often so wouldn't have noticed this until towards the end of the month!

For now, the only way to manage clients is via administrators, which are able to see all the clients. It would be great if certain users could have permission to manage only the clients created by them, without being able to see clients created by other users.

It would be helpful if Smart Scale would have an option which would allow a number of machines based on Zones. Like if we would want to have x number of machines powered on per Zone. And to be able to set separate schedules per zone.

When creating machine catalogues I notice that the keyboard changes from the studio default (UK) to US and this makes it difficult to enter UK characters such as \ and # into passwords and dialogues, could the current keyboard type be passed through

But your backend system dont know about this type of activation and everytime VDA VM template image should use workaround if Office 365 Pro Plus should be installed. Now we are suing workaround as described here

If you use a mandatory proxy server in your resource group deployment fails because of missing internet connectivity. There is no chance to deploy the proxy configuration via GPO or login script because deployment didn't start without internet.

It's a good idea to provide a configuration for the machines created from Citrix Cloud to add some important information (proxy settings in that case)