What causes delays in cross-context messaging?

Slowdown 1 – The receiving context is busy

Slowdown 2 – The task queue is congested

Slowdown 3 – Serialization and deserialization overhead

Using the Delayed Message Timing API

// Create a PerformanceObserver instance.
const observer = new PerformanceObserver((list) => {
  console.log(list.getEntries());
});

// Start observing "delayed-message" Performance entries.
observer.observe({type: 'delayed-message', buffered: true});

{
    "name": "delayed-message",
    "entryType": "delayed-message",
    "startTime": 154.90000009536743,
    "duration": 169,
    "traceId": 4,
    // The type of message-passing event.
    "messageType": "cross-worker-document",
    // The timestamp for when the message was added to the task queue.
    "sentTime": 155,
    // The timestamps for when the receiving context started and stopped
    // processing the message.
    "processingStart": 274.90000009536743,
    "processingEnd": 324.7000000476837,
    // The time the message spent waiting in the receiver's task queue.
    "blockedDuration": 119.90000009536743,
    // The time needed to serialize and deserialize the message.
    "serialization": 0,
    "deserialization": 0,
    // The number of queued tasks blocking the postMessage event.
    "taskCount": 38,
    // The number of entry-point JavaScript tasks, including those with
    // a duration lower than 5ms.
    "scriptTaskCount": 2,
    // The time needed to run all script.
    "totalScriptDuration": 119,
     // The list of PerformanceScriptTiming instances that contribute to the
     // delay.
    "scripts": [
        {
            "name": "script",
            "entryType": "script",
            "startTime": 154.90000009536743,
            "duration": 119,
            "invoker": "DedicatedWorkerGlobalScope.onmessage",
            "invokerType": "event-listener",
            "windowAttribution": "other",
            "executionStart": 154.90000009536743,
            "forcedStyleAndLayoutDuration": 0,
            "pauseDuration": 0,
            "sourceURL": "...",
            "sourceFunctionName": "runLongTaskOnWorker",
            "sourceCharPosition": 267
        }
    ],
    // The PerformanceMessageScriptInfo instance which provides details
    // about the script that sent the message.
    "invoker": {
        "name": "invoker",
        "sourceURL": "...",
        "sourceFunctionName": "sendMessage",
        "sourceCharPosition": 531,
        "sourceColumnNumber": 14,
        "sourceLineNumber": 13,
        "executionContext": {
            "name": "",
            "type": "window",
            "id": 0
        }
    },
    // The PerformanceMessageScriptInfo instance which provides details 
    // about the script that handled (or is handling) the message.
    "receiver": {
        "name": "receiver",
        "sourceURL": "...",
        "sourceFunctionName": "runLongTaskOnWorker",
        "sourceCharPosition": 267,
        "sourceColumnNumber": 41,
        "sourceLineNumber": 9,
        "executionContext": {
            "name": "",
            "type": "dedicated-worker",
            "id": 1
        }
    }
}

Let us know what you think

Get even more with Copilot Mode in Edge

Happy shopping!

Test the API today by registering to the origin trial

1. Go to the WebAppInstallation origin trial page, sign-in with your GitHub account and accept the terms of use.
2. Add your website's domain name to enable the Web Install API origin trial for that domain.
3. Copy the token string:
4. Add the following meta tag to your website's HTML code:
   <meta http-equiv="origin-trial" content="[paste the token here]">
   You can also send the origin trial token as an HTTP server response instead:
   Origin-Trial: [paste the token here]

Or test the API locally only

1. Open a new tab in Microsoft Edge and go to the edge://flags page.
2. Search for "Web App Installation API".
3. Change the flag's default value to Enabled and then restart the browser.

Let us know what you think

• Introducing Copilot Mode
• Multi-tab reasoning and other AI upgrades
• Secure AI browsing controls
• Microsoft named a Leader in IDC MarketScape
• Protect browsing for contractors
• Watermarking for sensitive files and sites
• Protecting copy/paste actions
• Unify policy management across platforms
• Simplify prerelease testing with built-in flexibility
• Take control of browser extensions
• Get started today

