How To
Summary
With Configuration Manager version 1910, administrators gained the ability not only to deploy the Microsoft Edge browser but also to manage its updates directly through SCCM. This enhancement means Edge updates can now be distributed in the same way as other software updates, simplifying lifecycle management across enterprise environments.
Steps
Creating the Microsoft Edge Application in SCCM
To set up Microsoft Edge as an application:
- Open the Configuration Manager console.
- Navigate to Software Library → Overview → Microsoft Edge Management.
- Right‑click Microsoft Edge Management and choose Create Microsoft Edge Application.
The wizard guides you through the process:
- On the Application Settings page, provide the application name and content location.
- Under Microsoft Edge client settings, select from the available channels: Dev, Beta, or Stable. For most enterprises, choosing Stable with the Latest version is recommended.
- Decide whether to deploy immediately or later. If you select Yes, specify the target device collection and distribution point.
- Complete the wizard, and on the Completion page, click Close.
Verifying Deployment
After deployment, you can confirm success by running the report All application deployments (basic) under Software Distribution → Application Monitoring. Select the Edge application and the relevant device collection to view the summary. Other built‑in reports can also provide similar insights.
Managing Microsoft Edge Updates
To bring Edge updates into SCCM:
- Ensure the Updates classification is enabled under Software Update Point properties → Classifications.
- Under Products, select Microsoft Edge. If it doesn’t appear, perform a synchronization and check again.
- Run Synchronize Software Updates. Once complete, you’ll see updates for all three channels—Beta, Dev, and Stable—within the console.
From here, Edge updates can be managed like any other update:
- Add them to a Software Update Group and deploy.
- Incorporate them into an Automatic Deployment Rule (ADR) for ongoing management.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
01 December 2025
UID
ibm17253117