Step by Step Installation and Configuration of Nerdio Manager for Enterprise 7.4 – Part Three
Published December 2025 at blog.youngtech.com
Click Here to Download this Full Guide as a PDF
Back in November I published the Full Guide linked above, which includes 165+ pages of Step by Step instructions for Installation and Configuration of Nerdio Manager for Enterprise 7.4. Part One of this Blog Series can be found here:
A couple weeks later, I published Part Two of this Blog Series, which can be found here:
This post is Part Three (of Four), all sections of which can be found in the Full Guide linked above.
As mentioned previously, this guide is not a replacement for the excellent documentation available at https://nmehelp.getnerdio.com. I highly recommend checking out the official Implementation Guide, which I’ve linked here.
What This Guide Covers
This walkthrough is designed to help you lay the foundation for a successful Proof of Concept (PoC) or initial deployment of Nerdio Manager for Enterprise. In the previous Blog Posts, I shared the first three section out of six outlined below. In this Part Three of the series, I’ll be sharing the fourth and fifth sections from the 165+ page guide.
- Initial Deployment of Nerdio Manager for Enterprise from the Azure Marketplace (Included in Previous Blog Post)
- Grant Consent using Global Administrator (Global Admin) account (Included in Previous Blog Post)
- Creating Initial Desktop Image (Included in Previous Blog Post)
- Creating Resource Group and IT Workspace (Included in This Blog Post)
- Assign the IT Workspace and Login (Included in This Blog Post)
To be shared in future parts of this multi-part blog series:
- Lock Down Nerdio Manager for Enterprise to an Azure Private Endpoint
If you want to review the entirety of the content that I’ll be releasing over the coming weeks in multiple parts, you may: Click Here to Download this Full Guide as a PDF
Reminder of Prerequisites for a Smooth Deployment
To ensure a time-efficient engagement, I always confirm the following basics are in place before starting:
- Nerdio Engineer Account: The engineer (typically the PoC contact) should have Owner privileges on at least one Azure subscription. In this case, my account dane@youngtechavd.com serves as the Nerdio Engineer, with the subscription PAYGO-SPOKE-NER-INFRA designated for deployment.
- Azure Virtual Network (VNET): Pre-staged with subnets and configured to allow:
- Internet access for Azure Portal connectivity
- Access to Active Directory Domain Controllers for AVD domain join
- Custom DNS pointing to AD DCs for private DNS resolution
- A Private DNS Zone to restrict App Service access from the public internet
- Global Admin Access: Required at specific stages for elevated privileges.
- Entra ID Synchronization: Ensures Workspaces can be provisioned to MFA-enabled AD domain users.
For this blog post (Part Three), let’s jump back in where we left off!
Section 4: Creating Resource Group and IT Workspace
Before creating our first Workspace, we should create a new Resource Group (RG) and link it to NME to use for initial resources being deployed. Click Settings Environment and expand Linked Resource Groups to see what RGs have been linked already.
Flip over to the Azure Portal and click Resource Groups in the main view (or search) to go to the RG view:
On the Resource Groups view, click Create Create new resource group as shown:
Provide a name for the new Resource Group. For example, I’ll be deploying a Resource Group for the initial deployment of the Desktop Image for IT purposes, so the initial RG name for this example is rg-nerdio-infra-itworkspace as shown. Click Review + Create:
Click Create:
Monitor the RG as it’s being created by watching the top right and notifications area. Click Refresh until the new RG is displayed:
After refreshing, you’ll see the new RG that was created:
Flip back over to the NME Console and click the Link button to tie in the new RG just created in the Azure Portal:
Click the drop-down and select the new RG that was created, rg-nerdio-infra-itworkspace as shown:
With the new RG added to the list, click OK:
Now, the original RG and the new RG are both showing linked as expected:
Next, go to the Workspaces section on the left, and click New Workspace:
Enter basic information for the new Workspace including: Name, Friendly Name, Description, Resource Group (just created and linked) and Location. It’s important to use the same location that was previously used when creating the initial Desktop Image. When reviewed, click OK:
Progress will be shown with the three dots as shown previously:
If successful, the new Workspace will be shown as follows. Click the Tasks section on the top to view progress:
Tasks show the Create workspace operation has a Status Complete:
Flip back over to the Workspaces section on the top, and click the three dots on the far right, then select Dynamic host pools as shown:
Click New Host Pool:
Enter the details for the new Dynamic Host Pool, using the information shown below as a reference:
Scroll down and review additional settings until everything has been entered. Click OK to proceed:
Progress is shown using the three dots as previously shown:
Once created, Manage Auto-Scale will likely be displayed, allowing you to further customize the settings of the Dynamic Pool:
Scroll down and review the additional settings. Recommended changes will be shared on future screens:
Initially I recommend changing the Session limit per host to 5, as this is typically a good starting point until a baseline performance per VM has been established through testing. Additionally, since this initial Dynamic Pool is being created for IT Administration and Management, changing the capacity to quantity 1 is acceptable for the initial deployment:

