Dynamics 365 Remote Assist Common Errors, Login, Sync, and Integration Fixes
Why This Is Happening
I've worked with Dynamics 365 Remote Assist deployments across field service teams, manufacturing floors, and industrial inspection crews. The same cluster of errors comes up again and again, and I get it, when your HoloLens is strapped to a technician's head forty feet up a wind turbine and the app just refuses to connect, the frustration is real. This isn't some desktop app you can just reboot at your desk. These issues block actual work, on actual job sites.
Here's the thing: most Dynamics 365 Remote Assist errors aren't app bugs. They're configuration mismatches. The app sits at the intersection of three Microsoft platforms, HoloLens device management, Microsoft Teams, and Dynamics 365 Power Platform, and every one of those layers has its own identity layer, its own permission model, and its own concept of "the right environment." When those three layers disagree about who you are or where you belong, the app breaks in ways that produce unhelpful error messages like "Contact your IT administrator."
The most common scenario I see: someone sets up a Dynamics 365 Remote Assist tenant environment, installs the app, hands a HoloLens to a field tech, and that tech signs in with their personal Microsoft account or a different work account than the one assigned to HoloLens. Instantly you get sign-in failures, blank contact lists, missing assets, sometimes all three at once. The app doesn't tell you "wrong account." It just silently refuses to load.
Second most common: the app is installed into the wrong Dynamics 365 environment. Your organization might have a sandbox environment, a UAT environment, and a production environment. If the Remote Assist app lands in sandbox but your asset records and security roles live in production, you'll see the Assets tab forever prompting you to call IT. The environments aren't talking to each other, and they shouldn't be. You just need to point the app at the right one.
Mixed Reality toolbar issues in Teams are a different flavor of problem. That toolbar lives on the Teams desktop client on the remote expert's PC, not on the HoloLens, and it only appears when Teams properly detects an active Dynamics 365 Remote Assist call. If Teams auto-updated overnight and is still running the old version in memory, the toolbar just doesn't show. Restarting Teams doesn't always fix it. Restarting the PC does.
Incoming call notifications failing almost always come down to account mismatch, the HoloLens device is logged in with account A, but Remote Assist is authenticated with account B. Notifications get routed to wherever account B is, which might be a device that's off or a profile that's never opened.
None of this is your fault. Microsoft's error messaging in Remote Assist is genuinely sparse. But every one of these issues has a specific, documented fix, and that's exactly what we'll walk through here. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before going deep on role assignments and environment configuration, run through this single check first. It resolves well over half of all Dynamics 365 Remote Assist issues I see in the field.
Verify that every account involved is the same work or school account.
This sounds almost embarrassingly simple. But the three-way account match, HoloLens device sign-in, Remote Assist app sign-in, and Microsoft Teams sign-in on the remote expert's machine, has to be perfect. Here's how to verify each one:
On HoloLens: open Settings → Accounts → Your info. You'll see the primary account the device is signed in with. Write it down.
In Dynamics 365 Remote Assist on HoloLens: once the app opens (even if it's behaving oddly), navigate to the profile icon or settings area and confirm the account displayed. It should match the HoloLens device account exactly, same email address, same tenant domain.
On the Teams desktop client (remote expert side): click your profile avatar in the top-right corner of Teams. The email shown there is what Teams will use to route calls and display contacts.
If any of those three don't match, sign out of the mismatched app and sign back in with the correct work or school account. Personal Microsoft accounts (Outlook.com, Hotmail, Xbox accounts) cannot be used with Dynamics 365 Remote Assist. This is a hard platform requirement. You need a work or school account tied to a Microsoft 365 subscription that has Teams enabled.
After fixing the account alignment, close Dynamics 365 Remote Assist on HoloLens completely, including the live tile, then reopen it. Wait about 60 seconds for it to fully initialize before testing contacts or assets.
Can't sign in to Dynamics 365 Remote Assist at all? There are four distinct reasons this happens, and the fix depends on which one you're dealing with.
Wrong account type: If the HoloLens is signed in with a consumer Microsoft account, the kind you'd use for Xbox, Outlook.com, or the Windows Store, Remote Assist will reject it. Sign out of the device, then sign back in with a corporate work or school account. Go to Settings → Accounts → Your info → Sign in with a work or school account instead.
Missing or invalid license: The work account needs a valid Microsoft 365 Business Premium or Microsoft 365 Business Essentials subscription with Microsoft Teams explicitly enabled. You can verify this in the Microsoft 365 admin center. Go to admin.microsoft.com → Users → Active users, find the user, and look at their assigned licenses. If Teams isn't checked under the license, enable it. License changes can take up to 24 hours to propagate, though usually it's faster, around 15–30 minutes.
No internet connection on HoloLens: Remote Assist requires an active internet connection for authentication. On HoloLens, open Settings → Network & Internet and confirm you're connected to a Wi-Fi network that has internet access. Corporate environments sometimes have captive portals or proxy settings that block authentication traffic, check with your network team if the Wi-Fi shows connected but authentication still fails.
Device or network configuration problem: If you've confirmed the account, license, and internet connection are all correct and you still can't sign in, the issue is likely at the network or device policy level. Common culprits include conditional access policies blocking HoloLens devices, MDM enrollment issues, or firewall rules blocking the Microsoft authentication endpoints. At this stage, escalate to your IT administrator with the specific error message displayed on screen.
After any sign-in fix, fully close and relaunch the Remote Assist app before testing. A cached failed authentication state can persist within the session.
This one generates more helpdesk tickets than almost any other Dynamics 365 Remote Assist issue. You tap the Assets tab on HoloLens and instead of your company's equipment records, you get a message telling you to contact your IT administrator. Here's what's actually going on and how to fix it.
Check the environment first. Dynamics 365 Remote Assist must be installed into the specific Power Platform environment your organization is using for production data. If your IT team installed it into a developer sandbox or the wrong environment, the app can authenticate fine but can't find any data. To fix this, have your Power Platform administrator navigate to admin.powerplatform.microsoft.com, locate the correct environment, and install the Dynamics 365 Remote Assist app into that environment specifically.
Verify security role assignments. Even with the app in the right environment, each user needs specific security roles assigned or the Assets tab stays locked. The user must have both of the following roles assigned simultaneously:
- Basic User, the baseline Dataverse access role
- Remote Assist - App User OR Remote Assist - Administrator, the product-specific role
To assign these roles, a Dynamics 365 administrator needs to go to admin.powerplatform.microsoft.com → Environments → [your environment] → Settings → Users + permissions → Users, find the affected user, and assign both roles. You need administrator permissions in Dynamics 365 to make this change, a standard IT helpdesk account usually won't have it.
After the roles are assigned, the HoloLens user needs to fully close the Remote Assist app, tap the app's live tile and swipe it away, then reopen it. The Assets tab should now load correctly.
If it still shows the IT administrator message after role assignment, double-check that you assigned the roles in the correct environment. It's easy to accidentally update roles in a different environment than the one the app is pointed at.
You've got past the IT administrator prompt, but the Assets tab is still empty or showing the wrong equipment records. This is a different problem from the permissions issue, and it has three distinct causes.
Multiple environments with Remote Assist installed: If your organization has Remote Assist deployed across more than one Dynamics 365 environment (common in larger enterprises with separate regional or divisional instances), the app may be pointed at the wrong one. On HoloLens, open the Remote Assist app and navigate to Settings → Dynamics 365 environment. You'll see a list of available environments. Select the correct one, this is usually your production environment, not a test or sandbox instance. After selecting it, tap the Assets tab and use the Retry button if prompted.
No asset records in the environment: The app is pointed at the right environment, but nobody has actually created asset records there yet. Asset records in Dynamics 365 Remote Assist are created through the model-driven app, not automatically. A Dynamics 365 administrator or data entry user needs to open the Remote Assist model-driven app, navigate to the Assets section, and create records for each piece of equipment. Once those records exist, the Assets tab on HoloLens will display them. After verifying records are present, tap Retry on the Assets tab.
Asset records added while the app was already open: This is an annoying timing issue. If a back-office user adds new asset records through the model-driven app while a field tech already has Remote Assist open on HoloLens, those new records won't appear automatically. The app doesn't poll for changes during an active session. The fix is straightforward: close the Remote Assist app completely on HoloLens and reopen it. The latest data will load on the fresh launch.
If none of these three fixes work and assets are still missing, confirm that the asset records in Dynamics 365 are actually assigned or visible to the user's account, record-level security in Dynamics 365 can hide records even when the user has the right app-level roles.
The contacts list in Dynamics 365 Remote Assist pulls from Microsoft Teams, specifically, the contacts and organizational directory visible to the signed-in account. When contacts don't appear or the list looks completely wrong, there are three things to check.
Account mismatch between HoloLens and Teams: This is the most common cause. Remote Assist uses your Microsoft Teams contact list to populate the contacts you can call. If you're signed in to Remote Assist with user@contoso.com but your HoloLens device account is techuser@contoso.com, or if the remote expert's Teams desktop app is signed in with a different account altogether, the contact directories won't align. Make sure the account used in Remote Assist and the account used in Teams on the remote expert's side are in the same Azure Active Directory tenant and have Teams enabled.
The app needs a refresh: Remote Assist doesn't always sync contact changes in real time. If someone was recently added to your organization's Teams or if contacts were modified, the app may still be showing a cached version of the directory. The fix is simple: close Dynamics 365 Remote Assist fully on HoloLens, then reopen it. A fresh launch triggers a new directory sync.
The HoloLens device itself needs a restart: If a full app restart doesn't refresh the contacts, the issue may be at the device session level. Restart the HoloLens by holding the power button until the power menu appears and selecting Restart. After the device comes back up, reopen Remote Assist. This clears device-level cache states that can interfere with directory synchronization.
One edge case worth knowing: if your organization uses Azure AD guest accounts or B2B collaboration, guests may not appear in the Remote Assist contacts list even if they appear in Teams. The app primarily surfaces internal directory contacts. External collaborators need to be in the same tenant directory, not just as guests, to reliably appear for Remote Assist calls.
Two separate issues, but both involve the connection between HoloLens and the remote expert's Teams client, so I'm addressing them together.
No incoming call notifications on HoloLens: When a remote expert calls a field tech through Remote Assist and the HoloLens shows nothing, no ring, no notification, nothing, the cause is almost always an account mismatch. Microsoft routes incoming call notifications to the HoloLens device account. If the Dynamics 365 Remote Assist app is authenticated with a different account than the one the HoloLens is signed in with at the device level, notifications get routed to the wrong place and simply never arrive.
To fix this: confirm the Remote Assist app account and the HoloLens device account are identical. Go to HoloLens Settings → Accounts → Your info to see the device account. Then check the Remote Assist app's signed-in account. They must match. If they don't, sign out of Remote Assist and sign back in with the HoloLens device account. No other fix will work if the accounts are different.
Mixed Reality toolbar missing in Teams during a Remote Assist call: The Mixed Reality toolbar appears on the Teams desktop client on the remote expert's PC, it's the panel that lets them annotate, share files, and interact with the HoloLens user's field of view. When it doesn't show up, there are two causes:
First, and most common, Teams downloaded an update in the background but is still running the old version. You'll notice this if Teams shows a small update indicator but you haven't restarted it. A simple app restart (close and reopen Teams) doesn't always clear this. You need to restart the PC entirely. Once Windows restarts, Teams launches fresh with the updated version and the Mixed Reality toolbar appears correctly during Remote Assist calls.
Second: the HoloLens user's spatial tracking has been lost. If the HoloLens loses positional tracking in the physical environment, this happens in areas with poor lighting, reflective surfaces, or rapid movement, it can cause the Remote Assist connection to degrade in a way that hides the Mixed Reality toolbar on the Teams side. The HoloLens user should look at a well-lit, feature-rich surface to help the device reacquire spatial tracking. Microsoft provides specific guidance on restoring HoloLens tracking in their support documentation.
Advanced Troubleshooting
If you've worked through every step above and Dynamics 365 Remote Assist is still misbehaving, the problem is likely in your Power Platform environment configuration, Azure AD tenant settings, or network infrastructure. Here's where to dig deeper.
Model-driven app not visible to users: If users can't find the Dynamics 365 Remote Assist model-driven app in their environment, the problem is almost always one of three things: wrong environment URL, app not installed in that environment, or security roles not granting access to the app itself. To check all three, you'll need admin access to the Microsoft Power Platform admin center, the Microsoft 365 admin center, and the Dynamics 365 environment in question.
Start by checking the environment URL. When a user navigates to their Dynamics 365 environment, the URL contains a unique identifier for that environment. Compare that URL against the environment listed in Power Platform admin center under Environments. A single wrong environment is the most common cause of "I can't find the app" tickets.
Next, in Power Platform admin center, go to the environment in question and confirm that the Dynamics 365 Remote Assist app is installed, not just enabled or licensed, but actually installed as an app in that environment. Then verify the user has both the Remote Assist - App User or Remote Assist - Administrator role AND the Basic User role in that environment.
Finally, verify the app is enabled for those security roles. In the model-driven app editor (via make.powerapps.com), open the Remote Assist app and check its security role visibility settings. If the app is configured to only show for specific roles and those roles don't match what the user has, they won't see it even with the right permissions technically assigned.
Conditional Access blocking HoloLens authentication: Enterprise environments that enforce Azure AD Conditional Access policies sometimes block HoloLens devices if they're not enrolled in Microsoft Endpoint Manager (Intune) or if the device compliance policy doesn't include HoloLens device categories. Check your Conditional Access policies in Entra admin center → Protection → Conditional Access → Policies and ensure HoloLens devices aren't excluded from the compliant device requirement in a way that blocks authentication.
Network requirements for Remote Assist: The app requires access to several Microsoft endpoints including Azure AD authentication services, Microsoft Teams signaling infrastructure, and Dynamics 365 Dataverse APIs. If your corporate firewall or proxy is blocking any of these, the app will fail in ways that look like account or permission errors. Microsoft publishes a list of required URLs and IP ranges for Teams and Dynamics 365, work with your network team to confirm these are whitelisted, particularly if the HoloLens connects through a corporate Wi-Fi network with deep packet inspection or strict egress filtering.
Power Platform solution version conflicts: If you recently updated the Remote Assist solution in your Dynamics 365 environment, there can be a brief window where the mobile or HoloLens app version doesn't match the solution version in the backend. Confirm that all HoloLens devices are running the latest version of the Remote Assist app from the Microsoft Store for Business or through your MDM deployment pipeline.
Prevention & Best Practices
After seeing the same Dynamics 365 Remote Assist issues recur across deployments, I've put together the practices that actually prevent them from coming back.
Standardize the provisioning checklist before handing over a HoloLens. Every HoloLens going to a field tech should be signed in with a dedicated work account tied to the correct tenant, with Dynamics 365 Remote Assist installed and tested before it leaves the IT room. That means actually launching the app, confirming the Assets tab loads, and placing a test call to verify notifications work. A five-minute verification at provisioning time prevents a two-hour helpdesk incident on the job site.
Use dedicated service accounts for shared HoloLens devices. In environments where multiple technicians share a single HoloLens, account switching becomes a major source of errors. Instead of personal accounts, create dedicated device service accounts (for example, hololens-unit01@contoso.com) with the correct licenses and roles. This keeps the device-app-Teams account chain consistent no matter who puts the headset on.
Maintain a single source-of-truth environment for asset records. Spread asset data across multiple Dynamics 365 environments and you're guaranteed to see the "wrong environment" asset issue repeatedly. Designate one environment as the production environment for Remote Assist and communicate that clearly to anyone who manages asset records in the model-driven app. Document the environment name and URL in your IT runbook.
Keep Teams desktop clients updated and restarted regularly. The Mixed Reality toolbar issue caused by Teams running a stale version is preventable. Configure Teams to auto-update and enforce a weekly PC restart policy for remote experts who use Teams for Remote Assist calls. This isn't just good practice for Remote Assist, it keeps the Teams client healthy across the board.
- Audit all HoloLens device accounts and Remote Assist app accounts quarterly to catch drift before it causes incidents
- Document your Dynamics 365 production environment name and URL in a shared IT knowledge base, half of all "wrong environment" issues come from people guessing
- Assign both security roles (Basic User + Remote Assist role) as a bundle when onboarding new users, missing either one breaks the Assets tab
- Schedule a monthly Teams client restart reminder for all remote expert workstations to prevent the Mixed Reality toolbar from silently breaking after background updates
Frequently Asked Questions
Why does Dynamics 365 Remote Assist keep saying "contact your IT administrator" on the Assets tab?
This message appears for one of two reasons: either the Remote Assist app is installed in a different Dynamics 365 environment than the one your assets and users are configured in, or the signed-in user hasn't been assigned the correct security roles. You need both the Basic User role and either the Remote Assist - App User or Remote Assist - Administrator role in the correct environment. An administrator must assign these roles through the Power Platform admin center, then the user needs to close and reopen the app completely for the change to take effect.
I can sign in to Remote Assist on HoloLens but my contacts list is completely empty, what's wrong?
An empty contacts list almost always means the account you're signed in to Remote Assist with doesn't have visible Teams contacts in your organization's directory. First, confirm you're using a work or school account, not a personal Microsoft account. Then make sure the account is part of the same Azure AD tenant as your colleagues, and that Teams is enabled for that account's Microsoft 365 license. If you just recently signed in or contacts were recently added to Teams, close and fully reopen the Remote Assist app to trigger a fresh directory sync.
The Mixed Reality toolbar disappeared in Microsoft Teams, how do I get it back during Remote Assist calls?
The Mixed Reality toolbar not showing in Teams is almost always caused by Teams running an outdated version in memory after a background update. Closing and reopening Teams alone often isn't enough, you need to restart the PC entirely. After the restart, Teams will launch with the updated version and the toolbar will appear again during Dynamics 365 Remote Assist calls. If the toolbar still doesn't appear after a PC restart, check whether the HoloLens user has lost spatial tracking, as tracking loss can also cause the toolbar to disappear on the remote expert's side.
Why am I not getting incoming call notifications on my HoloLens when someone calls me through Remote Assist?
Incoming call notifications are routed to the HoloLens device account, not necessarily to whatever account the Remote Assist app is signed in with. If those two accounts are different, notifications get sent to the wrong destination and never arrive. Go to HoloLens Settings → Accounts → Your info and note the device account email. Then check the account shown inside the Remote Assist app. They must be identical, same email, same tenant. Sign out of Remote Assist and back in with the correct account if there's a mismatch.
Dynamics 365 Remote Assist stops responding or freezes on HoloLens, what should I do?
When Remote Assist freezes or stops responding, start by closing the app completely, swipe away the live tile rather than just minimizing it, then reopen it. This clears whatever state caused the freeze. If the app continues to hang after a fresh launch, restart the HoloLens device entirely using the power menu. A full device restart resolves most persistent freezing issues. If freezing happens repeatedly in the same scenario (for example, always when loading a specific asset or during a call of a certain length), note the pattern and report it to your IT team, as it may indicate a resource or network issue specific to your environment.
Assets I added in the model-driven app aren't showing up in Remote Assist on HoloLens, is there a sync delay?
There's no automatic sync push to the HoloLens app for assets added while the app is already open. If someone creates new asset records in the Dynamics 365 Remote Assist model-driven app while a technician already has the HoloLens app running, those records won't appear until the app is restarted. Close Remote Assist fully on HoloLens, reopen it, then navigate back to the Assets tab. The newly created records will be there. This is a known behavior, not a bug, the app loads asset data on launch and doesn't poll for changes mid-session.