{"version":"2.1.232","anchor":"an-empty-alloweddomains-list-no-longer-produces-an-empty-egr","canonical_anchor":"an-empty-alloweddomains-list-no-longer-produces-an-empty-egr","heading":"An empty allowedDomains list no longer produces an empty egress allowlist","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/an-empty-alloweddomains-list-no-longer-produces-an-empty-egr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### An empty allowedDomains list no longer produces an empty egress allowlist\n\nAn empty allowedDomains list no longer produces an empty egress allowlist; you get a warning.\n\n**What**\n\nSetting `sandbox.network.allowedDomains` to an empty array in managed policy no longer derives an empty desktop egress allowlist; the derived value is skipped and a warning tells the admin to either remove the key or list the domains.\n\n**Details**\n\n- The derivation of `coworkEgressAllowedHosts` now requires the array to be non-empty. Previously the empty array was passed straight through.\n\n**Evidence**\n\n`coworkEgressAllowedHosts`\n\n- Area: Sandbox\n- Names: `sandbox.network.allowedDomains`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}