A security analyst monitors browser protection across laptops and phones on a centralized dashboard.
Devicie says its reporting connector for Microsoft Edge for Business now pulls browser security events from Windows, macOS, iOS and Android into the same console where IT teams manage their Intune devices. Most of the announcement came out as a press release, but Microsoft has confirmed the main point. That matters for any admin who has stared at a compliant-looking phone and still had no idea what was happening in its browser.

According to the company, Devicie, a continuous operating layer for Microsoft Intune, today announced that its Microsoft Edge for Business Reporting Connector now brings in security events from Edge for Business on Windows, macOS, iOS and Android. The announcement came during Microsoft Ignite 2026, and Microsoft's own Edge team confirmed the platform expansion a day earlier.

A security analyst monitors browser protection across laptops and phones on a centralized dashboard. What Microsoft confirmed​

The Edge team's Ignite post, written by Sean Lyndersay, says that "our reporting connector now supports macOS, Android, and iOS in addition to Windows, with partners including Devicie." The same post says device trust connectors now support macOS, which is a separate change that affects partners such as Cisco Duo and Omnissa.

Microsoft has had this on its roadmap for a while. In its RSAC 2026 post in March, the Edge team said that support for reporting connectors on iOS and Android would arrive "in the next few months." That post also listed the Devicie connector as generally available. The Ignite announcement delivers on that promise and adds macOS.

The short version: Microsoft extended its reporting connector framework beyond Windows. Devicie is one of the named partners, and it says its console can now show those events from all four platforms.

What the connector actually reports​

Devicie says that built on Edge for Business security events, the Devicie Reporting Connector reports on five kinds of browser activity: browser extensions, password security, unsafe browsing, risky downloads, and authentication activity. Here is how the company describes each category:

  • Extensions: installs, updates and removals, broken down by profile and user. Devicie specifically mentions AI assistants, which are now among the most common extensions people install without asking IT.
  • Password security: work passwords reused on unapproved sites, passwords changed after a reuse warning, and passwords found in known breaches.
  • Unsafe browsing: Microsoft Defender SmartScreen phishing and malware warnings, whether the user saw them or clicked past them, plus sites blocked by web content filtering.
  • Risky downloads: files SmartScreen flagged as dangerous, whether they were blocked or opened anyway.
  • Authentication: successful sign-ins to sites an administrator chooses to monitor.

Microsoft Learn's documentation for reporting connectors backs up the underlying event types. For example, it defines a malware transfer event as a download blocked by SmartScreen, or download block bypassed/opened by user, and an unsafe site visit event as a SmartScreen blocking page is shown or bypassed.

Microsoft's list is longer than Devicie's five categories, and some items come with conditions. Browser crash events are reported only when device-level reporting is available. DLP-related events need extra setup: a sensitive data transfer event means content marked as sensitive by DLP scan (requires Analysis connector to be configured). Microsoft also says plainly that supported events and configuration requirements vary by provider.

What this means in practice: don't assume every event in Microsoft's framework reaches Devicie, is turned on by default, or behaves the same on an iPhone as on a Windows 11 laptop. Microsoft's Ignite post confirms the new platforms. It does not promise identical features on each one. Test each platform before you rely on the data.

Setup: two consoles, one policy​

The company's summary is that setup takes a few steps: copy the endpoint and reporting key from Devicie, enter them in the Edge management service, and choose which events to send. Microsoft Learn's Devicie page and Devicie's own help center fill in the details.

Prerequisites listed by Microsoft Learn:

  • Microsoft 365 licenses in an Intune-enabled environment
  • An active Devicie subscription
  • Edge for Business installed on managed devices
  • Admin permissions to deploy and manage policies

Part 1 – in Devicie:

  1. Sign in to the Devicie admin console and open the Edge for Business Report panel.
  2. On the Settings tab, find your endpoint name and reporting key.
  3. Copy both values.

