Get error message ajax extended call failed

The ajaxExtended call failed message does not identify the underlying Marketplace problem, so first verify the private offer’s status and purchasing context in Azure portal → Private Offer Management.

Check the transaction state

1. Open Private Offer Management using the same account and directory used for the offer.
2. Locate the offer and verify:
   • Offer status: Accepted or Term Ending
   • Product status: Ready
   • The current date falls between the offer’s start and end dates.
3. If the offer was just accepted, allow 15–60 minutes for the product to become Ready and the purchase action to become available.
4. If its status is still Pending, select View + accept, accept the terms, and then retry the purchase after it becomes ready. Acceptance alone does not complete the purchase or start billing.^1^^2^

Verify tenant, billing account, and subscription

In the portal:

1. Select the account icon and confirm that the active Directory contains the billing account named in the private offer.
2. Reopen the private offer after changing directories.
3. Confirm the selected Azure subscription:
   • Belongs to that billing account.
   • Is eligible for Marketplace purchases.
   • Is not hidden by the portal’s global subscription filter.
4. If the subscription is missing, do not create another subscription solely as a workaround; have the billing or subscription administrator verify its directory, billing-account association, access, and Marketplace eligibility.^1^

Check the purchaser’s role

For most private-offer product types, the account completing Purchase/Subscribe must be an Owner or Contributor on the selected Azure subscription. The role needed to accept the offer is separate:

• Microsoft Customer Agreement (MCA): Billing Account Owner or Contributor accepts.
• Enterprise Agreement (EA): Enterprise Administrator accepts.
• For most products, Azure subscription Owner or Contributor purchases.
• VM software reservations have different purchasing-role options.^3^

To inspect the current role:

1. Azure portal → account profile → … → My permissions.
2. Select the intended subscription.
3. If the required role is absent, select Go to subscription access control, identify an Owner, and request the appropriate access.^3^

Conditional checks

• If the portal shows that the offer is not approved or Marketplace is disabled: ask the organization’s Marketplace administrator to approve the product and confirm that Azure Marketplace purchases are enabled for that subscription.
• If this is a CSP-managed subscription: the documented private-offer flow might not support purchasing through that subscription; verify its account type and use an eligible non-CSP subscription when required.^1^
• If this is SaaS and Subscribe succeeds: select Configure account now and finish registration on the publisher’s site. Allow pop-ups and access to the publisher’s domain. If Microsoft Entra consent is blocked, an Entra administrator must address the consent policy. For manual activation, the publisher must confirm the subscription within 30 days.^2^

If every requirement is correct

Retry once in an InPrivate/incognito session to exclude stale portal state. If the same failure remains, create an Azure support request and include:

• Private-offer and product name
• Product type: SaaS, VM, Managed App, or other
• Offer and product statuses
• Selected subscription and billing-account type
• Exact UTC failure time
• Full portal error details, including any session, correlation, or request identifier displayed

Do not post subscription, tenant, billing-account, or offer identifiers publicly.

References

1. Private offer troubleshooting - Marketplace customer documentation ...
2. Step 3 - Purchase and Subscribe to the Private Offer - Marketplace ...
3. Roles and permissions