Fix Azure Marketplace Validation Errors

Learn how to troubleshoot and fix common validation errors when publishing on Azure Marketplace to ensure a smooth submission process.

Sarvagya Pandey

Marketing Specialist

Publishing on Azure Marketplace can be tricky. Validation errors might block your offer from going live, but the good news is, most errors are fixable. Here's a quick guide to help you troubleshoot and resolve common issues:

Common Validation Errors and Fixes:

Publisher and Offer ID Issues: Double-check your IDs and ensure your offer is active.
Legal Terms Problems: Accept required agreements and verify your EULA and privacy policy.
Payment Method Errors: Update your billing details and ensure pricing matches regional settings.
Region Access Limits: Confirm service availability in your selected regions and adjust deployment settings.
Private Offer Setup Issues: Correct private store IDs and visibility settings.

Pre-Submission Checklist:

Set up billing accounts correctly.
Assign proper marketplace roles.
Complete legal requirements.
Verify regional settings and private marketplace rules.

Tools You Can Use:

Azure Activity Log: Find failed validations and review detailed error messages.
ARM Template Test Toolkit: Check for outdated configurations.
WeTransact Validation Tools: Automate compliance checks and error detection.

Quick Comparison of Common Errors and Solutions:

Error Type	Cause	Solution
Publisher/Offer ID Issues	Incorrect or inactive IDs	Verify and update Publisher and Offer IDs.
Legal Terms Problems	Missing/incorrect agreements	Accept agreements and ensure all legal docs are complete.
Payment Method Errors	Invalid billing or pricing setup	Update payment methods and ensure currency settings match.
Region Access Error	Service unavailable in selected regions	Adjust region settings and confirm resource availability.
Private Offer Setup Issues	Misconfigured private store settings	Fix visibility settings and private marketplace configurations.

Start by addressing errors in the Azure Activity Log and use tools like Partner Center Tests or WeTransact to validate your offer before submission. Following these steps ensures a smoother path to publishing your application on Azure Marketplace.

Building Apps and Services for Azure Marketplace and AppSource : Build 2018

Azure Marketplace

Main Types of Validation Errors

Navigating the Azure Marketplace certification process can be challenging, especially when validation errors crop up. Below, we break down common error categories and their causes to help you address them effectively. Each category has specific solutions, which are explored in detail in later sections.

Publisher and Offer ID Issues

One frequent stumbling block involves Publisher and Offer ID errors. These occur when your offer isn't recognized or there are conflicts in identification details. Here's an example of such an error:

"Offer with PublisherId: 'PUBLISHER', OfferId: 'OFFER' cannot be purchased due to validation errors. For more information see details." ^[2]

These errors typically stem from:

Recently created offers that haven't fully propagated through Azure's system
Errors in entering Publisher or Offer IDs
Offers that have been removed or revoked from the marketplace
Misconfigured private marketplace settings

Legal Terms Problems

Legal terms errors pop up when required agreements are not accepted, or when your documentation is incomplete or improperly formatted. The system checks for several key elements:

Acceptance of the standard marketplace agreement
Proper formatting of custom terms and conditions
Compliance with privacy policy requirements
Complete and accurate End-User License Agreement (EULA) documentation

Payment Method Errors

Issues related to payment methods are another common hurdle. These errors often result from:

Missing or incorrect payment details
Currency settings that don't match the configuration
Errors in pricing tier setups

Region Access Limits

Regional validation errors can restrict your offer's availability, creating significant challenges. For example:

"The requested size for resource '<resource ID>' is currently not available in location '<location>' zones '<zones>' for subscription '<subscription ID>'. Please try another size or deploy to a different location or zones." ^[4]

These errors are usually linked to:

Subscription quota restrictions
Limited resource availability in specific regions
Deployment restrictions for certain services
Inaccessibility of certain virtual machine SKUs in specific zones

Private Offer Setup Issues

Private offer configuration errors can cause problems when setting up offers for specific customers or groups. These issues often include:

Mismatched private store IDs
Incorrect visibility settings for the offer
Errors in programmatic deployment configurations
Invalid assignments for customer tenants

To minimize these errors, ensure your private marketplace settings meet Microsoft's guidelines for deployment and customer access. Regularly reviewing and validating your private offer configurations can help identify and resolve potential issues before they disrupt your certification process.

Pre-Submission Checks

Before submitting your offer to Azure Marketplace, it's crucial to address potential validation issues. Here's a checklist to guide you through the process:

Check Billing Account Setup

Your billing configuration directly impacts marketplace transactions:

For MCA accounts:
- Navigate to Cost Management + Billing in the Azure portal.
- Select your billing profile and enable the Azure Marketplace policy.
For EA accounts:
- Open Cost Management + Billing in the Azure portal.
- Enable the Azure Marketplace policy at the billing account level.
- Ensure Enterprise Administrator permissions are properly assigned.

Check Marketplace Access Rights

The right role assignments are essential for smooth marketplace operations. Here's a quick breakdown:

