Creating Workspaces and AVD Host Groups with spaces in the name

Avatar
David Sain

I'm new to the product but will be using it for some upcoming projects.  

I came across a situation where someone ahead of me created a Workspace and an AVD Host Group with spaces in the names.  I was trying to setup private endpoints to access the AVD environment and cannot because the names are invalid. For our application (CMMC) we don't want public access to the workspaces so need to turn that off.

So I performed a test - I tried to create “TEST Workspace” through the Azure Portal.  This failed because of the space in the name.  This implies that there is something with the product that allows it to create Workspaces with spaces in the name but they are invalid when trying other operations.

 

Another thing, I was referencing this
https://nmehelp.getnerdio.com/hc/en-us/articles/26124384553997-Workspace-Management

Maybe it's the wrong place.  Couldn't find Workspace anywhere.  Bumbled around and found it under the tenant > Settings > Azure > Azure Environment.

 

0

Comments (4 comments)

Sort by
0
Avatar
Anthony Sequeira

Hi David! 

Because Azure does not permit spaces in an AVD workspace name, Nerdio cannot permit that either. What you are seeing in Nerdio is the “Friendly Names” that were configured for these objects. 

So I might have a workspace name of “my_workspace_ajs_10”, but I can configure a Friendly Name of "Anthony S Workspace" for the display in the Nerdio GUI. 

Thank you so much for posting here in the Community and of course - for using Nerdio! 

0
Avatar
David Sain
(Edited )

Hi Anthony.

I checked and the named workspace had a space in it, it was not just a friendly name.  

Error message I received when trying to setup a private endpoint within portal.azure.com (x or X represents obfuscation of identifiers).

{
 "code": "InvalidResourceId",
 "message": "String /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/XXXX-RG/providers/Microsoft.DesktopVirtualization/workspaces/RSDN Workspace is not a valid resource ID.",
 "details": []
}

I received the same when using the Azure shell.  Examining the workspace shows it to have a space in its name.

Today, I tried and created one named "Test Workspace" in Nerdio, intentionally leaving a space in the name.

 And it certainly creates the Object ID in Azure with a space. 

{
   "name": "Test Workspace",
   "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourcegroups/XXXX-RG/providers/Microsoft.DesktopVirtualization/workspaces/Test Workspace",
   "type": "Microsoft.DesktopVirtualization/workspaces",
   "location": "westus2",
   "tags": {
       "WAP_OBJECT_TYPE": "AVD_WORKSPACE"
   },
   "kind": null,
   "systemData": {
       "createdBy": "c41d7734-65a6-4582-ab54-3a14248cabc0",
       "createdByType": "Application",
       "createdAt": "2025-11-10T15:20:29.15Z",
       "lastModifiedBy": "c41d7734-65a6-4582-ab54-3a14248cabc0",
       "lastModifiedByType": "Application",
       "lastModifiedAt": "2025-11-10T15:20:29.15Z"
   },
   "properties": {
       "description": null,
       "friendlyName": null,
       "applicationGroupReferences": [],
       "cloudPcResource": false,
       "objectId": "ffebf56f-da91-41f2-b580-0ad700fb8596"
   },
   "apiVersion": "2019-12-10-preview"

We are running version 6.4.3

Regards,

David

1
Avatar
Anthony Sequeira

Thank you so much for sharing this additional information, David. I am on NME 7.X and sure enough, you cannot use a space in a Workspace name in Nerdio. The GUI literally does not permit it. So it looks like this is something we corrected since your version. 
Thanks again so much for pointing this out and using the community. Please let me know if you have any further questions on this!

0
Avatar
David Sain

Just an update, Anthony Sequeira. 

We were working with Nerdio to setup a new customer and I noted the workspace name is created with a space by default. One can remove the space at this point so it is valid. We are using Manager for MSP 6.5.1 so I have this posted in the wrong place (manager for enterprise). I would call this a bug.


I hope this helps others in the future.

Please sign in to leave a comment.