July 31, 2026 Stories worth reading. Perspectives worth sharing.
Microsoft Edge’s Unified Google Data Import in Settings: What Admins Need to Know
Microsoft 365

Microsoft Edge’s Unified Google Data Import in Settings: What Admins Need to Know

Mo Wasay July 30, 2026 6 min read
Microsoft Edge’s Unified Google Data Import in Settings: What Admins Need to Know

Microsoft Edge is rolling out a long-awaited capability: users can now import data from their Google account—including passwords, bookmarks, browsing history, and autofill data—at any time via Edge Settings. Previously, this import was only available during the browser’s first-run experience, leaving admins and users with no direct recourse if data was missed during setup.

REPORT: What’s New This Cycle

General Availability for Edge’s unified Google account import experience is scheduled for August 2026 (roadmap item 568365). This feature introduces a single entry point in Edge Settings: Settings > Profiles > Import browser data. This replaces the fragmented experience where Chrome profile and Google account imports were initiated separately and only during onboarding.

Key changes:

  • One-click import at any time — Users can now import Chrome data and Google account data even after initial setup, simplifying migrations and late data recovery.
  • Broader data scope — The import supports passwords, bookmarks, history, and autofill data through direct Google authentication.
  • Settings location — Unified under Settings > Profiles > Import browser data within Edge.
  • PowerShell/API changes — No direct Microsoft.Graph/Entra endpoints for browser import, but use of Edge management policies via Intune and reporting user browser configuration is improved (see Detect section).

IMPACT: Who and What Is Affected?

This update impacts:

  • End users migrating from Chrome to Edge, especially in large enterprises, education, or hybrid environments.
  • Admins managing device onboarding, browser standardization, or security baselines. Missed imports can now be remediated without user profile resets.
  • Organizations with security and compliance concerns—import operations now happen post-setup, increasing the need for visibility and safe configuration.

Risk to consider: Users can now import personal Google account data (including passwords) into managed Edge profiles long after initial setup. If not governed, this introduces shadow data movement and potential policy non-compliance.

EDUCATE: Understanding the Import Flow

Historically, Edge’s “first run” wizard offered to import data from Chrome or a Google account by accessing Chrome’s local profile and, optionally, authenticating to Google to fetch cloud data. After setup, this wizard was inaccessible, leaving admins troubleshooting incomplete migrations with manual workarounds.

Now, the import browser data pane in Settings offers:

  • Chrome profile import — Reads local Chrome data if present.
  • Google account import — Authenticates to Google, retrieves cloud-based passwords, bookmarks, autofill, and history.
  • Granular selection — Users pick which data types to import.

This is especially useful for VDI/pooled device environments, device redeployments, or late-stage migrations where onboarding was skipped or interrupted.

DETECT: Auditing Edge Data Imports with Microsoft Graph and Intune

While Microsoft does not provide a direct API to enumerate Edge import activity, admins can use Microsoft Graph in combination with Intune to report which devices have Edge as the primary browser, and whether browser sync is enabled—an indirect but practical audit.

The following script reports all Intune-managed Windows devices with Edge installed, and retrieves browser sync status for signed-in users. (Pagination and error handling included.)

Import-Module Microsoft.Graph.DeviceManagement
Connect-MgGraph -Scopes 'DeviceManagementManagedDevices.Read.All','User.Read.All'

# Get all Windows devices
$devices = @()
$uri = 'deviceManagement/managedDevices?$filter=operatingSystem eq ''Windows'''
do {
    $response = Invoke-MgGraphRequest -Method GET -Uri $uri
    $devices += $response.value
    $uri = $response.'@odata.nextLink'
} while ($uri)

