Skip to content

Marketplace prerequisites

Complete these checks with your Azure billing, subscription, identity, and network administrators before opening the deployment form.

Marketplace and billing

  1. Confirm that Microsoft Marketplace purchases are enabled for the billing account and subscription.
  2. Confirm that the deploying user may purchase or accept the approved offer.
  3. If your organization uses Private Marketplace, confirm that the offer and plan are allowed.
  4. Use the offer link or offer identity approved by your procurement team. Do not choose a similarly named listing.

Microsoft documents the current purchasing controls in Enable Marketplace purchases.

Azure access

The deploying identity needs permission to create a managed application and its application resource group. Additional permissions can be required by your organization's policy, networking, role-assignment, or delegated identity model.

Do not assume that an Azure Contributor role can create every required role assignment. Ask an Azure administrator to validate the deployment against your tenant's RBAC and policy design.

Subscription readiness

Confirm:

  • the target subscription and Microsoft Entra tenant;
  • the approved Azure region;
  • sufficient compute, storage, networking, and public IP quota for the chosen deployment;
  • required Azure resource providers are registered;
  • Azure Policy permits the resource types and selected region;
  • naming and tagging requirements;
  • a resource group for the managed application;
  • customer contacts who can receive deployment and support communication.

Network decision

Choose public or private access before deployment. For private access, identify the client VNet, subnet, routing owner, DNS owner, and certificate authority.

Record the approved values in the deployment planning worksheet.