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.Agentic Marketplace publishing expands with broader product coverage and generally available APIs
When we introduced Marketplace Ingestion Model Context Protocol (MCP), the idea was simple: help developers start with what they want to accomplish, rather than with an API payload. Now, that workflow can go further. Marketplace Ingestion MCP and APIs have reached 100% product coverage for Microsoft Marketplace offers, giving publishers more ways to bring Microsoft Marketplace publishing into the development processes and tools they already use. We’ve also reached another important milestone: the Product Ingestion APIs for SaaS and virtual machine offers are now generally available (GA). Together, these updates give development teams more flexibility in how they build Marketplace publishing into their workflows, whether they work with an AI agent through Marketplace Ingestion MCP, integrate directly with APIs, or combine both approaches. From agentic publishing to broader product coverage In my previous post, I shared how Marketplace Ingestion MCP connects natural-language intent with Microsoft Marketplace publishing actions. That experience now supports a broader range of Marketplace products. With 100% product coverage across our MCPs and APIs, publishers can apply the same outcome-first approach across their Marketplace publishing workflows. Marketplace Ingestion MCP connects supported agentic experiences with Partner Center APIs. Instead of manually constructing API payloads, you can describe the publishing outcome you want. Your agent can then help retrieve the right schema, build and validate the payload, and perform supported publishing actions. For development teams, that means publishing can become part of the workflow rather than a separate activity after development is complete. SaaS and virtual machine APIs are now generally available Publishers that prefer to integrate directly with Marketplace publishing APIs also have an important update: Product Ingestion APIs for SaaS and virtual machine offers are now generally available. These APIs give development teams a programmatic way to create, publish, and manage their offers in Microsoft Marketplace. With these APIs now generally available, publishers have another way to build Marketplace publishing into their development and release processes. For teams already using the APIs, there is no need to immediately rework integrations built with older preview versions. Existing preview API versions continue to work. You can continue using those versions in your current integrations while adopting to the GA versions. If you're starting a new integration, we encourage you to use the latest generally available API versions for SaaS and virtual machine offers. Choose the workflow that works for your team There isn't one way every publisher needs to work. Some teams may want an agent-assisted experience, using natural language and Marketplace Ingestion MCP to handle more of the translation between publishing intent and API structures. Other teams may work directly with the Product Ingestion APIs to build publishing into automated processes. And some teams may combine both. The opportunity is to make Marketplace publishing fit more naturally into how your team develops and ships software. You can: Start with intent. Use Marketplace Ingestion MCP to describe the publishing outcome you want and let your agent help translate it into supported actions. Build repeatable workflows. Bring common offer creation and update tasks into development workflows, including CI/CD processes where appropriate. Integrate directly with APIs. Use the generally available Product Ingestion APIs for SaaS and virtual machine offers to build programmatic publishing experiences. Move forward at your own pace. Existing integrations using older preview API versions continue to work, giving teams flexibility in when they adopt the latest GA versions. What this means for publishers The goal is straightforward: give developers more flexibility in how they bring their cloud and AI solutions to customers through Microsoft Marketplace. Marketplace Ingestion MCP brings publishing closer to the tools and agentic workflows developers already use. The Product Ingestion APIs provide the foundation for teams that want direct programmatic integration. With expanded product coverage and GA APIs for SaaS and virtual machine offers, publishers have more options for building Marketplace publishing into the way they already develop and operate their products. If you've been exploring agent-assisted publishing, now is a good time to take another look. And if you're building directly with the Product Ingestion APIs, consider using the latest generally available SaaS and virtual machine API versions as you create new integrations. Get started Marketplace Ingestion MCP is included with access to Microsoft Marketplace submission APIs. To get started, you'll need: A Partner Center account with the required role Access to Microsoft Marketplace submission APIs An MCP-compatible client, such as Visual Studio Code or GitHub Copilot CLI, if you want to use Marketplace Ingestion MCP Learn more: Marketplace Ingestion MCP server | Microsoft Learn Product Ingestion API for Microsoft Marketplace | Microsoft Learn Product Ingestion API for SaaS | Microsoft Learn Product Ingestion API for virtual machines | Microsoft Learn Marketplace Ingestion MCP server - Marketplace publisher Publishing doesn't need to sit at the end of development. With agent-assisted workflows, broader product coverage, and generally available APIs, teams have more ways to make publishing a natural part of how they build and bring solutions to market.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 youMicrosoft Marketplace Partner Digest - August 2026
What's new in Marketplace Convert more buyers into customers Microsoft recently expanded Marketplace listing capabilities with enhancements to free trials and the introduction of an option to request private offers, giving partners more ways to engage buyers at different stages of the purchasing journey. Customers can now discover and evaluate solutions through expanded trial experiences and transition more easily into paid subscription discussions by requesting custom pricing and terms directly from your Marketplace listings. ✨ Help customers evaluate your solution with free trials What's new On July 23 we announced the release of Marketplace enhanced trial capabilities. Customers can try solutions with confidence with the free trials in Microsoft Marketplace. Trials are available for multiple offer types, including SaaS, Azure virtual machines, Dynamics 365, and Power BI offers. New capabilities include: Custom meter trials: Partners can configure trials for SaaS solutions with metered pricing. Flexible trial durations: Partners can now configure SaaS trial durations from 1 to 180 days. Partner analytics: Partners can access SaaS trial analytics - including free trials initiated, active free trials, free trials converted, free trials not converted, and average trial duration - all within Partner Center Insights workspace. Customer discovery and management: Customers can better discover and manage trials. Upgrade to paid subscription during trial: Customers can upgrade to paid subscription at public pricing any time during a SaaS trial. Why it matters With enhanced trial capabilities in Microsoft Marketplace, partners can run self-service trials that make it easier for customers to try before they buy — whether for metered, per-user, or flat-rate pricing offers. Marketplace gives partners one place to manage trials end to end — from provisioning and mid-trial changes to insights — while improving offer discoverability through improved search, filters, and dedicated trial badges. Recommended action Review your Marketplace offers and trial strategy. For eligible SaaS offers, evaluate whether free trials can help you engage with more qualified buyers, faster. 📖 Learn more about free trials for SaaS ⚡ Customers can now request a private offer on Marketplace What’s new As of July 20, you can add a private offer request option directly on your Marketplace product pages. Customer requests are captured as Marketplace leads in referrals workspace and connected customer relationship management (CRM) integrations you’ve setup. This setting is disabled by default. You can easily activate it for applicable public offers. Why it matters More and more customers are seeking customized contracts and subscription pricing and terms tailored to their individual needs. This simple call to action reduces friction and helps you start the conversation with prospective buyers. Recommended action In the Marketplace offers workspace of Partner Center, update each of your offers for which you provide customers private offers. Enable the Request Private Offer setting and republish the offer. Events Recent events Multiparty private offers expand channel growth opportunities in Australia, Japan and South Africa Multiparty private offers continue to help software companies accelerate channel-led sales through Microsoft Marketplace. This past month, we hosted two region-focused Marketplace office hours sessions designed to help partners better understand local market opportunities, engage distributors and resellers, and scale Marketplace transactions through channel ecosystems in Australia and Japan. Whether you're looking to expand an existing Marketplace motion or explore new geographic opportunities, these sessions will provide practical guidance and market-specific insights to help you grow. See a list of currently supported countries/regions. Check out the recorded sessions: • Channel growth in Australia (English) • Channel growth in Japan (Japanese) Helping developers build, monetize, and scale AI solutions with Marketplace Discover how Microsoft Marketplace helps software companies access AI models and developer tools, accelerate application development, and reach customers through Microsoft's global commercial ecosystem. Learn how to monetize applications and agents without building and maintaining your own commerce and distribution infrastructure. Watch the recording Upcoming events Build AI-powered solutions, monetize through Microsoft Marketplace, and scale revenue through Microsoft expertise, skilling, and investments. Frontier Accelerate for Marketplace is an upcoming unified offering for software development companies to bring AI-powered solutions to market, drive customer acquisition and revenue growth, and scale through Microsoft Marketplace with technical guidance, skilling, and investments aligned to every stage of growth. 📆 Join us on August 26th before general availability to learn about the new offering, benefit alignment, migration guidance, and enrollment requirements. Next steps Turn insights into FY27 success — starting today. Ready to carry the momentum forward from MCAPS Start for Partners? Get everything you need to refine and execute your FY27 strategy in the Partner Activation Zone, including session recordings, ready-to-use playbooks, and tools to start building pipeline. Leverage your Marketplace Rewards benefits Discover use cases and how to leverage your Azure sponsorship. With Marketplace Rewards Azure sponsorships, eligible software development companies can increase sales through Microsoft Marketplace by using the sponsorships for customer deployments tied to Marketplace deals—and to offset infrastructure costs from eligible free trial offers. 📍Review the Marketplace Rewards Azure sponsorship policy guide for the latestWhat'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!Clarity at every stage: App Advisor turns Marketplace complexity into action
For software development companies, the Microsoft Marketplace journey isn’t always linear. It’s a series of decisions: what to build, how to package it, how to publish, and how to sell it, each with real dependencies and real friction.
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!Dragon Copilot and Microsoft Marketplace are transforming the way healthcare is delivered
If AI has so much promise in healthcare, why does it still feel so hard to apply in everyday workflows? That question is starting to shape much of the conversation across the industry. Healthcare teams aren’t debating whether AI matters anymore, they’re focused on how to make it work in environments that are already stretched thin. Reality: Healthcare has a capacity problem Healthcare isn’t dealing with a demand problem; it’s dealing with a capacity constraint. In fact, 79% of healthcare workers say they don’t have enough time or energy to do their work, 51% of healthcare leaders say productivity needs to increase, and 79% are confident AI will play a role in expanding organizational capacity. That pressure shows up everywhere: in documentation backlogs, fragmented and click-heavy workflows, administrative overload, and ultimately less time spent with patients. This is where the conversation around AI is shifting; not toward adding more tools but toward removing friction from the workflows that already exist and helping care teams move faster with less overhead inside the flow of care. That reality came through clearly during a recent Microsoft Marketplace Customer Office Hour on Dragon Copilot and Microsoft Marketplace: how to operationalize AI within real-world clinical workflows and enterprise healthcare environments that are experiencing a capacity problem. Instead of focusing on future-state possibilities, the conversation centered on what it takes to move from promise to practice, and where AI can start delivering value today. That distinction matters because developers, healthcare architects, and AI engineers are no longer asking whether AI can create value. The industry has largely accepted that it will play a meaningful role across healthcare. The real challenge is how to integrate into environments already burdened by operational complexity, fragmented workflows, regulatory pressures, and disconnected technologies. In practice, most healthcare organizations aren’t lacking data or systems, they’re struggling with how those systems work together. Clinicians and administrative teams operate across EHRs, reimbursement platforms, documentation tools, referral systems, messaging apps, and care coordination workflows that often function in isolation. Each additional screen, handoff, or disconnected experience introduces friction, and over time that friction compounds into inefficiencies that impact clinicians, administrators, and ultimately patients. This is why AI cannot simply sit on top of existing systems as another productivity layer; it needs to act as an orchestration layer that reduces complexity directly within the flow of care. That shift fundamentally changes how we think about healthcare AI, moving from isolated features to embedded intelligence that supports the workflows where care teams already spend their time. Dragon Copilot as a clinical workflow platform Dragon Copilot is not positioned as just another ambient listening tool or conversational assistant. It's designed as a clinical workflow platform that integrates into how care is delivered. While voice capabilities like ambient listening and natural language interaction are foundational, the real value comes from combining contextual intelligence, workflow automation, and extensibility. In practice, that means clinicians can access relevant information directly within their workflow, reduce fragmentation across systems, and act using natural language without constantly switching between tools. Extending healthcare AI through Microsoft Marketplace What makes this even more compelling is how Dragon Copilot extends through AI apps and agents connected via Microsoft Marketplace. This shifts the conversation from a single AI solution to a broader ecosystem approach. Instead of relying on monolithic systems to solve every problem, healthcare organizations can layer specialized AI capabilities directly into their workflows. During the session, we walked through examples like coding and charge capture, denial prevention, eligibility verification, medication safety checks, and patient education each addressing a specific operational need without requiring organizations to replace core systems. From a technical perspective, what stands out is not just automation, but the ability to reduce workflow re-entry and repetitive administrative loops. Today, many processes require clinicians and administrators to document, submit, reprocess, and reconcile information across disconnected systems. By embedding AI into those workflows, whether for coding validation, reimbursement support, or clinical guidance, organizations can streamline those cycles, improve continuity between systems, and reduce the compounding operational burden that slows teams down. What does this mean for healthcare developers For developers building healthcare solutions, this shift opens meaningful opportunities across workflow orchestration, AI-assisted compliance, operational intelligence, policy validation, and real-time financial support. More importantly, it reflects a broader architectural change in how healthcare technology is evolving. Rather than attempting to replace existing systems, the industry is moving toward connected AI services that extend and augment what’s already in place. This approach matters because healthcare organizations rarely overhaul core infrastructure all at once. Instead, they evolve incrementally by layering new capabilities into existing workflows. Dragon Copilot, combined with Microsoft Marketplace, is designed to support that model. AI agents can surface insights, automate repetitive tasks, and support decision-making while staying embedded within established clinical environments, helping developers build solutions that are practical, scalable, and aligned with how healthcare systems actually operate today. The strategic value of ecosystem extensibility As the importance of ecosystem extensibility continues to grow, Microsoft is intentionally building beyond a standalone healthcare AI solution. Instead, the focus is on creating an ecosystem that enables connected intelligence across clinical and operational workflows. For developers, this shift has real implications. It directly impacts how quickly solutions can be built, how easily they can be deployed, and how far innovation can scale. Without extensibility, progress is constrained by the roadmap of a single platform. With it, developers and healthcare technology providers can target highly specific workflow gaps with purpose-built solutions. That opens the door to a new class of innovations from AI agents and workflow accelerators to embedded clinical decision support and healthcare-specific automation designed to fit seamlessly into existing environments and address the nuanced needs of modern care delivery. Reducing adoption friction in enterprise healthcare The Marketplace component of this strategy directly addresses some of the most persistent barriers to adoption in enterprise healthcare. Organizations can simplify procurement, reduce vendor onboarding friction, streamline licensing, and consolidate billing through Microsoft’s existing purchasing infrastructure. From a developer and software company perspective, this is significant because historically the challenge in healthcare hasn’t been building new capabilities but getting them adopted and scaled in complex environments. By reducing the effort required to evaluate, purchase, deploy, and operationalize AI solutions, Marketplace changes the pace at which organizations can move from experimentation to real-world implementation. That efficiency becomes critical as healthcare shifts from isolated pilots to production-scale deployments, where speed, integration, and operational alignment ultimately determine whether AI delivers meaningful impact. From AI experimentation to production-ready workflows Healthcare AI is no longer confined to pilots or conceptual experimentation. Organizations are now evaluating production-ready solutions that can integrate directly into enterprise workflows. That shift brings a different set of expectations for developers and architects. Instead of asking whether AI can generate useful outputs, the focus has moved to operational questions: Can these systems integrate seamlessly into clinician workflows? Will they reduce complexity without introducing disruption? Can they scale reliably, perform consistently, and meet regulatory requirements? These are not just AI challenges, they’re deeply rooted in systems integration, workflow design, operational engineering, and enterprise architecture. Success depends not only on model performance, but on how well AI fits into the realities of healthcare delivery, supports care teams in context, and operates within the constraints of highly regulated, mission-critical environments. Designing for operational value, not just model innovation This is exactly why the conversation matters for the healthcare developer community right now. Future success in healthcare AI will depend less on model novelty and more on how well those models integrate into real workflows. Most healthcare organizations are already navigating fragmented environments filled with disconnected systems, and the solutions that deliver lasting value will be the ones that reduce cognitive load, minimize context switching, surface information at the right moment, and integrate naturally into day-to-day clinical work. In that sense, the challenge becomes less about AI in isolation and more about systems design. Meaningful progress won’t come from standalone copilots operating outside enterprise infrastructure. It will come from connected ecosystems where AI services, workflow accelerators, and operational tools work together seamlessly. That’s how intelligent healthcare workflows take shape: not as a single application, but as a coordinated system designed around how care is actually delivered. Why this direction matters for the developer ecosystem Dragon Copilot is emerging not just as a healthcare AI experience, but as a platform that brings together workflow intelligence and ecosystem extensibility. By connecting directly into operational healthcare workflows and enabling integration through Microsoft Marketplace, it creates new opportunities for healthcare developers, enterprise architects, and workflow automation providers to build solutions that are both targeted and scalable. While the ecosystem is still evolving, the strategic direction is becoming increasingly clear: AI agents and connected applications are moving closer to the workflow layer itself. In healthcare, that proximity matters. The solutions that integrate most naturally into day-to-day operations, rather than existing alongside them, are the ones most likely to drive meaningful adoption and long-term impact. Watch the full session For organizations building healthcare software, enterprise AI systems, workflow automation platforms, or operational healthcare technologies, the Microsoft Marketplace Customer Office Hour session provides valuable insight into how Microsoft is approaching healthcare AI at ecosystem scale. 👉 Learn more and watch the full session here: Healthcare innovation with Dragon Copilot and Microsoft Marketplace Additional Resources You can learn more through Microsoft Marketplace, the Marketplace Customer Office Hours series, the Microsoft Marketplace Community, and the Dragon Copilot apps and agents resources.Step-by-Step: Setting Up GitHub Student and GitHub Copilot as an Authenticated Student Developer
To become an authenticated GitHub Student Developer, follow these steps: create a GitHub account, verify student status through a school email or contact GitHub support, sign up for the student developer pack, connect to Copilot and activate the GitHub Student Developer Pack benefits. The GitHub Student Developer Pack offers 100s of free software offers and other benefits such as Azure credit, Codespaces, a student gallery, campus experts program, and a learning lab. Copilot provides autocomplete-style suggestions from AI as you code. Visual Studio Marketplace also offers GitHub Copilot Labs, a companion extension with experimental features, and GitHub Copilot for autocomplete-style suggestions. Setting up your GitHub Student and GitHub Copilot as an authenticated Github Student Developer
