Failed to deploy Anthropic Claude Opus 4.7 in Azure Foundry even after quota approval. Error: ModelProviderData is required

Hello ASHIQ HUSSAIN,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are unable to deploy Anthropic Claude Opus 4.7 in Azure Foundry even after quota approval. Error: ModelProviderData is required.

Your deployment is failing after ARM validation, during Azure Marketplace SaaS fulfillment for Anthropic (Claude) in Microsoft Foundry not because of your template/CLI syntax, RBAC, quota, region selection, or provider registration. The signal is that no Microsoft.SaaS resource is ever created, which indicates the Marketplace fulfillment workflow never completes the publisher-side organization provisioning step. - https://learn.microsoft.com/en-us/azure/foundry/foundry-models/how-to/use-foundry-models-claude, and https://learn.microsoft.com/en-us/troubleshoot/azure/partner-solutions/marketplace-purchases-errors

What I verified that could be the causes are: (a) the subscription is not eligible for Claude partner model purchase/deployment (for example CSP, sponsored/credit-based, or other restricted subscription/payment setups), or (b) a stuck/corrupted Marketplace fulfillment state that requires Microsoft Marketplace engineering to reset/repair. - https://learn.microsoft.com/en-us/azure/foundry/foundry-models/how-to/use-foundry-models-claude, https://learn.microsoft.com/en-us/marketplace/purchase-validation-checks, and https://learn.microsoft.com/en-us/troubleshoot/azure/partner-solutions/marketplace-purchases-errors give more insight.

If you’re on a subscription type that’s restricted for Claude partner models, move the deployment to a paid, eligible subscription with a valid payment method and Marketplace purchasing enabled. For an example, If using standard MCA Pay-As-You-Go move deployment to:

• Enterprise subscription OR
• MCA-E eligible subscription

If you’re already on an eligible subscription as above, the fix is backend-side open an Azure support ticket and request escalation to Marketplace fulfillment engineering via your Portal. Because further client-side retries will continue to fail until fulfillment state is corrected. The https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/enable-marketplace-purchases, and https://learn.microsoft.com/en-us/troubleshoot/azure/partner-solutions/marketplace-purchases-errors serve as a reference.

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.