Edit

Share via

OriginAgentClusterDefaultEnabled

Origin-keyed agent clustering enabled by default

Supported versions

  • On Windows and macOS since 103 or later

Description

The Origin-Agent-Cluster: HTTP header controls whether a document is isolated in an origin-keyed agent cluster or in a site-keyed agent cluster. This has security implications because an origin-keyed agent cluster allows isolating documents by origin. The consequence of this for developers is that the document.___domain accessor can no longer be set when origin-keyed agent clustering is enabled.

If you enable or don't configure this policy, documents without the Origin-Agent-Cluster: header will be assigned to origin-keyed agent clustering by default. On these documents, the document.___domain accessor will not be settable.

If you disable this policy, documents without the Origin-Agent-Cluster: header will be assigned to site-keyed agent clusters by default. On these documents, the document.___domain accessor will be settable.

See https://go.microsoft.com/fwlink/?linkid=2191896 for additional details.

Supported features

  • Can be mandatory: Yes
  • Can be recommended: No
  • Dynamic Policy Refresh: Yes
  • Per Profile: Yes
  • Applies to a profile that is signed in with a Microsoft account: No

Data type

  • Boolean

Windows information and settings

Group Policy (ADMX) info

  • GP unique name: OriginAgentClusterDefaultEnabled
  • GP name: Origin-keyed agent clustering enabled by default
  • GP path (Mandatory): Administrative Templates/Microsoft Edge
  • GP path (Recommended): N/A
  • GP ADMX file name: MSEdge.admx

Example value

Disabled

Registry settings

  • Path (Mandatory): SOFTWARE\Policies\Microsoft\Edge
  • Path (Recommended): N/A
  • Value name: OriginAgentClusterDefaultEnabled
  • Value type: REG_DWORD

Example registry value

0x00000000

Mac information and settings

  • Preference Key name: OriginAgentClusterDefaultEnabled
  • Example value:
<false/>

See also