Building on the success of the first edition, we're excited to launch the 2nd Edition of '@MasteringAVD Azure Virtual Desktop.' With insights from @virtualmanc N, @MarcelMeurer , and myself as authors, this updated guide dives into the latest Azure Virtual Desktop features, offering fresh perspectives from three Microsoft MVPs. Why this edition stands out: ➡️Diverse Expertise: Benefit from the unique experiences and viewpoints of three End User computing experts. ➡️ Updated and new content! ➡️Current Insights: Get up-to-date with Azure Virtual Desktop's latest advancements and practical applications. ➡️Real-World Strategies: Apply proven tips and strategies in your work environment. ➡️Ideal for IT professionals and workspace administrators, this book is your key to mastering cloud virtualization and remote application delivery. Look out for the launch date to enhance your skills with this essential Azure Virtual Desktop resource! A big thanks to Packt for making this happen! + Technical Reviewer's and there is more to come soon. 😊 #AzureVirtualDesktop #CloudComputing #EndUserComputing #BookAnnouncement #MasteringAVD #AVD #Packt #Team

If MSI is what you know, MSIX can feel unfamiliar. It works differently: the app runs in a container, installs per user, and updates in blocks. Once you see how, it makes sense. Start with MSIX Fundamentals. It's free. What caught you out first, moving from MSI?

You've heard of MSIX. But could you explain how it works? App-V is end of life. What's your plan? We built free training to answer both: two courses, study guides to keep, a badge to prove it. Challenge: explain how an MSIX gets onto a device in one sentence.

ASK FOR THE SAVINGS REPORT FIRST Do not start with a clean-up project. Start with a savings report that shows what is still being paid for across Microsoft 365 and Azure, what is oversized or unused, and what can be fixed first. With #EtherInsights, the first step is low effort: - read-only visibility - no deployment - proof of unassigned licences, idle virtual machines, oversized resources and forgotten services - guided next actions, not another passive dashboard If you want a clear view of where spend has stopped earning its place, get your savings report. #CloudCostOptimisation #Microsoft365 #Azure

RISK, RECOVERY AND COST NEED ONE DECISION A VDI exit stalls when risk, recovery and cost are argued in separate rooms. The next step should be one planning motion, not three parallel debates. The Windows 365 Migration Assessment: Risk, Recovery & TCO gives the buyer group a usable decision pack: - first-wave cohort shortlist - one-to-one versus Frontline recommendation - Microsoft Hosted Network versus ANC rule - recovery baseline for post-cutover support - TCO assumptions shaped by the estate mix That matters because standard desktops do not need edge-case architecture. Move the stable majority first. Keep networking simple by default. Prove the recovery path. Then model the numbers against the right desktop mix. #EtherInsights carries that into day two by keeping sizing, usage and ownership clear after cutover. If you want the assessment outline, comment Assessment. #Windows365 #VDI #DigitalWorkplace

ETHERINSIGHTS SHOWS WHAT TO KEEP, FIX, OR REMOVE A cost view without a next move does not change the bill. That is why #EtherInsights is built as the visibility and action layer across Microsoft 365 and Azure. It helps teams see what is sitting in the estate, what is oversized, what is unused, and what has drifted away from value. - Expose idle and forgotten resources - Highlight oversized Azure capacity - Surface low-value or unused licences - Show spend with no clear owner - Turn findings into practical next steps Read-only access means no deployment work and no disruption to production. The result is proof in hours, not months, and a clearer route to a savings report that buyers can act on. #Azure #Microsoft365 #CloudCostVisibility