Offer Type	Required Roles
Public Offers	Subscription Owner or Contributor
Private Plans	Subscription Owner or Contributor
Private Offers (MCA)	Billing Account Owner/Contributor + Subscription Owner/Contributor
Private Offers (EA)	Enterprise Administrator + Subscription Owner/Contributor

Complete Legal Requirements

To meet legal obligations, confirm the following:

Acceptance of the standard marketplace agreement.
Alignment of your privacy policy with Azure requirements.
Completion of all necessary EULA documentation.
Adherence to Microsoft guidelines for any custom terms.

Check Region Settings

Azure Marketplace spans 141 regions ^[5]. Make sure to:

Select the target market locations (up to 141 regions).
Confirm the availability of required Azure services in those regions.
Review data residency requirements for compliance.
Verify local currency and pricing settings.

Set Private Marketplace Rules

To manage private offers effectively, follow these steps:

Assign the Marketplace Admin Role
- A Global Administrator must assign this role.
- The Marketplace Admin can oversee private offers, visibility, and access controls.
Configure Visibility Settings
- Define customer segments.
- Set tenant-specific access.
- Apply subscription restrictions as needed.

Once these checks are complete, address any errors that may arise during submission to ensure a smooth process.

Error Resolution Steps

The steps below are designed to address specific validation errors encountered during submission, offering clear methods to troubleshoot and resolve issues effectively.

Find Errors in Activity Log

The Azure Activity Log is a valuable tool for pinpointing validation errors. Here's how to use it:

Log in to the Azure portal and go to the Activity Log section.
Apply a filter where the "Operation Name" is set to Validate.
Look for entries marked with a red exclamation mark, indicating failed validations.
Open the failed entry and review the JSON tab.
Pay close attention to the statusMessage field for detailed error descriptions.

Fix Payment Settings

Once you've identified the errors, the next step is to address any payment-related issues:

Update Credit Card Information
In the Partner Center, navigate to Membership > Membership offers:
- Select your offer and click Buy Now.
- Choose the Pay by Microsoft Billing Profile option.
- Update your payment method during the Azure portal checkout process.
Configure Payout Profiles
Go to the Account settings section in Partner Center and follow these steps:
- Access the Payout and tax section.
- Select Payout and tax profile assignment.
- Assign the appropriate tax profile and payment method.
- Submit the changes for verification.

Accept Terms via Command Line

After verifying payment settings, you can streamline the agreement process using the command line:

az marketplace terms accept --publisher "<publisher-id>" --product "<product-id>" --plan "<plan-id>" --debug

Update Subscription Settings

Ensure your subscription settings meet the necessary requirements by verifying the following configurations:

Setting Type	Required Configuration
Marketplace Access	Enabled for the subscription
Purchase Policy	Allow marketplace purchases
Private Plans	Adjust visibility settings
Payment Methods	Attach a valid payment method

Fix Regional Settings

Regional settings can sometimes cause validation issues. Here's how to address them:

Market Availability
- Confirm that language settings align with the target markets.
- Verify pricing availability and compliance for the selected regions.
- Ensure Microsoft AppSource is accessible in the relevant markets. It supports 40 languages across 60 markets.
Regional Display
In the Partner Center Marketplace listings:
- Configure content tailored to specific markets.
- Check that currency and pricing are accurate for each region.

"Log into portal.azure.com. Open the Activity Log. Find the record with Operation Name of Validate in the list of activities. It should have a red exclamation mark because it failed. Click on that record. Then click on the JSON tab at the bottom. Review the returned JSON for any error details in the statusMessage."

sbb-itb-cd24f9b

Validation Tools Guide

Azure Marketplace provides a range of tools to help you validate and address offer issues before certification. Once you've resolved any errors, these tools can also help you prevent future validation problems.

ARM Template Checks

The ARM Template Test Toolkit is designed to ensure your technical configurations meet the required standards. To run the checks, use the following PowerShell command:

Test-AzTemplate -TemplatePath <path-to-template>

This toolkit identifies critical issues, such as outdated API versions (which must be no older than 730 days) and resource configurations that don’t align with compliance standards.

Partner Center Tests

Partner Center

The Partner Center offers a series of validation tests to ensure your offer meets infrastructure, content, and security requirements. Here's a breakdown:

Test Type	Purpose	Key Checks
Technical Validation	Infrastructure compliance	Resource deployments, API endpoints
Content Review	Marketplace listing quality	Descriptions, screenshots, support info
Security Scan	Security requirements	Vulnerability assessments, compliance

Before submitting your offer, confirm that all sections display a "Complete" status. Be sure to include clear testing instructions. For enhanced testing, WeTransact provides real-time reporting capabilities to streamline this process.

WeTransact Validation Tools

WeTransact

WeTransact tools simplify the validation process with features like:

Automated compliance checks
Real-time error detection
Actionable validation reports

These tools make it easier to identify and address potential issues quickly.

SaaS API Testing

When preparing a SaaS offer, thorough API testing is essential. Key areas to focus on include:

Endpoint Validation: Use Microsoft's test harness to ensure SaaS API endpoints function correctly.
Authentication Testing: Confirm that OAuth token handling and API security meet required standards.
Webhook Integration: Test webhook notifications for critical events, such as:
- Purchases
- Cancellations
- Plan updates
- Quantity changes

