M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

2026-11-21

Nerdio Manager for Enterprise – Simply Explained

Follow the showNew episodes on Microsoft 365, Copilot and more, free in your podcast app.Apple PodcastsSpotify
Cover: Nerdio Manager for Enterprise – Simply Explained
Nerdio Manager for Enterprise sits on top of Azure Virtual Desktop and Windows 365 and gives you one console to run, scale and pay for your desktops. This episode explains what it does, what it does not do, and where the limits are. In this episode of Simply Explained you will learn: - What Nerdio…

Show notes

Nerdio Manager for Enterprise sits on top of Azure Virtual Desktop and Windows 365 and gives you one console to run, scale and pay for your desktops. This episode explains what it does, what it does not do, and where the limits are. In this episode of Simply Explained you will learn:

  • What Nerdio Manager for Enterprise is and how it sits on top of Azure Virtual Desktop and Windows 365
  • Why it installs inside your own Azure subscription and what that means for your data
  • How host pools and images are built and managed as repeatable building blocks
  • How auto-scale helps you pay only for the desktops that are actually running
  • How apps, users and profiles are handled, and where Windows 365 Cloud PCs fit in
  • Which limits and mistakes to plan for, and how to prove the cost value

Simply Explained by M365.FM breaks down Microsoft 365, Azure and modern IT topics in clear, jargon-free language. Hosted by Mirko Peters. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support. This episode includes AI-generated content.

Apple Podcasts · YouTube · Deezer

Host: Mirko Peters

Guests

Guests in this episode:

Transcript

Transcript (TXT)

Read the full transcript

