Forum Discussion

jaurepo's avatar
jaurepo
Copper Contributor
Sep 07, 2026

Microsoft Edge default browser with Intune

Hello everyone,

I am looking for the best way to configure Microsoft Edge as the default browser for Windows devices managed through Microsoft Intune.

I have reviewed the available Microsoft Edge settings in the Settings Catalog but have not been able to identify a specific setting that configures Edge as the default browser.

Is there a supported and recommended way to enforce Microsoft Edge as the default browser for managed Windows 10/11 devices?

If there are multiple approaches available, I would appreciate recommendations on the preferred method for enterprise environments.

Thank you.

intune
microsoft edge

2 Replies

  • KNRizwanAhmedKhan's avatar
    KNRizwanAhmedKhan
    Tin Contributor
    Oct 08, 2026

    Hi Skandel590​,

    There isn't a dedicated Microsoft Edge setting in Intune's Settings Catalog that directly sets Edge as the default browser. The Microsoft-supported approach is to configure Default App Associations through the Windows ApplicationDefaults CSP, which is then deployed using Microsoft Intune. Microsoft documents that the DefaultAssociationsConfiguration policy is used to define default file type and protocol associations, including web browsers. https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationdefaults

    Recommended Enterprise Approach

    1. On a reference Windows device, configure Microsoft Edge as the default browser.
    2. Export the default app associations XML using:Microsoft recommends using DISM to generate the association file. https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationdefaults
    3. dism /online /export-defaultappassociations:C:\AppAssoc.xml
    4. Edit the XML to include only the required browser associations, for example:<DefaultAssociations>    <Association Identifier=".html" ProgId="MSEdgeHTM" ApplicationName="Microsoft Edge" />    <Association Identifier="https" ProgId="MSEdgeHTM" ApplicationName="Microsoft Edge" />
    5. </DefaultAssociations>
    6.     <Association Identifier="http" ProgId="MSEdgeHTM" ApplicationName="Microsoft Edge" />
    7.     <Association Identifier=".htm" ProgId="MSEdgeHTM" ApplicationName="Microsoft Edge" />
    8. <?xml version="1.0" encoding="UTF-8"?>
    9. Deploy the XML through Intune using:
      • Settings Catalog → Application Defaults → Default Associations Configuration, or
      • A custom OMA-URI policy targeting:
      ./Device/Vendor/MSFT/Policy/Config/ApplicationDefaults/DefaultAssociationsConfiguration
    10. The XML content must be Base64 encoded before deployment. Microsoft states that the policy applies the defined associations at user sign-in and that MDM policies take precedence over Group Policy for this setting. https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationdefaults

    Microsoft References

    • Policy CSP - ApplicationDefaults (DefaultAssociationsConfiguration)
      https://learn.microsoft.com/windows/client-management/mdm/policy-csp-applicationdefaults https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationdefaults
    • Configure Microsoft Edge for Windows with Intune
      https://learn.microsoft.com/intune/app-management/configuration/configure-edge-windows https://learn.microsoft.com/en-us/intune/app-management/configuration/configure-edge-windows

    Recommendation

    For enterprise environments, the Settings Catalog method using Default Associations Configuration is generally the preferred and most manageable approach because it is fully supported, easier to maintain than custom OMA-URI policies, and aligns with Microsoft's recommended management model for Windows default application associations. https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-applicationdefaults

    Hope this helps!