Microsoft Graph PowerShell
Errors from the Microsoft.Graph PowerShell SDK — connection scopes, missing cmdlets, token failures, and bad object IDs. All fixes assume you're running an up-to-date Microsoft.Graph module.
22 errors · See all →
Paste an IT error. Get the fix.
IT Error Decoder explains common Microsoft 365, Entra ID, Vercel, and Windows admin errors in plain English, with step-by-step fixes you can actually run. 90 errors and counting.
Ad placeholder · slot home-top
Common Microsoft Graph errors
See all →Permissions, scopes, and object IDs trip up almost every script. Start here.
- Get-MgUser insufficient privilegesFix 'Get-MgUser : Insufficient privileges to complete the operation' in Microsoft Graph PowerShell. Right scopes and role checks.
- Connect-MgGraph admin consent requiredFix Connect-MgGraph 'admin consent required' / AADSTS65001. How to grant tenant-wide consent for the right scopes.
- Request_BadRequestFix Microsoft Graph 'Request_BadRequest' (400). Diagnose malformed filters, properties, and JSON bodies.
- Authorization_RequestDeniedFix Microsoft Graph 'Authorization_RequestDenied'. Identify the missing scope, reconnect with the right permissions.
Common Teams Room errors
See all →Camera, microphone, audio, and video issues — usually physical, not software.
- Teams Room camera not detectedFix Microsoft Teams Rooms 'camera not detected' / black video tile. Power cycle, reseat USB, update firmware.
- Teams Room microphone not detectedFix Microsoft Teams Rooms 'microphone not detected'. Verify default capture device, power cycle, and update firmware.
- Teams Room audio cuts outFix Microsoft Teams Rooms 'audio cuts out'. Diagnose jitter, double-capture devices, and peripheral firmware.
- Teams Room video drops during meetingFix Microsoft Teams Rooms 'video drops during meeting'. Diagnose with CQD, check network path and peripheral thermals.
Common Vercel errors
See all →Build failures, missing output directories, env var problems, and timeouts.
- No Output Directory named "public" found after the Build completedFix Vercel 'No Output Directory named public found after the Build completed'. Framework presets and output directory setup.
- Next.js Module not found: Can't resolveFix Next.js / Vercel 'Module not found: Can't resolve'. Casing, dependencies, and path aliases.
- Vercel build fails with TypeScript 'Type error'Fix Vercel TypeScript 'Type error' build failures. Reproduce locally, pin versions, and use ignoreBuildErrors as a last resort.
- Vercel: 404 NOT_FOUND / DEPLOYMENT_NOT_FOUND after deployFix Vercel '404: NOT_FOUND / DEPLOYMENT_NOT_FOUND'. Aliases, deleted deployments, and how to recover.
Latest IT fixes
Recently reviewed errors and fresh fixes from across the database.
- Windows Admin0x80073cf9 Microsoft Store install failed
- Entra IDAADSTS500113: No reply address registered for the application
- Entra IDAADSTS50034: User does not exist
- Entra IDAADSTS50056: Invalid or null password
- Microsoft Graph PowerShellAuthorization_RequestDenied
- Entra IDConditional Access blocked because Multi-Factor Authentication is required
Browse by category
All 90 errors →Microsoft Teams
Issues with Microsoft Teams — desktop client, Teams Rooms devices, and federation between tenants. Most fixes can be done by an end user or a Teams admin.
15 errors · See all →
Vercel
Errors that show up in your Vercel build logs or deployment status. Most are configuration problems that resolve themselves once your framework preset, environment variables, and dependencies are aligned.
17 errors · See all →
Windows Admin
Classic Windows administration errors — domain trust, Group Policy, RPC, file shares, and authentication. Most assume a domain-joined workstation or server.
16 errors · See all →
Entra ID
Sign-in and authorization failures from Microsoft Entra ID (formerly Azure AD). AADSTS error codes, Conditional Access blocks, missing consent, and app registration problems.
20 errors · See all →