{"version":"2.1.283","anchor":"403-compliancezdr-restricted-responses-now-read-as-lane-un","canonical_anchor":"403-compliancezdr-restricted-responses-now-read-as-lane-un","heading":"Compliance-restricted accounts no longer get a misleading sign-in failure","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/403-compliancezdr-restricted-responses-now-read-as-lane-un","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Compliance-restricted accounts no longer get a misleading sign-in failure\n\nAccess refusals caused by compliance or zero-data-retention restrictions are now treated as \"unavailable\" rather than as unauthorised\n\n**Unclear.** Exactly which remote feature this applies to is not known.\n\n**What**\n\nSometimes a remote service refuses a request with a 403, meaning access denied. If the refusal says the resource is restricted for compliance or zero data retention, Claude Code now treats the feature as unavailable because of a compliance restriction. Zero data retention is an arrangement where Anthropic does not keep your data. Before, it treated these refusals as a failed login. Other 403 refusals are still treated as unauthorised. This handling sits alongside directory sync.\n\n**Why**\n\nIf your organisation is compliance-restricted, you should now see a restriction message rather than an authentication failure that points you in the wrong direction.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}