Use the following steps as a guide for troubleshooting a sync issue. :::image type="content" source="media/microsoft-edge-enterprise-sync-configure-and-troubleshoot/sync-identity-issue3.png" alt-text="Last Token Error EDGE_AUTH_ERROR: 3,54, 3ea"::: Basic troubleshooting stepsīefore you start troubleshooting, check the Common sync issues to see if any of these issues apply to your sync problem. The error is Last Token Error, EDGE_AUTH_ERROR: 3, 54, 3ea, which is found in edge://sync-internals under Credentials. The next screenshot shows an example of an identity error. Understand the difference between identity and sync issue before you start troubleshooting sync.īefore you treat an issue as a sync issue, check to see if the user is signed into the browser with a valid account. For this reason, identity issues are frequently confused with sync issues. A popular use case for maintaining user identity in the browser is to support sync. It's important to understand the difference between identity issues and sync issues. Before you begin: identity issues versus sync issues If the sync reset doesn't work, an admin or support staff member can use the guidance in this article to fix a sync issue.Īpplies to Microsoft Edge on Chromium, version 77 or later unless otherwise noted. If a user is experiencing an issue syncing browser data across their devices, they can reset sync in Settings > Profiles > Sync > Reset sync. It also includes troubleshooting steps and the recommended tools for gathering the logs needed for troubleshooting a sync issue. This article provides troubleshooting guidance for the most common sync issues in an Azure Active Directory (Azure AD) environment. Guidance and tools a Microsoft Edge admin can use to troubleshoot and fix common enterprise sync issuesĭiagnose and fix Microsoft Edge sync issues