Part 2 – in the Edge management service:

  1. In the Microsoft 365 admin center, make sure at least one Edge configuration policy exists. Devicie's help documentation says the connector must be assigned to an existing Edge configuration policy.
  2. Open the Connectors page. Under Connectors, find Devicie Reporting Connector and select Set up.
  3. In Chosen policy, select the policy.
  4. Fill in Host address, Port and Token ID.
  5. Select Test Connection to confirm the connection works.
  6. Under User & Browser events, choose the events to send. Then choose any Optional events and Devices events.
  7. Select Save configuration.

Checking that it worked: after saving, Devicie's guide says to return to the Devicie portal and navigate to Reports > Edge for Business. If no events show up there, check these first:

  • No configuration policy. The connector can't be set up without one, so create the policy before you start.
  • Field names don't match. Devicie gives you an "endpoint name" and a "reporting key," but Microsoft's form asks for Host address, Port and Token ID. Microsoft's Devicie page doesn't spell out which value goes in which field. If Test Connection fails, Devicie's own documentation is the best place to check.
  • Old prerequisites. Microsoft Learn's general connectors overview still lists Edge 135.0.3179.85 or later and only Windows 10/11 or Windows Server 2016 and later. That page predates the macOS and mobile expansion, so don't treat it as the final word on non-Windows requirements. Devicie's release only says that each platform needs a supported Edge version, without giving numbers.

The MSP angle and the "act on it" claim​

Devicie says that each tenant connects to Devicie with its own reporting key, so managed service providers see every customer's browser events in one multi-tenant portal while each customer's data stays separate. The company also says that because it deploys Edge policy too, admins can respond from the same console. Its example is blocking an unsanctioned extension and then confirming it was removed.

These are the company's claims, not independently audited guarantees. Microsoft Learn does list "automate response actions via Devicie's policy framework" as a benefit, but it doesn't certify how Devicie isolates tenants. Devicie also says the cross-platform reporting needs no extra agent on the device. Microsoft's Ignite post neither confirms nor contradicts that.

This fits a wider shift. At the same Ignite, Microsoft announced multi-tenant Edge policy baselines for MSPs through inforcer, and a native connector that sends Edge security events and audit logs into Microsoft Sentinel (in preview, with Sentinel licensing required). Organizations that already run Sentinel or a SIEM may decide that's where browser telemetry belongs. Devicie is betting that Intune-focused teams would rather see it next to device health and compliance.

Cost, timeline and an awkward placeholder​

On cost, the connector requires a Devicie subscription, and Microsoft provides Edge for Business connectors at no additional cost. Microsoft charges nothing extra for the connector, but the reporting itself needs a paid Devicie subscription.

The timeline, as Devicie describes it:

DateMilestone
April 2025Microsoft launches its security connector framework; Devicie's connector is in preview
RSAC 2026 (March)Microsoft names the Devicie connector generally available
May 2026Devicie says it released its full Edge for Business report to all customers
Nov. 17, 2026Microsoft confirms reporting connector support for macOS, iOS and Android
Nov. 18, 2026Devicie announces cross-platform reporting

There was also a small publishing slip. The first version of the release, which is still the version republished by The Manila Times, said the feature was available now with "[confirm before release]" still attached. PR Newswire later issued a correction saying in the "Availability" section, Sentence 1, the wording [confirm before release] should be removed. The corrected release says cross-platform reporting is available now to Devicie customers.

Bottom line for Windows admins​

Microsoft's own documentation and announcements back up the main development: Edge for Business reporting connectors now work beyond Windows. Devicie is one of the first named partners to bring that cross-platform data into an Intune management console.

If you already use Devicie, adding the connector is a short setup with no extra Microsoft charge. Before you rely on it for incident response, check which events actually arrive from each platform. If you don't use Devicie, the more important news may be the framework change itself, because the browser on your users' phones is no longer invisible to your reporting tools.

 

References

  1. Devicie Extends Microsoft Edge for Business Security Reporting across Platforms - The Manila Times The Manila Times 2026-11-18T14:43:01+00:00
  2. Setting Up Edge for Business in Devicie help.devicie.com
  3. Introducing Edge for Business security connectors - Microsoft Edge Blog blogs.windows.com