{"version":"2.1.317","anchor":"foundry-errors-attributed-to-azure","canonical_anchor":"foundry-errors-attributed-to-azure","heading":"Errors from Microsoft Foundry are now attributed to Azure","tier":"notice","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/foundry-errors-attributed-to-azure","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Errors from Microsoft Foundry are now attributed to Azure\n\nWith CLAUDE_CODE_USE_FOUNDRY set, recognised errors are now attributed to Azure, as errors were already attributed to AWS or Google Cloud\n\n**What**\n\nWhen `CLAUDE_CODE_USE_FOUNDRY` is set and an error matches one of a known set of error types, Claude Code now names Azure as the provider the error came from. This environment variable makes Claude Code use Microsoft Foundry for model access. Errors could already be attributed to AWS or Google Cloud; before this change, there was no Azure attribution.\n\n**Why**\n\nIf you use Foundry, errors are now traced to the right provider.\n\n- Area: Elsewhere\n- Names: `CLAUDE_CODE_USE_FOUNDRY`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}