Override Related Website Sets. (deprecated)
Supported on: Microsoft Edge version 121, Windows 7 or later
Registry
Software\Policies\Microsoft\Edge Software\Policies\Microsoft\Edge Options
RelatedWebsiteSetsOverrides text Description
DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. This policy provides a way to override the list of sets Microsoft Edge uses for Related Website Sets Each set in the browser's list of Related Website Sets must meet the requirements of a Related Website Set. A Related Website Set must contain a primary site and one or more member sites. A set can also contain a list of service sites that it owns, and a map from a site to all its ccTLD variants. For more information on how Microsoft Edge uses Related Website Sets, see https://github.com/WICG/first-party-sets. All sites in a Related Website Set must be a registrable domain served over HTTPS. Each site in a Related Website Set must also be unique, which means a site can't be listed more than once in a Related Website Set. When this policy is given an empty dictionary, Microsoft Edge uses the public list of Related Website Sets. For all sites in a Related Website Set from the replacements list, if a site is also present on a Related Website Set in the browser's list, then that site will be removed from the browser's Related Website Set. After this step, the policy's Related Website Set is added to the Microsoft Edge's list of Related Website Sets. For all sites in a Related Website Set from the additions list, if a site is also present on a Related Website Set in Microsoft Edge's list, then the browser's Related Website Set is updated so that the new Related Website Set can be added to the browser's list. After the browser's list has been updated, the policy's Related Website Set is added to the browser's list of Related Website Sets. The browser's list of Related Website Sets requires that for all sites in its list, no site is in more than one set. This requirement is also required for both the replacements list and the additions list. Similarly, a site can't be in both the replacements list and the additions list. Wildcards (*) aren't supported as a policy value, or as a value within any Related Website Set in these lists. This policy is deprecated as of Microsoft Edge version 144 with the deprecation of Related Website Sets. Example value: { "additions": [ { "associatedSites": [ "https://associate2.test" ], "ccTLDs": { "https://associate2.test": [ "https://associate2.com" ] }, "primary": "https://primary2.test", "serviceSites": [ "https://associate2-content.test" ] } ], "replacements": [ { "associatedSites": [ "https://associate1.test" ], "ccTLDs": { "https://associate1.test": [ "https://associate1.co.uk" ] }, "primary": "https://primary1.test", "serviceSites": [ "https://associate1-content.test" ] } ] } Compact example value: {"additions": [{"associatedSites": ["https://associate2.test"], "ccTLDs": {"https://associate2.test": ["https://associate2.com"]}, "primary": "https://primary2.test", "serviceSites": ["https://associate2-content.test"]}], "replacements": [{"associatedSites": ["https://associate1.test"], "ccTLDs": {"https://associate1.test": ["https://associate1.co.uk"]}, "primary": "https://primary1.test", "serviceSites": ["https://associate1-content.test"]}]}