📣 Help shape Firefox by joining our Test Days event on July 21–Aug 1 to test the Firefox Semantic History Search in Firefox Beta 142

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Fully disable Pocket to alleviate DNS requests

  • 3 replies
  • 2 have this problem
  • 96 views
  • Last reply by cor-el

We are working on implementing Firefox for Enterprise and rolling it out through Intune/Company Portal, one challenge we are encountering is that we have disabled Pocket as thoroughly as we can (followed the guide from Mozilla https://support.mozilla.org/en-US/kb/disable-or-re-enable-pocket-for-firefox) and we are still seeing requests go out to "img-getpocket.cdn.mozilla.net" we do not want Pocket available at all, we do not want queries made to those domains, is it not possible to completely eradicate Pocket?

It wouldn't be a problem but our AV solution (MDE) has a popup every time the URL is queried and blocked.

Attached image of our configuration profile for Pocket.

We are working on implementing Firefox for Enterprise and rolling it out through Intune/Company Portal, one challenge we are encountering is that we have disabled Pocket as thoroughly as we can (followed the guide from Mozilla https://support.mozilla.org/en-US/kb/disable-or-re-enable-pocket-for-firefox) and we are still seeing requests go out to "img-getpocket.cdn.mozilla.net" we do not want Pocket available at all, we do not want queries made to those domains, is it not possible to ''completely'' eradicate Pocket? It wouldn't be a problem but our AV solution (MDE) has a popup every time the URL is queried and blocked. Attached image of our configuration profile for Pocket.
Attached screenshots

Chosen solution

Note that there are DisablePocket and FirefoxHome policies.

Read this answer in context 👍 0

All Replies (3)

You can remove the Pocket section from the new tab page with the "FirefoxHome" enterprise policy or by changing browser.newtabpage.activity-stream.feeds.section.topstories to false in about:config.

Chosen Solution

Note that there are DisablePocket and FirefoxHome policies.

Moving thread to Firefox for Enterprise.