The tricky part: a "Nerdio issue" often isn't one. The root cause can sit in Nerdio Manager, Azure, identity, networking, a host pool, an application, or a dependency underneath them. Microsoft's Well-Architected guidance splits ownership between the AVD service and the customer-managed environment.
This guide covers how to choose the right channel, build a complete request, gather evidence, and escalate safely.
Key Takeaways
- Decide whether the fault sits with Nerdio, Azure, identity, or your own environment before you file.
- Include timestamps, scope, recent changes, exact errors, and screenshots or exports.
- Never send passwords, tokens, keys, or unredacted personal data.
- A Nerdio partner can investigate and co-manage when internal skills run thin.
Identify the Right Nerdio Support Path
When to contact Nerdio directly
Nerdio publishes separate help centers and request forms for its two products. Enterprise customers use the Enterprise request form, and MSP customers use the MSP help center. Check your subscription or partner agreement for the entitlement that applies to you.
Typical reasons to go to Nerdio:
- A suspected Nerdio Manager defect
- Product-specific errors in host-pool configuration, auto-scaling, or image creation
- Licensing or entitlement questions
- Documented behavior that doesn't match what you see
Version matters too. Nerdio's Enterprise policy provides standard support for the current and immediately prior versions, while older versions get best-effort help without bug fixes.
When Azure or internal IT should be involved
Nerdio's Enterprise scope excludes Azure errors, AVD performance, authentication/MFA, and Azure networking troubleshooting. Those belong with Microsoft or your own team.
A failure in a dependency can look like a Nerdio problem to users. Check these first:
- Azure App Service and the web app
- Azure SQL database
- Key Vault access
- Network path to Azure and AVD services
- Microsoft Entra ID sign-ins and Conditional Access
Azure technical requests require a paid support plan. The Basic plan covers billing and subscription issues only.
When a Nerdio partner is the practical option
Vendor tickets answer product questions. They rarely cover:
- Environment-specific troubleshooting
- Architecture review
- Remediation
- Cost optimization
- Documentation
A partner fills that gap, especially for teams without VDI specialists.
What to Include in a Nerdio Support Request
Environment and scope
Give the support engineer the full picture up front:
- Nerdio product (Enterprise or MSP) and version
- AVD or Windows 365 components involved
- Tenant, subscription, region, host pools, and session hosts
- Number and type of affected users
Scope tells support where to look. One user, one host pool, one application, one admin, or everyone? Each points to a different layer.
Symptoms, timing, and reproducibility
State what you expected and what happened. Add:
- Exact error text and codes
- First known occurrence, with time zone
- Frequency, and whether you can reproduce it
- Recent changes: image updates, policy edits, network changes, scaling-rule edits, role changes, app deployments
Recent changes explain a surprising share of incidents. In one admin audit, an administrator made 84 Nerdio Manager changes over nine days, including nine autoscale updates and eight host-pool re-images. Without a change list, nobody can untangle that.
Evidence and diagnostic context
Attach evidence tied to the affected component:
- Nerdio task logs. The Logs module shows task, resource, user, status, times, and details, with JSON export
- Azure activity log identifiers:
correlationId,operationId,eventDataId - AVD CorrelationID for errors where
ServiceError=true; Microsoft wants that for escalation - Entra sign-in request ID, time, and date for Conditional Access problems
- Azure Service Health and Resource Health findings
- Screenshots with enough surrounding context to interpret them
Security and requested outcome
Microsoft's own instructions say: "Be sure not to include any personal or confidential information here." Redact passwords, access tokens, private keys, personal data, and confidential documents. Scripted actions deserve extra care, since they sometimes hold hardcoded credentials or storage keys.
Close the request with:
- Business impact
- Any workaround in place
- The outcome you want
- Best contact for a callback
- Access support may need, granted through approved processes
Triage the Issue Before You Submit
Establish impact and urgency
Nerdio's published severity scale (tied to its CS+ program) runs from Critical outages and high-risk security issues down to general configuration questions. Azure uses its own A/B/C scale. Describe impact in plain terms:
- Isolated user problem
- Limited host-pool degradation
- Unable to provision or scale
- Widespread loss of desktop access
Note what still works and what doesn't. That saves support from rediscovering it.
Check service health and key dependencies
Work through this list:
- Nerdio Manager health. In Enterprise, System > Health shows component status and connection health. Confirm App Service connectivity to SQL, Azure, and AVD. On MSP, enable the health-status endpoint.
- Azure Service Health for region incidents and maintenance.
- Azure Resource Health for individual VMs.
- Entra sign-in logs and Conditional Access results.
- Host-pool and session-host status.
Narrow the fault domain
Test an unaffected user, host, pool, or admin account where safe, and compare it to the failing case. Record timestamps and correlation IDs from every test so support can line up events across Nerdio, Azure, identity, and session-host logs.
Preserve evidence and avoid risky changes
Resist the urge to make rushed changes. Don't repeatedly edit scaling rules, delete resources, rebuild host pools, or change production policy until evidence is captured and a rollback plan exists.
Keep a short timeline of observations, attempted fixes, changes, and results.
Decide whether to escalate immediately
Follow your incident and security procedures right away for:
- Broad outages
- Security concerns
- Data-access issues
- Failed recovery
- Rapidly growing user impact
Then use the official Nerdio, Microsoft, or managed-service path that matches the confirmed fault domain.
How a Nerdio Partner Can Help With a Support Request
TechSogna is an Authorized Nerdio Partner and Microsoft Partner serving US organizations from Austin, Texas. The team holds the Microsoft Certified: Azure Virtual Desktop Specialty and Nerdio Manager for Enterprise certifications.
TechSogna provides partner and consultancy support. It is not the official Nerdio vendor support desk.
What that looks like in practice:
- Assess the issue, gather evidence, and interpret Nerdio and Azure findings
- Help write a technically clear request for Nerdio or Microsoft
- Guide Nerdio Manager licensing, deployment, training, runbooks, and optimization
- Provide business-hours co-management (Monday to Friday, 9:00 a.m. to 6:00 p.m. CT), scoped light or deep
- Deliver fixed-fee, read-only Health Checks and As-Builts from $3,500
Co-management is not 24/7 support. For outages outside business hours, use your vendor's urgent channel.
Need a hand? Call +1 512-596-2758 or email info@techsogna.com with your company name and a short description of the issue.
Next Steps After You Submit a Nerdio Support Request
Keep the ticket number, submitted evidence, channel details, and your timeline in your incident record.
When support follows up, don't resend the original story. Send new timestamps, test results, logs, and configuration changes.
After resolution, run a blameless review. Microsoft's OE:08 guidance calls for root cause analysis and a postmortem. Record:
- Final root cause
- Remediation
- Preventive controls
- Monitoring improvements
- Runbook changes
The next AVD incident will go faster.
Frequently Asked Questions
How can I contact Nerdio customer support?
Use the official channel for your product: the Enterprise or MSP help center request form, or the process in your partner agreement. If the issue is on the Azure side, contact Microsoft or your service partner.
What information should I include in a Nerdio support request?
Include product, version, and environment; affected users or host pools; timestamps; exact errors; recent changes; logs or exports; business impact; and safe contact details.
Should I contact Nerdio or Microsoft Azure for an AVD issue?
Nerdio handles Nerdio Manager behavior such as auto-scaling and image operations. Azure, identity, networking, and AVD service errors go to Microsoft. Check Service Health and dependencies first.
Can a Nerdio partner help troubleshoot my environment?
Yes. An authorized partner can help with assessment, troubleshooting, deployment, optimization, documentation, training, remediation, and ongoing co-management.
What should I do if Nerdio Manager or Azure Virtual Desktop is unavailable?
Record the scope and timestamps, check service health, and follow your incident and security procedures. Preserve evidence, then use the urgent support channel for the failing layer.
