Payout and tax profiles non-us individual, no company, no tax ID
Subject: Tax profile for an individual in the UAE: is a VAT/Tax ID mandatory? Hello, I am an individual developer (account type: Individual), permanent resident of the United Arab Emirates, creating a tax profile in order to sell a paid add-on on the Microsoft Store. At the "Tax Residence Country/Region" step, the field "Tax ID type" is required and its only option is "VAT number", which then requires a Tax ID. I am not registered for VAT in the UAE and have no Tax Registration Number (TRN). Leaving the field empty blocks the Next button (screenshot attached). In the UAE, TAX registration is only required to businesses above a set yearly revenue. I am only an individual. Questions: 1. Is a UAE VAT number (TRN) mandatory to create a tax profile as an individual seller? 2. If so, is there an alternative path for individuals who are not VAT registered? 3. If a TRN is required, is registering for VAT the only option? Thank you.Work IQ Cost and Pricing Model for Agents published in Marketplace
I would very much like to ask for assistance and input in regards of "Consumption, cost forecasting, break-even analysis and recommended customer pricing. " I believe a bit of context is required. We are about to publish two Work IQ MCP Agent in Marketplace. Both agents will be integrated to our existing Apps that are published in Marketplace. 1. iGlobe CRM for Teams and 2. iPlanner Pro for Outlook and Teams. Both Apps are multitenant Apps running on customers own tenant. The Apps can only be deployed from Marketplace. Lets use iPlanner Pro Agent as an example. In short, iPlanner Pro Agent uses Work IQ and MCP tools to understand emails, meetings and Microsoft 365 context, while iPlanner Pro turns that intelligence into structured Planner execution, including the appropriate plan, bucket, assignment, priority and supporting email context. Including saving the email or attachments on the task. A prompt could look like this "Find the latest email from email address removed for privacy reasons. Create a task for in Planner, put it in the correct Plan and bucket, assign it to the appropriate owner, set a due date for next week and save the email on the Planner Task" Work IQ and MCP provide context and intelligence, iPlanner Pro executes the structured actions, and Microsoft Planner remains the source of truth. To my understanding Work IQ API usage is billed through Copilot Credits rather than a separate per-user Work IQ license. Microsoft 365 Copilot includes Work IQ functionality within native Microsoft Copilot experiences, but third-party solutions such as iPlanner Pro consume Copilot Credits when they call Work IQ APIs. Work IQ does not require a separate API subscription, SKU or per-user licence. API usage is consumption-based and is measured in Copilot Credits. Work IQ operation Credit consumption Planning note Chat API Variable Depends on grounding, retrieval and reasoning complexity. Context API Variable Depends on the scenario and the sources used. Tool API 0.1 credit per API call Static component: $0.001 per call at $0.01 per credit. Example: 1,000 Tool API calls consume 100 credits, equivalent to $1.00 at the planning rate. Now here comes my confusion. 1. How do we know how many credits we are using with a prompt like the example I showed? the consumption is 0.1 credit per API call. 2. If I understand the above correct, the total consumption is calculated on the customer tenant. That consumption includes much more than just iPlanner Pro. Is that correct? 3. OR, will the sum of all customer using iPlanner Pro Agent be direct to us and we will be billed based on the total consumption of all our customers? If that is the case ( I don't think it is) then how do we know how much each customer consumed? 4. If consumption and billing is on the customer, how can the customer see what iPlanner Pro cost in consumed credits? This is important in regards of giving a cost forecast for customers. I am sure they would want that before start using the Agent. It is also important in regards of the question of if we should charge or offer it as a free agent? If we are billed then we will need to change for it. If the customer is billed then we probably will not be able to charge for it. I hope I have been able to explain my confusion. I tried asking contacts I have at Microsoft, but unfortunately haven't heard anything. That is why I am asking in the community. Have any one else the same challenge? what have you done? Can Microsoft assist here? I will be happy to take a Teams call and others are welcome to join. Thank youWhat's preventing your Marketplace growth engine from scaling?
Many SDCs know where they want to go with Marketplace, but struggle to turn individual activities into a repeatable growth motion. The latest in the Sell more with App Advisor blog series, asks: ✅ What part of your Marketplace journey is most repeatable today? ✅ Where do you still rely on manual effort or tribal knowledge? ✅ If you could eliminate one friction point between building, publishing, and growing, what would it be? Read the blog and share your thoughts: Build a Repeatable Marketplace Growth Engine with App Advisor The responses could generate useful insights for future Marketplace content and help identify common challenges across the community!
UX Changes Need Approval?
Hey everyone. Quick question regarding Microsoft approvals. We’ve already secured approval for our test and production environments, but we recently changed out a new, slightly refreshed UX for the feature (this is still in out testing as we can't release without Microsoft's approval). Does anyone know if we need to re-submit for approval for a minor UX change? And if we do, can we just drop an email to the CSPP team, or do we need to fill out the official form as a brand-new request? Thanks in advance!Discover new Microsoft Marketplace innovations announced at Microsoft Build
At Microsoft Build, Microsoft shared new opportunities for software development companies and partners to build, scale, and monetize AI apps and agents through Microsoft Marketplace. Explore how Microsoft Marketplace is helping software companies accelerate go-to-market strategies, expand customer reach, simplify procurement, and unlock new revenue opportunities across the Microsoft ecosystem. Learn how organizations can take advantage of Azure and Marketplace capabilities to support AI innovation and deliver enterprise-ready solutions faster. Whether you’re building intelligent applications, growing your commercial marketplace presence, or exploring new ways to monetize AI-powered solutions, this is a valuable resource for understanding the latest Microsoft Marketplace announcements and opportunities coming out of Build. 👉 Read more: Build, scale, and monetize apps and agents with Microsoft MarketplacePartner perspective: How Breakthru uses App Advisor and AI-listing optimization to drive growth
Optimizing a Marketplace listing isn’t just a marketing exercise—it directly impacts discoverability, demand, and revenue. But knowing what to change (and when) can be challenging for software development companies. In this partner‑written blog post, Marketplace software development company Breakthru shares firsthand experience using AI‑powered listing recommendations in App Advisor to move from guesswork to confident, data‑driven optimization—without risking listing performance. Dan Langille also reflects on how App Advisor became a core part of their business, what’s working in practice, and how AI is changing how teams iterate on their Marketplace presence. 👉 Read the partner story here: Improve Marketplace outcomes with AI‑powered listing recommendations in App Advisor Discussion prompts for the community: Would AI‑driven recommendations change how often you iterate on your listing? Have you used App Advisor for selling and growing app and AI agent sales? Curious to hear how other Marketplace partners are approaching listing optimization today!How to choose the right Marketplace offer type for your AI app or agent
Selecting the right Microsoft Marketplace offer type is one of the most important—and often most complex—decisions when bringing AI apps and agents to market. In this latest Marketplace blog article, you’ll learn how different offer types align to AI delivery models and why this choice directly impacts architecture, security boundaries, customer experience, and monetization strategy. The article breaks down key considerations across SaaS, Azure Managed Applications, containers, and virtual machines, helping software development companies understand how to balance control, scalability, and operational ownership. It also highlights how offer type decisions influence where AI workloads run, how data is managed, and how customers deploy and interact with your solution. If you’re building or publishing AI solutions in Microsoft Marketplace, this guidance will help you make informed decisions early—before development, security, and go-to-market plans are locked in. Read the full article: Marketplace Offer Types for AI Apps and agents: SaaS vs Managed App vs ContainersSecuring and governing AI agents before deployment
April 30 | 2:00-3:00 PM (GTM +10) Join this live webinar to learn how to secure and govern AI agents before they go live. Explore how to provision agents with Entra Agent ID, manage identities and credentials, enforce least-privilege access, and prevent risks like Shadow AI and agent sprawl. Join to gain practical guidance on governing AI agents across their full lifecycle—so you can deploy with confidence. To view the session live, register here: Securing and Governing AI Agents Before They Go Live You can view previous Security for Software Development Company series sessions on demand here: Security for Software Development Company Series: Securing the Agentic EraHow to design production-ready AI architectures for apps and agents on Microsoft Marketplace
As organizations accelerate the development of AI-powered applications and agents, moving from prototype to production requires a strong architectural foundation. This article explores what it takes to build AI solutions that are ready for enterprise deployment through Microsoft Marketplace—where reliability, security, scalability, and operational readiness are essential. Learn why “production-ready” architectures are critical to meeting customer expectations, how early design decisions impact long-term success, and what patterns software development companies should consider when aligning solution architecture with Marketplace offer types. The article also highlights key considerations around ownership, runtime environments, and operational responsibilities that shape how AI solutions are deployed and supported. Whether you are building your first AI app or scaling an existing solution, this guidance provides a practical foundation for designing trusted, enterprise-ready offerings that customers can confidently run in production. Read the full article: Production ready architectures for AI apps and agents on Marketplace | Microsoft Community HubWhy building secure AI apps and agents early matters for Microsoft Marketplace
Security is a foundational requirement for publishing and scaling AI apps and agents on Microsoft Marketplace. As AI systems become more autonomous, they introduce new trust boundaries across prompts, identity, integrations, and runtime behavior. This article explores why security must be designed in from the start—and how clear guardrails, identity controls, and enforcement help reduce risk, streamline Marketplace review, and build customer trust. Learn what it takes to create Marketplace‑ready AI solutions that are secure, scalable, and enterprise‑ready. Read the full article: Securing AI apps and agents on Microsoft Marketplace | Microsoft Community Hub
