Azure IP Co-sell Reference Architecture

Azure IP co-sell eligible status, is a common goal for many software development companies (SDC) partnering with Microsoft, as it allows end customers to decrement their Microsoft Azure consumption costs at 100% when using the partner’s solution.

Requirements

There are 4 requirements to achieve Azure IP co-sell eligible status:

• Reach the required revenue threshold ($100K of Azure usage or sales through the Microsoft Marketplace over 12 months)
• Meets the Azure IP co-sell technical validation requirements
• Provide a reference architecture diagram
• Offer is transactable on Microsoft Marketplace

For a SaaS solution to pass technical validation, it must be “primarily platformed on Azure.” This is detailed in the Marketplace Terms and Conditions for SaaS offers.

Marketplace Offer Decision Chart

Use this chart to identify the Microsoft Marketplace offer type that best fits your delivery model, deployment target, and management responsibilities. The legend distinguishes Azure IP co-sell-supported offer types from other Marketplace and independent deployment options.

To adapt the chart, download the editable Draw.io source.

Example Architecture

Many SDC’s share similar architectural patterns, so this example is meant to give you a solid starting point. It’s built with Draw.io.

This example models a SaaS architecture where a customer (also on Azure) connects to the SDC’s API via Private Endpoint.

Components included:

• SDC Subscription
  • AKS
    • Ingress Controller
    • App pod (IP)
    • Data pod (IP)
  • Azure Load Balancer
  • CosmosDB
  • Storage Account
  • Azure Key Vault
• Customer Subscription

To use this as a starting point, download the Draw.io source file and modify it to reflect your own architecture.

Important considerations:

• Clearly show what’s in the your Azure subscription and what’s outside (e.g. use boxes to easily indicate).
• List each of the Azure Services your solution uses.
• Use red boxes with white bold text to showcase exactly where your Intellectual Property (IP) resides
• Provide a detailed, numbered flow of the data with the user interfaces and other services