Visual Studio Enterprise Monthly Azure Credits
Please confirm that all developers of MS partners are losing the individual Azure credits (150$ monthly) in the new MAICPP benefits. We just realized that our team will lose the ability to test Marketplace solutions, and now, in the time that we are trying to enforce the usage and explore the AI technology possibilities, it will set us back a lot. Also, the increased bulk credits do not add up, since we have 35 developers who are using these credits, totaling 63k$ per year, opposed to the 16k$ increase of bulk credits (we have 4 areas) is a significant loss. How come Microsoft decided to stop supporting the development? Is there any way to change these new benefits? Or is there a way to keep these Azure credits, maybe with an Enterprise agreement?Why build your AI apps and agents with Microsoft
Customer demand for AI solutions is accelerating rapidly, Microsoft has seen 2x growth in customers purchasing AI products. Organizations are looking for trusted, enterprise-ready platforms to support their innovation. Microsoft's AI-native ecosystem, backed by industry leading security, Responsible AI principles, and rapidly growing catalog of AI apps and agents, provides a strong foundation for building scalable, compliant, and high-impact AI solutions. Explore how developers and software companies can take advantage of Microsoft's integrated tools, streamlined publishing experience, and expansive Marketplace reach to deliver AI solution that meet customers where they are. Learn more and read the full article: Discover why to build AI apps and agents with Microsoft and sell through Marketplace | Microsoft Community HubHow do you actually unlock growth from Microsoft Teams Marketplace?
Hey folks 👋 Looking for some real-world advice from people who’ve been through this. Context: We’ve been listed as a Microsoft Teams app for several years now. The app is stable, actively used, and well-maintained - but for a long time, Teams Marketplace wasn’t a meaningful acquisition channel for us. Things changed a bit last year. We started seeing organic growth without running any dedicated campaigns, plus more mid-market and enterprise teams installing the app, running trials, and even using it in production. That was encouraging - but it also raised a bigger question. How do you actually systematize this and get real, repeatable benefits from the Teams Marketplace? I know there are Microsoft Partner programs, co-sell motions, marketplace benefits, etc. - but honestly, it’s been very hard to figure out: - where exactly to start - what applies to ISVs building Teams apps - how to apply correctly - and what actually moves the needle vs. what’s just “nice to have” On top of that, it’s unclear how (or if) you can interact directly with the Teams/Marketplace team. From our perspective, this should be a win-win: we invest heavily into the platform, build for Teams users, and want to make that experience better. Questions to the community: If you’re a Teams app developer: what actually worked for you in terms of marketplace growth? Which Partner programs or motions are worth the effort, and which can be safely ignored early on? Is there a realistic way to engage with the Teams Marketplace team (feedback loops, programs, office hours, etc.)? How do you go from “organic installs happen” to a structured channel? Would really appreciate any practical advice, lessons learned, or even “what not to do” stories 🙏 Thanks in advance!Discover why to build AI apps and agents with Microsoft and sell through Marketplace
Customer demand for AI is accelerating fast. And your company's AI app or agent should be there to meet it. In this fiscal year, Microsoft has already seen 2x growth in customers purchasing AI products through Microsoft Marketplace, while also being the largest catalog of AI apps and agents in the industry. Building AI apps and agents isn’t just about model performance or speed to market. It’s about meeting your customers’ needs when they have them. For software companies, success depends on whether your AI solution is secure, compliant, responsibly designed, and ready to scale in real-world work environments. That’s why App Advisor starts by showing the many reasons why building with Microsoft is the right foundation for AI apps and agents. Why building AI apps and agents with Microsoft is different Microsoft, named an AI Leader by Gartner, brings together AI innovation, Responsible AI, and enterprise-grade security into a single, integrated platform. This matters when you’re quickly building AI-powered experiences and agents that your customers can trust. When you build with Microsoft, you’re building on an AI-native platform designed for production use: Industry-leading AI and agentic capabilities supporting Gen AI, RAG, ML, predictive analytics, and multi-modal agent workflows, Integrated developer tools to help teams ship faster that you already use and trust (like GitHub Copilot, Visual Studio, and Microsoft Foundry), Seamless integration across the Microsoft stack to make it easier to connect data, services, and user experiences without stitching different systems together. This foundation helps you focus on what you’re building. Microsoft handles the complexity behind the scenes. Build confidently from day one, stay up to date with AI best practices Building with AI doesn't have to be risky. Data access, model behavior, governance, and compliance all matter more when AI and agents are embedded directly into customer workflows. Microsoft approaches this with end-to-end security and Responsible AI practices that are integrated throughout the development lifecycle. That's why App Advisor and Microsoft keep you up with the speed of designing with AI: Principles to design your own AI Center of Excellence, Sessions focused on the future of AI and agents in the AI Tour, Resources and webinars, like the AI envisioning sessions, to keep you current. This is especially critical for software companies selling into regulated or security-conscious industries. Security isn't an afterthought. You’re building on a platform where they’re already part of the system. How App Advisor can help answer questions about building AI apps and agents The first step in App Advisor is intentionally focused on clarity. Instead of jumping straight into tooling or publishing requirements, it helps you evaluate: Why Microsoft is the right platform for AI apps and agents, How building with Microsoft assists in development, scaling, and customer trust, What kinds of opportunities exist in the Microsoft Marketplace and how to maximize on them. However, App Advisor doesn’t stop at discovery or development. The same experience that helps you build AI apps and agents also supports growth through the Microsoft Marketplace—giving you access to global customers, streamlined procurement, and enterprise-ready distribution. From first line of code to go-to-market readiness, the platform is designed to support sustainable, scalable growth with confidence. Ready to build your AI app or agent? When you start with the right foundation, everything that follows moves faster—and with less risk. Start with the fundamentals: realize the potential of building with Microsoft with curated guidance in App Advisor We look forward to seeing your AI app or agent on Microsoft Marketplace!Explore the latest on SharePoint Embedded security
Security remains a top priority as organizations expand their content applications and workflows. This article outlines how the platform protects content through robust access controls, tenant isolation, data residency, compliance features, and Microsoft 365–integrated governance. For software developers building apps and AI agents for Microsoft Marketplace this Q&A guide provides details on the security capabilities build into SharePoint Embedded that help ensure solutions meet enterprise grade security and compliance expectations from day one. If you're evaluating content platform architectures or looking to strengthen your organization’s security posture, this guide offers clear insights into how SharePoint Embedded safeguards data across its lifecycle. Read the full blog post: SharePoint Embedded security features: A comprehensive Q&A guide | Microsoft Community HubMigrating your AWS offer to Microsoft Marketplace - AWS to Azure service comparisons
As an Independent Software Vendor (ISV), expanding your Marketplace offer's reach beyond AWS Marketplace by replicating to Microsoft Marketplace offers exciting opportunities to grow your customer base. With millions of customers across a global network of businesses and industries, Azure presents a thriving platform to enhance your app’s visibility and functionality. This post is part of a series on replicating apps from AWS to Azure. View all posts in this series. Boost your growth and access more customers by replicating your AWS app to Azure and selling through Microsoft Marketplace. This guide will compare commonly used AWS and Azure components, highlighting differences, to help you replicate your app quickly and easily to prepare it for publishing on Microsoft Marketplace. Future posts will dive deeper into each component area. To ensure a seamless app replication, start by reviewing the marketplace listing requirements. Understanding the key differences between AWS and Azure will help you transition and optimize performance on Azure while benefiting from its unique advantages. This guide will outline these differences, highlight similar services, and offer steps for a seamless replication or migration. You can also join ISV Success to get access to over $126K USD in cloud credits, AI services, developer tools, and 1:1 technical consults to help you replicate your app and publish to Marketplace. The benefits of replicating or migrating to Microsoft Marketplace Migrating to Marketplace unlocks a wealth of opportunities for ISVs. The Azure ecosystem offers several advantages, including: Global reach: Azure’s vast global network of data centers ensures high availability and low-latency access to your application for customers worldwide. Cost efficiency: Azure’s flexible pricing models and cost management tools allow ISVs to optimize their cloud spending. Scalability: With Azure’s powerful compute and storage options, you can scale your application effortlessly to accommodate growing demand. Security and compliance: Azure’s comprehensive security tools and certifications help you meet industry-specific compliance standards, ensuring that your application is secure and trusted. Meet where your customers are: Deploy into customer subscriptions, making your solution more integrated to customer workload. AWS vs. Azure AWS and Azure are the top cloud platforms with diverse services for developers and businesses. Below, we will highlight key areas where AWS and Azure differ—and how to leverage Azure services—when moving your Marketplace offer from AWS to Microsoft Marketplace. Microsoft Marketplace capabilities In Azure, ISVs can leverage metered billing to charge customers based on actual usage, similar to AWS's pay-as-you-go model. This flexible pricing model is ideal for SaaS solutions. Partner Center offers tools for setting pricing models, tracking usage, and adjusting billing. It also provides anomaly detection to help partners identify unexpected usage and ensure transparent billing. When creating SaaS offers in Marketplace, ISVs can define plans with various pricing strategies, such as usage-based or flat-rate billing. These plans, or SKUs, can be customized through free trials, BYOL (Bring Your Own License), or vCPU-based pricing for virtual machines. Both Azure and AWS allow flexible, metered billing based on usage. Azure also provides the ability to set customer discounts or negotiated pricing. Using Partner Center, you can configure and manage these offerings, providing flexibility for customers and partners to scale as needed. Like AWS Control Tower, Azure Lighthouse enables service providers to manage multiple customer Azure environments securely and at scale, offering enhanced visibility, control, and automation. For usage-based monthly billing, you can choose from predefined or custom pricing options (using metered billing APIs). Predefined options like per core, per node, or per pod let Microsoft bill customers based on hourly usage, billing them monthly. Learn more about usage-based pricing here: Setting Plan Pricing. Mapping AWS services to Azure services Your Marketplace offer may use multiple AWS services, and you can build the same offer using Azure services. However, this requires careful mapping to ensure your application functions seamlessly in the Azure environment. Here’s a quick overview of how popular AWS services map to Azure:: Networking: AWS VPC → Azure Virtual Networks (VNets) Compute Services: AWS EC2 → Azure Virtual Machines (VMs), Azure App Services (for web apps) Storage: Amazon S3 → Azure Blob Storage, Azure Data Lake Storage (for big data) Identity Management: AWS IAM → Entra ID Containers: EKS and Elastic Beanstalk → AKS and Azure App Services Serverless: AWS Lambda → Azure Functions Databases: Amazon RDS → Azure SQL Database, Azure Cosmos DB (for NoSQL) Azure for AWS professionals provides you with a more comprehensive mapping of different services. Let's take a deeper look into each of these areas. Cloud architecture and networking One of the primary differences between AWS and Azure lies in their cloud architecture and networking models. AWS uses Virtual Private Clouds (VPCs) to create isolated networks, while Azure employs Virtual Networks (VNets). Both services perform similar functions, but they have different terminologies and setups. For instance, in Azure, you'll be working with VNet Peering, Network Security Groups (NSGs), and Azure VPNs for secure networking. The goal is to map your AWS VPC setup to Azure VNets with ease. AWS needs a Nat Gateway for egress access whereas Azure does not need a Nat Gateway for default egress. AWS Subnets are pinned to Availability Zones (AZs) whereas Azure Subnets span across the AZs. Compute services: EC2 vs. Virtual Machines (VMs) AWS EC2 instances are one of the most widely used compute services, allowing you to run applications on virtual servers. In Azure, the equivalent service is Azure Virtual Machines (VMs). While both offer scalable compute resources, the key differences are in the range of VM sizes, configurations, and the management interface. When migrating from AWS EC2 to Azure VMs, it's important to assess the appropriate Azure VM sizes and configurations that match the performance of your EC2 instances. Additionally, Azure VMs support Azure Resource Manager (ARM) templates, which provide more automation for resource management. For those who have utilized EC2's Auto Scaling feature, Azure provides similar functionality through Azure Scale Sets. Storage: S3 vs. Blob Storage For object storage, AWS uses Amazon S3, while Azure uses Azure Blob Storage. Both services serve the same purpose — storing large amounts of unstructured data — but the underlying configurations, security features, and cost structures differ. While migrating from S3 to Blob Storage, it’s important to review your storage needs and adjust your application accordingly. Azure Blob Storage offers Cool and Archive tiers, which can be a great way to optimize storage costs for infrequently accessed data, and Azure's data redundancy options ensure high availability and durability. The Azure Storage Explorer tool also makes it easier for ISVs to manage their data after migration. Identity and Access Management (IAM) & billing: IAM vs. Entra ID IAM services on AWS and Azure differ in how they manage roles and permissions. AWS uses IAM for users, roles, and policies, while Azure uses Entra ID for IAM across cloud services. AWS organizes accounts through AWS Organizations, with IAM used for role-based access control (RBAC) and policies for service access. Azure’s structure involves Subscriptions and Management Groups, with Entra ID managing identity and access. Azure uses RBAC to assign roles at various levels (Subscription, Resource Group, Resource) and Azure Policies for governance and compliance. Azure Entra ID integrates with Microsoft services, like Office 365, SharePoint, and Teams, supporting identity federation, multi-factor authentication, and RBAC for granular permissions. It enhances governance and security across platforms. Azure handles billing management via subscriptions providing access to resources and can be reassigned to new owners. It offers three classic subscription administrator roles for resource access and management for billing and resource access. Container management: Elastic Beanstalk vs. Azure App Services and EKS vs. AKS For containerized applications, AWS offers Elastic Beanstalk for easy application deployment and management. Azure’s equivalent services include Azure App Services for simple web application hosting and Azure Kubernetes Service (AKS) for container orchestration. While Azure App Services is more suitable for traditional web applications, AKS provides a robust and scalable solution for microservices and containerized applications, similar to AWS’s Elastic Kubernetes Service (EKS). ISVs who are accustomed to Elastic Beanstalk for deploying containerized applications will find Azure App Services or AKS a seamless alternative, with Azure offering rich integrations with DevOps pipelines, CI/CD workflows, and container registries. Serverless: AWS Lambda vs. Azure Functions Both AWS and Azure support serverless computing, which allows developers to run code without managing servers. AWS offers Lambda, while Azure offers Azure Functions. Both services allow you to trigger code in response to events, such as file uploads or API calls. The key difference is that Azure Functions integrates deeply with other Azure services, such as Azure Logic Apps and Azure Event Grid. If your application leverages AWS Lambda, you will find that Azure Functions can serve as an excellent equivalent. Azure also provides Durable Functions, which extend Azure Functions for stateful workflows. Migrating from AWS Lambda to Azure Functions typically requires mapping your event-driven functions and configuring their triggers in the Azure ecosystem. Databases: RDS vs. Azure SQL and Cosmos DB When it comes to databases, AWS offers Amazon RDS for relational databases, and Amazon DynamoDB for NoSQL. Azure provides several alternatives, including Azure SQL Database for relational storage and Azure Cosmos DB for NoSQL storage. Both platforms support database scalability, automated backups, and high availability. If you are using Amazon RDS with services like MySQL or PostgreSQL, you can migrate to Azure Database for MySQL or Azure Database for PostgreSQL. Similarly, if you are using AWS DynamoDB, Azure’s Cosmos DB offers a global, scalable NoSQL database with low-latency access. Messaging: AWS SQS vs. Azure Service Bus Messaging services are crucial when your application handles high-throughput, asynchronous communication between different components. AWS offers Simple Queue Service (SQS) for messaging and SNS for pub/sub notifications while Azure offers Azure Service Bus and Azure Event Grid. Azure Service Bus provides similar functionality to SQS but offers additional capabilities like advanced message routing, dead-lettering, and sessions for handling ordered messages. If your application relies on a queuing mechanism for inter-service communication, you’ll want to map AWS SQS to Azure Service Bus. For event-driven architectures, Azure Event Grid can connect different services and trigger actions across Azure services. Security: Protecting your application on Azure When migrating from AWS to Azure, security is paramount. Both platforms offer strong frameworks to protect data, apps, and infrastructure. Azure provides a suite of integrated security services to maintain high security while enabling cloud scalability. AWS offers AWS Shield and WAF for DDoS and web application firewalls, while Azure offers Azure DDoS Protection and Azure Firewall for similar threat prevention. Azure Security Center monitors your security posture, and Azure Sentinel provides cloud-native SIEM (Security Information and Event Management) for threat detection and response. Microsoft Defender for Identity and Azure Entra ID Identity Protection integrate with Entra ID, ensuring your app security is tightly linked to user identity and governance. Compliance: Meeting regulatory standards on Azure Ensuring compliance with industry standards and regulations is crucial for many ISVs. Azure provides a robust compliance framework that aligns with global standards to meet the most stringent requirements. Whether your application deals with sensitive data or operates in highly regulated industries, Azure’s comprehensive compliance offerings can help you achieve the necessary certifications. Azure complies with key standards such as: GDPR HIPAA SOC 1, 2, and 3 ISO 27001 and other ISO standards FedRAMP Azure provides tools like Azure Policy for governance and Azure Blueprints for complex regulatory requirements. It offers a similar set of compliance certifications to AWS, with a stronger integration into Microsoft enterprise tools, easing compliance for businesses in regulated sectors. For apps handling sensitive data, use Azure Security and Compliance Blueprint to ensure regulatory adherence. Azure’s Compliance Manager helps track and manage compliance, simplifying the process of meeting industry standards. Key resources SaaS Workloads - Microsoft Azure Well-Architected Framework | Microsoft Learn Metered billing for SaaS offers in Partner Center Create plans for a SaaS offer in Azure Marketplace Metered billing with Azure Managed Applications Set plan pricing and availability for an Azure Container offer in Microsoft commercial marketplace - Marketplace publisher Configure pricing and availability for a virtual machine offer in Partner Center - Marketplace publisher Overview - CSP marketplace - Partner Center Azure for AWS professionals - Azure Architecture Center Azure networking documentation Microsoft Entra ID documentation - Microsoft Entra ID Azure security documentation Azure compliance documentation Azure Storage Documentation Hub Microsoft Azure container services documentation Azure serverless - Azure Logic Apps Migration examples Get over $126K USD in benefits and technical consultations to help you replicate and publish your app with ISV Success Maximize your momentum with step-by-step guidance to publish and grow your app with App AdvisorReplicating your AWS application to Azure: key resources for software development companies
Azure offers a broad global footprint, strong security and compliance foundations, flexible cost options, and the ability to deploy your solution directly into a customer’s subscription for tighter integration with their environment. While Microsoft Marketplace expands your reach instantly by connecting your solution to millions of customers across Microsoft’s global ecosystem. It also provides deeper integration with Azure services and a unified experience that makes it easier for organizations to discover, purchase, and deploy your app. You can scale with channel-led sales by extending your reach through an ecosystem of 500K+ partners through a variety of sales models. With ISV Success, you can also accelerate replication with cloud credits, AI services, and hands on technical guidance. Understanding how AWS and Azure services align — across networking, storage, identity, regions, and marketplace requirements — helps ensure a smooth replication process. This post highlights key resources that compare AWS and Azure components, outline migration considerations, and guide you through preparing an Azure‑ready version of your application. Essential guides for AWS‑to‑Azure replication To get started, here is a curated set of resources that cover architecture differences, identity, security, networking, regions, and marketplace publishing — all designed to help you build an Azure‑ready version of your existing AWS application. App replication foundations Advantages of replicating your app from AWS to Azure Guide to replicating your app from AWS to Azure Quick‑start toolkit for AWS‑to‑Azure replication Architecture & service mapping AWS to Azure service comparisons Storage migration paths AWS‑to‑Azure network design Region selection for AWS developers Identity & Security Identity and Access Management AWS‑to‑Azure security model comparison Marketplace Enablement Publishing and selling through Marketplace Step-by-step curated guidance through App Advisor These resources provide a complete starting point for understanding how to replicate your AWS‑based application to Azure, from comparing services and configuring infrastructure to preparing your Marketplace listing and extending your multi-cloud reach. Want more? Start coding in minutes with code templates, solution architecture, and how-to articles to start coding in minutes? Visit the AWS to Azure replication code library in the Quick-Start Development Toolkit.Key AI announcements for software developers from Microsoft Ignite 2025
At Microsoft Ignite 2025, Microsoft unveiled a series of AI innovations that signal a significant evolution in how software developers build, deploy, and scale intelligent solutions. Central to these announcements is Microsoft Foundry, a unified platform designed to simplify the development, orchestration, and governance of AI agents across Microsoft’s cloud and application ecosystem. The announcements also introduced Foundry IQ, enabling secure, compliant access to enterprise data for AI agents, along with a new Foundry Control Plane that provides centralized visibility and operational control. Together, these capabilities help reduce complexity while supporting enterprise-grade security, compliance, and scalability requirements. Additional highlights include expanded model choice and flexibility through enhanced Model Router support and deeper integration of third-party models, as well as new capabilities that allow developers to publish and distribute AI agents directly into Microsoft 365 and Teams, creating powerful new go-to-market opportunities. Read the full article to learn more about these Microsoft Ignite announcements, what they mean for software developers, and how to take advantage of Microsoft’s rapidly evolving AI and Marketplace ecosystem.
Microsoft Ignite 2025 AI announcements: What software developers need to know
Igniting what’s next: What software development companies need to know about Microsoft’s AI announcements at Ignite 2025 The AI landscape took a major leap forward at Microsoft Ignite 2025, and for software development companies and digital natives, the announcements represent a massive opportunity: faster innovation, simplified agent development, access to enterprise‑ready AI platforms, and a dramatically expanded ecosystem to build on. This year, Microsoft introduced the era of agentic AI—and software companies are at the center of this shift. Ignite 2025 formally unveiled Microsoft Foundry, our unified platform for building, governing, and scaling intelligent agents. From new agent runtimes to multi‑agent orchestration, enterprise‑grade knowledge access, and one‑click publishing to Microsoft 365, the momentum creates one clear signal: 💡 AI assistants are becoming intelligent agents—and Foundry is the platform software companies will use to build them. Why Microsoft Ignite 2025 mattered for software companies Across every session, Microsoft doubled down on helping partners accelerate time‑to‑market with agentic AI solutions. Whether you’re building vertical apps, automation copilots, knowledge systems, or developer tools, the new capabilities in Foundry eliminate much of the heavy lifting associated with retrieval, orchestration, compliance, hosting, and model selection. Key themes this year from Azure AI: Unified agent platform across all Microsoft clouds Framework‑agnostic development (bring your own models, tools, or frameworks) Enterprise‑grade governance built into the lifecycle Open ecosystem and interoperability using MCP, A2A, OpenAPI Seamless distribution through Microsoft 365 and Teams Let’s break down what’s new—and what it means for your product strategy. Top announcements for software companies at Ignite 2025 Microsoft Foundry: A unified brand for AI agent development Azure AI Foundry is now Microsoft Foundry—a consolidated platform for building, deploying, and managing intelligent agents. For software companies, this means: One consistent developer experience Shared governance and compliance across products A more integrated ecosystem for publishing and distributing agentic solutions This rebrand isn’t cosmetic—it reflects Microsoft’s strategic shift to deliver a platform built explicitly for the next generation of AI agents. Introducing Foundry IQ: Your enterprise knowledge engine One of the most exciting announcements is Foundry IQ, a new engine that gives agents instant access to enterprise data from SharePoint, OneLake, ADLS, and the web, all governed by Purview. For software companies, this unlocks: Reliable, production‑grade knowledge retrieval without building RAG pipelines Consistent compliance and security models Faster customer onboarding with fewer integration gaps Foundry IQ is a game‑changer for teams who have spent months building retrieval layers or maintaining custom RAG components. Foundry Control Plane: Unified governance for all agents Now in public preview, the Foundry Control Plane enables teams to manage agents across frameworks, clouds, and environments. Highlights: Unified visibility and observability Built‑in security & compliance (Defender, Purview) Fleet‑wide monitoring for cost, health, and risk For software companies offering multi‑tenant solutions or operating in regulated industries, this dramatically simplifies the operational burden of managing AI agents. Agent Framework (public preview): SK + AutoGen, Unified The Microsoft Agent Framework, now in public preview, merges the strengths of Semantic Kernel and AutoGen into a single SDK for building durable, interoperable agents. Software companies gain: A consistent programming model Durable memory Strong interoperability with MCP, A2A, OpenAPI Framework‑agnostic design This is the developer foundation for future AI applications built on Microsoft clouds. Hosted Agents: Enterprise‑grade runtime, no infrastructure needed With Hosted Agents, teams can deploy custom‑code agents directly into a fully managed runtime—no containers, pipelines, or infra setup. What this enables for software companies: Faster deployment cycles Secure, autoscaling environments Simple onboarding for customer‑specific agents Observability and monitoring built in This drastically reduces the operational overhead many software companies face today. Multi‑agent workflows & connected intelligence Ignite 2025 introduced major advancements in multi‑agent orchestration: Built‑in memory across sessions A catalog of 1,000+ Microsoft & partner tools (with private catalogs for software companies) Visual and programmatic orchestration tools Enterprise‑ready coordination for long‑running workflows Foundry IQ for instant knowledge access This allows software companies to design more autonomous, intelligent, and interconnected systems—moving beyond assistants toward true digital workers. Model Router GA + Anthropic partnership expansion There are two major updates for model flexibility: Model Router GA Now supporting 11,000+ models, the router helps developers intelligently choose the best model for each task, optimizing both cost and performance. Anthropic Claude models in Foundry Claude Sonnet 4.5, Opus 4.1, and Haiku 4.5 are now integrated into Microsoft Foundry through an expanded partnership with Anthropic. This gives software companies more choice, capability, and model‑agnostic development paths. One‑click publishing to Microsoft 365 & Teams One of the biggest wins for software companies: Agents built in Foundry can now be published to Microsoft 365 and Teams Chat with one click. This means: Access to hundreds of millions of users Unified governance through Microsoft Admin Center Seamless integration with Copilot experiences For software companies, this is a massive new distribution channel. Why this matters for software development companies Ignite 2025 didn’t just introduce new products—it signaled a platform shift. software companies now have: A full-stack platform for agentic applications - From data access to orchestration, hosting, deployment, and compliance. A unified runtime and SDK - Reducing fragmentation and speeding up development cycles. Enterprise reach through Microsoft 365 - Making your agents as discoverable as apps. A rapidly expanding ecosystem - More models, more tools, more integration points. If you’re building AI-powered products, this is your moment. Get hands-on: Sessions & resources for software companies Here are links to top Ignite sessions to dive deeper. Build & Manage AI Apps with Your Agent Factory AI Agents in Azure AI Foundry: Ship Fast, Scale Fearlessly AI‑Powered Automation & Multi‑Agent Orchestration Agent Developer Guide for Foundry Agent Service The Future of RAG with Agentic Retrieval & AI Search What’s next: December Foundry Council Session Join us on Dec 18 for the Ignite Recap session through the Foundry Partner Council. It’s the best opportunity for software companies to: Get deeper into the new capabilities Share partner/DN feedback Join focus groups For more information about the December 18 session, contact foundrycouncil@microsoft.com or visit aka.ms/foundrycouncilNew in App Advisor: Guidance for resale enabled offers (REO)
The latest enhancement to App Advisor introduces guidance for resale enabled offers (REO), helping you understand where reseller-led distribution aligns with your offer strategy. Want to see if REO fits into your sales strategy for 2026? If you're just getting started with REO, you can learn how to: Assess REO as a new sales tool with other negotiated deals in App Advisor Prepare your offer and organization for reseller participation Follow improved, set-up REO steps in Partner Center Scale into new markets with less effort 👉 Go here to read our blog post on how to accelerate your sales growth with resale enabled offers (REO) through guidance in App Advisor.