Post-Submission Steps

After resolving errors and validating your offer during pre-submission, the next step is to focus on monitoring and ensuring ongoing compliance and performance.

Track Status in Partner Center

Keep an eye on your offer's progress through the Overview tab in Partner Center. Here's a quick guide to the different statuses you might encounter:

Status	Description	Required Action
Publish in progress	Your offer is currently under review	Monitor progress
Attention needed	A critical issue was found during certification	Review the certification report
Preview	Certification is complete, awaiting your approval to go live	Select "Go live" to publish
Live	Your offer is now available to customers	Monitor performance

Make sure your email is verified and that the appropriate developer or manager roles are assigned to receive important notifications.

Check Azure Monitor Logs

Azure Monitor Logs can help you identify validation errors effectively. Use queries like these to locate issues:

_LogOperation | where Level == "Error"
_LogOperation | where Level == "Warning"

Set up alerts based on the severity of the issues:

Error-level issues: Check every 5 minutes for immediate action.
Warning-level issues: Review daily for less critical concerns.

These alerts ensure you’re notified of potential problems as soon as they arise.

Contact Microsoft Support

If you encounter issues, gather all relevant details - including certification failure reports and Azure Monitor logs - and contact Microsoft Support based on your support plan:

Developer Plan: Expect a response within one business day.
Standard Plan: Response times range from 1 to 8 hours, depending on the case's urgency.
Professional Direct Plan: Offers faster response times and additional support.
Enterprise Plan: Provides the quickest response and escalation options.

Having detailed documentation ready will help expedite the support process.

Use WeTransact Reports

Leverage WeTransact's validation dashboard for real-time updates on your offer's status. The platform provides automated error detection and compliance tracking, making it easier to stay on top of potential issues. For more complex challenges, their Customer Success team is available to assist.

Conclusion: Quick Reference Guide

Here’s a handy guide to help you tackle Azure Marketplace validation errors:

Error Type	Common Cause	Solution
ResourcePurchaseValidationFailed	Invalid subscription or missing payment	Double-check your subscription type and ensure a valid payment method is added ^[7]
RequestDisallowedByPolicy	Azure policy blocking deployment	Review your Azure policies and adjust any that are blocking the deployment ^[6]
Region Access Error	Deployment to unauthorized region	Confirm tenant permissions and check if the marketplace is available in the region ^[1]
Publisher/Offer Issues	Incorrect IDs or deactivated product	Ensure the Publisher ID and Offer ID are accurate and active ^[3]

To address these issues, take the following steps:

Immediate Actions

Turn on Azure debug logging to track error details.
Use Azure Monitor Logs to run error-level queries and pinpoint issues.
Check the Partner Center certification report for any flagged issues.
Confirm that your billing account is properly set up and that you have the necessary marketplace access rights.

Expert Recommendations

Keep Application Insights active for ongoing monitoring.
Set up automated alerts to notify you of errors or warnings in real time.
Maintain thorough documentation of your deployment configurations.
Use tools like WeTransact’s validation dashboard for real-time compliance monitoring.

FAQs

What should I do if I encounter a validation error while publishing on Azure Marketplace?

If you're facing a validation error while trying to publish on Azure Marketplace, the first step is to double-check your technical setup. Pay close attention to authentication flows, API reliability, and security compliance, as these are frequent trouble spots.

Next, take a thorough look at your offer's metadata. Errors here - like incorrect product descriptions, misconfigured endpoints, or missing required fields - can easily trigger validation issues. Also, make sure your subscription is tied to a valid payment method, as outdated billing details can cause problems.

By focusing on these key areas, you can usually resolve validation errors and move forward with your Azure Marketplace listing without much delay.

How can I correctly set up payment and billing details to avoid validation errors on Azure Marketplace?

To avoid running into payment and billing validation errors on Azure Marketplace, make sure your details are correctly configured:

Update Your Payment Method: Ensure you have a valid credit card with enough funds added or updated in the billing section of the Azure portal.
Review Your Billing Profile: Double-check that all required fields in your billing profile are filled out accurately and completely.
Allow Marketplace Purchases: Confirm that your billing policy settings permit marketplace purchases.
Check Your Subscription Status: Verify that your Azure subscription is active and properly linked to a valid payment method.

If issues continue, take a look at any error codes provided by Azure. These can help pinpoint the exact problem with your payment or billing setup.

How can I check for validation issues before submitting my offer to the Azure Marketplace?

When preparing to submit your offer to the Azure Marketplace, it’s crucial to avoid validation errors. Thankfully, there are tools available that can help identify and fix common problems. For instance, DataBuck uses machine learning to spot and correct data issues, helping ensure your offer aligns with quality requirements. Similarly, the Commercial Marketplace SaaS Accelerator is designed to confirm that your offer is ready for deployment, minimizing the chances of rejection during validation.

Using these tools can simplify the submission process and increase your chances of successfully listing your offer on the Azure Marketplace.