While Azure does permit multiple RemoteApps to share the same display name across different application groups—provided each has a unique resource identifier—the import process within Nerdio currently enforces uniqueness at the host pool level, rather than at the application group level. This behavior appears to stem from Nerdio’s internal design, which utilizes the RemoteApp display name as part of its tracking mechanism, rather than relying exclusively on Azure’s underlying resource identifiers.
As a result, even though the Azure platform technically allows for more flexibility, the current implementation in Nerdio imposes this naming constraint.
It would be very handy to have this more flexibility and have the same possibilities as the underlying Azure platform already offers, namely, to enforce RemoteApp uniqueness at application group level rather than at host pool level.
Comments (1 comment)