SAVINGS REPORTS SHOULD SHOW WHAT IS STILL BILLED A savings report is only useful when it shows exactly what is still being paid for. #EtherInsights turns read-only tenant visibility into a report your team can review, challenge and act on. Key Features - Read-only visibility across Microsoft 365 and Azure - Unassigned licence analysis by SKU - Duplicate licence allocation detection - Idle and oversized Azure resource review - Costed findings with prioritised next actions - Output built for operational and commercial review Technical Benefits - Separates billed estate from active estate - Connects allocation, usage and spend in one view - Highlights shelfware and low-value capacity clearly - Gives buyers proof before broader optimisation work starts - Makes remediation easier to assign and validate Deployment fit & scope - Microsoft 365 licence estates - Azure subscriptions and resource groups - Read-only access model - No deployment-heavy change required - Suitable for IT, operations and finance stakeholders When the report shows what is unused, oversized or forgotten, the savings conversation becomes specific. Recovered budget can then be redirected with evidence, not assumption. #CloudCostVisibility #Microsoft365 #Azure

ESTATE MIX SHAPES WINDOWS 365 TCO A TCO model fails when every desktop is treated as the same desktop. Key Features - Cohort-based estate modelling for the stable majority and genuine exceptions - One-to-one versus Frontline recommendation based on concurrency, not an average user profile - Microsoft Hosted Network as the default design, with Azure Network Connection separated as an exception path - EtherInsights as the assessment and day-two control layer for sizing, usage, ownership, and recovery - Open modelling of licence baseline, networking exceptions, and rollout assumptions Technical Benefits - Replaces blended desktop pricing with cohort-specific assumptions - Shows where Frontline share changes the estate shape - Prevents ANC exceptions being buried inside the default model - Connects failure domain decisions to recovery planning and operating ownership - Gives finance, architecture, and service teams one model to evaluate Deployment fit & scope - Enterprise or Business one-to-one for mainstream all-day users - Frontline dedicated for shift, part-time, and contingent users who need a personal desktop - Frontline shared for short task-based access with one user at a time - Microsoft Hosted Network first, Azure Network Connection only where controls or application reach require it - Source VDI estates under review: Citrix, VMware Horizon, on-premises pools, and IaaS-hosted desktops If the estate model is still split across separate spreadsheets, pilot notes, and architecture decks, the decision is still too loose. Start with the Windows 365 Migration Assessment: Risk, Recovery & TCO. #Windows365 #EUC #VDI

THE PILOT NEEDS A RECOVERY SCORECARD A pilot is not credible until you can show the recovery path. The service desk does not sign off because a desktop launched. It signs off when a user can get back to work quickly after something breaks. For a Windows 365 pilot, prove recovery in a clear order: - Restart for routine stuck-session issues - Restore to a known-good earlier state where policy allows - Reprovision when the Cloud PC needs a clean rebuild Windows 365 gives teams a practical ladder here. - Enterprise supports point-in-time restore - Business uses defined restore point intervals - Action status for Restart, Restore and Reprovision can be tracked through the Cloud PC actions report Then publish the numbers that matter to service delivery: - P50 and P90 time to productivity by recovery action - Tickets per 100 users for desktop access and performance - Self-resolved restart rate - Action success rates by restart, restore and reprovision That is where the operating model changes in practice. - Recovery becomes part of the service, not a separate architecture exercise - Many single-user incidents avoid the old VDI cycle of recompose, pool rebuild or profile repair - Service desk leaders get evidence they can defend internally #EtherInsights helps teams make that proof usable. - Identify the stable majority to move first - Match one-to-one or Frontline to actual concurrency - Keep networking simple by default - Keep sizing, usage, ownership and recovery visible after cutover If you want the assessment structure we use before pilot design, comment Assessment. #Windows365 #EUC #ServiceDesk

