Azure Native Integrations: Public Preview of Napster Companion API on Azure
What is Napster Companion API? Napster Companion API is Napster's platform for building Omniagents: persistent, multi-channel AI agents with one identity, one memory, and one set of tools that show up across every channel an end user touches. The same Omniagent meets the customer on the website, in the mobile app, on video, and on the phone line with the same face, the same voice, and the same memory of the last conversation. The Omniagent as a digital worker The clearest way to think about an Omniagent is as a digital worker: It has a role (customer support specialist, sales advisor, internal IT assistant). It carries the memory of past shifts and prior conversations. It has the tools it needs to do the job which include APIs, knowledge bases, ticketing systems, CRMs. It shows up across every surface the end user touches, like a human worker who answers the door, the phone, and the inbox. When something is outside its scope, it hands off to a human colleague with the context already attached and picks the thread back up when the human is done. Use cases for the Companion API Teams are already exploring the Companion API across a wide range of scenarios: Agentic commerce. Agents that guide end users through discovery, recommendations, purchase, and post-sales support all in one continuous conversation across channels. Customer service. Agents that resolve issues end to end, escalate to humans with full context attached, and pick the thread back up across sessions. Internal operations and digital coworkers. Agents that orchestrate workflows, retrieve knowledge, and automate repetitive tasks for the workforce. Capabilities introduced by Napster Companion API The Companion API public preview brings the following capabilities to Azure customers: Persistent multi-channel agents that maintain identity, memory, and context across web, mobile, voice, video, and telephony. Real-time multimodal interactions across voice, video, and text for natural back-and-forth conversation. Tool and API orchestration that lets agents take real actions like opening tickets, updating records, retrieving documents, and triggering workflows. Persona-driven agents with configurable behavior, conversational style, and avatar-based interaction. Knowledge bases and deterministic question-and-answer pairs for grounded, accurate responses on topics where exactness matters. Developer SDKs and a no-code Dashboard for building, testing, deploying, and iterating on agents. Better together: Napster and Microsoft This integration is the result of a long-term Azure-native partnership between Napster and Microsoft. It is not an external service layered onto Azure infrastructure but it is a co-engineered offering designed to help enterprises operationalize persistent AI agents at scale. In practice, the Azure Native integration delivers: Benefit What it means for you Seamless development experience Provision and manage Companion API resources directly from the Azure portal, alongside your other Azure services. Build and operate Omniagents in the Napster Dashboard, reached through single sign-on. Bring your own model or use Napster Hosted Connect your Azure OpenAI realtime deployment on Microsoft Foundry so inference runs in your tenant. Or use the Napster Hosted tier where Napster manages the model for you. Simplified billing Manage Companion API spend through Azure Marketplace, on the same invoice as the rest of your Azure consumption which means no separate procurement, no separate billing relationship. Single sign-on with Microsoft Entra Switch between Azure resources and the Companion API Dashboard without re-entering credentials. Enterprise-ready foundation Built on Azure's compliance, security, and global infrastructure footprint. How it works?    If the player doesn’t load, open the video in a new window: Open video Get started in minutes Provisioning Napster Companion API on Azure takes just a few clicks: Open the Azure portal and search for *Napster Companion API*. Create a new resource and choose your subscription, resource group, region, and pricing tier. Link your Napster organization (or create one as part of resource provisioning). Launch the Companion API Dashboard from the resource overview page using single sign-on, and start building your first Omniagent in the Napster portal. Full step-by-step guidance is available in the Napster Companion API documentation on Microsoft Learn Resources Product documentation: Napster Companion API on Microsoft Learn Quickstart: Create a Napster Companion API resource Azure Marketplace listing: Napster Companion API Napster for partners: napster.com/partners Azure Native Integrations overview: Azure partner solutions What's next This public preview is the first milestone on a broader roadmap. We are eager to hear from early adopters. Try the public preview, build your first Omniagent, and let us know what you think as your feedback will shape what ships next. Get started today by searching for Napster Companion API in the Azure portal.Agent Builder, Copilot Studio, or Azure AI Foundry: How We Decide for Every Client
Every client conversation starts the same way. Someone has seen a demo, attended an Ignite session, or read a press release. They want to build an agent. Then comes the question that derails more projects than any technical challenge: "Which tool should we use?" After deploying agents for clients across industries - insurance, professional services, manufacturing, public sector - we have developed a repeatable framework for answering that question. It is not based on which tool is newest or which has the best marketing. It is based on where projects actually succeed or fail in production. The three tools are not competitors The first mistake most teams make is treating Agent Builder, Copilot Studio, and Azure AI Foundry as a hierarchy - basic, intermediate, advanced. That framing leads to bad decisions. They are not a ladder. They are three distinct tools built for three distinct contexts. The right question is not "which tool is most powerful?" It is "which tool fits this project's constraints?" The framework: 4 questions We evaluate every project against four dimensions before recommending a tool: Who is building it? Where do users live? How complex is the logic? Who owns it after go-live? Agent Builder Copilot Studio Azure AI Foundry Builder profile Maker, no code Developer / power user Pro developer, Python User surface M365 Copilot Chat Teams, web, M365 Copilot Custom app, any surface Logic complexity Simple Q&A, task routing Multi-step flows, connectors Fully custom orchestration Post-go-live ownership Business team IT + Business joint Engineering team Governance M365 Admin Center Power Platform DLP Custom, Azure RBAC When we recommend Agent Builder Agent Builder is the right call when the business team wants to own the agent end-to-end, the use case is bounded, and the users already live inside M365 Copilot Chat. The key advantage is distribution - an Agent Builder agent surfaces natively inside Copilot Chat with zero additional deployment work. No IT ticket, no app registration, no Teams app package. The ceiling is real. Agent Builder does not support complex branching logic, external API calls, or dynamic prompt injection. The moment a client asks "can it also update a record in our CRM?" the answer is usually no. Use it when: The maker owns it, the use case is narrow, and M365 Copilot is already the user's primary surface. When we recommend Copilot Studio Copilot Studio is our default recommendation for the majority of enterprise agent projects. It covers the wide middle ground between no-code simplicity and full-code flexibility - within the Microsoft governance perimeter most enterprise IT teams already control. Power Platform connectors - 1,000+ out-of-the-box connectors means most enterprise data sources are reachable without custom API development M365 Copilot channel - surface a Copilot Studio agent directly inside M365 Copilot Chat, Agent Builder-level distribution with enterprise-grade logic underneath Topic-level governance - fallback behaviors, confidence thresholds, escalation paths configurable without code DLP policy enforcement - the agent operates within the same data loss prevention perimeter as the rest of the Power Platform tenant The most common mistake: under-investing in the knowledge layer. The agent authoring is the easy part. Getting SharePoint content structured, metadata consistent, and documents deduplicated is where most projects hit delays. Budget for it. Use it when: The use case requires connectors, dynamic responses, or M365 Copilot integration - and you want IT to own governance without requiring a developer team. When we recommend Azure AI Foundry Foundry is the right call when you need to bring your own model, build a fully custom orchestration pipeline, or integrate into a surface that has nothing to do with Microsoft 365. In practice, this means one of three scenarios: The client has a model fine-tuned on proprietary data that must be used The agent is embedded inside a custom-built web or mobile application The logic requires Python-level control - complex reasoning chains, multi-agent coordination, custom evaluation loops Foundry projects require a professional developer, take longer, and produce something the business team cannot maintain without engineering support. That is not a reason to avoid it - it is a reason to be honest with the client upfront. Use it when: You need full control of the model, the orchestration, or the surface - and you have a developer team to own it. The question that resolves most debates When a client is torn between Copilot Studio and Foundry, we ask one question: "Who is answering the 2am support call when this breaks in production?" If the answer is a developer, Foundry is viable. If the answer is the IT admin or the business owner, Copilot Studio is the right call. Not because Foundry is unreliable, but because the operational model has to match the tool. More projects fail from ownership mismatch than from technical limitations. What we see go wrong Reaching for Foundry too early. Developers often want full control and reach for Foundry before validating the use case. We have rebuilt several Foundry POCs in Copilot Studio when the production constraints called for it - faster to ship and cheaper to run. Under-scoping Agent Builder. Business teams choose Agent Builder because it looks simple, then hit the ceiling at month two. The re-platform cost is higher than building in Copilot Studio from the start. Ignoring the M365 Copilot channel. Many Copilot Studio projects are deployed as standalone Teams apps when they could surface directly inside M365 Copilot Chat. The distribution advantage is significant and underused. The short version Agent Builder - maker-owned, bounded use case, M365 Copilot surface, fast Copilot Studio - IT + business joint ownership, connectors, production governance, M365 Copilot integration Azure AI Foundry - developer-owned, custom model or surface, full control, higher cost Start with the ownership model. Everything else follows. Elliot Margot - Team Lead Jumpstart, Copilot and Agents at Witivio (Microsoft Partner). Connect on https://www.linkedin.com/in/elliot-margot-52742a156/.Three Tiers, One Platform: Building Agents Together with the Build-Along Series
The Agentic Opportunity Every partner has agent ambition, but a single workshop format cannot serve every builder. Business makers want a fast win without writing code. Citizen developers want to orchestrate real processes across enterprise systems. Pro developers want a code-first surface with evaluations, tracing, and managed identity. Run the wrong session for the wrong audience, and engagement collapses - too abstract for one group, too constrained for another. The Agent Build-Along Series solves that by meeting builders exactly where they are, across three tiers of the Microsoft platform stack. Behind the series sits a self-serve GitHub repository - a curated library of build-along sessions with easy-to-follow, step-by-step instructions, scoped to specific industry scenarios and business functions. Partners pick the scenario that fits the room, clone the assets, and run the session. No bespoke content build, no facilitator guesswork. A Self-Serve Repository for Build-Along Sessions Diagram illustrating three tiers of agent building The repo at Agent Build-Along Github is a self-serve catalog of ready-to-run workshops. Every session is curated for a specific industry and business function, with easy-to-follow instructions a facilitator can pick up and deliver. Pick the combination that matches the room and run the session - the content, scenario, and assets are already there. Sessions are organised across three axes so partners can find the right fit fast: Industry - Financial Services, Healthcare, Retail, Manufacturing, Public Sector, Energy, Professional Services Business function - Sales, Marketing, Finance, HR, Operations, IT, Customer Service Workload - Agent Builder, Copilot Studio and Azure AI Foundry Each session in the repo includes a real-world scenario, step-by-step build instructions, sample data, prompts and configuration, and a facilitator narrative. Clone, brief the room, build the agent - that is the loop. Three Tiers - Meet Builders Where They Are The pyramid is intentional. Builders start where their skills are today and move up as confidence grows. The tier defines platform, audience, duration, and approach - content stays consistent. Tier Platform Audience Duration Approach 1 - Foundation Microsoft 365 Copilot Agent Builder Business makers, end users, departmental teams 60 min No-code 2 - Extend Copilot Studio Citizen developers, power users, ops teams 90 min Low-code 3 - Pro-Code Azure AI Foundry Pro developers, architects, AI engineers 180+ min Code-first Tier 1 - M365 Copilot Agent Builder Author your first agent - no code required. Microsoft 365 Copilot Agent Builder virtual workshop overview, What your customers will build A custom agent scoped to a real workplace scenario Grounded with knowledge sources (SharePoint sites, files, web URLs) Configured with custom instructions and conversation starters Tested in the preview pane and shared with a team Session flow Define → Ground → Refine → Test & Share Prerequisites Microsoft 365 Copilot licence (or Copilot Chat free) Modern browser (Edge / Chrome) A workplace scenario in mind, or use our template Outcome Attendees leave with a working agent they can use immediately, plus a repeatable pattern for future use cases. This is the right entry point for departmental teams who want to operationalise Copilot without engineering involvement. Tier 2 - Copilot Studio Orchestrate multi-step agents across enterprise systems. Microsoft Copilot Studio virtual workshop overview What your customers will build A copilot with generative answers and authored topics Custom actions that call APIs and Power Platform connectors Knowledge sources spanning SharePoint, Dataverse, public web, and enterprise data Channel deployment to Microsoft Teams and a public web embed Session flow Design → Connect → Author → Publish Prerequisites M365 Copilot license with access to Copilot Studio Familiarity with Power Platform helpful, not required A multi-step workflow or process in mind Outcome Attendees leave with a published copilot running in Teams or on the web, plus a pattern for connecting copilots to enterprise systems. This is where citizen developers and ops teams turn manual processes into orchestrated, agent-driven workflows. Tier 3 - Azure AI Foundry Ship a code-first agent with evaluations and observability. What your customers will build A code-first agent with custom tools and function calling Grounding via Azure AI Search and the customer's own data Model selection from the Foundry catalog, with optional fine-tuning Evaluations, tracing, and managed-identity deployment Session flow Provision → Build → Evaluate → Deploy Prerequisites Azure subscription with Azure AI Foundry access VS Code, plus Python or .NET familiarity Sample data or a use case ready to ground on Outcome Attendees leave with a deployed agent - code, evaluations, and tracing in place - plus reusable SDK templates. This is the right tier for architects and AI engineers shipping agents into production with the governance bar enterprise customers expect. How the Repository Works The repo removes the heaviest lift in running these workshops: content creation. Every session is curated against the same three axes - industry, business function, tier - and shipped with step-by-step instructions a facilitator can follow with minimum prep. Industry/Business Function × Tier → Ready-to-run Build-Along Each session in the repo ships with: A real-world scenario grounded in the chosen industry and business function Step-by-step build instructions tuned to the selected tier Sample data the agent can ground against Prompts, conversation starters, and configuration snippets Facilitator narrative so anyone can run the session Need an enterprise agent that can handle integrate with CRM data? There is a curated Copilot Studio session with a deal-desk scenario and sample CRM data. Need a pro-code health care agent? Choose the Foundry session with a patient-flow scenario and a grounded dataset. Same repo, different curated paths - at the right depth for the room. What Attendees Walk Away With Agent-Builder - A working agent in Microsoft 365 Copilot, ready to share with colleagues. Copilot Studio - A published copilot running in Teams or on the web, connected to enterprise systems. Foundry - A deployed Foundry agent with evaluations, tracing, and SDK templates for the next build. In all cases attendees leave with assets - not slides - and the confidence to build the next one without facilitation. Next Steps - Host a Build-Along Pick your tier - Start where your skills are today. Move up the pyramid as confidence grows. Drive Registration – Socialise your Build-Along session to maximise attendance. Show up and build. Bring a real scenario. Customers leave with a working agent to share. Where to Next Browse the self-serve repository of Build-Along sessions - curated by industry and business function, with step-by-step instructions ready to run: Agent Build Along.Pitch Maker Agent: Turn Copilot Chat Signals into Microsoft 365 Copilot Deals
Executive Summary Customers are already using free Copilot Chat at scale, but adoption is often ungoverned and disconnected from the Microsoft 365 workloads where measurable productivity and risk controls live. The Pitch Maker Agent (BETA) helps partners convert Partner Center Copilot growth opportunity signals into customer-ready narratives—reducing pitch preparation from days to minutes and improving consistency across stakeholders (replace with your measured baseline). What it enables (partner outcomes) Turn raw usage signals into an executive business case with clear opportunity, risk, and next steps. Standardize value conversations across IT and business buyers while keeping customer context specific. Accelerate conversion from exploration to governed deployment by anchoring on Microsoft 365 workloads. Why it’s different Evidence-led: uses Partner Center Copilot growth opportunities (ASPX) signals rather than generic prompts. Buyer-ready: outputs a structured narrative (not a feature list) designed for executive alignment and action. Inputs required Partner Center Copilot growth opportunities export (all columns) for the target customer. The Opportunity: From AI Exploration to Enterprise Direction The move from free Copilot Chat to Microsoft 365 Copilot is a timing advantage: customers have intent and familiarity, but need a governed path that ties AI to real work in Teams, Outlook, Excel, and beyond. Advisory gap: translate usage metrics into business insight executives can fund. Governance gap: balance opportunity with security, compliance, and lifecycle controls. Workflow gap: connect AI usage to measurable outcomes inside Microsoft 365 workloads. How the Agent Works (BETA) The Agent follows a simple, repeatable flow to generate an executive-ready pitch narrative from Partner Center Copilot growth opportunity signals. See the agent in action below. In three steps Upload the Partner Center Copilot growth opportunities export (all columns). Run the Agent to translate usage signals into a customer-specific executive narrative. Use the generated business case, recommendations, and next steps in the customer conversation. What the Output Enables Translate Partner Center signals into a fundable business case, faster. Improve executive alignment by presenting opportunity, risk, and plan in one narrative. Increase repeatability across accounts with a consistent structure and messaging. The figure below illustrates how the Agent turns usage signals into a concise, executive-ready pitch narrative and action plan. Figure 1. From Copilot Chat signals to an executive pitch narrative and next-step plan. For customers, the conversation shifts from features to outcomes—clear productivity impact, role-based change, and risk-aware governance. Deployment and Execution The Agent is delivered as a solution package and deployed through Copilot Studio with a straightforward publish-and-run flow. Prepare Partner Center ASPX export (all columns) and validate sensitivity labels. Import the solution package into Copilot Studio. Verify dependencies, publish the Agent, and enable access in Microsoft 365 Copilot and Teams. Run the guided pitch flow by uploading customer data and capturing the narrative output. The run guide provides step-by-step visuals for data preparation, import, publication, and how to use the output in customer conversations. Why This Matters for Partner Practices The Pitch Maker Agent (BETA) supports a repeatable value motion: identify opportunity, align stakeholders, and move customers from experimentation to governed Microsoft 365 Copilot adoption. Higher conversion: clearer executive rationale anchored in evidence and outcomes. Lower effort: less time drafting, more time on discovery and delivery. Better governance: built-in prompts to address risk, readiness, and controls early. Call to Action This week: 15-minute start Locate the solution package and run guide in the Agent folder. Deploy the Agent in Copilot Studio and publish to Microsoft 365 Copilot/Teams. Export Partner Center Copilot growth opportunities data and validate sensitivity labels. Upload the dataset and generate a customer-specific executive pitch narrative. Resources Helpful links to learn more and access supporting materials: Partner Center Copilot growth opportunities data GitHub repository Overview: Run guideScaling Seller Impact with ASPX Insights: From Data Access to AI-Driven Execution
ASPX Insights in Partner Center Most sellers are not constrained by opportunity; they are constrained by time and signal. With up to 70% of effort spent on administrative work, portfolio coverage continues to expand while insight quality declines. Sellers are forced to manually interpret fragmented telemetry across multiple systems, slowing decision-making and reducing precision in where they focus. The result is missed revenue signals, delayed interventions, and inconsistent execution at scale. Productivity is not just about efficiency, it is about enabling every seller to consistently identify and act on the highest-value opportunity, in real time. To drive consistent, data-led growth across Security and AI Business Solutions, partners should connect to ASPX Insights within Partner Center. This provides direct access to adoption propensity models, customer telemetry, and actionable account-level insights across Microsoft 365 Copilot, E7, and Agent 365 scenarios. Access to ASPX Insights is only the starting point. The real value comes from how you operationalise that data and surface it directly to sellers in the flow of work. The most effective pattern is to build a lightweight “opportunity agent” that connects to ASPX data via API and translates telemetry into clear actions. This ensures your sales teams have the right conversation with the right customer at the right time - Conversations that are backed by intelligent insights to help guide your customer's on their AI and security journey. The Architecture ASPX Insights is powered by Partner Center data and exposes rich telemetry and propensity signals that can be accessed programmatically. This allows partners to move beyond dashboards and embed insights directly into seller workflows. As demonstrated in internal adoption patterns, partners can connect to ASPX via API and pull Customer-level adoption and usage telemetry Copilot, Security, and Agent usage signals Propensity scores for expansion, adoption, and conversion Licensing, whitespace, and engagement indicators The M365 Partner API – AI Business Solutions & Security Insights allows partners to ground an agent in real, actionable data rather than static pipeline assumptions. By pulling live telemetry and seat-level signals directly into the agent, the solution continuously reflects actual customer usage patterns - who is adopting, who is stalled, and where there is untapped potential. This means opportunity identification is no longer based on periodic reporting or manual interpretation, but on near real-time behavioural insight. As a result, account prioritisation, upsell motions, and intervention strategies are driven by evidence rather than instinct, enabling account teams to act with precision and focus on the highest-impact opportunities across their portfolio. The agent should act as a translation layer between raw telemetry and seller action. The goal is not to expose more data, but to remove ambiguity and tell the seller exactly where to focus. A simple architecture looks like this: Data layer Ingest ASPX Insights data via API on a daily or scheduled basis. Optionally store monthly snapshots to track trends and smooth out variability. This creates both real-time signal and historical context. With the data layer you have a couple of options. You can integrate directly into Partner Centre ASPX Insights by using the API. This is technically complex and may have a longer lead time to see results. Alternatively, to see results with less complexity, you can simply download snapshots of the data monthly from ASPX Insights in Partner Centre. This is manual but easy to achieve and offers a shorter time to value for your agent. Scoring layer Use ASPX propensity outputs directly or combine them with your own logic to rank accounts across a small set of opportunity lenses Expansion ready (Copilot scale) Conversion ready (free to paid) At risk (low adoption vs paid licenses) Transformation ready (Agent 365 and advanced AI scenarios) These align directly with the machine learning models and signals already surfaced in ASPX. Action layer Translate scores into next best actions Who to engage Why now What motion to run (sell, enable, expand, govern) This is where agents create value. Sellers should not see raw dashboards. They should see prioritised accounts and recommended actions. Internal Adoption Path The key design principle is simple: bring insight into the tools sellers already use. CRM integration Push ranked accounts and recommendations directly into CRM as opportunities, tasks, or account insights. This ensures data becomes part of pipeline management, not a separate activity. Copilot / Agent interface Expose the agent through Microsoft 365 Copilot or a custom chat interface where sellers can ask Which customers should I prioritise this week Which accounts are ready for Copilot or E7 expansion Where are my adoption risks The agent queries the ASPX-backed dataset and returns structured recommendations in seconds. Proactive notifications Trigger alerts based on signal changes Spikes in Copilot usage Drops in adoption for paid tenants New high-propensity accounts entering threshold This shifts sellers from reactive to proactive engagement. Portfolio dashboards (secondary) Maintain dashboards for leadership and planning, but not as the primary interaction model for sellers. Dashboards support strategy, agents drive execution. Extending into E7 and Agent 365 scenarios Once the agent is connected to ASPX, partners can extend the same model across broader solution plays E7 opportunities Use signals such as usage depth, licensing posture, and workload adoption to identify customers progressing toward advanced security and compliance requirements. The agent can flag these accounts as ready for E7-led conversations. Agent 365 opportunities Combine Copilot maturity with agent usage signals to identify customers moving beyond productivity into process automation. These are high-value transformation plays where partners should proactively engage. This ensures sellers are not operating in silos but are guided toward the next logical workload based on real behavior, not assumptions. Where to Next If you lead a partner sales team, connect to ASPX Insights and see how these insights can empower your sales teams to achieve more. Check out our ready made ASPX Insights agent in Github.Microsoft Partners: Accelerate Your AI Journey at AgentCon 2026 (Free Community Event)
Recently, a customer asked me a question many Microsoft partners are hearing right now: “We have Copilot — how do we actually use AI to change the way we work?” That question captures where we are in the AI journey today. Organizations have moved past curiosity. Now they’re looking for trusted partners who can turn AI into real business outcomes. That’s why events like AgentCon 2026 matter. A free, community-led event built by practicioners AgentCon is not a traditional conference. It’s a free, community-driven global event organized by the Global AI Community together with Microsoft partners and ecosystem leaders. Simply put: it’s for the community, by the community. Across cities worldwide, developers, consultants, architects, and Microsoft partners come together to share practical experiences building with AI agents, Copilot, and the Microsoft platform. The focus isn’t theory — it’s implementation: What worked What didn’t What partners can apply immediately with customers This peer learning model reflects how many of us actually grow in the Microsoft ecosystem: by learning from other partners solving real problems. Why this matters for Microsoft partners The opportunity for partners is evolving quickly. Customers aren’t just asking about AI tools — they’re asking how to redesign processes, automate work, and unlock productivity using AI-powered solutions. The Microsoft AI Cloud Partner Program emphasizes partner skilling and helping customers realize value from AI investments. Community events like AgentCon accelerate that learning by bringing partners together to exchange proven approaches and practical insights. When partners upskill faster, customers succeed faster. Why attend AgentCon is designed to help partners move from AI awareness to AI delivery. As an attendee, you can expect: Practical sessions and demos from practitioners Real-world AI and agent scenarios Direct conversations with builders and peers New collaboration and co-sell opportunities You’ll leave with ideas and approaches you can bring directly into customer engagements. Why speak AgentCon thrives because partners share openly with one another. If you’ve implemented Copilot, explored AI agents, or learned lessons from customer deployments, your experience can help others accelerate their journey. Speaking at AgentCon allows you to: Share your expertise with the global partner community Build credibility within the Microsoft ecosystem Create new partnerships and opportunities Contribute to collective partner success You don’t need a perfect story — just an honest one others can learn from. Join the global AgentCon community AgentCon 2026 events takes place around the world including these upcoming events: March 9 - New York: https://aka.ms/AgentconNYC2026 April 11 - Hong Kong: https://aka.ms/AgentconHongKong2026 April 16 - Seoul: https://aka.ms/agentconLondon2026 April 22 - London: https://aka.ms/agentconSeoul2026 Each event is locally organized, community-led, and free to attend. Help shape the next phase of AI adoption AI transformation is happening now — and Microsoft partners play a critical role in guiding customers forward. AgentCon is an opportunity to learn together, share experiences, and strengthen the partner ecosystem driving AI innovation. 👉 Register or apply to speak: https://aka.ms/agentcon2026 We hope you’ll join us — and be part of the community helping customers turn AI potential into real impact.Learn to maximize your productivity at the proMX Project Operations + AI Summit 2026
As organizations accelerate AI adoption across business applications, mastering how Microsoft Dynamics 365 solutions, Copilot, and agents work together is becoming a strategic priority. Fortunately, businesses no longer need to rely on speculation — they can gain practical insights with fellow industry professionals during a unique two-day event: On April 21-22, 2026, Microsoft and proMX will jointly host the fourth edition of proMX Project Operations Summit at the Microsoft office in Munich, but this time with an AI edge. The summit brings together Dynamics 365 customers and Microsoft and proMX experts to explore how AI is reshaping project delivery, resource management, and operational decision‑making across industries. On day one, participants will discover how Dynamics 365 Project Operations, Copilot, Project Online, proMX 365 PPM, and Contact Center can strategically transform business processes and drive organizational growth. On day two, they can explore the technical side of these solutions. Secure your spot! What to expect from the summit Expert-led, actionable insights Join interactive sessions led by Microsoft and proMX experts to learn practical AI and Dynamics 365 skills you can use right away. Inspiring keynotes Gain future-focused perspectives on Dynamics 365, Copilot, and AI to prepare your organization for what’s next. In between our special guests we have Microsoft's Rupa Mantravadi, Chief Product Officer, Dynamics 365 Project Operations, Rob Nehrbas, Head of AI Business Solutions, Archana Prasad, Worldwide FastTrack Leader for Project Operations, and Mathias Klaas, Partner Development Manager. Hands-on AI workshops Take part in workshops where Sebastian Sieber, Global Technology Director (proMX) and Microsoft MVP will show the newest AI features in Dynamics 365, giving you real-world experience with innovative tools. Connect with industry leaders Engage with experts through Q&A sessions, round tables, and personalized Connect Meetings for tailored guidance on your business needs. Real customer success stories Hear case studies from proMX customers who are already using Dynamics 365 solutions and learn proven strategies for successful digital transformation. Who should attend? This summit is tailored for business and IT decision-makers that are using Dynamics 365 solutions and want to drive more business impact with AI, but also for those who might be planning to move away from other project management solutions such as Project Online and need practical guidance grounded in real-life implementations. Date: Apr 21 & 22, 2026 | 2 -Days event Location: Microsoft Munich, Walter-Gropius Straße 5, Munich, Bavaria, DE, 80807 Ready to maximize your productivity? Register here.
