As of August 1, the built-in Microsoft Translator in Edge simply stopped working for anyone still running version 135 or earlier. If your browser hasn’t moved past that mark, foreign-language pages will no longer offer a translate button. The fix is straightforward—update to a current version—but the cutoff has already passed, and organizations that deferred updates are feeling the disruption now.

What Just Changed in Edge

Microsoft flipped the switch on the Edge 135-and-older translation backend on July 30, 2026. That was the hard deadline announced in the release notes for the Edge 151 release cycle. The browser’s built-in translation uses Microsoft Translator, and after July 30, the older service endpoint no longer responds. You won’t see an error message; the translation prompt simply disappears. This isn’t a bug—it’s the planned retirement of a legacy stack, with version 136 and newer relying on a different, more modern architecture.

The news comes alongside the beta build 151.0.4129.59, which dropped on July 31. That build itself is largely a maintenance release, but the 151 branch carries a raft of changes that will soon land in the Stable channel, as first reported by Neowen. Beyond the translation cutoff, here’s what the beta brings:

  • Clipboard suggestions in the address bar: Copy a link or text anywhere, and Edge may offer it as a suggestion when you click the address bar. The feature is controlled by the new AddressBarClipboardSuggestEnabled policy.
  • Enterprise passkey sync: Sign-in credentials built on public-key cryptography can now roam across a user’s managed devices via Edge, controlled by the existing PasswordManagerPasskeysEnabled policy.
  • The end of Edge Drop: The feature that let you shuttle files and notes between your devices through Edge is retiring “in the near future.” Files are already stored in OneDrive, but text notes must be downloaded manually before the shutdown.
  • Sidebar app list removal: New apps can no longer be pinned to the sidebar, existing pinned apps are being removed, and any sidebar app policies no longer apply.
  • macOS 12 Monterey loses support: Edge 151 requires macOS 13 Ventura or later. Macs stuck on Monterey cannot upgrade past Edge 150.

What This Means for You

If you’re a home user

The most immediate takeaway: your browser’s translate feature is dead if you haven’t updated to at least version 136. That means no automatic “Translate to English” prompts on French news sites, no on-demand translation for Japanese product pages. The remedy is simple—jump to the newest release—but if you’ve been ignoring updates, you’re also missing security patches and performance fixes.

When you do update, you might notice a new convenience: the address bar now peeks at your clipboard. Copy a tracking number, a restaurant address, or a URL, and Edge may suggest it right in the drop-down. It’s a timesaver for many, but if you regularly copy sensitive data (passwords, account numbers), you might not want that information surfacing in your browser chrome. Microsoft provides a policy to disable it, though a simple settings toggle hasn’t appeared yet in the beta; expect one in the stable release.

