- MICROSOFT EDGE NOT WORKING ON PHONE INSTALL
- MICROSOFT EDGE NOT WORKING ON PHONE UPDATE
- MICROSOFT EDGE NOT WORKING ON PHONE UPGRADE
- MICROSOFT EDGE NOT WORKING ON PHONE LICENSE
PS C:\Work\scripts\PowerShell> Get-AIPServiceOnboardingControlPolicy
The next two examples show an unscoped configuration and a configuration scoped to a specific security group.
MICROSOFT EDGE NOT WORKING ON PHONE INSTALL
You can get it here: Install the AIPService PowerShell module for Azure Information Protection. Make sure the aIPService PowerShell monitor is installed. You can use the Get-AIPServiceOnboardingControlPolicy PowerShell cmdlet to see if scoping is enabled. You can turn off ESR if this step fixes the issue.Ĭonfirm that Azure Information Protection isn't scoped via an onboarding policy. If you need to enable ESR, see these instructions: Enable Enterprise State Roaming in Azure Active Directory.ĮSR doesn't need to stay on. If step 2 shows that AIP is active but sync still doesn't work, turn on Enterprise State Roaming (ESR). If you need to check AIP status and, if necessary, activate AIP, see these instructions: Activating the protection service from Azure Information Protection. If a supported subscription is available, verify that the tenant has Azure Information Protection (AIP).
MICROSOFT EDGE NOT WORKING ON PHONE UPGRADE
If the tenant doesn't have a supported subscription, they can either purchase Azure Information Protection separately, or upgrade to one of the supported subscriptions. To find out which subscription you have, see What subscription do I have?. Verify that the enterprise tenant has one of the supported subscriptions in Configure Microsoft Edge enterprise sync. If this error is encountered for an Azure Active Directory account, or if DISABLED_BY_ADMIN appears in edge://sync-internals, follow the steps in the next procedure sequentially until the problem is fixed.īecause the source of this error usually needs a configuration change in an Azure Active Directory tenant, these troubleshooting steps can only performed by a tenant admin. Issue: "Sync is not available for this account." See the instructions for resetting data in Issue: Cryptographer error encountered.
MICROSOFT EDGE NOT WORKING ON PHONE UPDATE
This page also shows Policy Precedence and Microsoft Edge Update Policies.Ĭommon sync issues Issue: Can't access Microsoft 365 or Azure Information Protection subscriptionĭo you have a previous Microsoft 365 or Azure Information Protection (AIP) subscription that expired and then replaced with a new subscription? If so, then the tenant ID has changed and the service data needs to be reset. The next screenshot shows an example of active policies for a signed in user. Go to edge://policy/ to see the Policies page. The next screenshot shows the sign-in status for a user.Ĭheck to see if there are any policies that might prevent syncing. Open the Device info folder to see which devices are in the sync list.Ĭheck your sign-in status. Go to edge://sync-internals/ and select the Sync Node Browser tab. Verify that the device you're on is getting sync'ed.
The Summary section, shown in the next screenshot shows that sync is enabled.
On a new tab, go to: edge://sync-internals/. Verify that your account is enabled for syncing. For more information, see Perform a reset to fix a synchronization problem. Sign back into your profile on Microsoft Edge. Make sure you're on the latest version of Microsoft Edge that supports all the sync features (at least. Sign out your account on all Microsoft Edge browsers on all the computers and/or mobile devices - not just the one you're using.
MICROSOFT EDGE NOT WORKING ON PHONE LICENSE
Sign in your Azure portal and verify that your Azure license is valid. Sign in your Office 365 or Microsoft 365 admin portal and verify that your license is valid. Use the following steps as a guide for troubleshooting a sync issue. The error is Last Token Error, EDGE_AUTH_ERROR: 3, 54, 3ea, which is found in edge://sync-internals under Credentials.īefore you start troubleshooting, check the Common sync issues to see if any of these issues apply to your sync problem. 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 Applies to Microsoft Edge on Chromium, version 77 or later unless otherwise noted.
0 kommentar(er)
