Overview
Same idea as the other Azure guide: deploy the model, then give Loom the resource name, a key and the deployment name. This one uses Anthropic’s Messages format through your Foundry resource.
Get a key
- 1In the Azure portal, open your Microsoft Foundry resource.
- 2In the Foundry portal choose Discover → Models, search for Claude, then Deploy → Custom settings. Where it offers a choice, pick Global scope.
- 3Choose the deployment name carefully: it cannot be changed after creation.
- 4Copy a key from the resource’s Keys and Endpoint page. Your resource name is the part before
.services.ai.azure.com.
Cost. Billed through your Azure subscription. Which Claude models are offered on Azure varies, so check the model catalog.
Add it to Loom
- 1Open Loom, then Providers in the menu, and choose Add provider.
- 2Pick Claude on Azure Foundry (the search box finds it).
- 3Fill in the fields in the table below.
- 4Choose Connect. Loom checks the key and says how many models it found. If it cannot check, it says so, and you can Save anyway and try a message.
- 5Open the model chip below the message box and pick a model.
- Resource name: only the name.
- Deployment names: comma-separated; the first is the default.
| Field in Loom | What to put | Needed |
|---|---|---|
| API key | Paste the key you copied. In the Foundry portal open your resource → Keys and Endpoint. | Yes |
| Resource name | my-resource The first part of your endpoint: https://my-resource.services.ai.azure.com | Yes |
| Deployment names | claude-sonnet-4-6 The names you gave your Claude deployments. Separate several with commas. | Yes |
| Endpoint | https://{resource}.services.ai.azure.com/anthropicfilled in from the fields above | Pre-filled |
| Name | Anything you like. It is shown in the model picker | Optional |
At a glance
| Appears in Loom as | Claude on Azure Foundry |
| Sign-in | Your key, sent in the x-api-key header (set automatically) |
| Models | You type or pick model names; this service has no list call Loom can use |
| Tools (connectors, search) | Yes |
| Photos | Yes |
| PDFs | Yes |
If something goes wrong
| What you see | What to do |
|---|---|
| 404 or “model not found” | The deployment name is not exact, or the model is not deployed in that resource. |
| 401 | Wrong key, or a key from another resource. |