Policy evaluation failure (InvalidResourceProperties) when deploying GPT-4.1-mini and other models in specific regions

1. The error pattern is consistent with a policy-definition mismatch rather than the model name/version itself being invalid. The troubleshooting guidance for built‑in model‑deployment policies shows that:
   • Policy failures of this kind typically occur when the policy’s expected resource properties or parameter values (for example, model asset IDs, publisher names, or parameter keys) do not match the actual model asset being deployed.
   • For model‑deployment policies, asset IDs and publisher names must match exactly and are case‑sensitive, and parameter names must match the policy definition (allowedPublishers, allowedAssetIds).
   • If a policy is written or parameterized against an older set of models, newer models such as gpt-4.1-mini/2025-04-14 can be blocked until the policy parameters are updated.
   From the available guidance, this is the expected behavior when the policy definition or its parameters are out of sync with the current model catalog, rather than a problem with the Azure OpenAI service itself. The recommended actions are:
   • Verify the policy assignment is using the correct parameter names and values by inspecting the definition (for example, via az policy definition show --name "<definition-id>").
   • Ensure the allowed model asset IDs and publishers in the policy match the current model entries from the model catalog.
   • Confirm the policy effect is Deny only where intended; otherwise use Audit while updating the allowed list.
2. For regional availability of gpt-4.1-mini/2025-04-14 on Standard deployments, the model‑summary tables show:
   • Standard (regional) deployments: gpt-4.1-mini/2025-04-14 is not listed as available in the Standard deployment table excerpt provided. That table lists Standard availability for several models (including gpt-4.1, o4-mini, gpt-4o, gpt-4, gpt-35-turbo, etc.) but does not mark gpt-4.1-mini as available in the shown regions.
   • Chat completions / regional model availability: In the chat‑completions regional table, gpt-4.1-mini/2025-04-14 is shown as available (✔) in multiple regions such as germanywestcentral, japaneast, koreacentral, northcentralus, norwayeast, polandcentral, southafricanorth, southcentralus, southindia, swedencentral, switzerlandnorth, and uksouth.
   • Data zone provisioned managed: In the data‑zone provisioned managed table, gpt-4.1-mini/2025-04-14 is also shown as available (✔) in regions including eastus, eastus2, francecentral, germanywestcentral, northcentralus, polandcentral, southcentralus, swedencentral, westeurope, westus, and westus3.
   Based on these tables, gpt-4.1-mini/2025-04-14 is available in many regions for chat completions and data‑zone provisioned managed deployments, but it is not listed as available for Standard SKU deployments in the Standard deployment table excerpt. This explains why deployments may succeed in some configurations/regions and fail in others where Standard SKU is not supported for that model. For IaC templates targeting multiple regions and SKUs, the deployment logic needs to align with the model‑summary tables:
   • Only deploy gpt-4.1-mini/2025-04-14 as Standard where the Standard table explicitly lists it (none of the shown Standard rows do), or
   • Use the supported deployment types (for example, data‑zone provisioned managed or chat completions) in the regions where gpt-4.1-mini is marked as available.

References:

• Azure OpenAI in Azure AI Foundry Models
• Built-in policy for model deployment in Microsoft Foundry portal
• Control AI model deployment with built-in policies in Microsoft Foundry portal (classic)
• Azure OpenAI On Your Data
• Azure Deployment Takes 70 Minutes to Fail with Obscure Error - Microsoft Q&A
• Deployed Claude and getting API deployment resource is not ready even though it has been an hour - Microsoft Q&A
• Microsoft Foundry publish to Teams Bot service error - Microsoft Q&A
• How do I work around this Exchange Online Rule error? - Microsoft Q&A
• Azure Local - Failover Cluster Validation undocumented warning - Microsoft Q&A