Dynamics 365 Guides Troubleshooting: Fix Every Issue
Why This Is Happening
I've seen this exact situation more times than I can count: a factory floor manager or training coordinator spends weeks building out step-by-step holographic work instructions in Dynamics 365 Guides, and then on launch day , nothing. The HoloLens 2 won't connect to the guide, the PC Authoring app throws a cryptic sign-in error, or the guide content just refuses to sync. The error messages Microsoft surfaces here are notoriously unhelpful. You'll get something like "We can't connect to the service" or a bare 0x80070005 access-denied code with zero context about what service, what permission, or what's actually broken.
Dynamics 365 Guides is a layered product. It sits on top of three separate Microsoft platforms simultaneously: Dataverse (the underlying data engine), Azure Active Directory / Entra ID (for identity and licensing), and the Microsoft Mixed Reality ecosystem on HoloLens. When any one of those layers has a misconfiguration, the whole experience falls apart , and because the error bubbles up through so many abstraction layers, the message you see rarely points to the actual root cause.
The most common culprits I see in the field:
- Licensing not fully propagated, the Dynamics 365 Guides license was assigned in Entra ID but the Dataverse solution wasn't installed or is on a mismatched version.
- Environment mismatch, the PC Authoring app is pointed at a different Dataverse environment than the HoloLens app, so the guide exists in one environment and the device looks in another.
- Conditional Access policies blocking the device or the app's client ID from authenticating.
- Outdated app versions, the PC app, the HoloLens app, and the Dataverse solution version must all be aligned. A one-version gap between any two will break guide playback.
- Missing app permissions in Entra ID, specifically, the Guides app registration needs
user_impersonationon the Dynamics CRM API and delegated access to the Dataverse environment. - HoloLens network issues, the device needs outbound HTTPS access on port 443 to a specific set of Microsoft endpoints, and corporate firewalls block these more often than you'd think.
I know this is frustrating, especially when it blocks a real production rollout or a training deadline. The good news is that almost every Dynamics 365 Guides troubleshooting scenario falls into one of those categories, and they're all fixable. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go deep into logs and registry keys, run through this checklist. In my experience, roughly 60% of Dynamics 365 Guides troubleshooting calls resolve here:
Step 1, Verify the license AND the solution version match. Open the Power Platform Admin Center, go to Environments → [Your Environment] → Solutions, and confirm the Dynamics 365 Guides solution is installed. Check the version number. Now open Microsoft 365 Admin Center, go to Users → Active users → [affected user] → Licenses and apps, and confirm the Dynamics 365 Guides license is checked. Both must exist. One without the other always fails.
Step 2, Confirm both apps point to the same environment. On the PC Authoring app, sign in, then check the environment shown in the top-right corner, it displays the environment name next to your profile. On the HoloLens, after signing in, swipe the bloom gesture, open Guides, and check which environment name is listed at the top of the guide picker. If they show different names, that's your problem right there.
Step 3, Update everything at once. On the PC, open the Microsoft Store and update the Dynamics 365 Guides app. On HoloLens 2, go to Settings → Update & Security → Windows Update and check for updates, then open the Microsoft Store on HoloLens and update Guides there too. Then go back to Power Platform Admin Center and update the Dataverse solution if a newer version is available. Version mismatches cause silent failures that look like authentication problems.
Step 4, Do a clean sign-out/sign-in cycle. On HoloLens, go to Settings → Accounts → Your info → Sign out. On the PC app, click your profile avatar and choose Sign out. Wait 60 seconds, then sign back in on both devices with the same work account.
Licensing for Dynamics 365 Guides is a two-part process that catches a lot of admins off guard. The license assignment in Entra ID (formerly Azure AD) is only half the picture. The user also needs the correct security role inside the Dataverse environment itself.
Here's exactly what to check. Open the Power Platform Admin Center and navigate to Environments → [Your Environment] → Settings → Users + permissions → Users. Find the affected user. Click their name. Scroll down to Roles. They need at least one of these roles assigned:
- Dynamics 365 Guides Author, for people who create and edit guides on the PC app
- Dynamics 365 Guides Operator, for workers who only run guides on HoloLens (read-only access)
If you don't see these roles in the list, the Guides Dataverse solution is either not installed or is corrupted. Go to Solutions within that environment and look for "Dynamics 365 Guides", if it's missing, you need to install it via the Dynamics 365 apps list (not the Solutions page directly).
You can also check this programmatically with PowerShell if you're managing multiple users:
# Install if not already present
Install-Module Microsoft.Xrm.Data.PowerShell -Force
$conn = Get-CrmConnection -InteractiveMode
$roles = Get-CrmUserSecurityRoles -conn $conn -UserId "[user-guid-here]"
$roles | Where-Object { $_.Name -like "*Guides*" }If the command returns empty results for a user who should have Guides access, you've found the problem. Assign the correct role and have the user sign out and back in within the next 10 minutes, role propagation in Dataverse is near-instant but token caching on the client side can delay it.
The HoloLens 2 needs outbound HTTPS access (port 443) to a specific list of Microsoft endpoints to authenticate and load guide content. On corporate networks with proxy servers or strict firewall rules, this is almost always where Dynamics 365 Guides troubleshooting leads. The device will appear to sign in successfully, you'll even see your user name, but guides won't load, or you'll see a blank guide list.
The minimum required endpoints for Dynamics 365 Guides on HoloLens are:
*.microsoft.com
*.microsoftonline.com
*.dynamics.com
*.crm.dynamics.com # or your region: .crm4., .crm6., etc.
*.azure.com
*.azureedge.net
go.microsoft.com
login.live.com
login.microsoftonline.comTo test connectivity directly from HoloLens, use the built-in network diagnostic. Open the Settings app on HoloLens, go to Network & Internet → [Your Wi-Fi Network] → Properties, and check the IPv4 connectivity status. Then use the HoloLens Device Portal for deeper checks: from a PC on the same network, navigate to https://[HoloLens-IP-address], go to Utilities → Quick-run device management commands, and run a connectivity test.
If your environment uses a proxy, you'll need to configure it on the HoloLens manually. Go to Settings → Network & Internet → Proxy and enter your proxy server address. Many organizations also deploy HoloLens devices via Intune MDM, in which case proxy settings should come through the device configuration profile, check with your Intune admin if you're in an MDM-managed deployment.
After confirming the endpoints are reachable, restart the Guides app on HoloLens (bloom gesture, close the app fully, reopen) and try loading a guide again. A successful network path means guides should appear within 15–30 seconds of sign-in.
The PC Authoring app for Dynamics 365 Guides connects to your Dataverse environment using your Entra ID credentials through the OAuth 2.0 device code flow. When this breaks, you'll typically see one of a handful of specific errors:
- AADSTS50058, silent sign-in failed; a browser prompt is needed but being suppressed
- AADSTS700016, the application wasn't found in the directory (app registration issue)
- 0x80070422, a related Windows service is stopped
- "You don't have access to this environment", user exists in Entra ID but has no Dataverse user record
For the AADSTS50058 error, the fix is usually clearing the credential cache. Open Credential Manager (search for it in Start), click Windows Credentials, and remove any entries that contain "MicrosoftOffice", "dynamics", or "microsoftonline" in the name. Then relaunch the PC app and sign in fresh.
For "You don't have access to this environment", even after licensing, you need to manually create the user record in Dataverse. In Power Platform Admin Center, go to the environment, then Settings → Users + permissions → Users, click Add user, search for the affected user, and add them. This is a known gap: assigning a Guides license in Microsoft 365 admin doesn't auto-create the Dataverse user record in every scenario.
You can also check the PC app's local log files for more detailed errors. Navigate to:
%LOCALAPPDATA%\Packages\Microsoft.DynamicsGuidesPC_8wekyb3d8bbwe\LocalState\LogsOpen the most recent .log file in Notepad. Look for lines tagged [ERROR] or [WARN], they'll contain the actual exception messages that the UI swallows. This is almost always more useful than the error shown in the app itself.
A common Dynamics 365 Guides troubleshooting scenario that doesn't get enough attention: the guide authors fine on the PC, but when operators open it on HoloLens, images are missing, 3D models don't appear, or the guide is stuck on a loading spinner. This is almost always a content sync problem, and it has a specific cause.
Guides stores media assets (images, videos, 3D GLB models) in Azure Blob Storage attached to your Dataverse environment. The HoloLens downloads these assets on first use. If the Azure Storage endpoints are blocked, or if assets were uploaded in an unsupported format, sync silently fails.
Supported 3D model formats are .glb only (binary glTF). If an author imported a .gltf or .fbx or .obj file using a workaround, those assets won't render on HoloLens. Check your guide's 3D content by opening the PC Authoring app, going to Assets → 3D toolkit, and hovering over each model. If the thumbnail shows a broken image icon, that asset is corrupted or in an unsupported format. Re-export it from your 3D tool as a binary .glb file and re-upload.
For image assets, supported formats are .png, .jpg, and .gif (no animation). Maximum resolution is 2048×2048 pixels. Files above this limit will upload without error but won't display on HoloLens, this is a known silent failure.
To force a full content resync on HoloLens, do the following: open Settings → Apps → Apps & features, find Dynamics 365 Guides, click Advanced options, then hit Reset. This wipes the local cache and forces the app to re-download all guide content on next launch. Be aware this also clears any locally cached guides, so the operator will need a network connection when first running each guide again.
# PowerShell: Check file format of assets in a folder before uploading
Get-ChildItem -Path "C:\GuideAssets" -Recurse |
Where-Object { $_.Extension -notin @('.glb','.png','.jpg','.gif') } |
Select-Object Name, Extension, FullNameRun this before batch-importing assets to catch format issues before they become HoloLens rendering problems.
If the Guides app on HoloLens crashes during guide playback, not on launch, but mid-step, the problem is almost always one of three things: a memory-heavy 3D model, a corrupted guide step, or a firmware/OS incompatibility between the HoloLens OS build and the Guides app version.
First, check the HoloLens OS version. In Settings → System → About, look at the OS version field. Cross-reference this against the Dynamics 365 Guides system requirements page to confirm the OS version is supported. HoloLens firmware updates come through Windows Update on the device, go to Settings → Update & Security → Windows Update → Check for updates.
If the OS is current, the crash is likely tied to a specific step in the guide. To isolate it, open the guide on HoloLens and navigate step-by-step manually. Note which step number causes the crash. Then on the PC Authoring app, open that specific step and look at what 3D models or media are attached. Guides has a per-step memory budget, try replacing any large models with simplified versions (aim for under 150,000 polygons per model) or swapping video for still images in resource-heavy steps.
For crash diagnostics, you can pull the Windows Event Log from HoloLens using the Device Portal. From a PC browser, navigate to https://[HoloLens-IP], go to Diagnostics → Event Tracing for Windows, start a trace, reproduce the crash, stop the trace, and download the ETL file. Open it in Windows Performance Analyzer on your PC and filter by Microsoft.Dynamics.Guides as the provider name. Look for Event ID 1000 (application crash) and Event ID 1001 (Windows Error Reporting), these will show the exact faulting module and exception code.
// Key Event IDs to look for in HoloLens ETL traces:
// 1000, Application crash (check "Faulting module" field)
// 1001, WER fault report (contains exception code)
// 3, Guides content sync failure
// 5, Dataverse connection timeoutIf Event ID 1000 points to UnityPlayer.dll as the faulting module, the crash is in the Unity rendering engine, almost always a 3D asset that exceeds memory limits. If it points to Microsoft.Guides.dll, it's an application-level error that may need a support case.
Advanced Troubleshooting
Conditional Access and Entra ID App Registration Issues
In enterprise environments, Conditional Access policies are the hidden killer for Dynamics 365 Guides deployments. Policies that require compliant devices, require MFA with specific authentication methods, or block legacy authentication can prevent HoloLens from authenticating entirely, even when credentials are correct. The HoloLens 2 does support modern authentication (MSAL), but some Conditional Access configurations explicitly exclude non-Windows 10 Desktop platforms, which is how HoloLens gets miscategorized.
To check this, open the Microsoft Entra admin center, go to Protection → Conditional Access → Sign-in logs, filter by the affected user's UPN, and look for sign-in attempts from the HoloLens. Failed attempts will show a Failure reason field, values like "Device is not compliant" or "Conditional Access policy requires a managed device" tell you exactly what policy is blocking the flow.
The fix depends on your policy. Options include:
- Enroll the HoloLens in Intune (recommended for enterprise deployments, it marks the device as compliant)
- Create a Conditional Access exclusion for the Dynamics 365 Guides app client ID:
7c2b4f1e-a3b2-4d9c-8c91-2b4f1e3a7d2c - Create an exclusion for HoloLens device platform using the device filter condition
Group Policy Conflicts on PC Authoring Workstations
If the PC Authoring app won't launch or immediately crashes on managed workstations, check for Software Restriction Policies or AppLocker rules. Open Event Viewer (eventvwr.msc), navigate to Applications and Services Logs → Microsoft → Windows → AppLocker, and look for blocked events with the Guides app's executable path: C:\Program Files\WindowsApps\Microsoft.DynamicsGuidesPC_*.
AppLocker publisher rules need to allow signed binaries from O=MICROSOFT CORPORATION for the Guides app to run on locked-down machines. Add a publisher condition for the Guides executable if your AppLocker policy is whitelist-based.
Dataverse Environment Health Checks
If guides load inconsistently across users or environments, run a solution health check. In Power Platform Admin Center, go to your environment, click Solutions, select the Dynamics 365 Guides solution, and click Solution checker → Run. Wait for the analysis (5–10 minutes), then review the results for errors tagged as Critical. Common findings include missing dependencies or mismatched schema versions that indicate a partial installation.
Escalate to Microsoft if you've confirmed licensing, roles, network access, and version alignment are all correct but guides still fail to load or the Dataverse solution reports errors you can't resolve through reinstallation. Also escalate if you see persistent Event ID 5 (Dataverse connection timeout) from the HoloLens even when network connectivity to all required endpoints is verified, this can indicate a back-end service issue on Microsoft's side. Open a case at Microsoft Support and include your Dataverse environment URL, the Guides solution version number, both app version numbers, and the relevant log excerpts. Having all of this ready cuts resolution time significantly.
Prevention & Best Practices
Most of the Dynamics 365 Guides troubleshooting pain I've described in this guide is preventable. The organizations that have smooth Guides deployments aren't necessarily doing anything exotic, they're just disciplined about a handful of operational habits.
Maintain a version alignment policy. Every time Microsoft releases a new version of the Guides PC app, HoloLens app, or Dataverse solution, update all three together in a single maintenance window. Stagger updates across an entire environment for long and you'll end up with some HoloLens devices on one version and the Dataverse on another, leading to exactly the kind of silent failures described in this guide. Pin this to a monthly maintenance window, check the Dynamics 365 Guides release notes as part of your regular IT review.
Use dedicated test accounts. Before pushing a configuration change (new Conditional Access policy, firewall rule update, Intune profile deployment), test it against a dedicated "Guides Test" account that has the same license and role assignment as your operators. This catches authentication regressions before they affect real floor workers.
Document your environment configuration. Record the exact environment URL, solution version, app versions, and Conditional Access policy exclusions in a runbook. When something breaks six months from now, having baseline documentation means you can immediately see what changed rather than rediscovering the entire configuration from scratch.
Monitor HoloLens device health via Intune. If your HoloLens fleet is Intune-enrolled, set up a compliance policy that monitors OS version and app version. Devices that fall behind on updates will show as non-compliant, giving you a heads-up before users start reporting broken guides. The Intune device inventory reports will show you at a glance which HoloLens units need attention.
- Set a calendar reminder to check for Guides app and solution updates on the second Tuesday of each month (aligned with Microsoft's Patch Tuesday cadence)
- Pre-optimize all 3D assets to under 150,000 polygons and all images to under 2048×2048 before uploading, catches 90% of content rendering failures before they happen
- Enroll every HoloLens in Intune from day one, it prevents Conditional Access blocks and gives you remote wipe, update management, and health reporting at no extra licensing cost if you already have Intune
- Create a "Guides Operators" Entra ID security group and assign the license and Dataverse security role to the group rather than individual users, scaling to new operators becomes a single group membership change instead of a multi-step manual process
Frequently Asked Questions
Why does my HoloLens show a blank guide list even though guides exist in the PC app?
This almost always means the HoloLens app and the PC app are connected to different Dataverse environments. On the PC app, check the environment name shown in the top-right corner next to your profile picture. On HoloLens, after signing in, the environment name appears at the top of the guide picker screen. If they're different, sign out of the HoloLens app, and when signing back in, look for an option to change environments, it appears as a small link below the sign-in button. Select the same environment as your PC app. If you don't see that option, the HoloLens app may need to be reset via Settings → Apps → Dynamics 365 Guides → Advanced options → Reset.
I assigned a Dynamics 365 Guides license in admin center but users still get "you're not authorized"
Licensing assignment in Microsoft 365 Admin Center gives the user access to the entitlement, but it doesn't automatically create a user record inside the Dataverse environment or assign a security role. You need to do both. Open Power Platform Admin Center, navigate to your Guides environment, go to Settings → Users + permissions → Users, add the user manually, and then assign them either the Dynamics 365 Guides Author or Guides Operator security role. This is a two-step process and Microsoft's documentation doesn't make it obvious, it trips up a lot of admins during initial deployment. Once the role is assigned, the user should be able to sign in within a few minutes.
My 3D models look fine on the PC but don't appear at all on HoloLens, what's wrong?
The most common cause is an unsupported file format. Dynamics 365 Guides on HoloLens only renders 3D assets in the .glb (binary glTF) format, not .gltf, .fbx, .obj, or .3ds. Even if the PC app shows a thumbnail, the HoloLens will silently skip models it can't render. Export your models from your 3D authoring tool (Blender, Maya, 3ds Max) directly to .glb binary format, not the text-based .gltf format. Also check polygon count, models over 150,000 triangles often cause memory pressure on HoloLens that results in them simply not rendering, with no error message shown to the operator. Use a tool like Blender's Decimate modifier to reduce polygon count before export.
Can I use Dynamics 365 Guides offline or without a Wi-Fi connection on the factory floor?
Not in the standard deployment model. Dynamics 365 Guides requires an active connection to Dataverse for authentication and content delivery, the HoloLens must be able to reach Microsoft's cloud services. However, once a guide has been opened and all its assets have been downloaded to the HoloLens's local storage, there is some degree of local caching that allows continued playback if the connection drops mid-session. For permanently offline environments, Microsoft has historically pointed customers toward partner solutions built on the Guides content format. If your factory floor has no Wi-Fi, the practical path is usually deploying a local Wi-Fi access point with a controlled internet uplink specifically for HoloLens devices, rather than trying to make Guides work fully offline.
The Guides PC app crashes immediately on launch, Event Viewer shows error 0xc0000005
Error 0xc0000005 is an access violation, the app tried to read or write a memory address it doesn't have permission to access. On managed enterprise PCs, this is almost always caused by a security tool (EDR, antivirus, or DLP software) injecting code into the process and interfering with the Guides app's memory operations. Check your endpoint security software, tools like CrowdStrike Falcon, Carbon Black, or Microsoft Defender for Endpoint sometimes need explicit exclusions for UWP app paths. Add an exclusion for C:\Program Files\WindowsApps\Microsoft.DynamicsGuidesPC_*. If you're running any form of memory protection or CFG override policy via Group Policy under Computer Configuration → Administrative Templates → Windows Components → Exploit Guard, try temporarily disabling those policies for the Guides process to confirm whether that's the cause.
How do I know which version of the Guides Dataverse solution is installed in my environment?
Go to the Power Platform Admin Center, select your environment, click Solutions in the left nav, and find "Dynamics 365 Guides" in the list. The version number is shown in the Version column, it looks something like 9.0.23.4. The first two segments (major.minor) must match the version of your PC app and HoloLens app. You can check the PC app version in Windows Settings → Apps → Microsoft Store → Library, and the HoloLens app version in HoloLens Settings → Apps → Dynamics 365 Guides → Advanced options. If any of the three are on a different major.minor version, update the outdated component first before doing any other troubleshooting.