Scroll to review additional settings:
As with most initial Dynamic Host Pools, it’s recommended to select Auto-heal broken hosts as a default and general rule. Leave all defaults set to provide a good starting point for Auto-heal:
At the very bottom, ensure Auto-Scale is toggled to Enabled as it’s by default set to Disabled for any new Dynamic Host Pools. When finished reviewing, click Save:
The settings are being saved, as shown below:
If there were no errors, in the bottom right a pop-up will be displayed as shown below:
Flipping back to the Dynamic Pools view will show these configurations and settings:
Section 5: Assign the IT Workspace and Login
Next to the new Dynamic Host Pool, click the three dots and select Manage Users and Groups to assign the IT Workspace to appropriate Entra ID users:
Search for the e-mail addresses of the appropriate users and click the checkboxes next to each name (or group) and click Assign:
Click OK to assign the IT Workspace to the users or groups:
Once successfully assigned, the Assign button will be grayed out and replaced with a button that says Unassign. This indicates the users are properly assigned. Another clue is that the far right column for Assignment will show the appropriate appgroup, as shown below:
Click back to the Workspaces view, and next we’ll complete the validation steps to login to the new IT Workspace created:
Open the Windows App and authenticate with Entra ID using an account that was assigned to the IT Workspace (for example dane@youngtechavd.com):
Enter the credentials for the assigned account:
Complete the Entra ID Multi-Factor Authentication process as shown:
Validate the new Win11_IT_Workspace icon shows as configured through NME Workspaces. Click Connect:
Depending on how much time was taken between steps, the Dynamic Host Pool may not be fully provisioned yet, and a similar error may appear as shown:
If an error is displayed, navigate to the Tasks view of the IT Workspace and determine if there are any operations that are still In Progress as shown below:
Clicking the Information ( i ) icon on the far right shows the progress as the steps are being completed against the IT Workspace, as shown:
Scroll down to see what steps are still In Progress as shown below:
Continue to monitor this process until all steps that show In Progress show as Complete as shown below:
If all tasks are successful, switching back to the Tasks view should show all status is Complete as shown:
With all tasks Complete, click Connect from the Windows App again:
If a Dynamic Host Pool has a host available, a password prompt should be displayed for RDP authentication against the IT Workspace. Enter the appropriate user credentials and click OK:
The Windows App shows the connection is in progress with a spinning wheel while connecting:
Successfully launching the IT Workspace should display a Windows 11 Desktop as shown below.
Stay tuned in the coming weeks for Part Four to be published! In the meantime…
Click Here to Download this Full Guide as a PDF
To compliment this Blog Post, I have created a 165+ page PDF with the remaining steps in the following sections:
- Initial Deployment of Nerdio Manager for Enterprise from the Azure Marketplace
- Grant Consent using Global Administrator (Global Admin) account
- Creating Initial Desktop Image
- Creating Resource Group and IT Workspace
- Assign the IT Workspace and Login
- Lock Down Nerdio Manager for Enterprise to an Azure Private Endpoint
This PDF guide is available free of charge to Subscribers of the YOUNGTECH BLOG. To continue reading, please request access to this free resource using the following link: https://lp.constantcontactpages.com/sl/CJIeeLI/nme74
Click Here to Download this Full Guide as a PDF
By completing the form above, you will receive an e-mail to download a PDF of the full guide and continue reading from this section. Once you’ve received the link, you can unsubscribe from the blog at any time, but it’s our way of staying connected to our audience. Please advise if you have any challenges reaching the link provided in the e-mail.
I trust this will be a useful resource to you and that you’ve enjoyed this Step by Step Installation and Configuration of Nerdio Manager for Enterprise 7.4 guide. Best of luck in your NME deployments! If you need any help along the way, don’t hesitate to reach out.
Thank you so much!
Dane Young, MBA
My X | My LinkedIn
















































