AppSense and Microsoft Edge Legacy migration to Chromium with UEM
Microsoft Edge Legacy, built on EdgeHTML, is being replaced by Chromium-based Microsoft Edge. For AppSense-managed organisations, this is more than a browser upgrade: package detection, administrative policies, profiles and User Experience Management (UEM) personalisation all need attention. A staged migration helps retain control of defaults, extensions, security settings and access to internal applications.
AppSense adds context to endpoint management by linking software behaviour to a person, device, location or role. That context can shape a UEM experience, such as giving a field worker a different browser start page and extension set from a finance employee. Chromium Edge can support that model, but its executable, policies and first-run sequence differ from Edge Legacy, so existing conditions and actions should be tested rather than copied.
The practical starting point is an inventory of operating systems, browser versions, extensions, critical websites and business workflows. Windows 10 and Windows 11 devices may still present different upgrade and support constraints, especially for remote users. Australian IT teams should also separate managed corporate devices, BYOD and contractor equipment, since identity, ownership and acceptable configuration levels differ across those groups.
Build a reliable browser inventory
Start with data from AppSense, endpoint management and a quick user-side check, because each source can miss part of the estate. Record the Windows build, Edge architecture, version, install path, update channel and any kiosk configuration. Note applications that depend on browser identity, certificate selection, plug-ins or legacy authentication, especially where staff use hot-desking and shared workstations in Melbourne, Brisbane or Perth offices.
Microsoft has ended support for Edge Legacy, but retiring it does not automatically make every legacy website obsolete. Chromium Edge includes an Internet Explorer mode for sites that still require that rendering path. Test those sites separately, including sign-in, ActiveX and download workflows, rather than maintaining Edge Legacy for the whole organisation on the assumption that every internal page needs it.
Set a measurable baseline before changing packages: first-run time, page failures, extension conflicts, crash rates and support contacts involving the browser. Teams that use Google Workspace for communications can consult the Google Duo help guidance when preparing recorded demonstrations and user updates through that channel. A plain-language cutover brief will make the change easier to understand across the support desk.
Choose a risk-based pilot
Choose a risk-based pilot rather than a broad deployment. Start with staff who represent normal AppSense personas, including office-based users, remote workers and an administrator, while excluding specialist workflows until they have been validated. Define exit criteria such as successful policy application, retained bookmarks, working extensions and no new sign-in failures. Keep Edge Legacy available only where a documented exception still applies.
Australian conditions deserve specific attention. A pilot that includes people in Perth, Darwin and regional Queensland can expose bandwidth, DNS and proxy differences that a Sydney or Melbourne office may not reveal. Test laptops that alternate between office and home networks, as well as devices that wake from sleep or update while disconnected. Avoid treating a successful metropolitan pilot as proof that remote connectivity is sound.
Plan the ramp-up in rings, with an agreed soak period and rollback point between each ring. Match the support roster to operating hours in each state, and publish a run sheet that says who can approve exceptions, who will watch dashboards and when the change is declared complete. Where internal delivery capacity is limited, a specialist partner can add local delivery advice on packaging, change planning and support handover.
Prepare AppSense for Chromium Edge
Create a dedicated software deployment or AppSense task for Chromium Edge instead of reusing a generic Microsoft Edge rule. Give the package an explicit detection method and separate it from Edge Legacy during the transition. Review pre-install and post-install scripts for registry paths, file checks and shortcuts that still point to EdgeHTML. Edge can update independently in the background, so conditions tied to one exact build number will age quickly.
Translate the policy baseline rather than assuming a like-for-like mapping. EdgeHTML and Chromium Edge use different administrative templates, and a setting with a similar name may behave differently or be ignored. Cover URL allow and block lists, extension permissions, proxy configuration, download handling, sign-in controls, password storage, telemetry, startup behaviour and managed banners. Validate each policy on edge://policy and through the relevant cloud reporting surface.
Before writing a custom script, search the community tools library for an existing package, configuration or removal utility that has already been discussed by AppSense users. Test any imported file in a lab, because scripts can contain assumptions about paths, user privileges and older builds. Keep a copy of the current Edge Legacy policy export and package detection rules so the previous state can be reconstructed.
Move profiles and policies without losing control
Deploy Chromium Edge through AppSense or the approved software distribution route, normally from a stable enterprise release channel. Install it alongside Edge Legacy for the pilot, then remove the legacy browser only after the exception list and rollback window close. Check that users receive one supported shortcut, that update services remain healthy and that no self-update overwrites the deployed configuration during testing.
Handle browser data as a separate workstream. Chromium Edge may offer to import favourites, history and passwords, but import is not a guaranteed backup and work-profile sign-in can change what synchronises. Publish simple instructions for keeping or exporting bookmarks, and confirm whether corporate credentials are permitted in the browser password store. Existing proxy and certificate rules must be ready before first launch, or profile creation may fail and appear as a personalisation issue.
Translate user experience policies for the new browser and test them against actual personas. A field-worker profile might need a restricted extension set and an internal start page, while a contractor profile should receive less access and no retained browsing data. Apply policies in a deliberate order, then confirm that Edge first-run pages do not overwrite an administrator’s homepage, search provider or download location. Keep the rollback package and browser data export available until the final cohort is stable.
Validate UEM personalisation in real use
Validation should cover more than whether Edge opens. Exercise installation, first launch, navigation to an internal site, authentication, extension use, printing, file download and the browser update path. Include standard users, local administrators and users whose AppSense context is discovered through a VPN or corporate network. Compare results with Edge Legacy and record the expected policy source for every control.
New users often expose sequencing problems that established profiles hide. If a person receives the default Edge experience instead of the intended UEM bundle, consult the personalisation troubleshooting notes for checks around app installation, persona evaluation and user-session timing. Re-test after the client has completed its context discovery rather than forcing every rule to run as a one-off task.
Use support feedback to refine the migration rather than treating every complaint as an Edge defect. Australian teams often work from a cutover run sheet and require clear sign-off from the change owner, so record browser-related tickets against the pilot cohort, configuration change and device state. A small decline in first-run errors, extension faults or sign-in calls is meaningful only when the sample and observation period are stated.
Decode failures from AppSense event logs
AppSense event logs can show whether a deployment or personalisation action was detected, attempted, denied or failed. Community members have documented common patterns in the failed action decoding guide, which is useful when the visible symptom is simply “the browser is wrong”. Correlate the event time with the client, user and AppSense action rather than reading one red status in isolation.
Common causes include a package path that no longer exists, an update running while files are locked, a script expecting elevation, a proxy rejecting the download, or a condition that identifies the old browser. Check the Edge version and executable first, then compare the action log with Windows application and system event logs. Test the same command manually with the same account and architecture to separate endpoint failure from server-side delivery failure.
Make one controlled change at a time: correct the app definition, rerun the action, and verify both the task result and the resulting Edge policy. Do not clear profiles or caches until the logs show where the sequence broke, since that can erase useful context and trigger another first-run state. Capture a sanitised event excerpt in the change record so the next administrator can repeat the diagnosis.
Govern the rollout and activate the support path
A controlled Chromium migration should have named owners for engineering, service desk, security and change approval. Track the pilot measures defined earlier, review Edge-related incidents at agreed intervals and record risk acceptance for any business that must retain EdgeHTML temporarily. The change should fit the organisation’s ASD Essential Eight obligations, particularly for application control, patching, vulnerability management and user-access controls, without treating migration as a one-off technical task.
Review the data used by UEM as part of governance. If rules rely on location, role, device ownership or application telemetry, document the purpose, retention and access controls in line with the Australian Privacy Act and Australian Privacy Principles where they apply. Give employees a clear explanation of the change and a practical route to report a wrong browser configuration. That is especially important for BYOD and contractor devices excluded from corporate management.
Start the Chromium Edge pilot today: choose representative AppSense personas, publish the acceptance criteria, and record every deployment result and policy check in the cutover log. Use the AppSense Exchange forums to compare edge cases with other Australian administrators, then move to the next ring only after the support desk can explain the new browser behaviour. Make each successful cohort the tested template for the next new hire or re-provisioned device.