Forum Discussion

finnborg's avatar
finnborg
Copper Contributor
Jul 14, 2026

Edge Block/Add Site Notification - How to Disable with GPO?

Hello,

I haven't been able to find answers anywhere so far to figuring this out.

Currently looking into using GPO for disabling the Block/Allow to send site notifications tabs found in Privacy, search, and services -> Site permissions -> All permissions -> Notifications.

 

 

I have been able to block to turn off notifications for all websites by default and block the "Ask before sending" notification settings in the same menu as mentioned above. I did so by creating a GPO with the following settings:

Computer Configuration -> Policies -> Administrative Templates -> Microsoft Edge -> Content Settings

After navigating to this folder, I opened the "Default Notification Setting" setting. Inside of it I switched it to Enabled and Don't allow any site to show Desktop notifications.

I have already looked at the "Allow notifications on specific sites" and the "Block notifications on specific sites" settings, however these just allow you to add websites that you want to block or allow that the user cannot remove. I have discovered that putting a wildcard "*" into the "Block notifications on specific sites" settings values will not allow the user to add any more sites to the list. However this still leaves the user to add any site they wish to the "Allow notifications from specific sites" setting, which is the main concern considering all sites should have notifications disabled.

Has anyone else had this problem and found a solution or workaround?

This works in Chrome, but Edge has been difficult

Thanks.

edge

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Jul 19, 2026

    DefaultNotificationsSetting is the control for this requirement. Keep it in the mandatory Microsoft Edge template and set BlockNotifications, value 2. You do not need NotificationsBlockedForUrls with a wildcard; that policy is meant for URL-pattern exceptions, while NotificationsAllowedForUrls explicitly creates administrative allow exceptions.

     

    The Add buttons are not a reliable indication of effective permission. Microsoft describes mandatory Edge policies as overriding user preferences, so validate the applied policy rather than the presence of those controls. On a test client, run gpupdate /force, restart Edge, open the Edge policy diagnostics page, and confirm DefaultNotificationsSetting appears with value 2, status OK, and the expected machine scope. Remove any configured NotificationsAllowedForUrls entries, then test a clean site that has no existing permission.

     

    If the policy is absent or ineffective, check the profile type: Microsoft documents that this notification policy does not apply to profiles signed in with a personal Microsoft account.