# For each device, check if Edge is installed (via discovered apps)
foreach ($device in $devices) {
    try {
        $apps = Invoke-MgGraphRequest -Method GET -Uri "deviceManagement/managedDevices/$($device.id)/detectedApps"
        $hasEdge = $apps.value | Where-Object { $_.displayName -like 'Microsoft Edge*' }
        if ($hasEdge) {
            # Report browser sync status for primary user
            $user = Get-MgUser -UserId $device.userId -ErrorAction SilentlyContinue
            if ($user) {
                Write-Output "Device: $($device.deviceName), User: $($user.DisplayName), Edge Installed: Yes"
                # Placeholder: enumerate browser sync status if available via Graph extensions
            }
        }
    } catch {
        Write-Warning "Failed to query device $($device.deviceName): $_"
    }
}

Notes: Pagination is handled via @odata.nextLink in device queries. No device/app data is modified. Reporting on actual import events is not exposed in Graph; for more detail, audit browser sync status or consider Microsoft Defender for Endpoint browser telemetry if licensed.

REMEDIATE SAFELY: Managing Google Import via Policy

Admins wishing to control or restrict the new import behavior can use Edge policy settings via Intune or Group Policy, such as:

  • ImportBrowserSettings — Controls whether import is allowed.
  • ImportSavedPasswords — Controls password import from other browsers/accounts.

For PowerShell-based policy management, always perform a dry run by reviewing targeted groups and current policy assignments:

# DRY RUN: List Edge browser policy assignments in Intune
Connect-MgGraph -Scopes 'DeviceManagementConfiguration.Read.All'
$policies = Get-MgDeviceManagementConfigurationPolicy | Where-Object { $_.DisplayName -like '*Edge*' }
foreach ($policy in $policies) {
    Write-Output "Edge Policy: $($policy.DisplayName), Id: $($policy.Id)"
    $assignments = Get-MgDeviceManagementConfigurationPolicyAssignment -DeviceManagementConfigurationPolicyId $policy.Id
    foreach ($assignment in $assignments) {
        Write-Output "  Assigned to: $($assignment.Target.DisplayName)"
    }
}

No bulk policy changes are made—review assignments and use the portal for final changes, or add -WhatIf where supported.

PORTAL EQUIVALENT: Where to Find and Control the Setting

  • User-side: Edge Settings > Profiles > Import browser data
  • Admin-side: Microsoft Intune admin center > Devices > Configuration profiles > Create profile > Windows 10 and later > Settings catalog > Microsoft Edge > Import browser settings
  • Policy reference: See the official Edge policy documentation for import-related policy keys.

WHAT’S COMING IN THE NEXT 90 DAYS

  • Edge for Business profile separation (roadmap 124939, GA Q2 2024): Enforced work/personal data boundaries in Edge, with improvements to policy-driven separation and sync control.
  • Edge management via M365 admin center (roadmap 145917, Preview Q3 2024): New unified browser management pane for reporting, extension control, and security baselines from the Microsoft 365 admin center.
  • Defender for Endpoint browser telemetry expansion (roadmap 93281, rollout Q3 2024): Additional visibility into browser events—including import activity—for licensed organizations.
  • Chrome/Edge password manager harmonization: Work is ongoing to enable secure migration of password vaults (watch for Edge and Entra product team blogs).

THE UPGRADE: Why This Matters for Admins

  • Productivity: Fewer support calls and tickets around missed imports; late onboarding is now trivial.
  • Security: Easier to audit browser data flows and enforce policy; Edge policy controls have expanded to match new import options.
  • Compliance: More predictable browser data state, especially for regulated environments needing evidence of managed browser configuration.

Related changes—such as Edge for Business profile separation and Defender for Endpoint telemetry—amplify these benefits by giving IT better tools to detect, report, and control browser data movement.

RECOMMENDATION: Prioritised Takeaway

  • Review and update your Edge/Intune policies now to explicitly permit or restrict Google account imports based on your security posture.
  • Educate users on the new import experience to reduce migration friction and shadow IT risk.
  • Pilot browser telemetry solutions if you need evidence of import activity or browser data flows.
  • Stay ahead of roadmap items—Edge for Business and unified browser management are rapidly improving end-to-end visibility for Microsoft 365 admins.