Introducing Copilot Mode

Multi-tab reasoning and other AI upgrades

Secure AI browsing controls

Microsoft named a Leader in IDC MarketScape

Protect browsing for contractors

Watermarking for sensitive files and sites

Protecting copy/paste actions

Unify policy management across platforms

Simplify prerelease testing with built-in flexibility

Take control of browser extensions

Get started today

• Enable Copilot Mode in Edge for Business and get started with the Copilot-inspired new tab page, available today. Learn more at https://aka.ms/ConfigureEdgeAI
• Try the consumer version of Copilot Mode in Edge now to try more AI features that are coming to Edge for Business. Learn more at https://aka.ms/Copilot-mode
• Download the IDC MarketScape excerpt at our website: https://aka.ms/EdgeforBusiness
• Configure the secure enterprise browser you already have, with an expert-curated guide at https://aka.ms/ConfigureEdgeSEB

• Global presence
• Ability to provide direct support to customers
• Hybrid architecture compatibility
• Ecosystem partnerships
• Sustained market presence

"Microsoft implements a sophisticated zero trust security model that incorporates users identity, device health, location, and risk signals into access decisions. Edge for Business enforces conditional access policies that can require additional verification factors before accessing organizational resources, even on unmanaged devices."– IDC MarketScape Excerpt

"This integration enables unified policy management across applications, simplified administration through familiar interfaces, and consistent security controls that span the entire digital workspace, significantly reducing management complexity while enhancing security posture."– IDC MarketScape Excerpt

"The browser creates distinct profiles with visual differentiation between work and personal browsing, preventing cross-contamination by maintaining separate cookies, cache, and browsing data between contexts, effectively balancing security with user experience."– IDC MarketScape Excerpt

Why should I use passkeys?

• Passkeys can't be guessed or reused like passwords.
• They're resistant to phishing and credential stuffing attacks.

• No need to remember complex passwords or type them manually.
• Just use your fingerprint, face scan, or device PIN to sign in.

• Passkeys sync securely via your Microsoft account and are currently available on Windows devices – with planned future availability on additional platforms.

• Your biometric data is processed locally on your device.
• Websites only get a cryptographic proof that you are you.

How can I use passkeys in Microsoft Edge?

Ready to try passkeys?

• Windows device (version 10 and above)
• Microsoft Edge (version 142 and above)
• Microsoft account

Frequently Asked Questions

What happens to my saved passwords?

Your saved passwords remain untouched. You can continue using them as usual. But whenever a site supports passkeys, you'll have the option to upgrade to a passkey for stronger security and faster logins.

Do I need to create new accounts to use passkeys?

No. For most existing accounts, you can simply add a passkey without changing anything else.

What if I switch devices?

Your passkeys are securely backed up and synced through your Microsoft account. When you sign in to a new device, your passkeys come with you. Note: This requires verifying yourself with the Microsoft Password Manager PIN on the new device. Passkey sync capability is available on Windows and will be expanded to other platforms soon.

Is syncing passkeys available on mobile or for work or school accounts (Microsoft Entra)?

No, this functionality is currently not available for mobile devices or for Microsoft Entra accounts.

Are passkeys safe if someone steals my device?

Yes, passkeys are designed to be secure even if your device is lost or stolen. Without your fingerprint, facial recoginition, or device PIN, no one can use them.

Can I still view or manage my saved passwords?

Absolutely. You can manage both your existing passwords and passkeys from your Microsoft Password Manager in Edge.

Where can I learn more?

You can learn more about Azure confidential ledger by visiting Azure confidential ledger documentation.

Blocks scams before they catch victims

One report can protect 50 others

Jump-starting the connection to SmartScreen

Edge 142 adds a scareware sensor for faster detection

Accelerating the pipeline

Thanks to the scam-fighting community

What’s new: expanded connector availability

