Microsoft Edge: 152.0.4191.137 to 154.0.4258.62

[added: OBSOLETE: This policy is obsolete and doesn't work after Microsoft Edge 152. Starting in Microsoft Edge version 153, this policy is obsolete because the Collections feature was removed. ]List specific services and export targets that users can't access in the Collections feature in Microsoft Edge. This includes displaying additional data from Bing and exporting collections to Microsoft products or external partners. If you enable this policy, services and export targets that match the given list are blocked. If you don't configure this policy, no restrictions on the acceptable services and export targets are enforced. Policy options mapping: * pinterest_suggestions (pinterest_suggestions) = Pinterest suggestions * collections_share (collections_share) = Sharing of Collections * local_pdf (local_pdf) = Save local PDFs in Collections to OneDrive * send_word (send_word) = Send collection to Microsoft Word * send_excel (send_excel) = Send collection to Microsoft Excel * send_onenote (send_onenote) = Send collection to Microsoft OneNote * send_pinterest (send_pinterest) = Send collection to Pinterest Use the preceding information when configuring this policy. Example value: collections_share local_pdf send_word send_excel send_onenote

[added: OBSOLETE: This policy is obsolete and doesn't work after Microsoft Edge 152. Starting in Microsoft Edge version 153, this policy is obsolete because the Collections feature was removed. ]Lets you allow users to access the Collections feature, where they can collect, organize, share, and export content more efficiently and with Office integration. If you enable or don't configure this policy, users can access and use the Collections feature in Microsoft Edge. If you disable this policy, users can't access and use Collections in Microsoft Edge.

[removed: DEPRECATED:][added: OBSOLETE:] This policy is [removed: deprecated. It is currently supported but will become obsolete in a future release.][added: obsolete and doesn't work after Microsoft Edge 152.] This policy lets you control the enablement of the Related Website Sets feature. Related Website Sets (RWS) is a way for an organisation to declare relationships among sites, so that Microsoft Edge allows limited third-party cookie access for specific purposes across those sites. If this policy set to True or unset, the Related Website Sets feature is enabled. If this policy is set to False, the Related Website Sets feature is disabled. This policy is deprecated as of Microsoft Edge version 144 with the deprecation of Related Website Sets.

[removed: DEPRECATED:][added: OBSOLETE:] This policy is [removed: deprecated. It is currently supported but will become obsolete in a future release.][added: obsolete and doesn't work after Microsoft Edge 152.] 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"]}]}