Speaker 1: Let's walk through Nerdio Manager for enterprise. It's a management layer on top of Azure Virtual Desktop and Windows 365, so you run and scale desktops without clicking through a dozen Azure blades. It installs into your own Azure subscription, so your environment stays where it is and your data stays in your tenant. On a normal day, it handles images, host pools, scaling, and app delivery, and it manages Windows 365 Cloud PCs too. There are real limits, and those matter as much as the features. Azure Virtual Desktop and Windows 365 solve one problem and create another. They give you Windows desktops in the cloud, and then they hand you a pile of moving parts to keep running. You have host pools to build, images to patch, session hosts to watch, apps to deliver, and a bill that grows if you look away for a week. Nerdio Manager for Enterprise is a deployment, management, and auto-scaling platform for Azure Virtual Desktop and Windows 365 Cloud PCs. It's a layer that sits on top of Microsoft's desktop services, and it gives your team one console to run the whole environment. Microsoft still runs the desktops. Nerdio gives you the controls that Microsoft leaves to you to assemble. That distinction matters more than it sounds. You're not replacing Azure Virtual Desktop or Windows 365, and you're not moving your users onto some other platform. You're adding a management layer to the environment you already have. Nerdio Manager can attach to an existing deployment or it can help you stand up a new one from scratch and it uses the same building blocks either way. The goal stays simple. Nerdio Manager makes the environment you already pay for easier to operate without asking you to rebuild it. That's the whole idea in one line. It helps to know who this version is for. Nerdio Manager for enterprise is built for internal IT teams. It's a separate product from Nerdio Manager for MSP which service providers use to run many customer tenants at once. At a glance, the platform covers host pools and session hosts, desktop images, auto-scaling, application delivery, user and profile management, cost reporting, and the automation that ties it all together. Picture your desktop environment as a building with a lot of wiring behind the walls. Azure Virtual Desktop and Windows 365 are the wiring, and Nerdio Manager is the control panel that lets you work with it without pulling the wall apart. The rest of this video walks through each piece, starting with where the tool actually lives, because that's the first question most IT teams ask. Here is the detail that usually decides the conversation. Nerdio Manager installs from the Microsoft Azure marketplace, and it runs as an all-pass Azure application inside your own Azure subscription and your own EntraID tenant. You choose the region it lives in, the management tool sits in your house, not the vendors, Nerdio states that no user data ever leaves the Azure environment and that there's no third-party access to the deployment. Those are vendor statements and they are worth repeating to your security team because they answer the first question that team will ask. Here is what actually gets installed. The deployment is a managed application and it drops a set of Azure services into a resource group you control. That includes two app services, a set of automation accounts and runbooks for scripted actions, a key vault, log analytics workspaces, a SQL database and server and storage accounts. If you already run Azure Virtual Desktop, you will recognize most of those as the same services you would otherwise assemble by hand. Now the permissions, because this is where people get nervous. Whoever installs Nerdio Manager needs the global administrator role in Entra ID and the owner role on the Azure subscription. That's a big ask and it's temporary. Nerdio says those elevated permissions are needed only for the initial install and configuration. not for ongoing use. Once the platform is running, no Azure user permissions are required to manage the environment because most actions run on Nerdio Manager's behalf. Billing follows the usual marketplace pattern. Activating the license creates a SaaS subscription object on your Azure subscription so the Nerdio chart shows up as a third-party service on the bill you already pay. You can also tighten the deployment over time. Nerdio's documentation walks through hardening the app service, the storage account, the SQL database, and the key vault. That way, the management tool itself meets the standards you hold your workloads to. None of this changes how your users connect. They still sign in the same way they do today. That covers where the tool lives and what it asks of you. Now let's look at what it does, starting with the two ideas everything else is built on. Everything in Nerdio Manager starts with the host pool and the desktop image. A host pool is a group of session hosts, and each session host is a virtual machine that a user actually connects to. The pool can be pooled where several users share sessions on the same machines or personal where each user gets a desktop of their own. That choice is really a choice about cost and control. Pooled hosts stretch a single virtual machine across several people, which is cheaper for shift work and task-based roles. Personal desktops give one person a machine of their own, which is simpler to support but costs more because that machine stays there whether they're using it or not. A desktop image is the template behind all of it. It's the Windows build plus the apps and settings that every session host starts from. Get the image right and every machine you create inherits that work. Get it wrong and you feel it everywhere. This is where Nerdio Manager earns its keep. It can create version test deploy backup and restore desktop images and it works with Azure Marketplace images your own custom images, images from Azure Compute Gallery and CIT. The lifecycle covers patching, versioning, staging, and testing, so you update the template once and roll it out, instead of touching machines by hand and hoping you caught them all. To see why that matters, look at what the manual version takes. You spin up a virtual machine, configure it the way you want, generalize it so it can be copied, shut it down, capture the disk, and turn it into an image. Then you do it again the next time Windows or an app needs updating, Nerdio Manager automates that sequence and the documentation describes exactly that flow of building the image, then feeding it to the pool. You can also bring existing host pools under management rather than rebuilding them. If your team already built host pools by hand in Azure, Nerdio Manager can import them and take over the day-to-day work. That matters when you inherit an environment instead of designing one from scratch. From the image and the host pool, you publish what users actually see. Workspaces and application groups decide which desktops and remote apps each group of people can reach. You build the pieces once, then point the right users at the right ones, which is a lot cleaner than assigning people to machines one at a time. Once those hosts are running, though, the next question is how many of them you actually need, and that's where the cost story starts. Now we reach the feature most teams care about, because it's the one that shows up in the budget. Autoscale keeps only the number of session host virtual machines your environment actually needs. When demand drops, Nerdio Manager stops or deletes idle virtual machines. When demand rises, it starts or creates them again. It reacts in two ways. The first is a schedule you set, so hosts come up before the workday and go down at night and on weekends. The second is live usage, so it can add capacity as people log in and pull it back when they're gone. You can combine those triggers, which is what keeps a busy Monday morning from fighting a quiet Friday afternoon. The settings around it are what make it usable in a real environment. You set host pool sizing so there's always a floor of capacity. You can use rolling drain mode to retire hosts without cutting someone off mid-task. You can pre-stage hosts so they're ready before users log in and send a message to anyone still connected before a host is removed. The reason pre-staging matters is that a virtual machine takes time to boot and join the environment. If you only start hosts when the first user connects, that user waits. Pre-staging brings the capacity up ahead of the demand, so the experience feels normal even though the machines weren't running a few minutes earlier. Scaling also has to be careful about the people already working. Pulling a host out from under an active session is the fastest way to lose trust in the automation. That's why the drain mode and messaging options exist. A second job runs alongside the scaling. AutoHeal watches for unhealthy session hosts and can take action when one goes bad. It can try a restart, run scripted remediation, or remove and rebuild the host. If it has to rebuild, it can power on a spare virtual machine to hold capacity steady. While that happens, you also get the safeguards you would want before you trust any automation with production desktops. You can exclude specific hosts from scale-in or scale-out operations. And you can pause a host pool's autoscaling entirely for maintenance or a holiday. When you need proof the work paid off, there's an autoscale history report you can share. One honest note before we move on. Nerdio's own guidance is that the savings come from configuring those triggers, watching utilization and right-sizing over time. Autoscale is a tool, not a switch, and it rewards the team that tunes it. Scaling and images take care of the machines. The next part takes care of what people do on them, application management is where a lot of desktop teams lose their week. Getting the same app onto every session host at the right version is repetitive and easy to get wrong. Nerdio Manager brings that into one place with unified application management. It deploys and manages applications across Azure Virtual Desktop, Windows 365, and Intune managed endpoints from the same console, It supports public and line-of-business apps through Winget and private repositories, and it can import the applications you already have in SCCM. For the awkward ones, Shell apps let you package an application with PowerShell, and MSIX AppAttach handles the AppAttach format. Think about the daily reality in An app gets a security update and now someone has to find every session host, confirm which ones are in use, schedule a window, push the update and verify it landed. Multiply that by every application your business runs and you can see why app delivery becomes a full-time job on its own. The private repository support matters for line of business software. The apps your finance or operations team depends on that will never show up in a public catalog. You host them yourself and Nerdio Manager delivers them just like everything else in the platform. On top of delivery, you get lifecycle and version management. So installing, updating and removing an app becomes a policy instead of a ticket. Deployment policies decide how, where and when an application lands, which means the person who owns the app can define the rule once and stop repeating it. Then there are the pieces that follow the user. Profile management covers FSLogix and user experience sync so a person gets the same desktop files and settings wherever they land. You can manage user sessions directly and run onboarding and offboarding flows so new starters and leavers are handled the same way every time instead of by whoever remembers. Finally, there's access control. Granular role-based access control with custom roles lets you give the right people the right access without handing everyone the keys. A self-service portal can hand some of the routine actions back to end users, which is one fewer request sitting in your queue on a Monday morning. Everything so far applies to Azure Virtual Desktop, but Nerdio Manager also manages Windows 365. That raises a fair question because the two products sound almost identical and they're not. Azure Virtual Desktop session hosts live in your Azure subscription, You control the sizing, the networking, the disks, and the scaling, and you pay for what you use. So compute charges stop when machines power down. Windows 365 is different. Microsoft hosts each cloud PC in its own Azure subscription and sells it as a flat per user monthly license. And you manage those cloud PCs through Intune like any other endpoint. The user experience hides that difference. Both run Windows 11 desktops. Both connect through the same Windows app client. and both authenticate through Microsoft Entra ID. From the user's chair, they are nearly the same thing. Nerdio's own guidance is to match the model to the workload. Use Windows 365 for dedicated desktops where predictable cost matters, and use Azure Virtual Desktop for pooled or variable workloads where scaling can drive the cost down. Many enterprises end up running both, and that's where a single console helps the most. Choosing between the two is less about which product is better and more about which cost model fits the user. A person who needs their desktop every working day at a predictable price is a natural fit for a cloud PC. A team that shares machines across shifts or that spikes during certain hours usually does better on pooled Azure Virtual Desktop. You only pay for the hosts that are actually running. And there's one nuance worth saying out loud because it changes the math. Cloud PCs are built per assigned user, whether that person logs in or not, while pooled Azure Virtual Desktop builds on consumption. In most environments, far from all named users are logged in at the same time. If you're paying per seat for people who aren't at their desks, that's money you can see and don't have to spend. Nerdio Manager keeps both worlds in one place with Windows 365 provisioning policies, user settings, role-based access, image management, and application delivery handled from the same console. That is how to run two cloud desktop models without two consoles. If you have to justify any of this to someone holding the budget, this section is for you. Nerdio Manager ships with tools built for that conversation. The cost modeler lets you model Windows 365 and Azure Virtual Desktop scenarios before you deploy them so you can compare configurations and estimated cost instead of finding out later. Nerdio Advisor and its total cost of ownership analysis look at your environment and point out cost configuration and optimization opportunities. Per user cost reporting attributes, Azure Virtual Desktop costs to individual users, which is what you need when Inance asks who is spending what. The modeler is worth calling out because it runs before you commit. You describe the scenario and it gives you an estimate you can take to a budget meeting, which is a very different conversation from deploying first and explaining the invoice later. Comparing a Windows 365 option against an Azure Virtual Desktop option on paper is often the difference between a project that gets approved and one that stalls. For day-to-day visibility, real-time insights monitors live performance, health, and user experience signals, and reporting covers workspaces, host pools, hosts, images, and applications. That matters when someone asks whether the environment is actually healthy and whether the money went where it was supposed to. On savings, here is the honest framing. Nelio publishes its own savings estimates and customer stories. Treat those as vendor figures and measure the effect in your own environment with the cost reports. Those are vendor and vendor published numbers. Your result depends on your workloads, your sizing, and how well you tune autoscale, so treat them as what is possible rather than what is promised. Reporting closes the loop. Once the environment is live, you can show what changed, where the hours went, and how the spend moved. That's exactly what you need the next time someone asks whether the tool was worth it. Now the limits, because there are a couple of things to note before you plan a rollout, and you will meet them if you plan around the marketing instead of the documentation, these come from Nerdio's own guidance and they're the kind of detail that decides whether a rollout goes smoothly or becomes a project review. Let's start with scale. Nerdio Manager supports a maximum of 2,500 virtual machines per subscription per region, in line with Microsoft's guidance. That's a real ceiling, and if you're planning a large estate, you plan around it from the beginning. Then there's density. For best performance, Nerdio recommends putting each host pool's session hosts in their own dedicated resource group and keeping the number of session hosts per resource group at 100 or fewer. Packing hundreds of hosts into a single resource group is a common shortcut and it costs you performance later. What's the API limits as well? Azure throttles API calls and large operations like starting, stopping, creating or deleting many hosts at once can trip that throttle. Nerdio Manager has a built-in group processing function for batching those operations and you should use it instead of firing everything off in one burst. One infrastructure requirement catches people out. Nerdio Manager needs its own newly created, dedicated pass SQL instance. Nerdio states that it's not supported to create the Nerdio Manager database inside an existing SQL instance or to host other databases in that dedicated instance. Plan for that database as its own resource. There's also the addition nuance. Not every feature is in every edition or license tier, so check the feature table for the edition you're considering before you assume something is included. And the biggest mistake is the simplest one, which is treating autoscale as set and forget. The savings are real, but they're operational. Someone has to configure the triggers, watch utilization, and right-size host pools as usage changes. The teams that get the most out of Nerdio Manager treat it as ongoing work, not a one-time setup. The theme across all of these is planning. None of them are reasons to avoid the platform. They're the details you want in the design document before the first host pool goes live, so you're not discovering them at 2,000 virtual machines. A little planning up front saves a painful redesign later. So that's Nerdio Manager for Enterprise, a management layer that runs in your own Azure subscription. It handles images, host pools, autoscale, apps, profiles, cost and reporting for Azure Virtual Desktop and Windows 365. The question for your team is simple. Ask yourself which of those jobs is still eating your wheat. If this made the topic feel less intimidating, subscribe to M365FM to master the tools and the mindset shaping the future of work.