AutoLaunchProtocolsFromOrigins
Define a list of external protocols that can be used from listed origins without prompting the user. The origin is the scheme plus the hostname.
The syntax of this policy is exactly the same as the Chrome AutoLaunchProtocolsFromOrigins policy except that you can only use valid origins (not just hostnames).
This also means that you cannot specify a wildcard (*) for all origins.
The schema is:
{ "items": { "properties": { "allowed_origins": { "items": { "type": "string" }, "type": "array" }, "protocol": { "type": "string" } }, "required": ["protocol", "allowed_origins"], "type": "object" }, "type": "array"}Compatibility: Firefox 90, Firefox ESR 78.12
CCK2 Equivalent: N/A
Preferences Affected: N/A
Windows (GPO)
Section titled “Windows (GPO)”Software\Policies\Mozilla\Firefox\AutoLaunchProtocolsFromOrigins (REG_MULTI_SZ) =[ { "protocol": "zoommtg", "allowed_origins": [ "https://somesite.zoom.us" ] }]Windows (Intune)
Section titled “Windows (Intune)”OMA-URI:
./Device/Vendor/MSFT/Policy/Config/Firefox~Policy~firefox/AutoLaunchProtocolsFromOriginsValue (string):
<enabled/><data id="JSON" value='[ { "protocol": "zoommtg", "allowed_origins": [ "https://somesite.zoom.us" ] }]'/>If you are using custom ADMX and ADML administrative templates in Intune, you can use this OMA-URI instead to workaround the limit on the length of strings. Put all of your JSON on one line.
OMA-URI:
./Device/Vendor/MSFT/Policy/Config/Firefox~Policy~firefox/AutoLaunchProtocolsFromOriginsOneLineValue (string):
<enabled/><data id="JSONOneLine" value='[]'/><dict> <key>AutoLaunchProtocolsFromOrigins</key> <array> <dict> <key>protocol</key> <string>zoommtg</string> <key>allowed_origins</key> <array> <string>https://somesite.zoom.us</string> </array> </dict> </array></dict>policies.json
Section titled “policies.json”{ "policies": { "AutoLaunchProtocolsFromOrigins": [ { "protocol": "zoommtg", "allowed_origins": ["https://somesite.zoom.us"] } ] }}