AI Foundry Microsoft-Decision-1 listed as available in all regions, but can't deploy

Deploy Microsoft-Decision-1 in West US using DataZoneStandard; the model-specific matrix explicitly marks westus as supported for that deployment type, while availability still depends on the selected SKU and your subscription quota.^1^

Deploy in West US

In the Foundry portal:

1. Open your West US project.
2. Select Model catalog.
3. Open Microsoft-Decision-1 and select Deploy.
4. For Deployment type, select Data Zone Standard.
5. Complete the deployment.

Microsoft’s model page identifies the supported types as DataZoneStandard in selected regions and GlobalStandard; its documented portal workflow is Project → Model catalog → Microsoft-Decision-1 → Deploy.^2^

Alternatively, create the West US deployment through Azure CLI:

az cognitiveservices account deployment create \
  --name <ACCOUNT_NAME> \
  --resource-group <RESOURCE_GROUP> \
  --deployment-name <DEPLOYMENT_NAME> \
  --model-name "Microsoft-Decision-1" \
  --model-format Microsoft \
  --model-version "1" \
  --sku-name DataZoneStandard \
  --sku-capacity 1

This keeps inference processing within the US data zone. If that locality is unnecessary, GlobalStandard is the broader-routing alternative documented for this model.^2^

If Data Zone Standard still fails

Check what is deployable for the same subscription, because the general Foundry region list only says that a Foundry project can exist in West US; it is not a real-time guarantee for every model and deployment type.^3^

1. In the Foundry portal, open Manage → Quota.
2. Turn on Show all.
3. Locate:
   • Model: Microsoft-Decision-1
   • Version: 1
   • Deployment type: Data Zone Standard
4. Check the Scope and available quota:
   • Data Zone means subscription-level quota within that data zone.
   • A region such as West US means quota is managed per region.
5. If available quota is zero or fully allocated, move unused quota from another deployment or submit a quota-increase request.

Microsoft-Decision-1 has separate RPM limits for Global Standard and Data Zone Standard based on subscription tier; a deployment cannot be created without usable quota.^4^

Also confirm the account has permission to create model deployments. The documented prerequisite is Cognitive Services Contributor or equivalent deployment-management permission.^2^

If the portal and CLI both reject it

Capture the complete deployment error, including:

• error code and message;
• deployment type/SKU;
• model version;
• subscription type;
• correlation or operation ID;
• timestamp and resource region.

If the quota page shows nonzero Microsoft-Decision-1 Data Zone quota and the CLI still reports that version 1 is unavailable in westus, open an Azure support request. That combination conflicts with the current model-specific matrix and needs subscription/resource-side investigation rather than moving the existing project blindly.

References

1. Region availability for Foundry Models sold by Azure (standard)
2. Deploy and use Microsoft-Decision-1 in Microsoft Foundry
3. Microsoft Foundry feature availability across cloud regions
4. Microsoft Foundry Models quotas and limits