Why does Appsource still have "Power Virtual Agents" and not Copilot as a Product filter?
I'm shocked that there is no Copilot/Agentic AI product filter. It makes it hard to publish consulting listings for AI solutions if people won't know where to find them. I mean, didn't the name Power Virtual Agents go away like, 4 years ago?! Can we petition to get this updated so people know where to browse for Copilot listings properly?Accelerate your growth on Azure Marketplace [French]
Hi everyone, If you’re a French speaker looking to ramp up on Azure Marketplace, join us today at 15:00 CET for a focused, no-fluff webinar. We’ll hit the accelerator from four angles: Fundamentals, fast – a concise refresher to get everyone on the same page Co-sell the Microsoft way – practical examples that actually land deals Resell like BeCloud – tactics for turning Marketplace listings into revenue Archera’s best practices – proven plays you can put to work tomorrow Cut the guesswork—come ready to level up. Registrations: https://events.teams.microsoft.com/event/fa1f174d-6e04-4dcd-8eb7-cf95ea0d1ac9@cc399a02-f38a-4820-a991-894e8c59d676.
Modifying Plan Minimum Number of Users for Private Offers
Hi, I’m curious to know if there are any plans to allow ISVs to modify the Minimum Users/Seats when creating a private offer, even if that value differs from the limits defined in the corresponding public plan. At present, it appears private offers must stay within the min/max seat range configured in the public plan. However, there are strategic opportunities where we may need to override the minimum user count (e.g., to accommodate a smaller pilot or proof of concept for a large customer). Thanks, TimDo you need admin privilege to purchase on AppSource?
Hi Community, We are an ISV and publish Apps on AppSource. I’ve always assumed that anyone with a valid email and credit card could purchase a product through AppSource. The requirements on this Microsoft page seem to support that: https://learn.microsoft.com/en-us/marketplace/purchase-software-appsource However, I recently discovered that only Microsoft 365 admins can access order details in the Admin Center. For example, clicking on your badge in AppSource, View all orders in Admin Center, redirects you to this link: https://admin.microsoft.com/Adminportal/Home#/subscriptions/apps But if your account isn’t an admin, you’ll see this message: Switch to an account that has permission Your account (xxxxxx) doesn’t have permission to view or manage this page in the Microsoft 365 admin center. This is confusing. If any user can initiate a purchase, why can’t they view or manage their orders? And if only admins are meant to complete or manage purchases, why is the checkout process open to all users? Would appreciate any clarification or official guidance on this. Thanks!
Inquiry on Licensing Requirements and Usage Process for Published Power Automate Connector
I have created and published a Power Automate connector on Microsoft AppSource. I need assistance in understanding the following What license capabilities or subscriptions are required for clients who wish to purchase and use this connector? What steps do clients need to follow after purchasing the connector to begin using it within their Power Automate environment? Please provide guidance or relevant documentation to help ensure a smooth experience for end users.
GST/VAT in Microsoft-managed countries
Hi, I am in a Microsoft -managed jurisdiction and have a transactable offer in AppSource. I have only recently onboarded some customers and I don’t fully understand how GST is being managed. We are in Scenario 5 as described in https://learn.microsoft.com/en-us/partner-center/marketplace-offers/tax-details-marketplace which means Microsoft collects from the customer at the list price + GST. Ignoring store fees for this purpose, Microsoft pays the (10%) GST to the tax authority then pays out the balance. Unfortunately, the way GST works here, we have to show the amount we receive from Microsoft as gross revenue and then deduct a further 10% to pay to the tax authorities. In other words, we get no credit for the tax Microsoft has paid. As I understand it, the publisher should invoice Microsoft for the sale price + GST then Microsoft invoices the customer at the price plus GST and claims an input tax credit for the GST it pays to the publisher. There may be some specific tax ruling that overrides this. Would be very grateful if any ISV in a similar jurisdiction has encountered this issue.Transitioning SaaS Offers with Multi-Year Pricing from AppSource to Azure Marketplace
When a SaaS transactable offer on Microsoft AppSource includes a pricing plan for more than 1 year, the offer is delisted from AppSource and becomes available on Azure Marketplace. This is due to the platform's structure: AppSource primarily supports monthly or annual subscription models for SaaS offers. Any pricing model that exceeds 1 year (e.g., 2-year, 3-year plans) is outside the scope of AppSource’s transaction capabilities. When a SaaS solution introduces https://learn.microsoft.com/en-us/partner-center/marketplace-offers/marketplace-commercial-transaction-capabilities-and-considerations, it is automatically transitioned to Azure Marketplace, which can accommodate longer-term contracts and subscription models (such as 2-year, 3-year, or longer terms). Azure Marketplace is designed for more complex transactions, including multi-year deals, and supports deeper infrastructure integration and contract management features compared to AppSource. Thus, any SaaS offer that requires multi-year pricing terms will shift from AppSource to Azure Marketplace, where such transactions can be handled effectively.Challenges Business Users Face with Microsoft's Transactable Offers in the Marketplace
Here’s a summary of the challenges faced by business users when purchasing solutions through Microsoft's transactable offer setup in the marketplace: Limited Pricing Flexibility: Business users may find it challenging to secure multi-year or customized pricing as AppSource primarily supports monthly or annual subscription plans. This limits their ability to negotiate bulk discounts or tailored pricing, common in traditional procurement. Complex Procurement Processes: The setup of transactable offers on Azure Marketplace often requires coordination with IT departments for deployment, making it cumbersome for non-technical business users to manage purchases independently. The process may feel less intuitive compared to traditional software procurement methods. Integration Issues with Existing Systems: Many businesses have third-party procurement platforms or internal systems for billing and spend management. The reliance on Microsoft’s native billing system may not align with these existing tools, leading to difficulty in reconciling purchases, tracking invoices, and managing budgets efficiently. Lack of Contract Negotiation: Business users often rely on personalized contract negotiations for larger purchases. Microsoft’s marketplace setup offers standardized pricing without room for customized contracts, making it hard for customers to negotiate terms, volume discounts, or extended payment plans. Limited Cross-Platform Compatibility: Since Microsoft’s marketplace is primarily focused on the Microsoft ecosystem, it may not be the best fit for organizations that operate in multi-cloud environments or use non-Microsoft tools. This limits the flexibility for businesses looking for cross-platform solutions. Lack of Detailed Usage Reports for Business: Business users may find it difficult to get granular visibility into usage and costs, which can make it harder to track software ROI or align expenditures with department budgets. While basic reporting is available, it may not provide the level of detail needed for large organizations. Summary: The way Microsoft’s transactable offer setup is structured presents challenges for business users, including limited pricing flexibility, complex procurement coordination, and difficulty integrating with existing systems. These issues can create friction for organizations seeking more customized contracts, clearer usage visibility, and better alignment with multi-cloud environments.Transactable vs. non-Transactable marketplace offer?
Peer ISV experiences appreciated. Throughout this fiscal Msft has pushed hard towards the marketplace transactability with various initiatives and this was strongly presented also at Ignite. The list of arguments from Msft is extensive (buyer behavior, co-sell, multi-party offers, MACCs, etc...). However I would like to here real-life experiences from peer ISVs who have both transactable and non-transactable offers / have migrated the existing non-transactable offer to transactable offer: Impact on lead generation and closed deals? Impact on co-sell among Msft and/or CSPs? Does MACC eligibility matter? Any other pros / cons? Bonus question: If you have the same offer on both Azure Marketplace and AppSource: Which one has been the place to be? Or both? Thanks a million in advance! 🙏
