# Atlas error: AZURE_RESOURCE_NAME is missing > Export AZURE_RESOURCE_NAME in the shell that launches Atlas, or set an explicit baseURL on the azure provider entry in atlas.json, which bypasses the check. Atlas throws "AZURE_RESOURCE_NAME is missing, set it using env var or reconnecting the azure provider and setting it" because the azure provider loader found neither a resource name nor an explicit baseURL, and the fix is to export AZURE_RESOURCE_NAME in the shell that launches Atlas. You can also re-run atlas auth login for azure and supply the resource name when prompted, or set an explicit baseURL on the azure provider entry in atlas.json, which bypasses the check entirely. ## Symptom Selecting an Azure model throws: AZURE_RESOURCE_NAME is missing, set it using env var or reconnecting the azure provider and setting it. ## Cause The azure provider loader in Atlas checks for a resource name or an explicit baseURL. With neither present, it returns a provider whose getModel throws that message, so the failure appears the first time you use the Azure model rather than at Atlas startup. ## Fix 1. Export AZURE_RESOURCE_NAME in the shell that launches Atlas, so the azure provider loader can read it from the environment. 2. Or re-run `atlas auth login` for azure and supply the resource name when prompted. 3. Or set an explicit `baseURL` on the azure provider entry in atlas.json, which bypasses the resource-name check. 4. Restart Atlas and re-select the Azure model, so the provider loader re-reads the environment and the config. ## Why does Atlas say AZURE_RESOURCE_NAME is missing Atlas says "AZURE_RESOURCE_NAME is missing" because the azure provider loader checks for 2 things, a resource name or an explicit baseURL, and found neither. With both absent, the loader returns a provider whose getModel throws that exact message the moment you select an Azure model. Atlas needs one of two things to address an Azure deployment: the resource name, or a baseURL that already encodes where to send the request. The azure provider loader accepts either. When you have configured neither, the loader does not fail loudly at that moment. It hands back a provider object that is fine to exist but cannot produce a model, and the error surfaces at getModel. That design is worth knowing because it explains the timing of the failure, which is the thing most people find confusing about this error. ## Why the error appears when I select the model, not at startup The AZURE_RESOURCE_NAME error appears when you first select an Azure model rather than at Atlas startup because the azure provider loader defers the failure. In 2026 the loader returns a provider whose getModel throws, so Atlas starts cleanly and the missing resource name only bites at first use. Atlas loads providers without demanding that every one of them be fully configured, which is what lets you run Atlas with a dozen providers registered and credentials for two of them. The azure loader participates in that contract: no resource name and no baseURL means the provider still loads, but its getModel throws. So a session can look completely healthy until the moment you switch to Azure. If you were expecting a startup warning and did not get one, nothing is wrong with your installation. That is the intended behavior of the azure provider loader in Atlas. ## How to fix AZURE_RESOURCE_NAME is missing in Atlas Fix "AZURE_RESOURCE_NAME is missing" in Atlas by exporting AZURE_RESOURCE_NAME in the shell that launches Atlas. 2 alternatives work equally well: re-run atlas auth login for azure and supply the resource name when prompted, or set an explicit baseURL on the azure provider entry in atlas.json. Pick the path that matches how you manage configuration. Exporting AZURE_RESOURCE_NAME is the fastest and is right for a local shell or a dotfile. Running `atlas auth login` for azure and entering the resource name when prompted stores it with the rest of the azure provider connection, which is the better fit if you already manage credentials through Atlas auth. Setting an explicit `baseURL` on the azure provider entry in atlas.json is the option for teams that already point at a specific endpoint, and it bypasses the resource-name check outright rather than satisfying it. All three clear the error. Only pick one, so the source of truth stays obvious. ## How to verify the AZURE_RESOURCE_NAME fix worked Verify the AZURE_RESOURCE_NAME fix in Atlas by restarting Atlas and re-selecting the Azure model. The azure provider loader reads its 2 sources, the environment and atlas.json, only at startup, so a shell export made after Atlas launched will not be visible until you restart. Restart matters here more than in most fixes. If you exported AZURE_RESOURCE_NAME into a shell that Atlas is not running in, or exported it after Atlas started, the loader never sees it and the error repeats identically, which looks like the fix failed when it simply was not applied. After restarting, select the Azure model and send a message. A completion, with no "AZURE_RESOURCE_NAME is missing" thrown at getModel, confirms the azure provider now resolves a resource name or a baseURL. Atlas lets you switch the active model and provider on the fly with favorites and recents, so the confirmation takes one switch. ## FAQ ### How do I set AZURE_RESOURCE_NAME for Atlas Export AZURE_RESOURCE_NAME in the shell that launches Atlas, then restart Atlas so the azure provider loader re-reads the environment. Re-select the Azure model afterwards. ### Why does Atlas only throw AZURE_RESOURCE_NAME is missing when I pick an Azure model The azure provider loader returns a provider whose getModel throws when it finds neither a resource name nor an explicit baseURL. The failure therefore appears at first use rather than at Atlas startup. ### Can I use a baseURL instead of AZURE_RESOURCE_NAME in Atlas Yes. Set an explicit baseURL on the azure provider entry in atlas.json. The azure provider loader accepts a resource name or an explicit baseURL, so a baseURL bypasses the resource-name check. ### Does atlas auth login fix AZURE_RESOURCE_NAME is missing Yes. Re-run `atlas auth login` for azure and supply the resource name when prompted. That reconnects the azure provider with the resource name it needs. ### I exported AZURE_RESOURCE_NAME and Atlas still throws the error Restart Atlas and re-select the Azure model. The azure provider loader reads the environment at load time, so an export made after Atlas started, or in a different shell, is invisible to it. ### Is AZURE_RESOURCE_NAME an Atlas setting or an Azure one AZURE_RESOURCE_NAME is the environment variable the Atlas azure provider loader reads to address your Azure deployment. Atlas accepts it from the env, from atlas auth, or bypasses it with an explicit baseURL. --- Canonical HTML: https://runatlas.sh/resources/troubleshooting/azure-resource-name-missing Source of truth: aeo_pages row `/resources/troubleshooting/azure-resource-name-missing` (segment: Troubleshooting) (this file is generated from it, never hand-edited). Licence: Atlas is proprietary with a free core. It is not open source and there is no public source repository.