Do 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!How we increased trials 200% with Marketplace Rewards
Hi All, Kitameraki Limited's TeamsWork brand provides intuitive and collaborative apps for Microsoft Teams that cater to the needs of small and medium-sized businesses and has successfully launched https://appsource.microsoft.com/en-us/product/office/WA200003945?tab=Overview and https://appsource.microsoft.com/en-us/product/office/WA200004511?tab=Overview apps, and just recently https://appsource.microsoft.com/en-us/product/office/WA200007702?tab=OverviewApp on the Microsoft Marketplaces. As a Microsoft partner for nearly four years, TeamsWork recognized the importance of maximizing visibility and reach within the Microsoft ecosystem. Our team has been able to leverage many of the benefits available through Marketplace Rewards to help drive significant growth and quantifiable results, thanks to expert guidance and the broad range of resources available to better market apps on Microsoft marketplaces. Just a few of these benefits included: The listing optimization allowed us to receive expert recommendations from Microsoft about how to optimize our marketplace offer pages. Azure sponsorship credits cut down on our costs of marketplace solutions. Press release support featuring a quote from a Microsoft executive helped amplify the announcement of our marketplace availability Our customer success story demonstrated how one of our customers increased administrative efficiency by 20 percent using our marketplace solution. featured category placement on the Azure Marketplace, which spotlighted TeamsWork and drove more users to view offer pages. Marketplace Rewards has helped drive a 200% increase in new trials for our marketplace offerings! Read the full story here: https://partner.microsoft.com/en-us/case-studies/kitameraki-rewards What success has your organization seen with Marketplace Rewards?Teams App - Copilot vs Azure Open AI
Morning, For our gauge.it Teams app we have implemented AI to allow the feedback generated by employees to be summarised into suggestions for the manager. When we look at the Team's store I would like it to appear in the AI-powered apps - what is the best process for doing this if we are using Azure Open AI, do we need to add anything to the manifest when pushing the update? Thanks AlasdairA 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:https://customers.microsoft.com/en-us/story/1820562770190814501-designforleisure-excel-retailers-en-germany. 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 https://learn.microsoft.com/en-us/microsoft-365-app-certification/docs/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 https://aka.ms/CertifiedsoftwarepartnerFAQ, 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!Is Anyone Else Facing Issues with SaaS Subscriptions on Teams Store/AppSource?
Hi All, We’ve published two Teams Apps with SaaS subscriptions. While most customers can subscribe without issues, we still receive numerous contacts from those unable to subscribe through the Teams Store/AppSource. The most frustrating part is the vague error messages when a subscription fails, providing no clear explanation. As a result, we often need to redirect customers to a different payment platform. Microsoft, we ask for your support in helping ISVs by: Fixing whatever is causing subscription failures for some customers. We are loosing money here!!! Providing clearer error messages when a subscription fails. I don’t believe this is a widespread issue, as most subscriptions go through smoothly. Anyone else experiencing this?Action required to prepare your app for cloud.microsoft
Hey there, Perhaps this is the wrong forum to ask, but since we're discussing Teams apps here, I thought I'd ask. Did anyone get emails from Microsoft regarding the changes to the cloud.microsoft? The changes involve: Upgrade to version 2.19 or above of the https://www.npmjs.com/package/@microsoft/teams-js Retain the domains that your app’s CSP headers/ x-frame-options currently refer to Update your x-frame-options/CSP headers to allow for add: *.cloud.microsoft The corresponding blog is here: https://devblogs.microsoft.com/microsoft365dev/action-required-ensure-your-microsoft-teams-apps-are-ready-for-upcoming-domain-changes/ We're reviewing some options currently and its looking like there could be wide-spread affect on existing customers of our Teams apps. Anyone gone through this? Do we know the actual timeline were this will be mandated?OpenAI Bot SDK in Microsoft Teams - Technical Question
Currently, we are working on a new feature for our 'check it' Microsoft Teams product, we have a technical challenge that MS support is unable to help with and want to see if anyone in here has had a similar issue: Using the OpenAI models, specifically with the OpenAIClient SDK (.net) it has become a common behaviour for all AI bots to stream their response to the user in an organic conversational manner (open AI playground, Chat GPT etc..). When trying to do the same with the team's bot SDK on await turnContext.UpdateActivityAsync(newActivity, cancellationToken); call. I receive a 429 Too many requests issue. Even with the guidance to allow for retries* it fails to find the correct exception type within the retry policy indicating that this is not teams. The same calls can be made in the AI playground without issue or streamed out to a web application. This leads us to assume it's the bot rates that are failing. Is there any way to update an activity in a streaming manner or will the bot SDK look to support this now or in the future? https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/rate-limit