DO NOT DRAG VDI NETWORKING INTO WINDOWS 365 If every Cloud PC depends on customer routing, DNS and subnet hygiene by default, you have copied the old failure domain into a new service. Key Features - Microsoft Hosted Network as the default deployment path for most users - No need to build and maintain customer-managed VNets, firewalls, routing rules, or NAT gateways - Multi-region selection helps spread users so one regional issue affects only a fraction of the estate - Windows 365 Enterprise uses Intune for device management and Entra ID for identity and access control - Azure Network Connection stays available for genuine line-of-sight requirements - MHN and ANC can run side by side in the same estate Technical Benefits - Removes avoidable network complexity from standard desktop delivery - Reduces shared failure modes tied to customer DNS, IP capacity, routing, and sync timing - Shrinks the operational handoff between EUC, network, and platform teams - Supports a simpler management model centred on endpoint operations, not VDI platform engineering - Keeps Conditional Access close to the identity plane Deployment fit & scope - Use Microsoft Hosted Network for the stable majority of desktop users - Use ANC only where hybrid join, Kerberos or NTLM, SMB, or on-prem line-of-sight is genuinely required - Choose one-to-one Cloud PCs or Frontline from concurrency, not an average user profile - Assess legacy VDI pools separately so edge cases do not set the default architecture - Use #EtherInsights to prove who moves first, where ANC is truly needed, and how the estate should be controlled after cutover If you want a rules-based path that keeps the default simple and isolates the exceptions, ask for the Windows 365 Migration Assessment: Risk, Recovery & TCO. #Windows365 #EUC #DigitalWorkplace

WASTE NEEDS A NAMED NEXT STEP Waste stays put when the next move is unclear. In Microsoft 365 and Azure, teams can usually spot the symptoms: - idle environments still running - oversized capacity after peak demand - old test and dev estates left in place - spend that nobody owns What is usually missing is the operational hand-off. #EtherInsights gives teams read-only visibility across the estate, then turns that proof into guided next actions: - show what is idle - show what is oversized - show who should act - provide guided fixes and ready-to-run scripts That is the difference between seeing waste and removing it. It is how visibility becomes a savings report buyers can use. #CloudOptimisation #AzureCostManagement #Microsoft365

FRONTLINE STARTS WITH CONCURRENCY The average user does not exist - and desktop teams inherit the mess when you pretend otherwise. Shift staff, part-time teams and contingent users do not consume desktops like all-day knowledge workers. Force them into one model and the problem reappears in blocked access, unclear ownership and a pilot that teaches the wrong lesson. For Windows 365, the better question is simple: who needs a desktop all day, and who only needs one when a shift starts? - All-day, predictable users -> 1:1 Cloud PC - Personal desktop, non-concurrent use across shifts -> Frontline dedicated - Short task access, one user at a time -> Frontline shared That is why Frontline starts with concurrency, not headcount or an average profile. #EtherInsights helps teams prove those cohorts early, set pilot KPIs around real usage, and keep sizing, ownership and recovery under control after cutover. If your VDI exit still starts with user averages, start with the Windows 365 Migration Assessment: Risk, Recovery & TCO. #Windows365 #DigitalWorkplace #EUC

VALIDATE ONE MSIX PATH IN 7 DAYS Use the 7-day EtherApps Forge trial to validate one MSIX path on a real application. It is a practical way to see whether a live installed app can move into a modern deployment workflow without starting from scratch. In the trial, you can: - capture the application directly from the running system - work from the real footprint, even when installer media is missing - review files, registry, AppData, services and dependencies - use AI agent based packaging guidance to assess likely routes and packaging risks - produce deployment-ready outputs for MSIX-led environments, including MSIX, MSI, IntuneWin and App Attach This turns the MSIX discussion into an execution decision. You can test: - a no-installer application - an App-V migration case - a Windows 11 or Intune packaging path - an application that may still need MSIX fix-up work before delivery If you want a clear next step, start with one app. Message us with the application name and we will arrange the 7-day trial. etherapps.ai #MSIX #Windows11 #ApplicationPackaging

READ-ONLY REVIEW EXPOSES OVERSIZED AZURE Oversized Azure is easier to ignore when nobody can see it clearly. A VM sized for a past project. Reserved capacity sitting below use. An environment left at peak specification long after demand dropped. This is where EtherInsights helps. With read-only access, teams can surface: - compute provisioned above actual demand - underused reserved capacity - environments left unchanged after peak periods - spend no longer aligned to the workload No deployment. No disruption to production. Results in hours, not months. That matters because buyers do not need another generic dashboard. They need proof that specific resources are oversized, idle, or simply no longer justified. #EtherInsights turns that proof into practical next steps: - clear visibility across the estate - findings commercial teams can challenge - simple actions for IT generalists and small cloud teams - a route to a savings report without extra operational drag #AzureCostManagement #CloudOptimisation #ITOperations

