Marketplace Cashflow Management
A new one on me, but one to watch for if you haven't yet yourselves encountered it: Back in April, we created an Azure Marketplace private offer for an enterprise customer Customer has a MACC; but instead of their EA number, they gave us a subscription ID with the explanation they separate their internal consumption from Marketplace purchases Customer waited until 2 May to purchase their private offer Seemed innocuous at the time, but . . . the combination of purchasing under a subscription ID + waiting until early in a new month to execute the purchase = the transaction not landing on their Microsoft Azure bill until June. Which in turn means they don't have to pay Microsoft until July. Which in turn means we don't receive our payout until August. Or maybe September. Clever, eh? Good for the customer's cash flow. Less good for ours. Some customers are getting wise to the nuances of Marketplace billing and payment cycles, so be wary of the impacts on your cashflow! #MarketplaceChampions #SponsoredAccelerate 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: here.
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!🚀 Now available: Flexible billing schedules in Microsoft marketplace
Microsoft is making it easier than ever to meet customer procurement needs with flexible billing schedules for private offers—available globally across all marketplace-supported currencies. ✅ Align deals with any virtually and contract value and billing timeframe ✅ Streamline sales and accelerate deal velocity ✅ Supports SaaS flat rate offers, VM software reservations, and professional services ✅ Available for customer private offers and multiparty private offers Over 100 partners in preview are already seeing success—now it’s your turn. 📖 Read more about how it works and explore real-world use cases: 👉 Meet customer business needs with flexible billing schedules in the marketplace
Build and extend your own agents using pro-code capabilities
We recently hosted the exciting new training session, “Build and extend your own agents using pro-code capabilities”, This event offered invaluable insights and hands-on experiences designed to elevate your skills and knowledge in developing and extending Microsoft 365 Copilot and custom engine agents. Event highlights: Day 1 dove into extending Microsoft 365 Copilot with declarative agents and custom engine agents, exploring the Copilot Stack, building agents using natural language coding, and adding skills with plugins. Using natural language, you are empowered to use your tool of choice to create a declarative agent app package with Teams Toolkit, Copilot Studio Agent Builder, Copilot Studio, or SharePoint. Learners experienced the ease and speed of building agents with the Copilot Studio Agent Builder in Microsoft 365 Copilot. Day 2 covered developing AI agents with Azure AI Foundry, understanding the Azure AI Foundry SDK, deploying models, implementing Retrieval Augmented Generation (RAG), and learning about fine-tuning and synthetic data generation. Day 3 focused on building multi agents with Semantic Kernel or AutoGen, securing and governing copilots and agents with Microsoft Security, and implementing Responsible AI. Semantic Kernel is lightweight, open-source, production-ready, orchestration middleware that lets you easily add AI to your apps, with AI safety at the center. Missed the Event? No Worries. Sign up today for the on-demand session here. Plus, don't miss out on our full calendar of upcoming events, including Azure OpenAI, Build and Modernize AI Apps on Azure, and many more. Follow this link for more details.
