{"version":"2.1.273","anchor":"bedrockvertexfoundrygateway-auth-errors-get-provider-spec","canonical_anchor":"bedrockvertexfoundrygateway-auth-errors-get-provider-spec","heading":"Bedrock\/Vertex\/Foundry\/Gateway auth errors get provider-specific guidance","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/bedrockvertexfoundrygateway-auth-errors-get-provider-spec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Bedrock\/Vertex\/Foundry\/Gateway auth errors get provider-specific guidance\n\nLogin errors from Bedrock, Vertex, Foundry and Gateway now show provider-specific fix-it guidance instead of one generic message\n\n**What**\n\nWhen a request to a model provider fails with an authentication error (401\/403), Claude Code now shows guidance tailored to which provider you're using, instead of one generic error for all of them:\n\n- Amazon Bedrock: including a new check for when a model simply isn't enabled for your account\/region, with instructions to enable it in the Bedrock console\n\n- Google Vertex AI\n\n- Foundry: a new dedicated auth-failure message\n\n- Gateway: a special message for 403 errors\n\n**Why**\n\nAuthentication failures have different causes and fixes depending on which backend you're connecting through, so pointing you at the right console or setting saves time compared to a one-size-fits-all error.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}