APP-V PRESSURE SHOULD RESET THE PLAN Use the App-V deadline to widen the strategy. A like-for-like replacement mindset keeps packaging teams tied to legacy decisions. The consequence is predictable: - more legacy maintenance - narrower deployment choices - less visibility into what applications actually need A better route is to use App-V pressure as the trigger for broader packaging modernisation. EtherApps Forge captures installed Windows applications from live systems, analyses the real footprint, and uses AI agent based packaging guidance to recommend the most suitable packaging route. That helps teams move from legacy package preservation to deployment-ready outputs for modern estates: - MSIX - MSI - IntuneWin - App Attach For Windows 11, Intune, AVD, and cloud-managed endpoints, the question is not how to keep App-V alive. It is how to package once for where the environment is going. If App-V is creating urgency in your estate, test one real application and see whether the next step should be MSIX-led modernisation rather than another holding pattern. etherapps.ai #MSIX #ApplicationPackaging #Windows11

ONE CAPTURE. MULTIPLE DEPLOYMENT OUTPUTS. One capture should not force one packaging decision. The 2026 MSIX report card shifts the category discussion from format readiness to execution. This datasheet sets out the practical detail teams usually need next. Key Features - Live capture from running Windows systems - Real footprint analysis across files, registry, AppData, services and dependencies - AI agent based packaging guidance for packaging decisions - Packaging route recommendation support across MSI, MSIX, IntuneWin, App Attach and Portable - Support for no-installer applications and App-V transition scenarios - Deployment-ready outputs for modern management workflows Supported Environments - Windows XP - Windows 7 - Windows 10 - Windows 11 - Windows Server - Server capture support for legacy and complex estates Technical Benefits - Captures what actually exists on the system - Reduces packaging unknowns before MSIX work begins - Supports modernisation without rebuilding the application - Helps teams assess when MSIX is the right route and when another output is more practical - Produces deployment-ready outputs faster for Intune, AVD and broader Windows delivery models - Improves repeatability and reduces avoidable rework If you are reviewing MSIX execution paths, test one real application first. Start with a no-installer app, an App-V package, or a Windows 11 migration holdout. etherapps.ai #MSIX #ApplicationPackaging #Windows11

NORMAL REPORTING HIDES WHO OWNS THE SPEND If no one can name the owner, the cost stays put. That is why waste survives in Microsoft 365 and Azure for longer than it should. Most teams are looking at separate views: - finance sees the total - admins see the estate - departments see their own activity - nobody sees a clear line from spend to accountability That gap is where idle licences, oversized resources and forgotten services keep running. The issue is not a lack of data. It is that standard reporting rarely shows spend in a way that helps teams decide what should be challenged, reduced or removed. A better approach is to make visibility operational. #EtherInsights gives read-only visibility across Microsoft 365 and Azure, helping teams see what is sitting in the estate, what has drifted away from value, and where the next review should start. That means clearer ownership, faster conversations, and practical proof before wider optimisation work begins. #CloudCostVisibility #Azure #Microsoft365

CLIENT CHANGE SHOULD TRIGGER A VDI REVIEW Changing the access app without reviewing the delivery model is how legacy VDI survives on inertia. That cost is operational. Standard users stay tied to shared infrastructure built for exceptions. What gets carried forward: - the same broad failure domain - the same slower recovery path - the same renewal-time complexity - the same support drag for users who do not need it Windows App transition is a practical moment to stop and ask a better question. Which users still need legacy VDI at all? For the stable majority, Windows 365 is usually the cleaner operating model. Move the mainstream cohort first. Sequence genuine edge cases later. #EtherInsights helps teams make that call with evidence: - identify who should move first - choose one-to-one or Frontline by concurrency - keep networking simple by default - control sizing, usage, ownership and recovery after cutover If Windows App work, renewal planning, or accumulated VDI drag is already on your desk, use it to review the model properly. Start with a Windows 365 Migration Assessment: Risk, Recovery & TCO. #Windows365 #VDI #EndUserComputing