Partner Blog | From Microsoft Build to AI implementation: Build the skills to lead Frontier Transformation
Microsoft Build showcased the next phase of AI transformation. Across AI platforms, agents, and secure development, one message came through: customers are moving from AI exploration to implementation. For partners, that shift creates a practical opportunity. Customers are looking for guidance on ways to design, deploy, manage, secure, and scale AI-powered solutions that create measurable business value. That takes skilled teams, repeatable delivery capabilities, and a clear path from learning to implementation. This month’s skilling updates focus on turning Build momentum into action. New Frontier Transformation Engineering resources, on-demand Frontier Transformation Summit content, upcoming certification preparation, Microskilling, and go-to-market assets give partners multiple ways to strengthen AI implementation capabilities and show customers they are ready to lead. Build Frontier Transformation Engineering capability Frontier Transformation describes the shift from AI pilots to embedded, governed operating models. It requires technical depth across agents, Copilot, Microsoft Foundry, Microsoft IQ, security, governance, and business process transformation. The Frontier Transformation Engineer Badge is designed for technical professionals building this capability. It validates the skills needed to design and deliver AI agents across Copilot Studio, Microsoft Foundry, and the broader Frontier stack. For partners, the badge signals readiness to move from AI vision to execution. To support that journey, all of the Frontier Transformation Engineer Summit sessions are now available on demand, giving your teams a chance to revisit key content or catch up on sessions they missed. Use the recordings to continue progressing toward badge attainment and prepare your teams for the AI implementation work customers are prioritizing now. Continue reading here
FPGA vs ASIC for AI at the Edge: What factors influence your hardware choice?
As AI continues to move closer to edge devices, choosing the right hardware platform has become an important design decision. While both FPGAs and ASICs have their strengths, the best choice often depends on the application's requirements. Here are some of the key factors that engineering teams typically evaluate: Performance and latency requirements Power efficiency Development cost and NRE Time-to-market Production volume Need for future hardware updates FPGAs offer flexibility for rapid prototyping and evolving workloads, making them well-suited for early-stage development. ASICs, on the other hand, can provide significant advantages in performance, power consumption, and cost efficiency for high-volume production. I recently came across a technical article that explains these trade-offs in a structured way and found it useful as a reference: https://www.signoffsemiconductors.com/asic-vs-fpga/ I'd be interested to hear how others approach this decision. Have you migrated a design from FPGA to ASIC? What factors influenced your choice? Are there workloads where you would always choose one over the other?GitHub Copilot App - Canvas Is Not a UI Builder
What if your development environment didn't just help you write code, but helped you observe, steer, and evolve a living system while it runs? That's the shift GitHub Copilot App Canvas represents. Canvas redefines how developers interact with agent-driven software: not by building traditional user interfaces, but by creating interactive environments where humans and AI co-create, test, and iterate in real time. This post walks through a real Canvas extension we built, a Multi-Agent Dev Canvas that demonstrates how Canvas becomes a runtime observability and control plane for an agent-driven system. We'll cover why Canvas exists, how it differs from traditional UI development, and how you can use it to accelerate the design-test-evolve loop for any multi-agent application. The Misconception: "Canvas Is for Building UIs" The first instinct many developers have when they see Canvas is to treat it like a UI framework, a place to build dashboards, boards, or user-facing applications. That's not what Canvas is for. Here's the distinction that matters: Traditional UIs are for using software. They serve end-users who interact with a finished product. Canvas is for shaping software while it runs. It serves developers and AI agents who are actively building, testing, and evolving a system. Canvas solves problems your final UI should never try to solve in a visible way. It's the observability layer, the control plane, the validation surface — all the things you need during development that disappear before production. Think of it this way: you wouldn't ship your debugger to users, but you absolutely need it while building. What We Built: A Multi-Agent Dev Canvas To demonstrate Canvas as a development runtime, we built a Multi-Agent Dev Canvas, a standalone GitHub Copilot Canvas extension (this repo, copilot-canvas-runtime) that treats an entire multi-agent system as a living, observable environment. The same pattern applies to any agent-driven system built on services such as Microsoft Foundry. The Multi-Agent Dev Canvas: a runtime observability and control plane where developers and AI agents collaborate to design, test, and evolve an agent-driven system in real time. The canvas provides four integrated panels: System View: See Your Agents Working Five specialised agents are displayed as live cards with real-time status indicators. Each card shows the agent's name, responsibility, current status (idle, running, done, or error), task count, and last action taken. When an agent is active, its card pulses blue. When it fails, it glows red. You see the system breathe. decompose_system — Breaks requirements into agent tasks execute_workflow — Coordinates agents to perform tasks validate_output — Runs evaluation tests and returns structured results update_system_design — Modifies architecture based on feedback track_state — Persists and updates system state over time Task Flows: Watch Work Move Through the Pipeline Below the agents, a flow graph visualises how tasks route between agents. When you decompose a system requirement like "Build an AI-powered code review agent," the canvas shows five components (pr-ingestion, code-analysis, feedback-generator, learning-loop, notification-service) flowing from the decomposer to the executor and designer agents. Each flow carries a status badge, pending, pass, or fail. Validation Panel: Continuous Testing, Not Afterthought Testing The validation panel displays structured test results with pass/fail badges and reasoning. When you run validation, each test case evaluates against specific criteria: ✅ "PR ingestion handles large diffs" — Meets criteria: process diffs over 5,000 lines without timeout ❌ "Feedback is actionable" — Failed: does not satisfy criteria that each suggestion includes a code fix ✅ "Learning loop converges" — Meets criteria: accept rate improves over 10 iterations ✅ "Notifications are non-blocking" — Meets criteria: delivery latency under 500ms This isn't a test runner you invoke separately, it's a validation surface embedded in the development loop. You see failures the moment they happen, in context, alongside the agents and flows that produced them. Live State Timeline: Every Mutation, Visible The right panel tracks every state change with timestamps. Decomposition events, workflow executions, validation runs, failure injections — all appear chronologically. This is the system's memory, visible to both the human developer and the AI agents working alongside them. Canvas as a Runtime: The Key Capabilities What makes Canvas a runtime rather than a display layer is that the agent can act through it. The canvas exposes seven agent-callable actions: Action What It Does decompose_system Accept requirements and components, generate task flows, update the system design execute_workflow Run pending tasks through the agent pipeline, produce artifacts validate_output Evaluate test cases against criteria, return structured pass/fail with reasoning update_system_design Modify the architecture description, constraints, or component list live track_state Read the full system state — agents, flows, validations, history, artifacts inject_failure Force an agent into an error state to test system adaptation pause_resume Toggle execution on and off The human developer can click Decompose, Execute, or Validate directly in the canvas. The AI agent can invoke the same actions programmatically. Both parties operate on the same surface, the same state, the same system, that's what makes Canvas collaborative in a way traditional tooling is not. Why This Matters: Canvas vs. Figma vs. Traditional UIs It helps to position Canvas against tools developers already know: Figma is Human-to-Human collaboration on design. Multiple people interact with the same visual surface, but nothing executes. It's a design tool. Traditional UIs are Human-to-System. Users interact with finished software through a polished interface. Canvas is Human-to-AI-to-System. It's a shared space where things actually execute. The developer steers, the AI acts, and the system evolves, all visible, all in real time. Canvas is collaborative in the Figma sense — it's a shared space, it's visual, multiple participants interact with the same surface. But unlike Figma, the participants include AI agents, and the surface isn't a mockup — it's a live system. How the Extension Works: Under the Hood A Canvas extension is a standard GitHub Copilot CLI extension, a single extension.mjs file that speaks JSON-RPC over stdio. The key components: 1. State Management Each canvas instance maintains its own system state: agents, task flows, validations, a state history timeline, artifacts, and the current system design. State is held in-memory per instance and pushed to the iframe via Server-Sent Events whenever it changes. function createInitialState() { return { agents: [ { id: "decomposer", name: "decompose_system", status: "idle", responsibility: "Break requirements into agent tasks" }, { id: "executor", name: "execute_workflow", status: "idle", responsibility: "Coordinate agents to perform tasks" }, // ... three more agents ], taskFlows: [], validations: [], stateHistory: [], artifacts: [], systemDesign: { description: "", constraints: [], components: [] }, execution: { paused: false, stepCount: 0 }, }; } 2. Real-Time Updates via Server-Sent Events The canvas runs a loopback HTTP server per instance. The iframe connects to an /events endpoint and receives state updates as they happen — no polling, no websocket complexity. if (req.url === "/events") { res.writeHead(200, { "Content-Type": "text/event-stream", "Cache-Control": "no-cache" }); clients.add(res); // Push current state immediately on connect res.write(`data: ${JSON.stringify(getState(instanceId))}\n\n`); } 3. Dual Interaction Model Every action is available through two paths. The human clicks a button in the iframe, which POSTs to the local server. The AI agent calls invoke_canvas_action through the SDK. Both paths mutate the same state and trigger the same SSE broadcast. Neither is privileged over the other. 4. Canvas Declaration The canvas registers with the Copilot SDK using createCanvas , declaring its identity, description, and all agent-callable actions with JSON Schema validation on inputs: createCanvas({ id: "multi-agent-dev", displayName: "Multi-Agent Dev Canvas", description: "Runtime observability and control plane for multi-agent development", actions: [ { name: "decompose_system", description: "Break requirements into agent tasks", inputSchema: { type: "object", properties: { requirements: { type: "string" }, components: { type: "array", items: { type: "string" } } }, required: ["requirements"] }, handler: async (ctx) => { /* ... */ }, }, // ... six more actions ], open: async (ctx) => { /* start server, return URL */ }, onClose: async (ctx) => { /* clean up */ }, }); Scenarios This Enables The Multi-Agent Dev Canvas supports four development scenarios that would be impossible with traditional tooling: 1. End-to-End Feature Design Tell the agent "Build an AI-powered code review system." Watch it decompose the requirement into five components, route tasks to specialist agents, execute the workflow, and validate the outputs, all visible in real time. Iterate by modifying constraints or components and re-running. 2. Live Agent Collaboration Observation See how agents hand off work to each other. The flow graph shows which agent produced what, which tasks are pending, and where bottlenecks form. This is the kind of observability you need when debugging multi-agent orchestration but would never expose in a production UI. 3. Fault Injection and Adaptation Testing Use inject_failure to force an agent into an error state. Watch how the system responds. Does the orchestrator recover? Do downstream tasks fail gracefully? This chaos-engineering approach, applied during development, visible in real time, catches integration failures before they reach production. 4. Validation-Driven Iteration Define test criteria, run validation, see which tests fail, update the system design, re-run. The validation panel isn't a separate CI pipeline, it's embedded in the development surface, creating a continuous feedback loop between design decisions and their measurable outcomes. Getting Started: Build Your Own Canvas Extension To create a Canvas extension in your own project: Read the SDK docs — Run extensions_manage({ operation: "guide" }) in GitHub Copilot CLI to get the canonical documentation paths. Scaffold — Run extensions_manage({ operation: "scaffold", kind: "canvas", name: "my-canvas", location: "project" }) to generate the boilerplate. Implement — Edit extension.mjs with your canvas logic: state model, actions, renderer HTML, and SSE updates. Reload — Run extensions_reload to activate your changes. Drive — Open with open_canvas , invoke actions with invoke_canvas_action , and iterate. The canvas extension lives in .github/extensions/your-canvas/extension.mjs for project-scoped extensions, or in your user extensions directory for personal use. No package.json needed, the github/copilot-sdk import is auto-resolved. Key Takeaways Canvas is a development runtime, not a UI framework. You don't build Canvas instead of your UI, you use Canvas to figure out, test, and evolve the UI and system before and during building it. Canvas solves problems your final UI should never expose. Agent observability, fault injection, live state mutation, validation feedback loops, these are development concerns, not user concerns. Canvas is Human-to-AI-to-System collaboration. Both the developer and the AI agent operate on the same surface, the same state, the same running system. It's Figma-like collaboration, but with AI agents, and things actually execute. Canvas turns debugging, testing, and execution into a continuous visual feedback loop. Instead of switching between an editor, a terminal, a test runner, and a monitoring dashboard, you have one surface where the system lives and evolves. Canvas extensions are lightweight. A single extension.mjs file, no dependencies, loopback HTTP server with SSE, the infrastructure gets out of the way so you can focus on the system you're building. The Bigger Picture Canvas redefines software development by shifting from writing static code to orchestrating living systems. Developers and AI co-create, observe, and evolve solutions in real time. Instead of building UIs for users, we build interactive environments for agents, turning debugging, testing, and execution into a continuous, visual feedback loop that accelerates innovation and brings ideas to production faster than ever. The Multi-Agent Dev Canvas we built here is one example. The pattern applies anywhere you're building agent-driven systems: AI orchestration, workflow automation, data pipelines, autonomous services. Anywhere you need to see, steer, and validate a complex system as it runs, that's where Canvas belongs. Resources copilot-canvas-runtime — this repository: the Multi-Agent Dev Canvas extension, scenario, and demo prompt GitHub Copilot Documentation — Official documentation for GitHub Copilot features Microsoft Foundry Documentation — Build and deploy AI agents with Microsoft Foundry
Getting Started with AI and MS Copilot - English
🚀 Ready to explore AI and Microsoft Copilot in a fun, hands-on way? Join our session: “Introduction to AI and Microsoft Copilot”—designed for educators who are just getting started! ✅ Learn the fundamentals of generative AI ✅ Master the art of creating effective prompts ✅ Discover practical ways to use these tools in your classroom ✅ Access ready-to-use teaching resources ✅ Practice with 10 interactive exercises 📅 Don’t miss this opportunity to boost your teaching with AI! #MicrosoftCopilot #Educators #Innovation #TeachingTools Getting Started with AI and MS Copilot - English | Meeting-Join | Microsoft TeamsFrontier Transformation campaign in a box now available in Partner Marketing Center
AI transformation is moving beyond isolated experimentation to organization-wide initiatives and customers are looking for partners who can help them scale. Organizations scaling AI are seeing measurable gains across productivity, efficiency, and customer engagement. To support this shift, the Frontier Transformation campaign in a box provides a ready-to-launch, co-branded marketing campaign aligned to Microsoft AI solutions. This campaign is aligned with the Frontier Success framework and engages customers as they advance in their AI maturity, with messaging that connects AI capabilities to real business context while reinforcing trust, governance, and security. Available in Partner Marketing Center Pro, the Frontier Transformation campaign in a box empowers you to go market faster, support lead generation, and build pipeline. Partner Marketing Center Pro is available to partners who have purchased a partner benefits package, attained a Solutions Partner designation or are enrolled in ISV Success. Explore Frontier Transformation campaign in a box.📣 Getting Started with AI and MS Copilot — Português
Olá, 👋 📢 Quer explorar IA e Microsoft Copilot de forma prática para o aprendizado? Participe da sessão “Introdução à IA com o uso do MS Copilot”, pensada especialmente para docentes que estão começando a usar o Copilot. Vamos aprender os fundamentos da IA generativa, como criar boas instruções e aplicar essas ferramentas na sala de aula. 📌 Sessão com exemplos práticos, materiais para utilizar e um espaço ideal para praticar e tirar dúvidas. No horário indicado, favor realizar acesso ao link.📣 MSLE Onboarding Session — Português
Olá, 👋 Espero que estejam bem! ✨Participe da sessão de introdução ao programa MSLE para Educadores! Nesta sessão: ✅ Vamos explorar os benefícios e o alcance do programa ✅ Conhecer em detalhe os dois portais principais aos quais você terá acesso ✅ Esclarecer todas as suas dúvidas em um ambiente colaborativo Este é o seu primeiro passo rumo a uma experiência enriquecedora, onde conhecimento, inovação e comunidade se unem para impulsionar você ao próximo nível. No horário indicado, favor realizar acesso ao link.Ability Summit 2026: Accessibility-first innovation and your next partner opportunity
Accessibility is increasingly both a business imperative and a meaningful commercial opportunity for partners. At this year’s Microsoft Ability Summit, leaders across technology, education, and advocacy reinforced a clear point: accessibility-first innovation is creating new demand across AI, collaboration, learning, and customer experience. For partners, accessibility represents a clear opportunity to grow customer value. Accessibility-first innovation is becoming a mainstream expectation, opening opportunities to build differentiated services and solutions across AI, collaboration, learning, compliance, and customer experience. Organizations are increasingly viewing accessibility as part of a broader shift in how they approach AI, employee experience, and customer engagement. For partners, that shift creates an opportunity to lead higher-value conversations around innovation, trust, and long-term business impact. I encourage you to read Microsoft Chief Accessibility Officer Neil Barnett’s full recap of this year’s announcements and stories from the summit, including updates across AI, developer tools, Windows, devices, learning, Xbox, and inclusive packaging design. Why accessiblity matters for partners now Accessibility is becoming part of how customers evaluate experience quality, employee productivity, compliance expectations, and technology trust. Organizations are looking for technology that works consistently across real-world scenarios, roles, abilities, and environments. That expectation is accelerating as AI adoption grows. Accessibility is increasingly becoming part of how customers evaluate transformation readiness, technology trust, and the quality of the experiences they deliver across their organizations. A 2026 Forrester Consulting study commissioned by Microsoft found that assistive technology is already part of everyday work and life. Consumers reported using assistive features across at least six activities in the past month, on average. The same study found that 63% of respondents reported some level of difficulty with daily tasks related to vision, hearing, learning and cognition, mobility, and/or mental health. It also found that 71% of respondents would use assistive tools more often if enhanced with AI capabilities, and 55% said they feel a stronger commitment to employers when companies prioritize assistive tools and features. For partners, this points to a broader opportunity. Accessibility-first design can expand participation, strengthen employee and customer experiences, and build greater trust in technology, making it an increasingly important part of long-term transformation strategy. Where partners can lead The opportunity for partners is to bring accessibility into the conversations that are already shaping customer priorities, including AI transformation and adoption, modern work, application innovation, employee experience, customer engagement, and compliance. As accessibility becomes more central to business and technology strategy, partners can differentiate by making it part of the broader value they bring to customers. Partners that bring accessibility-first innovation into these conversations can deepen trust, expand strategic relevance, and create more differentiated value over time. This opportunity spans organizations of every size. Across both SMB and enterprise customers, accessibility is increasingly part of how leaders think about growth, workforce experience, customer connection, and technology modernization, and the Microsoft partner ecosystem is well positioned to meet that need. Partner opportunities in Microsoft Marketplace Microsoft Marketplace offers a useful view into how partners are translating accessibility-first innovation into practical customer value. The examples below illustrate how that opportunity is taking shape across different business and technology scenarios. Level Access makes digital accessibility a streamlined, scalable part of everyday operations The Level Access platform supports a continuous approach to accessibility, embedded into design, development, governance, and training workflows. Unlike point tools or episodic audits, this integrated solution helps organizations accelerate remediation, reduce risk, and demonstrate progress over time. Organizations can extend the power of the Level Access platform through private offers with capabilities such as LevelDocs for accessible content creation and remediation in Microsoft Word, Excel, and PowerPoint; LevelCI for automated web accessibility testing within CI/CD pipelines; and Mobile Testing for native iOS and Android accessibility across physical and virtual devices. Retain Connector by Inclusively Many organizations have invested heavily in benefits, workplace accommodations, mental health resources, and employee support programs. But employees, especially those navigating disabilities or workplace barriers, often don't know what is available or how to access it. Retain Connector by Inclusively closes that gap directly inside the tools employees already use. Deployed within Microsoft Teams, SharePoint, Outlook, and Microsoft 365 with no heavy integrations required, Retain acts as a workforce intelligence layer that lets employees describe their needs in plain language and get routed to the right benefits and resources through Inclusively's Success Enabler framework without needing to know what to search for or where to look. For employees who may feel hesitant to disclose a need or navigate a fragmented benefits landscape, the anonymous, conversational experience lowers the barrier to getting support. For HR and people leaders, Retain surfaces something equally valuable: real-time, aggregated insights into the benefits and barriers employees are actually experiencing. That intelligence helps organizations understand unmet demand, allocate benefits investments more effectively, and demonstrate a genuine commitment to inclusion not just in policy, but in practice. Creating differentiated value through accessibility offerings Taken together, these examples reinforce a broader point: accessibility is becoming an increasingly important part of how partners create differentiated value across both employee and customer experiences. Marketplace solutions can strengthen how partners bring accessibility-first innovation into customer conversations and platform experiences. The Microsoft Accessibility Partner Onboarding Guide also provides a useful foundation for partners looking to expand their accessibility focus on Microsoft platforms. The opportunity ahead for partners Accessibility is becoming an increasingly important part of the conversations customers are having around AI, modern work, security, application development, and industry transformation. The opportunity is not to treat accessibility as a separate conversation. It is to make accessibility part of how customers modernize, adopt AI, and build more trusted digital experiences. Ability Summit 2026 reinforced that accessibility-first innovation is shaping the future of AI, productivity, learning, collaboration, and end-customer experience. For partners, the opportunity is to turn that innovation into real customer impact. It is about building AI-powered experiences that are more trusted, more inclusive, and more effective for the people they serve. As Frontier Transformation accelerates AI adoption, partners are uniquely positioned to turn accessibility-first innovation into lasting business impact deepening customer relationships, expanding strategic relevance, and building stronger momentum as accessibility-first expectations continue to rise for our customers. Additional resources Read the Ability Summit 2026 blog by Neil Barnett, Chief Accessibility Officer at Microsoft. Explore the Forrester Consulting thought leadership paper commissioned by Microsoft, May 2026. Visit the Unique Unites Us accessibility hub. Watch for Ability Summit sessions to be available on demand in the coming weeks.Copilot, Microsoft 365 & Power Platform Community call
💡 Copilot, Microsoft 365 & Power Platform weekly community call focuses on different use cases and features within the Copilot, Microsoft 365 and Power Platform - across Microsoft 365 Copilot, Copilot Studio, SharePoint, Power Apps and more. 👏 Looking to catch up on the latest news and updates, including cool community demos, this call is for you! 📅 On 2nd of July we'll have following agenda: Copilot prompt of the week CommunityDays.org update Microsoft 365 Maturity model Latest on PnP Framework and Core SDK extension Latest on PnP PowerShell Latest on script samples Latest Copilot pro dev samples Latest on Power Platform samples Picture time with the Together Mode! Shahab Matapour (Systra Canada) – How to build an offline SharePoint Form Customizer Sudipta Kumar Basu (Capgemini) AI-Driven Underwriting Hub (SharePoint AI with Outlook Add‑In) Chris Kent (Takeda) – List Formatting Tips & Tricks 📅 Download recurrent invite from https://aka.ms/community/m365-powerplat-dev-call-invite 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/m365-powerplat-dev-call-join 👋 See you in the call! 💡 Building something cool for Microsoft 365 or Power Platform (Copilot, SharePoint, Power Apps, etc)? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!Copilot, Microsoft 365 & Power Platform Community call
💡Copilot, Microsoft 365 & Power Platform product updates call concentrates on the different use cases and features within the Microsoft 365 and in Power Platform. Call includes topics like Microsoft 365 Copilot, Copilot Studio, Microsoft Teams, Power Platform, Microsoft Graph, Microsoft Viva, Microsoft Search, Microsoft Lists, SharePoint, Power Automate, Power Apps and more. 👏 Weekly Tuesday call is for all community members to see Microsoft PMs, engineering and Cloud Advocates showcasing the art of possible with Microsoft 365 and Power Platform. 📅 On the 30th of June we'll have following agenda: News and updates from Microsoft Together mode group photo Joe Komban – How to improve your SharePoint Skills using out of the box skills Paolo Pialorsi - Work IQ: Leveraging A2A for context-aware agents interaction Bert Jansen & Vesa Juvonen – Considerations for SPFx Copilot Apps - SPFx Copilot Apps 3/3 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/community/ms-speakers-call-join 🗓️ Download recurrent invite for this weekly call from https://aka.ms/community/ms-speakers-call-invite 👋 See you in the call! 💡 Building something cool for Microsoft 365 or Power Platform (Copilot, SharePoint, Power Apps, etc)? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 📖 Resources: Previous community call recordings and demos from the Microsoft Community Learning YouTube channel at https://aka.ms/community/youtube Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/home 🧡 Sharing is caring!
