A story about our journey on the marketplace. I hope it will inspire and help on your journey
I would like to share my experience with publishing transactable apps on the Microsoft commercial marketplace, the Microsoft 365 App Certification Program, Marketplace Rewards, and certified software designations. Starting with publishing our apps on to the marketplace: We have several apps that operate within the context of Microsoft 365, including apps for Outlook, Microsoft Teams, Copilot Agent, Office, and SharePoint. We have been in AppSource for many years and have customers worldwide. We developed an in-house license application to manage our customers' licenses. Before the commercial marketplace, we managed all invoicing and license management manually. Now, everything has become much easier. We have published monetized SaaS apps connected to the AppSource apps. Using the SaaS Fulfillment API, we integrated the purchasing process with our in-house license application. We have gained numerous benefits, including: Significant time savings in the invoicing and billing process, as purchasing, adding, removing, or cancelling licenses is automated and managed by Microsoft Customers appreciate the ability to manage licenses themselves, finding it easier Improved market awareness due to promotion in the marketplace And new customers are joining regularly. It is also important to mention Marketplace Rewards, which offer various benefits. For example, customer case stories can be published through Marketplace Rewards on Microsoft customer case stories. Here is a link to our latest story: Microsoft Customer Story - Design for Leisure improves efficiency 30% with iGlobe solutions and Microsoft Planner. Additionally, the Transact & Grow Incentive Campaign has provided us with financial incentives through marketplace sales, as well as Azure sponsorship credits to offset deployment costs. Considering these advantages, there is potential to make the apps CSP Ready as well: https://aka.ms/P2PeBook. Equally important is obtaining the Microsoft 365 App Certification. Certification confirms that an app solution is compatible with Microsoft technologies, compliant with cloud app security best practices, and supported by Microsoft. This is significant because: It provides certification from Microsoft, confirming app security and compliance It saves time in the sales process, as security and compliance are already verified It makes the app easier to find on AppSource, the Commercial Marketplace, and in the Teams App admin portal, where it will be listed in a special category Achieving sales in the marketplace, having customer case stories, and obtaining the Microsoft 365 App Certification provides the foundation to obtain Certified Software Designations, which come with additional benefits and opportunities for co-selling with Microsoft. Today two of our apps have achieved the Certified Software Designation for Modern Work. Soon iPlanner Pro for Teams that includes a Copilot Agent will follow as well. I share this story not to boast but to inspire and motivate others. There is nothing exceptional about us or our experience here – it can be completely replicated by leveraging the resources that Microsoft provides.Was it all very easy…. No. Is it doable? Yes!Essential Customer Requirements for Purchasing SaaS Solutions on Microsoft Marketplace
Customer requirements to purchase a SaaS solution through Microsoft Marketplace (AppSource or Azure Marketplace): Microsoft Account: Requirement: The customer must have an active Microsoft work or school account. This account is essential for managing subscriptions, billing, and accessing the purchased SaaS solution. Reason: The marketplace transactions are tied to Microsoft accounts for security and authentication Microsoft 365 Subscription (In Some Cases): Requirement: For many transactions, particularly through AppSource, customers may need to have an active Microsoft 365 (M365) subscription. This is often necessary to facilitate billing and integrate SaaS solutions with Microsoft productivity tools. Reason: Some SaaS solutions are designed to integrate directly with M365 apps (e.g., Dynamics 365, Microsoft Teams), and the marketplace uses M365 for account and payment management. Azure Subscription (For Azure Marketplace): Requirement: To purchase a SaaS solution on Azure Marketplace, the customer typically needs an Azure subscription. This subscription allows the customer to manage billing, access SaaS services, and deploy cloud solutions within their Azure environment. Reason: SaaS offers in Azure Marketplace are often integrated with other Azure services, requiring an Azure account for deployment, management, and billing. Billing Information: Requirement: Customers must provide valid billing details, such as a credit card, or set up invoicing through their Microsoft or Azure account. Reason: Billing is handled through the Microsoft or Azure billing system, and payment details are necessary to complete transactions for SaaS subscriptions or services. Access to Admin or Purchasing Permissions: Requirement: The customer must have the necessary permissions (e.g., admin or purchasing rights) within their organization to make purchases through Microsoft Marketplace. Reason: Some organizations restrict purchase permissions to specific roles (e.g., IT admin, finance team). Users without these permissions may need approval from their organization’s administrator. Agreement to Terms of Service: Requirement: Customers need to agree to the terms and conditions of the SaaS solution and the Microsoft Marketplace before completing the purchase. Reason: Legal requirements ensure that both Microsoft and the SaaS vendor are covered by the agreement, and customers understand their rights and obligations. Compatibility with Existing Microsoft Ecosystem: Requirement: In some cases, customers may need to verify that the SaaS solution is compatible with their existing Microsoft ecosystem, such as M365, Azure, or Dynamics 365. Reason: Many SaaS solutions on Microsoft Marketplace are designed to work with Microsoft services, so compatibility is critical for successful integration. Payment Model Understanding: Requirement: Customers need to understand the payment models (e.g., monthly subscription, annual billing, pay-as-you-go) offered for the SaaS solution. Reason: Each SaaS solution has its own pricing structure and understanding the payment model ensures that the customer is aware of recurring fees or usage-based charges. Organization's Compliance with Microsoft's Billing and Procurement Policies: Requirement: The organization must comply with Microsoft’s billing and procurement policies, which may involve certain approvals or process steps depending on the size and type of the company. Reason: Larger enterprises often have internal procurement processes that must align with Microsoft's marketplace systems. Geographical Availability: Requirement: The SaaS solution must be available in the customer’s region. Certain offers might have regional restrictions based on service availability or regulatory reasons. Reason: Microsoft Marketplace enforces regional availability for certain solutions due to compliance or technical constraints.
