2026-11-22
Nerdio Manager for MSP – Simply Explained

Show notes
Nerdio Manager for MSP gives managed service providers one console to deploy and run Azure Virtual Desktop and Windows 365 for every customer. This episode explains how the multi-tenant account structure works, what a normal week looks like, and where the honest limits are. In this episode of Simply Explained you will learn:
- What Nerdio Manager for MSP is and why multi-tenant management matters for service providers
- How it sits on top of Azure and Microsoft 365 instead of replacing them
- How a customer account is added and kept separate from every other customer
- How Azure Virtual Desktop and Windows 365 are run from a single console
- How standard setups are reused across customers and what a typical MSP week looks like
- Which common mistakes and limits to plan for
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.
Host: Mirko Peters
Guests
Guests in this episode:
Transcript
Read the full transcript
Speaker 1: Running virtual desktops for a lot of customers gets messy fast. Every customer has their own tenant and their own logins, and they all do things a little differently, so you end up juggling it all by hand. Nerdio Manager for MSP is built to change that. It's one console that sits on top of Azure and lets you deploy and run Azure Virtual Desktop and Windows 365 for every customer you support. We'll walk through what it actually is, how the account structure works, what a typical MSP does with it, and where the honest limits are. So let's start with the plain version. Nerdio Manager for MSP is a management platform for managed service providers. It handles the everyday work of deploying, running, and tuning Azure Virtual Desktop and Windows 365, and it does that for many customers from one place. It also reaches into Microsoft 365 and Microsoft Intune, so the same console covers more than just desktops. The word to hold onto here is multi-tenant. is one customer's own slice of Microsoft's cloud with its own users, its own logins, and its own settings. Multitenant just means one tool can work across many of those slices at once. That's the whole point of the product, and it's what sets it apart from managing a single company's environment. There's a part people get wrong at first, and it's worth clearing up now. Nerdio Manager doesn't replace Azure, and it doesn't replace Microsoft 365. Those services are still doing the real work underneath hosting the virtual machines, and holding the identities. Nerdio Manager sits on top as a management layer, so you spend less time clicking through each customer and more time on the work that needs you. That layer is built around how a service provider actually operates. You onboard a customer, you give them a standard setup, and then you look after them for years. Nerdio Manager treats each customer as its own account, so the way you organize your business and the way you organize the tool line up instead of fighting each other Think about the scale this solves. A growing MSP might look after dozens of customers, and each one arrives with its own history, its own settings, and its own idea of normal. Holding all of that in your head stops working somewhere along the way, and that's usually the point where a platform starts to earn its keep. The name is worth clearing up to. A media manager for MSP is the multi-tenant version built for service providers who look after many customers. There's also Nerdio Manager for Enterprise, which is built for a single organization running its own environment. They share a lot underneath, but they're aimed at different jobs, and picking the right one starts with knowing which side of that line you're on. Now, this next part surprises plenty of admins. Nerdio Manager for MSP isn't a shared website that every partner logs into. It runs inside your own Azure tenant, in your own subscription, and you deploy it straight from the Azure Marketplace. You follow a wizard and the platform lands in your environment as an Azure application. That choice matters for two reasons. First, you keep control of the data, the networking, and the identity behind the portal. Nobody else is sharing the infrastructure that runs your management plane, and you decide where the metadata lives and who can reach it. Second, it's built from native Azure services, so the parts underneath are managed by Microsoft and designed to stay available. There's a practical side to that ownership, too. Because it lives in your tenant, you can give the portal your own web address, back up and restore its configuration, and even move it to a different subscription if your business needs change. None of that is possible if the vendor holds the keys to a shared service. Once it's installed, that installation becomes the foundation for onboarding as many customers as you need. Think about the old way for a second. You had a script over here, a ticket over there, and a spreadsheet to remember which customer used which settings. The new way is one account list, one set of policies and one place to check on everything. There are a couple of things to note before we go further. Installing Nerdio Manager is a one-time job in your tenant, but every customer you manage still lives in their own tenant. Nerdio Manager connects to them and it doesn't absorb them. That distinction is the key to the whole account model and it's exactly where we're going next. After you install Nerdio Manager, the first real step is connecting an account to manage. Usually that's a customer account, but you can connect and manage your own Azure tenant too, which is handy for testing before you touch anything live. Every account you add shows up in the same list, so the console grows with your customer base instead of getting more complicated. Every account starts with permissions, so let's be honest about what you need. You want a Microsoft untry ID user in the customer tenant who has global administrator and subscription owner roles. If the customer still runs an existing Active Directory, you'll also need the domain name and the domain admin credentials. Get those lined up first because everything else depends on them. From there, the flow is fairly calm. You add the account, connect the customer's tenant, and then link one or more Azure subscriptions to it. Linking more than one subscription matters because it lets you create virtual machines, desktop images, and Azure Files shares in any of those subscriptions, not just the first one you connected. There are a few account types to know. You've got a standard account, an Entra ID account, and a cloud PC account, and each one suits a different starting point. If a customer only needs Windows 365 cloud PCs, that cloud PC account is the right door to open. Your own team lives at the MSP level above all of those accounts. Users and roles there decide who can reach which customers and which features so access is managed in one place instead of customer by customer. Two things make onboarding easier at scale. You can import customer accounts straight from Partner Center so you're not typing out tenants you already manage there. You can group customers together with account groups as well, which is useful when several of them share the same standards and you'd rather apply something to the group than to each one by hand. Permissions deserve a second look because there's a real trade-off here. Nerdio Manager offers a granular permission model with least privilege roles so a technician gets only what they need There's also a limited access mode that tightens what the Nerdio Manager app can do inside the customer's tenant, but it cuts functionality at the same time. And the documentation describes that switch as irreversible. It's a decision you make on purpose, not a free upgrade. One last detail that saves confusion later. When you destroy an account, you're only removing the record from the Nerdio Manager database. It doesn't clean up. the customer's Azure environment, so anything left behind is still yours to remove by hand. With an account connected, the real work begins, and Azure Virtual Desktop is where most MSPs spend their day. The building blocks are host pools and session hosts, and if you already run AVD, those names will be familiar. A host pool is the collection of machines that serve a group of users, and the session hosts are the machines themselves. The part that pays off across many customers is images. You build a golden image once and Nerdio Manager lets you keep it as a global image so it can be reused across customers instead of rebuilt every time. Then you manage the image lifecycle, which means you update that image and roll the change out to the hosts that need it. That's how a single improvement reaches every customer who shares the same image. Scaling is the next lever. Nerdio Manager supports global and local autoscale profiles, so you can set the rules once and apply them where they fit. You can also pre-stage autoscale schedules, which helps when you already know a customer's busy hours. The point of all of this is simple. You run the machines you need when they're needed, and you stop paying for capacity that sits idle overnight. That is how scaling turns into a real cost saving instead of a talking point. Around the edges, there are the pieces that keep AVD running smoothly. FSLogix handles user profiles and apps so a user's desktop follows them between machines. And there's a cloud cache option for when profile storage needs to be more resilient. You can set hosts to re-image automatically when a user signs off so the next person gets a clean machine. There are a few more controls that matter day to day. The Azure Capacity Extender can borrow capacity when a region is tight with an auto-revert option that returns the machines to their normal size afterward. StartVM on Connect wakes a machine when someone connects, and ephemeral OS disks and session time limits help keep things clean. You can publish remote applications and set up single sign-on, so users get a smoother start. Smaller conveniences add up as well. Session host names are generated for you, and bulk actions let you act on many session hosts at once, which matters once a host pool grows large. There's a costs and savings view too, which matters because desktops are the part of the bill customers notice first. Being able to see where the money goes, host pool by host pool, makes the next conversation about scaling far easier. Here's how one task feels end to end. You update the golden image, push it out to a host pool, and then check that the new hosts came up and are serving users. That's the rhythm you want, and it works the same way, whether the customer has five desktops or 500. Azure Virtual Desktop is the headline, but it's only part of the picture. Nerdio Manager also administers Windows 365 Cloud PCs, covering both the business and enterprise options. Cloud PCs get their own account type, so if a customer's desktops are really Windows 365 rather than AVD, you set them up that way and manage them from the same console. A customer can even have both, with Cloud PCs for some users and AVD for others, and you keep it all in one place. Then there's Microsoft 365, And this is where the multi-tenant idea shows its value. Nerdio Manager handles policy-based automation and license optimization, and it speeds up onboarding for new customers. There's even a tenant assessment that looks at how an inherited tenant is configured, which matters a lot when you take over an environment someone else built. Instead of guessing, you get a clear picture of what you're walking into before you change a thing. Intune fits in the same way. You get pre-built policies and policy baselines, device management, endpoint analytics scores, application management, group templates, Windows updates, and autopilot device preparation. Assignment filters and named locations for conditional access are in there too, so the policies you write can target the right devices without you rebuilding them per customer. Reporting pulls the whole picture together. Automator reports give you a view across client environments so you can spot a customer that's drifting or a setting that keeps coming up. and bring that to a review instead of building slides by hand. Security and governance get the same treatment. You can apply defender policies and baselines across customers, use EIS-approved hardened images and policies, and control access with role-based access control so each technician sees only what they should. There's also backup and disaster recovery for policies, which takes daily snapshots of your policies, baselines, and assignments, so a bad change can be undone. A few more tools round out the set. There's a cost estimator, console connect for remote support, reserved instance management, and assist pro for in-product help. There's a PSA integration and a REST API for automation and a white label option if you want your own branding on the portal. For customers in regulated spaces, there's a GovEdition that supports Azure Government and GCC high. Now we reach the idea that ties all of this together, which is why a console alone isn't the whole story. The real enemy when you manage many customers is drift. One customer's policies quietly change, another keeps an old image, and a third uses settings nobody remembers choosing. Do that by hand for long enough, and no two customers look alike. Nerdio Manager answers that with standardization. Secure policy baselines and solution baselines give you a known good starting point. global images, global and local autoscale profiles and account groups that you define something once and apply it consistently, instead of building the same policy for the 10th time, you build it once and push it at scale. The phrase to remember is build once, push at scale. A policy, an image or a scaling profile becomes your standard and a new customer simply inherits it. That's the difference between starting from scratch each time and starting from something you already trust. When a new technician joins, they work from your standards too, which is a quiet benefit that shows up over time. Two supporting pieces make that safe. Role-based access control keeps a technician's reach matched to their job so nobody has more access than they need. Backup and disaster recovery for policies means your standards are protected and if someone changes something they shouldn't, you can restore it. Account groups are what make this practical when the customer list gets long. You apply a standard to a group and everyone in it picks it up which beats repeating the same change a dozen times and hoping you didn't miss one. This is the same idea we saw with images and scaling, just applied to policies and whole talents. You set the standard once, you keep it up to date, and you let the console carry it across every customer you look after. That is how to turn a pile of separate environments into one operation you can describe in a sentence. Standards sound good in theory, so let's make them concrete with a week that looks like the real thing. On Monday, a new customer signs on, and you run a tenant assessment to see what you're inheriting. You add the account, link the right subscriptions, and deploy a host pool from your standard image. Because the baselines already exist, the policies come along with it. What used to be a project turns into an afternoon. Tuesday brings the messy tenant you inherited from another provider. The assessment shows you what's out of line, and the baselines give you a target to move toward. You're not inventing a standard on the spot, and that's the relief. You're bringing a tenant back to one you already use and you can show the customer exactly what changed. Wednesday, a user can't sign in. You open the account, check the session host, and then check the FSLogix profile because that's usually where a sign-in problem hides. You fix the actual cause instead of rebuilding a machine and hoping that the whole check happens in the same console you were already using so you're not hunting for the right portal in the middle of a ticket. Thursday is the money conversation. A customer asks what they're spending and whether it can come down. You open the cost estimator, pull the reports for that account, and answer from the same place you manage everything else. Autoscale profiles often do the heavy lifting here because off-peak hours are where waste collects, and the customer can see the difference without you hand-building a spreadsheet. Friday, someone leaves the customer's company. You run an off-boarding flow from a template, and approvals and notifications make sure the steps actually happen. Nothing gets missed because it depended on one person remembering. That's the kind of weak standardization buys you. Now for the honest part, because a good tool still has limits and knowing them is what separates a smooth rollout from a painful one. The first mistake is treating Nerdio Manager as a replacement for Azure, Microsoft 365 or Intune. It isn't a replacement and the underlying resources are still Microsoft's. You still need to understand those services and you still own how they're configured. The second mistake is expecting it to fix a bad architecture. If a customer's design is weak, the tool doesn't repair the design. What it does is make your standard easier to apply, which is a different thing. You still have to decide what good looks like. The third mistake is over-permissioning every customer. Handing out global administrator and subscription owner everywhere is the easy path, and it's the risky one. The granular permission model with least privileged roles exists for a reason, and it's worth the extra thought upfront. There's a limit hiding inside the permission story, too. Limited access mode heightens what Nerdio Manager can do in a customer's tenant, but it reduces functionality and the documentation calls that change irreversible. It's a deliberate trade-off, so choose it with your eyes open. Ignoring the image and policy lifecycle is another common slip. You build your standard and then you stop updating it. Drift comes right back and within a few months your customers have quietly drifted apart again. A standard is only as good as the habit of maintaining it. One more mistake is assuming every account type behaves the same way. A Cloud PC account and a standard account don't expose the same set of features, and the docs are clear that some capabilities are preview, version-specific, or limited by the account model. Read the current documentation for your version instead of assuming everything is universally available. Finally, remember where responsibility sits. Licensing and identity stay with you as the partner. Nerdio Manager is an automation and management solution, and the partner is responsible for understanding and managing Microsoft Identity Services, Microsoft 365 and Azure resources. The tool makes that work faster, but it doesn't take the ownership of your desk. So here's the reframe. The value of Nerdio Manager for MSP isn't any single feature you just heard. It's one console you own sitting inside your own Azure tenant, plus a set of standards you apply everywhere with the limits understood before you lean on them. How are you managing virtual desktops across your customers today? And is any of it still by hand? If this made the topic feel less intimidating, Subscribe to M365FM to master the tools and the mindset shaping the future of work.