• Symantec Data Loss Prevention – Allows customers to identify, monitor and protect sensitive, confidential or regulated data. This includes controlling data that is uploaded, pasted or printed from the web.

• RSA ID Plus – Leverages device signals from Microsoft Edge so only verified, managed endpoints can access critical apps.

• Omnissa Access Device Trust Connector – Allows administrators to enforce conditional access to web, native and virtual applications protected by Omnissa Access.

• KnowBe4 SecurityCoach – Enables real-time monitoring of risky browser activities like unsafe site visits, password reuse and malware downloads.

• Trellix DLP – Applies Trellix DLP Endpoint policies to inspect for sensitive content within the Edge for Business browser.

Easy to deploy, easy to manage

Deploy connectors today

• Refer to partner licensing requirements for any costs associated with using the connector.
• The Trellix connector is not enabled by default in DLP Endpoint Windows version 11.12.0. Customers can contact Trellix Customer Support through their online portal or by calling their designated contact to enable this capability.

“Ignore All Previous Instructions”: Prompt injection attacks

Our approach to Prompt Injection attacks

• Untrusted input: We start by assuming that any input from an untrusted source may contain unsafe instructions.
• Detect deviations: Prompt injections generally cause the model to do something different from what the user asked of it. Mitigations can be created to detect and block those deviations.
• Limit access to sensitive data or dangerous actions: Simply put, if the model can’t get to something or do something bad, then the risks are lower.

Protecting from untrusted Input

• Scoped to known sites by default – In the default “Balanced Mode” setting, Actions in Edge only allow access to a curated list of sites. Users can allow Actions to interact with other sites by approving them. Users can also configure “Strict Mode” in settings which overrides the curated allow list and gives them full control to approve every site Actions interacts with.

• SmartScreen protection – Microsoft Defender SmartScreen detects and protects millions of Edge users every day from sites confirmed as scams, phishing, or malware. While Copilot is controlling the browser, suspicious or bad sites are blocked automatically by SmartScreen, and the agent is prevented from bypassing the block page.

• Azure Prompt Shields mitigate attacks by analyzing whether data is malicious.
• Built-in safety stack – Copilot is trained specifically to detect and report safety violations if malicious content tries to encourage violence or harmful behavior.
• Spotlighting (in testing) – Kiciman, et al, of Microsoft Research, described a technique called Spotlighting to better separate user instructions from grounding content (documents and web pages) so the model can better ignore injected commands without impacting efficacy. We will be testing Spotlighting with Actions in Edge and will report on its effectiveness.

• Real-time SmartScreen blocks – when new sites are confirmed as scams, phishing, or malware, the SmartScreen service can block them for all Edge users worldwide within minutes.
• Global blocklist updates within hours – When new sites are identified as unsafe for Copilot to read, we can update the global blocklist within hours.

Detecting and blocking deviations from the task

• Relevance checks, shown above, give the user a chance to stop an action if a secondary model detects possible task drift.
• High risk site prompts – when a context is detected to be sensitive (e.g. email, banking, health, sensitive topics) the model will stop and request permission to continue.
• Task Tracker (in testing) - Paverd et al described a novel technique known as Task Tracker, which monitors activation deltas to detect when the model drifts from the user’s original intent after processing external data. We are integrating these techniques into our orchestration layer, validating their precision, and reducing false positives with the MAI Security team. We will report on progress here as well.

Limit access to sensitive data or dangerous actions

• No interaction with edge:// pages (e.g., Settings) or UI outside a tab’s web content.
• External app launches are blocked (protocol handlers).
• Downloads are disabled.
• No ability to open the file or directory selection dialog.
• No access to data or apps outside of Edge
• Context menus are disabled.
• Tab audio is muted by default.
• Site Permission changes are blocked (For example, if a site requests camera access permissions, the agent cannot grant that permission).

Closing

Get tasks handled for you with Copilot Actions in Edge

Jump back in with Journeys

You’re always in control

Tell us what you think