If you relied on Edge Drop to pass notes or screenshots between your laptop and phone, you need to act. Microsoft hasn’t set a final shutdown date, but the “near future” language is your cue. Open Edge’s Drop panel (edge://favorites?drop), download any text notes to a safe place, and confirm that your files appear where you expect in OneDrive. Once Drop retires, those notes will be gone.

If you’re an IT administrator

This is more than a translation inconvenience. The deadline has already passed, so any endpoint still running Edge 135 or older is now a compliance and productivity gap. Translation may be a critical feature for loan origination workflows, international procurement, or customer service agents. Those functions are broken until you push a modern Edge release.

Start with an inventory check—your management tools can report installed Edge versions. Flag anything below 136. These are likely unmanaged devices, outdated virtual desktop images, kiosks, or machines where update rings were paused. Pushing the latest stable build (or 151.0.4129.59 if you’re in the beta channel) restores translation and plugs the security holes.

Then, turn to the new policies. Clipboard suggestions (AddressBarClipboardSuggestEnabled) may be helpful for your users, but they introduce a new data-handling surface. A copied customer identifier, invoice number, or internal URL appearing in the address bar could be a privacy concern. Decide where your organization lands and set the policy (mandatory or recommended) across your Windows and macOS fleets. Remember that this policy requires an Edge restart to take effect.

Passkey sync (PasswordManagerPasskeysEnabled) is a bigger strategic decision. If you’re already piloting Windows Hello for Business, FIDO2 keys, or Microsoft Entra ID, enable the policy and start testing. The real value of passkeys—phishing resistance—only materializes when credentials roam with the user. Make sure your sign-in flows are ready: verify that the SaaS apps and internal services your employees use actually support passkeys, and map out what happens when a device is lost or an employee departs.

Other items to act on:

  • Export Edge Drop data: Even if you’ve never encouraged its use, some of your users may have stored meeting notes or project snippets there. Communicate a deadline for them to retrieve text notes, or script an export if you can.
  • Purge sidebar app policies: Any Group Policy Objects, Intune configuration profiles, or baselines that manage sidebar apps are now dead weight. Remove those settings to avoid confusion and clutter.
  • Identify Macs on Monterey: Any Mac that can’t move to Ventura or later won’t get Edge 151. That gap isn’t just about new features; it means no Chromium security fixes delivered through Edge. Decide whether to upgrade macOS, replace the hardware, or formally accept the risk.

How We Got Here

Edge’s rapid release cadence means significant changes land roughly every four weeks, but the translation cutoff is unusual in its abrupt, hard-stop nature. Microsoft has been migrating Edge’s translation engine to a V2 architecture for performance and accuracy. The older backend, which Edge 135 and earlier rely on, just can’t be supported indefinitely. The July 30 date was likely published months ago in Microsoft 365 message center posts or tech community blogs, but many administrators tune out such notices.

The other changes in version 151 fit a broader pattern. Edge Drop was an experiment in cross-device collaboration that never became essential; retiring it cleans up the browser surface while steering users to OneDrive. The sidebar app list was a relic of an earlier Edge design, and its removal aligns with Microsoft’s current focus on tabs, web apps, and the Copilot sidebar. Clipboard suggestions and passkey sync are modern conveniences that mirror Chrome’s direction—and they tie tighter to the Windows and Microsoft 365 ecosystems.

For IT, the translation deadline is a reminder that browsers are no longer static tools. Services can be cut off if you stay too far behind. Microsoft commits to Edge and WebView2 updates on Windows 10 22H2 through at least October 2028, but that commitment doesn’t guarantee every connected service works on old builds.

What to Do Now

For home users

  1. Update Edge now – Open the three-dot menu, go to Help and feedback > About Microsoft Edge, let it download the update, and restart. Translation will return.
  2. Check Edge Drop – Navigate to the Drop pane (you can find it in the Edge sidebar) and save any text notes you want to keep. Confirm that any files you shared are safely in your OneDrive.
  3. Weigh clipboard suggestions – The feature appears with Edge 151. If you’d rather not see copied content in your address bar, you can disable it via policy once it reaches the stable channel, or clear your clipboard after copying sensitive data for now.

For IT admins

  1. Inventory and update – Use your endpoint management platform to find all Edge installations below 136. Push the latest stable or beta build. For air-gapped or offline machines, download the full installer from the Microsoft Edge for Business page.
  2. Configure key policies –
    - AddressBarClipboardSuggestEnabled: Set to disabled if clipboard data in the browser UI is a risk. Otherwise, consider leaving it unconfigured to let users decide, but be aware that until a UI toggle exists, it may be on by default.
    - PasswordManagerPasskeysEnabled: Enable if you’re ready to support passkeys. Start with a pilot group.
  3. Clear out sidebar app settings – Remove any GPO or profile that references sidebar apps. They won’t break things, but they’ll add confusion.
  4. Manage Edge Drop retirement – Send a company-wide communication asking users to export text notes. Consider using policy to block Drop if you want to prevent further use.
  5. Address Macs on Monterey – Run a report on macOS versions across your estate. Flag any that can’t receive Ventura. Plan upgrades or replacements before the 151 stable update becomes mandatory.
  6. Communicate – Let users know translation is fixed after the update, and if you enabled clipboard suggestions, explain what they’ll see.

What’s Next

Edge 151 is slated for the Stable channel around the end of July, so the features and retirements described here will become the default experience for millions of users. The translation cutoff is permanent—there is no going back—and future Edge releases will no doubt continue to shed older services while adding new integration points with Windows and Microsoft 365. For home users, the lesson is simple: let automatic updates run. For organizations, the message is sharper: treat browser updates with the same rigor as OS patches, or risk losing business-critical features.