{"version":"2.1.260","anchor":"managed-settings-now-fail-closed-for-nonessential-services-a","canonical_anchor":"managed-settings-now-fail-closed-for-nonessential-services-a","heading":"Managed settings now fail closed for nonessential-services and deep-link blocking","tier":"notice","area":"Admin Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/managed-settings-now-fail-closed-for-nonessential-services-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Managed settings now fail closed for nonessential-services and deep-link blocking\n\nTwo more managed settings now fail closed if their value can't be verified.\n\nThe `disableNonessentialServices` and `disableDeepLinkRegistration` managed settings now have `failClosedValue: true`, so if the managed-settings value can't be read or verified, the CLI defaults to the safe, blocking behavior instead of leaving the feature open.\n\n- Area: Admin Settings\n- Names: `disableNonessentialServices`, `disableDeepLinkRegistration`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}