Azure Private Offer ARM模板部署验证失败问题求助

First, let's call out the exact error you're facing for clarity:

{"code":"MarketplacePurchaseEligibilityFailed","details":[{"code":"BadRequest","message":"Offer with PublisherId: 'PUBLISHER', OfferId: 'OFFER' cannot be purchased due to validation errors. For more information see details. Correlation Id: 'ID' Sku 'SKU' of offer 'OFFER' by publisher 'PUBLISHER' is not available to you for deployment per the policy set by your IT Admin."}]}

Since you've already accepted terms via PowerShell, ruled out browser-specific issues, and confirmed your environment has no explicit custom policies, here are targeted troubleshooting steps to resolve this:

• Double-check your PowerShell term acceptance scope
  When you ran Set-AzMarketplaceTerms, ensure you specified the exact subscription (or resource group) you're using for the ARM deployment. It's easy to accidentally accept terms for a different subscription if you have multiple linked to your account. Verify the status with this command:

  Get-AzMarketplaceTerms -Publisher "PUBLISHER" -Product "OFFER" -Name "SKU"
  

  Confirm the Accepted flag is True and the Scope matches your target subscription ID.

• Check for inherited management group policies
  Even if you have no policies set at the subscription or resource group level, policies from a parent management group could be blocking access. Use this command to list all policy assignments affecting your subscription that relate to marketplace restrictions:

  Get-AzPolicyAssignment -Scope "/subscriptions/your-subscription-id" | Where-Object {$_.Properties.PolicyDefinitionId -match "marketplace"}
  

  Look for policies that restrict allowed publishers, offers, or SKUs—these can be inherited from higher levels without you explicitly setting them.

• Verify the private offer's access list with the publisher
  Reach out to the offer's publisher to confirm your Azure subscription ID is explicitly added to the private offer's allowed access list. Typos or delays in setting up access on their end can trigger this "not available" error, even if you've accepted the terms correctly.

• Reset your PowerShell/Azure context
  Local cached credentials or marketplace metadata can sometimes cause mismatches. Reset your session with these commands and try the deployment again:

  Disconnect-AzAccount
  Clear-AzContext
  Connect-AzAccount -Subscription "your-subscription-id"
  

  You can re-run the term acceptance command with the fresh context to eliminate any cached state issues.

• Check subscription-level marketplace restrictions
  In the Azure portal, navigate to your target subscription > Settings > Marketplace. Ensure there are no blocked publishers, offers, or SKUs listed here. Even default restrictions (or inherited ones) could be blocking access to your private offer.

• Escalate to Azure Marketplace support
  If all the above checks come up empty, create a support ticket with Azure and include the correlation ID from your error message. The Marketplace team can directly inspect the eligibility checks for your subscription and the specific private offer, which may reveal hidden issues not visible through standard tools.

内容的提问来源于stack exchange，提问作者moxpox