Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
165146 stories
·
33 followers

How deep do you want to go? Microsoft Copilot, Cowork, and Viva Engage in action

1 Share

There’s so much beneath the surface in Engage, including insights into:

  • How employees are feeling
  • The questions they keep asking
  • Feedback that can sharpen your next message
  • Knowledge worth sharing more widely

New Copilot in Engage and Copilot Cowork experiences help communicators, community managers, and leaders bring more of it into view, connect these insights with the work they’re already doing, then make better decisions from what they learn.

Join our webinar: Go Deeper with Engage with Copilot and Cowork
December 3, 2026, 9:00 AM PT

See Copilot in Engage, Cowork, and Community Agent in action through live demos of real scenarios. You’ll also learn how to get set up with the Engage plugin and ready-made skills so you can try it yourself right away.

What’s new

Enhanced Copilot in Engage

Coming soon, the enhanced Copilot in Engage can analyze conversations, connect Engage insights with your wider Microsoft 365 work, and creating outputs such as community health reports, posting plans, and presentations.

Engage plugin for Copilot Cowork

Rolling out now, the Engage plugin brings community knowledge, conversations, and actions into Copilot Cowork. Cowork can combine Engage content with your meetings, chats, emails, and files to complete multistep tasks on your behalf, like posting to Engage and sending emails.

Use Viva Engage in Microsoft 365 Copilot Cowork

Use plugins with Copilot Cowork

Ready-made skills for common jobs

To get you started, we’ve built skills that help community managers and corporate communicators complete repeatable work faster. Choose a workflow from the Community Pack or Comms Pack, such as reviewing how a message landed, preparing a leader briefing, or drafting a community roundup, and prompt Cowork to begin.

Get the skills and learn how to add them to Cowork

New capabilities for Community Agent

Community Agent is an AI agent available in public preview for Viva Engage communities that helps admins and experts keep up with colleagues' questions. Recent updates to Community Agent bring more knowledge sources, clearer answers, and easier draft review and activity tracking. 

Read the full roundup of Community Agent improvements

Note: the Microsoft Copilot, Cowork, and Community Agent experiences described in his blog require a Microsoft 365 Copilot license.

Go deeper: three everyday scenarios

The possibilities for going deeper with Copilot, Cowork, and Engage are endless. The following examples show how you can get deeper levels of help with your work, from exploring information to bringing together context and carrying out a task.

How did your leader’s message land?

Deep: Review an announcement’s post analytics, including sentiment and themes from comments. Gather the questions and reactions from the comments that should shape your follow-up.

Deeper: Ask Copilot in Engage to identify themes and unresolved questions and turn the findings into a presentation.

Deepest: Have Cowork prepare a repeatable leader-ready briefing that brings together post metrics, comment themes, and recommended next steps. Review it before by sending to your leader by email.

Try it in Cowork:

  1. Get the /how-did-it-land skill for Cowork.
  2. Prompt: /how-did-it-land, how did the post by [leader] about [topic] land?
  3. When you’re happy with the report, ask for an overview email you can send to the leader.
Video created with Copilot Cowork

Is your community getting the answers it needs?

Deep: Review community analytics, including sentiment and themes. browse discussions and find questions that need an answer.

Deeper: Ask Copilot in Engage to summarize recurring questions and suggest useful follow-up content. Could an FAQ or pinned “Start here” post help?

Deepest: Let Community Agent help handle questions using community conversations and configured knowledge sources. It drafts answers for review or posts automatically according to community settings.

Us the /community-report and /questions-needing-help skill to ask Cowork to give you a readout on how your community is doing and where to focus attention. Ask for an interactive dashboard to share.

Try it with the Community Agent and Cowork:

  1. Add the Community Agent to the community and provide it with relevant knowledge sources from SharePoint and public websites.
  2. Get the /community-report and /questions-needing-help skills for Cowork.
  3. Prompt: /community-report give me a readout on [community name]. /questions-needing-help Include a view of questions that haven’t been answered or need additional help. Make it an interactive dashboard I can share.
Video created with Copilot Cowork

How do you turn a busy week into a great update?

Deep: Gather meeting notes, chats, and files, then write an Engage update.

Deeper: Ask Copilot in Engage to turn that context into a draft for your audience, informed by your work and writing style.

Deepest: Ask Cowork to gather the context, prepare the post, and publish through the Engage plugin after you approve it.

Try it in Cowork:

  1. Prompt: Use my meetings, chats, and files about [project] from the last week to draft an update for the [community name]. Explain the latest status, celebrate successes, highlight what we are learning, outline next steps, and invite questions. Thank contributors. Show me the draft and publish to Engage only after I approve. 
  2. Provide feedback on the message, then approve. Cowork will post to Engage on your behalf.
Video created with Copilot Cowork

Engage skills for Cowork

We're introducing 17 skills for community managers and corporate communicators to use with the Engage plugin in Microsoft Copilot Cowork.

Start with the result you need: use /how-did-it-land to review available post metrics, recurring questions, and feedback, with a suggested next step. Try /leader-briefing to turn selected conversations into a concise private brief, or /community-roundup to draft a summary of useful conversations on a chosen topic.

How skills work

The Engage plugin lets Copilot Cowork find and read conversations in Engage. Once you add the plugin, you can bring those conversations into the work you do in Cowork. A skill is a set of instructions for a specific job. You choose the skill and provide the community and/and topic; Cowork follows the instructions and uses the plugin to get the information it needs.

 

Download the skills

 

  1. Add the Engage plugin for Cowork.
  2. Download the pack of skills, then extract the files
  3. Open Copilot Cowork. Select Customize. Select the Add menu, then Upload and choose a skill to add.
  4. Try the skill. Start a new Cowork conversation. Type / to choose an installed skill, or simply prompt in plain language. For example, "how did [leader name] message about [topic] land?"

Do you have feedback on these skills or an idea for a skill you'd like us to create? Share your feedback in a short survey.

For more setup details, see Customize Copilot Cowork and Use plugins with Copilot Cowork.

Choose your skills

Comms Pack

Use these skills to prepare communications, understand the response, and organize follow-up work.

Skill

What it helps you do

/how-did-it-land

See how an Engage post was received: its first-week numbers against your recent posts, the main themes and open questions, and one next step.

/network-themes

See the main topics people have discussed across Engage in the last 28 days, with example conversations.

/metrics-tracker

Put first-week reach, reactions and comments for the Engage posts you choose into a new or existing Excel tracker.

/ama-question-tracker

Build an Excel tracker of AMA questions grouped by theme, or safely update one this skill created.

/leader-briefing

Turn selected Engage conversations into a short private brief for a leader, with a suggested next move for each.

/leader-reply-radar

Find up to 5 conversations where a reply or thank-you would help, with draft wording to paste.

/pre-flight-check

Check a draft against its sources and get a go / no-go, each error with evidence, and the smallest fixes.

/event-close-out

Sort an event's questions into answered, partly answered and open, and draft follow-up text for the event owners.

/question-forecaster

Prepare likely questions and a draft FAQ from approved facts, flagging answers that still need a decision.

/leader-moment-composer

Turn a brief into draft of a leader post with two alternative openings and notes on where each claim comes from.

/recommended-leaders

Review Engage's recommended-leader suggestions and visible setup, and prepare an admin checklist.

/what-to-feature

Get 2-5 recent conversations worth featuring or pinning, each with a reason. You decide and take the action.

Community Pack

These workflows focus on understanding a community, helping members find useful information, and handling membership tasks.

Skill

What it helps you do

/community-review

Explains what your community contributes, how people participate, who helps keep it active, and where you could focus next.

/community-roundup

Turns useful updates, answers, resources and event takeaways into a catch-up post for members who missed the conversations.

/contributor-recognition

Helps you decide whom to recognize and why, based on helpful answers, useful resources and constructive contributions.

/questions-needing-help

Finds question posts that still need a specific answer or follow-up after reviewing the replies. Separately identifies existing answers worth reviewing for verification.

/community-membership-summary

Shows who is represented in your community through breakdowns by job title, community role and recorded office location, where available.

 

Read the whole story
alvinashcraft
13 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

AI Skills Navigator at Microsoft Ignite 2026: Learn, practice, apply

1 Share

Discover new ways to personalize learning, practice with AI, and apply your skills through on-demand labs with AI Skills Navigator.

As technology evolves, so do the skills we need. But finding learning that's relevant to our goals isn't always easy. That's why we introduced AI Skills Navigator last year: to help make skilling more personal, relevant, and accessible. 

AI Skills Navigator is an AI-powered skilling experience that helps you build the skills you need whether you’re investing in your own development or building capability across your organization. 

At Microsoft Ignite 2026, we're building on that foundation with new and enhanced capabilities that help you discover relevant learning, practice what you've learned, and apply your skills. 

Here's what's new: 

  • An enhanced For you experience: Discover more relevant learning recommendations informed by your profile, goals, preferences, and previous activity, and create tailored skilling playlists around what you want to achieve. 
  • On-demand labs: Apply what you've learned by working directly with Microsoft products and technologies in free, on-demand labs you can launch from AI Skills Navigator. 
  • Practice boost [public preview]: Practice what you're learning through realistic scenarios, interacting with AI through natural conversation and receiving questions, hints, and feedback along the way. Practice boost is available as a public preview for select learning content in AI Skills Navigator. 
  • And more: Explore Microsoft Pro Badge, our new first-of-its-kind credential that recognizes proficiency through everyday use of technology, expanded language support to make AI Skills Navigator more accessible to learners globally, and organizational reporting to help leaders make informed skilling decisions. 

 

Video: AI Skills Navigator | AI-powered learning for what matters to you

Discover learning tailored to your role and goals 

The enhanced For you page in AI Skills Navigator helps you discover more relevant learning based on the role, goals, and learning preferences you share, along with your previous activity. 

You can now explore featured skilling playlists recommended for your role. And with new conversational capabilities, you can tell AI Skills Navigator what you want to accomplish or start with a suggested prompt. Through that conversation, AI Skills Navigator helps turn your goals into a personalized skilling playlist that you can review and shape around your needs. 

For you also brings together learning you've already started, making it easier to pick up where you left off, while learning streaks help you track your momentum and stay motivated. 

Ready to get started? Visit For you.

Put your skills to work with on-demand labs 

New on-demand labs let you get your hands on the technology and try it for yourself. Experiment, make mistakes, troubleshoot real tasks, and build practical experience and confidence before applying those skills at work. 

Labs are free, with no subscription or license required, so you can explore and practice when you're ready. 

Ready to try it yourself? Explore labs and apply what you've learned. 

Practice with AI that responds to you 

The new practice boost feature helps bridge the gap between learning concepts and applying them through realistic scenarios that challenge your thinking. 

To use practice boost, just start your learning content, and then interact with AI using natural conversations to practice: explain your thinking, tackle challenges, and explore different approaches. Along the way, AI responds with relevant questions, hints, and feedback to help you deepen your understanding and build confidence. 

Practice boost is available as a public preview for select learning content in AI Skills Navigator.  

AI Skills Navigator is evolving for you and your teams 

Connect learning to your priorities with organizational reporting. For leaders, gaining visibility into how employees are building skills and where they stand in their learning journey can be challenging. Organizational reporting in AI Skills Navigator provides insights into learning engagement and progress, helping organizations identify trends and make more informed decisions about where to focus their skilling efforts. 

Learn in more languages. New at Ignite, AI Skills Navigator is expanding beyond English to Japanese, Spanish, German, French, Portuguese (Brazil), Indonesian, Simplified Chinese, Korean, and Italian. More learners can use the experience and access learning in a language they know, helping organizations support skilling across teams and regions.  

Build skills in the flow of work. Generally available since July, Learning Agent in Microsoft Copilot helps you build skills as needs arise in your everyday work. Using context about your role, skills, and work, it surfaces personalized recommendations from AI Skills Navigator and connected organizational sources. New at Ignite, Learning Agent can also recommend featured skilling playlists, helping you discover structured learning around relevant topics and goals. 

Prepare for Microsoft Credentials and demonstrate your skills 

Last month, we announced the general availability of Microsoft Pro Badge, a new credential that recognizes proficiency demonstrated through everyday use of technology, starting with GitHub Copilot. Unlike traditional credentials, Pro Badge doesn't require a separate exam, helping make the skills you demonstrate at work visible. 

We recently enhanced the dedicated space for Microsoft Credentials in AI Skills Navigator, bringing together curated training and preparation resources, including practice assessments for certification exams. You can also now see your earned Microsoft Certifications, Applied Skills, and Pro Badge credentials in your profile, keeping your achievements connected to your learning. Explore Microsoft Credentials and find resources to help you prepare. 

Make your next step yours 

AI Skills Navigator can help turn what you want to achieve into a path forward, with opportunities to practice in ways that respond to you and apply what you’ve learned through hands-on experiences. Sign in to AI Skills Navigator and make your next step yours. 

 

 

Read the whole story
alvinashcraft
25 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Virtualization Mode in Windows Admin Center is now generally available!

1 Share

Windows Admin Center: Virtualization Mode (vMode) is now generally available and ready for your production environments! Released as part of Windows Admin Center version 2611, a single vMode instance can manage up to 1,000 Hyper-V hosts and 25,000 VMs. This release also adds Azure Arc onboarding, built-in backup and restore, and certificate management with Active Directory Certificate Services (AD CS).

Administration Mode (aMode) gets resilience and security fixes, plus a redesigned Azure registration experience that asks only for the permissions each task needs. Both modes now share one installer, so you can get started in one step. Just pick your mode during setup.

A huge thank you to our customers, partners, and fans—your feedback has shaped Windows Admin Center and vMode all the way to this GA milestone. Keep it coming! You can share your thoughts on this release through our official feedback portal.

What is Virtualization Mode?

Many organizations are rethinking their virtualization platform right now. Licensing changes and renewal uncertainty have pushed teams to look for alternatives, and not every workload is ready to move to the cloud. If you’re moving to Hyper-V, or already running it, vMode gives you the centralized management you’d expect from a modern virtualization platform, at no additional cost.

Today, you probably manage Hyper-V one piece at a time: Hyper-V Manager for one host, Failover Cluster Manager for another, and PowerShell scripts to fill the gaps. vMode brings all of this into one place. From a single gateway, your team can onboard Hyper-V hosts and clusters, apply consistent networking and storage configuration, and manage compute, storage, and networking as one environment, with role-based access so everyone can work together.

Because vMode keeps a central record of your environment, it can also protect itself with built-in backup and restore, certificate management through your existing PKI, and Azure Arc onboarding at scale. Administration Mode is still the right tool for hands-on work with individual servers. vMode is for running your virtualization environment as a whole.

We recommend reading more about the architectural differences between the modes before reading the rest of this article. Afterwards, check out the vMode documentation for more information.

What’s new in Windows Admin Center 2611

Virtualization mode 

Navigation hierarchy

In vMode, everything you manage lives in a single navigation hierarchy on the left side of the screen. Instead of connecting to servers one at a time, you browse your whole environment at once: resource groups, plus the hosts, clusters, VMs, and storage they contain. Switch between the Compute, Storage, and Network views to focus on the part of your fabric you’re working on.

 

Resource groups are the top-level containers in the hierarchy, and they work like folders. Organize them however makes sense for your team, whether that’s by site, environment, or workload. Every resource belongs to a resource group, resource groups don’t nest, and each host belongs to exactly one resource group. Because access is assigned through role-based access control, each user only sees the resources they’ve been given access to.

Compute view

The Compute view brings your Hyper-V hosts, clusters, and VMs together, organized by resource group so you can browse your environment without switching between individual server connections. Select a host to open its management tools, or select a VM to see its details and current state. From here, you can get on with everyday tasks like creating VMs, starting them, and live migrating them between standalone hosts—all within the same experience you use to manage the rest of your virtualization environment.

Storage view

The Storage view brings your storage resources together, organized by resource group so you can find the storage your VMs depend on without browsing through individual hosts. Whether you’re using Windows Scale-Out File Servers, non-Windows SMB file servers, or SAN storage, you can manage your onboarded storage here and see which compute systems are linked to each resource. It’s a way to explore your environment from the storage side, with those connections in view as you move between your storage and compute resources.

Networking view

The Networking view is where you create and manage reusable Network ATC intent templates for your cluster networking. Define the traffic types and networking settings once, then select a template and map it to physical adapters in the Add resource wizard. This helps you apply consistent configurations across deployments without starting from scratch each time.

As your networking needs evolve, you can refine these templates for future deployments. In this release, template changes apply only to future deployments that use the template. Intents already configured on your hosts or clusters remain unchanged.

Use the Network ATC PowerShell cmdlets to manage deployed intents. For guidance on updating intent settings, changing assigned network adapters, or removing intents, see Manage Network ATC.

Add resource 

Add resource is how you bring your infrastructure under vMode management. Instead of piecing together onboarding with separate tools and scripts, a single guided workflow adds your hosts to a resource group, applies consistent networking, storage, and compute configuration, and installs the vMode agent that keeps everything connected to the gateway.

Adding compute resources

Using the Compute profile, you can bring three kinds of Hyper-V infrastructure into vMode:

  • Standalone hosts: Individual Hyper-V hosts that aren’t part of a failover cluster.
  • Existing clusters: Enter the cluster’s fully qualified domain name (FQDN), and vMode automatically detects and onboards every member node.
  • New clusters: Create a failover cluster from two or more standalone hosts as part of onboarding.

To get started, select the ellipsis (...) next to a resource group and choose Add Resource. The wizard then walks you through each part of the configuration before anything is applied:

  1. Getting started: Select the Compute profile, validate each host or cluster FQDN, and turn on Clustered to create a new cluster.
  2. Clustering (clusters only): Confirm existing cluster settings or name a new cluster and choose DHCP or static IPs.
  3. Networking: Bind Network ATC intent templates to physical adapters for clusters. Network ATC configuration is skipped for hosts that will remain standalone. To learn more about the changes we’ve made to this page since preview, read our dedicated blog post.
  4. Storage: Pick a storage option or use storage already connected to your hosts.
  5. Compute: Set host options like enhanced session mode, concurrent live migrations, and the default VM path.
  6. Review: Confirm your selections and select Submit.

Before you begin, review the prerequisites for machines managed by Windows Admin Center vMode.

Adding storage resources

Using the Storage profile, or the Storage step when you add compute resources, you can bring the storage your VMs run on into vMode. Like everything else in vMode, each storage resource belongs to a resource group. Today, vMode supports three types of storage:

  • Windows Scale-Out File Servers (SOFS): Enter the SOFS share path, and vMode validates the share, installs the vMode agent on the file server, and can configure share permissions and SMB delegation for you so live migration works. If delegation can’t be configured automatically, such as when Active Directory permissions are missing, vMode tells you so you can set it up manually.
  • Non-Windows SMB file servers: Enter the share’s UNC path (for example, \\storage01\share1), and vMode confirms the share exists and is accessible before registering it. Permission and delegation options aren’t available for non-Windows file servers. If you enter the share path while adding compute resources, vMode registers the storage for you automatically.
  • SAN storage (Fibre Channel and iSCSI): Register a SAN by its hostname. When you add hosts or clusters connected to a SAN, the Storage step scans shared LUNs and shows which are ready to use, which vMode can configure automatically, and which need manual configuration. Network ATC Storage intents are optional for SAN deployments.

After onboarding, you can manage your storage from the Storage view, where you’ll also see which compute systems are linked to each storage resource.

Tracking deployment status

Onboarding can take a while, especially when hosts need to reboot, so vMode gives you a couple of ways to keep tabs on progress and get things back on track if something goes wrong.

Workflow status pane: Select the workflow status icon in the header bar to open the workflow status pane from anywhere in vMode. It lists your workflows, like Add resource, along with their current status and the progress of each step, including any required reboots. You can filter the list by status to quickly find workflows that need your attention, and open a workflow to see details and error information for any step that failed.

Deployment status: As soon as deployment begins, the machine you’re adding appears in the navigation hierarchy. If you select it before it’s ready, you’ll see its deployment status, similar to what’s shown in the workflow status pane. That way, even if you don’t make it back to the workflow for a while, you’ll know exactly where to look to check progress or address any issues.

Resuming and retrying workflows: Transient issues like lost connectivity, a gateway service restart, or configuration changes can interrupt a workflow. If a workflow is paused by a service disruption, you can resume it from where it left off. If a step fails, you can review the error, fix the underlying cause, and retry that step if rerunning it won’t disrupt anything else in the workflow.

Authentication and Role-based Access Control (RBAC)

vMode is built for teams, so access is checked in layers. Users sign in to the gateway with their Active Directory account through Windows authentication, and vMode RBAC then decides what each person can do and where. You can assign roles at the gateway root, a resource group, a cluster, or a host, and assignments flow down to everything beneath them. Today vMode includes three built-in roles:

  • Global Administrator: Full control of the gateway, including access, resource group structure, certificates, and backup and restore.
  • Fabric Manager: Day-to-day fabric management in their assigned scope, like adding hosts and clusters, managing templates, and onboarding to Azure Arc.
  • Reader: View-only access to resources in their assigned scope.

Keep in mind that right after installation, only the account that installed vMode has access, so be sure to add other users and assign roles before rolling it out to your team. vMode roles also don’t replace Windows permissions on your hosts, so users still need administrative rights on the hosts they manage. Learn more about authentication and role-based access control in vMode.

Backup and restore 

Because vMode keeps a central record of your environment, a failed gateway shouldn't mean rebuilding everything from scratch. Built-in backup and restore creates an encrypted, password-protected copy of the vMode management database, which holds your virtualization inventory, cluster metadata, gateway configuration, RBAC settings, templates, and operational state. Backup and restore is available to Global Administrators, and you can save backups to a local folder or a UNC share.

If you lose data or need to rebuild your gateway, you can restore from a backup and pick up where you left off. Before anything changes, vMode validates the backup’s password, checks it for unauthorized modifications, and confirms it’s compatible with your gateway. Restore recovers the management database only. It doesn’t roll back your servers, clusters, VMs, storage, or networks, and vMode picks up their current state as agents reconnect. Store your backup password separately from the backup file. If the password is lost, the backup can’t be restored.

To get started, go to Overview and select Backup & Restore. Learn more about backup and restoration in vMode.

Global search

When you’re managing hundreds of hosts and thousands of VMs, browsing the navigation tree to find one machine gets old fast. Global search lets you find any resource in your vMode environment from a single search bar, without needing to remember which resource group, cluster, or host it lives on.

Search spans the resources in your navigation hierarchy, including resource groups, hosts, clusters, and VMs. As you type, suggestions appear, and you can narrow results by object type. Select a result to jump straight to it and get to work, whether you’re checking on a VM during an incident or confirming that newly deployed machines landed on the right hosts.

 


Global search supports three search types, so you can be as broad or as targeted as you need:

Search typeSyntaxExample
BasicType partial names or use * as a wildcard. Matching is case-insensitive.uster0 finds Cluster01 and Cluster02; web-0* finds web-01 and web-02.
HierarchicalStart with the full resource group path, use / between levels, and place : before the search term. Wildcards aren’t supported in the path./ResourceGroup1/Cluster1: web searches hosts and VMs under Cluster1. Leave the term blank to see everything under that location.
ObjectPut the object type in square brackets followed by a colon, or select an object type icon.[Virtual machine]: WS2025; [Network intent]: Intent1. Broad types include [Compute], [Storage], and [Network].

 

Keep in mind that search respects role-based access control, so you only see results for resources you have access to. Deleted resources and attached objects, such as virtual hard disks, aren’t included in search results.

Azure Arc onboarding 

With vMode, you can connect the Hyper-V hosts you already manage to Azure Arc in bulk, right from the gateway. Azure Arc represents your on-premises servers as resources in Azure, so you can manage them with Azure services. Select multiple machines, apply one set of Azure settings (subscription, resource group, region, cloud environment, and optional tags), and vMode installs the Azure Connected Machine agent and connects each machine for you.

Getting connected starts in the Me control, where you register your vMode gateway with Azure and sign in to your Azure account—no trip to gateway settings needed. The redesigned registration flow requests only the permissions needed for the current user and registration task, without requiring tenant-level administrator consent. That means you can get started without coordinating with a highly privileged tenant administrator, while Azure role-based access control (Azure RBAC) lets administrators restrict who can perform Azure operations.

Each machine gets its own onboarding workflow, so a failure on one machine doesn’t stop the others. Track each machine’s progress in the workflow status pane as it downloads and installs the agent, connects to Azure Arc, and refreshes its status. Once onboarding completes, machines show as Connected on the Azure Arc page, along with their Azure resource group.

Once you’re signed in, select your navigation root, then Azure Arc to start onboarding your machines. In this release, machines connect through a public endpoint, either directly or through a proxy server. Learn more about onboarding to Azure Arc in vMode.

Using Administration Mode? You’ll find its redesigned Azure registration experience in gateway settings under Register. See Configuring Azure integration for more on connecting aMode to Azure.

Certificate lifecycle management 

vMode uses certificates to secure communication between the gateway and managed hosts. Self-signed certificates are great for testing, since they don’t require an existing certificate authority or PKI. For production, you can now manage vMode certificates through Active Directory Certificate Services (AD CS), using centralized issuance, certificate templates, and automated renewal to align with your existing PKI policies and reduce the risk of outages from expired certificates.


To get started, go to your gateway settings and select the Certificates tab. To learn more, see our documentation.

Keeping vMode up to date

Staying current is how you get the latest features, reliability fixes, and security updates in vMode. The good news: updating vMode is a two-part story where you only have to do one part. You update the gateway, and the gateway takes care of the agents.

Updating the gateway

To update your gateway, run the latest Windows Admin Center installer on your vMode gateway machine and complete the upgrade wizard. When prompted, reuse your existing PostgreSQL credentials. The installer upgrades your gateway in place and keeps your existing database, inventory, and configuration, including resource groups, managed hosts and clusters, network intent templates, and access assignments.

Before you upgrade, we recommend taking a backup of your vMode environment (or a checkpoint, if your gateway runs in a VM) so you have a known-good restore point. After the upgrade completes, sign back in and confirm your gateway version by navigating to Settings > About.

Updating the agents

There’s no separate step for agents. Updating your gateway automatically triggers an update of the vMode agents on all hosts and clusters managed through vMode. The agent installer is delivered with the gateway installer, so you never need to download or deploy agent updates to each host yourself.

After the gateway upgrade, managed hosts reconnect and their agents upgrade or report healthy. You can track progress with the agent health indicators in the navigation hierarchy and in the workflow status pane. If an agent shows as disconnected after updating, check out our documentation for troubleshooting guidance.

Hyper-V Replication

You can now set up and manage Hyper-V Replica right in vMode, alongside your hosts, clusters, and VMs. Configure Replica Brokers and enable VM replication over HTTP or HTTPS, then choose which disks to replicate, how often replication runs, how many recovery points to keep, and how to handle the initial copy.

 

 

Once replication is configured, open VM details to check its health and statistics. Need to make a change? You can pause or resume replication, update replication or failover-network settings, or remove and re-enable replication. VM details also gives you access to checkpoint management and lets you move clustered VMs between nodes.

When it’s time to test your recovery plan, you can run a test failover on an isolated copy without interrupting the original VM. If you need to move or recover a workload, use planned or unplanned failover, then reverse replication to support failback. You can also set up extended replication to keep an additional copy at a third site.

 

Want to see which replicated workloads need attention across your environment? Replication Monitor, entering private preview alongside vMode GA, brings replication health and test-failover information for primary and extended replication into one view across your hosts and clusters. Dashboard cards and filters help you narrow in on workloads that need attention. To try it, sign up for the private preview with your email address, and we’ll send you the steps to enable Replication Monitor.

Check out our documentation to learn more about Hyper-V Replica.

Update on the VM Conversion tool 

VM Conversion is coming to vMode in private preview, bringing VMware ESXi-to-Hyper-V migration into the same experience you use to manage your virtualization environment. This new appliance-based implementation replaces the earlier preview extension, with prechecks to help you prepare, data synchronization ahead of cutover to help limit downtime, and batch operations for moving multiple VMs. You can follow each VM’s progress in the workflow status pane, then keep managing the workload in vMode once it’s running on Hyper-V. For a closer look at how it works and how to express interest in the private preview through Windows Server TAP, read our companion blog.

New SDK — now with React support 

The Windows Admin Center SDK has been updated to version 6.0.0! This new version features two major updates: commands for upgrading existing Windows Admin Center extensions to Angular 20 as well as commands for creating and testing React-based Windows Admin Center extensions. The documentation for preparing your development environment and creating a tool extension has been updated to reflect these changes.  

Partner Ecosystem

The Windows Admin Center management experience wouldn’t be complete without our development partners, who make managing your hardware, storage, and firmware through Windows Admin Center a streamlined experience. Since the last generally available release of Windows Admin Center, three partners have made updates to their extensions.

  • The Dell OpenManage Integration extension has been upgraded to version 3.8.0—this version contains the following improvements:
    • Support for aMode and vMode: Dell OpenManage Integration now supports Windows Admin Center 2611 GA in both Administration Mode and Virtualization Mode. In vMode, you can manage and monitor infrastructure, perform lifecycle management operations, and use virtualization management experiences from a unified interface.
    • 18G PowerEdge server support: Added support for the R9815 and R9825 platforms.
    • Security improvements: Addressed security vulnerabilities and improved stability and compliance posture.
    • Reliability improvements: Improved error handling and validation across multiple workflows for a better user experience and greater operational stability.
  • The Dell APEX Cloud Platform extension has been upgraded to version 3.0.7—this version contains the following improvements:
    • Security hardening
    • Fix for a reported certificate expiry issue
  • The Dell PowerPath extension has been upgraded to version 3.0.0—this version contains the following improvements:
    • Upgraded to Angular 15
  • The Lenovo XClarity Integrator extension has been upgraded to version 5.2.1—this version contains the following improvements:
    • New system support: Added support for FX650 V4 and FX630 V4 systems.
    • Best Recipe support: Added support for ThinkAgile MX Best Recipe 2605.
    • Software support: Added support for Lenovo XClarityEssentials OneCLI 5.4.0 and Windows Admin Center 2511.
    • Cluster consistency fix: Fixed a failure to compute cluster consistency when all nodes are not using a Host Bus Adapter.
    • Best Recipe compliance fix: Fixed an issue where Best Recipe compliance results ignored capacity disks.
    • Security improvements: Addressed CVE-2026-65949, CVE-2025-4947, CVE-2025-5025, and LEN-223105.
  •  The Everpure FlashArray extension has been upgraded to version 1.1.180—this version contains the following improvements:
    • A new array must be registered by a gateway administrator before anyone can connect to it. A new Registered Arrays page provides this.
    • Arrays with self-signed certificates require a one-time administrator approval.
    • Unregistering an array signs out everyone currently using it.
    • Existing connections are migrated automatically on upgrade and continue to work without administrator action.

Known issues 

Visit our documentation to learn about the current known issues with this version. Additionally, check out our documentation for additional troubleshooting information.

Download today!

Thanks for reading along! Virtualization mode going GA is a big moment for us, and we can’t wait for you to try it. We hope you love this new version and everything it brings.

Download now! 

As always, thanks for your ongoing support, adoption, and feedback. Your contributions through user feedback continue to be vital and valuable to us, helping us prioritize our investments.  

vMode GA is a big step, but it’s not the finish line. Windows Admin Center keeps growing as both a tool and a platform, and we’re beyond thrilled to have you along for the ride. Stay tuned—there’s plenty more to come!

Thank you,  

Windows Admin Center Team (@servermgmt)  

Read the whole story
alvinashcraft
41 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Enterprise Architecture with Microsoft Foundry: Capability Hosts, BYO Resources, Private Networking

1 Share
Introduction

An AI agent can deliver an impressive demo—and still face a production roadblock when enterprise data must stay in organization-controlled storage behind private endpoints. Moving to production means deciding not just what an agent can do, but where its data lives and how it reaches private resources.

Microsoft Foundry brings these decisions together through outbound virtual network injection, bring-your-own (BYO) Azure resources, and Capability Hosts. This post connects the dots between them: establishing private connectivity, choosing your backing resources, and configuring each project to use them—so data ownership and network isolation become part of your architecture, not last-minute deployment hurdles.

Connecting agents to private resources

By default, agents use public outbound connectivity to access external services and Azure resources. If an agent must connect to resources that are accessible only through a private network, you can configure outbound virtual network injection.With outbound VNet injection, the Foundry Agent Service runtime is connected to a dedicated subnet delegated to Microsoft.App/environments. This delegation allows Foundry to deploy and manage the networking required for the agent runtime.The same VNet also contains a separate private-endpoint subnet that hosts private endpoints for resources such as Azure Storage, Azure Cosmos DB, Azure AI Search, and the Foundry account. Agent traffic flows from the delegated subnet through the VNet to these private endpoints, without traversing the public internet.

Note : Private endpoints can be in the same VNet or in a reachable peered VNet.

Foundry Agent Service

Foundry Agent Service is a managed platform for building, deploying, and scaling AI agents. By default, Foundry Agent Service manages storage for files, conversations, and vector stores. If your organization requires full data ownership, customer-managed keys (CMK), or network isolation i.e. enforce enterprise security and compliance policies, you can connect or use your own Azure resources instead.

  1. Azure Cosmos DB for NoSQL  — stores conversations, agent state, and related metadata.
  2. Azure Storage — stores uploaded files and intermediate file-processing data.
  3. Azure AI Search — stores and searches vector indexes used for retrieval.
Capability Host

Capability hosts are sub-resources that you configure at both the Microsoft Foundry account and Foundry project scopes. They tell Foundry Agent Service where to store and process agent data, including Conversation History, File uploads and Vector stores. This is like a configuration mapping between Agent Service and its required backing resources.

Note: If you don't create capability hosts, Agent Service automatically uses Microsoft-managed Azure resources for history, file uploads and vector stores.

Account Capability Host : enables the Agent Service capability at the Foundry account level and associates agent service with the delegated subnet .

 In a private-network deployment using network injection, the account capability host can be created automatically as part of provisioning (refer Template 15 deployment).

Project Capability Host: tells Agent Service exactly which resources a particular project should use. Even if the account capability host references connections, Agent Service doesn't use them for a project unless those connections are explicitly referenced in a project capability host.

Capability-host propertyPurposeAzure resource
storageConnectionsUploaded files and intermediate dataAzure Storage
threadStorageConnectionsConversations, agent state, and metadataAzure Cosmos DB
vectorStoreConnectionsVector indexes and retrieval dataAzure AI Search

In summary the account-level Capability Host enables Foundry Agent Service and associates it with the delegated subnet to enable access to private resources/connections referenced by the projects. The project-level Capability Host defines where the project’s agent data is stored by referencing its Azure Storage, Azure Cosmos DB, and Azure AI Search connections. 

Deploying a Foundry Account with ARM Json Template

Template 15 – Private Network Standard Agent Setup, which deploys Foundry Agent Service with BYO data resources and Vnet injection. Below link takes you to custom deployment  in Azure Portal. 

https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fazure-ai-foundry%2Ffoundry-samples%2Frefs%2Fheads%2Fmain%2Finfrastructure%2Finfrastructure-setup-bicep%2F15-private-network-standard-agent-setup%2Fazuredeploy.json

Follow below instructions to run the deployment and once its completed, we will have a Foundry account and the first project created with both Account and project level Capability Hosts.

Prerequisites :
  1.  Virtual network with 2 subnets created one each for Private endpoints and another delegated subnet
  2.  Cosmos, Storage and Search Services created

Custom Deployment Parameters:

Successful deployment :

Verifying the Account and Project  Capability Hosts:

Account Capability Host:

az rest --method get --url "https://management.azure.com/subscriptions/<subscriptionid>/resourceGroups/<resourcegroupname>/providers/Microsoft.CognitiveServices/accounts/<foundryaccountname>/capabilityHosts?api-version=2025-06-01"

Output:

{ "value": [ { "id": "/subscriptions/<subscriptionid>/resourceGroups/<resourcegroupname>/providers/Microsoft.CognitiveServices/accounts/<foundryaccountname>/capabilityHosts/<accountlevelcapabilityhostname>", "name": "<accountlevelcapabilityhostname>", "properties": { "aiServicesConnections": null, "capabilityHostKind": "Agents", "customerSubnet": "/subscriptions/<subscriptionid>/resourceGroups/<resourcegroupname>/providers/Microsoft.Network/virtualNetworks/<vnetname>/subnets/<delegatedsubnetname>", "description": null, "properties": null, "provisioningState": "Succeeded", "storageConnections": null, "tags": null, "threadStorageConnections": null, "vectorStoreConnections": null }, "systemData": { "createdAt": "2026-11-08T18:21:21.0327639+00:00", "lastModifiedAt": "2026-11-08T18:25:17.3252644+00:00" }, "type": "Microsoft.CognitiveServices/accounts/capabilityHosts" } ] }

 

 

Project Capability Host

az rest --method get --url "https://management.azure.com/subscriptions/<subscriptionid>/resourceGroups/<resourcegroupname>/providers/Microsoft.CognitiveServices/accounts/<foundryaccountname>/projects/<projectname>/capabilityHosts?api-version=2025-06-01"

 

Output:

{ "value": [ { "id": "/subscriptions/<subscriptionid>/resourceGroups/<resourcegroupname>/providers/Microsoft.CognitiveServices/accounts/<foundryaccountname>/projects/<projectname>/capabilityHosts/<projectlevelcapabilityhostname>", "name": "<projectlevelcapabilityhostname>", "properties": { "aiServicesConnections": null, "capabilityHostKind": "Agents", "customerSubnet": null, "description": null, "properties": null, "provisioningState": "Succeeded", "storageConnections": [ "<storageconnectionname>" ], "tags": null, "threadStorageConnections": [ "cosmosconnectionname" ], "vectorStoreConnections": [ "searchconnectionname" ] }, "systemData": { "createdAt": "2026-11-08T18:34:34.6044253+00:00", "lastModifiedAt": "2026-11-08T18:37:12.8222622+00:00" }, "type": "Microsoft.CognitiveServices/accounts/projects/capabilityHosts" } ] }

 

Creating account/project level capability hosts on a Foundry Account with VNET injection.
This is mainly required to understand the flow how capability host provisioning works and troubleshoot any existing project.
Sign in and set variables 
$tenantId = '<tenantid>' $subscriptionId = '<subscriptionId>' $resourceGroup = '<resourceGroup>' $accountName = '<FoundryAccountName>' $projectName = '<FoundryProjectName>' $storageAccountName = '<StorageAccountName>' $cosmosAccountName = '<CosmosAccountName>' $searchServiceName = '<AzureAISearchServiceName>' $accountHostName = 'account-agents-host' # new host name: letters, digits, '-' or '_' only (no '@') $projectHostName = 'project-agents-host' $storageConnectionName = 'hub-storage-connection' $searchConnectionName = 'hub-search-connection' $cosmosConnectionName = 'hub-cosmos-connection' $agentSubnetId = '<ResourceIdOfDelegatedSubnet>' $apiVersion = '2025-06-01' $accountResourceId = "/subscriptions/$subscriptionId/resourceGroups/$resourceGroup/providers/Microsoft.CognitiveServices/accounts/$accountName" $accountUri = "https://management.azure.com$accountResourceId" $projectUri = "$accountUri/projects/$projectName" # Stop early if any variable is blank (for example, if this block was not run in the current session) $required = 'accountName','projectName','storageAccountName','cosmosAccountName','searchServiceName','accountHostName','projectHostName','storageConnectionName','searchConnectionName','cosmosConnectionName','agentSubnetId' $missing = $required | Where-Object { [string]::IsNullOrWhiteSpace((Get-Variable -Name $_ -ValueOnly -ErrorAction SilentlyContinue)) } if ($missing) { throw "Variables not set: $($missing -join ', ')" } az login --tenant $tenantId if ($LASTEXITCODE -ne 0) { throw 'Azure login failed.' } az account set --subscription $subscriptionId if ($LASTEXITCODE -ne 0) { throw 'Could not select the Azure subscription.' } az account show --query '{subscription:id,tenant:tenantId}' --output json if ($LASTEXITCODE -ne 0) { throw 'Could not verify the Azure context.' }
Inspect the existing account connections
az rest --method get --uri "$accountUri/connections/$($cosmosConnectionName)?api-version=$apiVersion" az rest --method get --uri "$accountUri/connections/$($searchConnectionName)?api-version=$apiVersion" az rest --method get --uri "$accountUri/connections/$($storageConnectionName)?api-version=$apiVersion"
Creating Connections

Run below function to create connections for Search, Storage and Cosmos

function Set-FoundryConnection { param( [Parameter(Mandatory)] [string] $Name, [Parameter(Mandatory)] [string] $Category, [Parameter(Mandatory)] [string] $Target, [Parameter(Mandatory)] [string] $ResourceId ) $body = @{ properties = @{ category = $Category target = $Target authType = 'AAD' metadata = @{ ResourceId = $ResourceId } } } | ConvertTo-Json -Depth 5 $file = [IO.Path]::GetTempFileName() try { [IO.File]::WriteAllText($file, $body, [Text.UTF8Encoding]::new($false)) az rest --method put --uri "$accountUri/connections/$($Name)?api-version=$apiVersion" --headers 'Content-Type=application/json' --body "@$file" if ($LASTEXITCODE -ne 0) { throw "Connection PUT failed: $Name (az exit code $LASTEXITCODE)." } } finally { Remove-Item -LiteralPath $file } } $backingResourceId = "/subscriptions/$subscriptionId/resourceGroups/$resourceGroup" Set-FoundryConnection -Name $storageConnectionName -Category 'AzureStorageAccount' -Target "https://$storageAccountName.blob.core.windows.net/" -ResourceId "$backingResourceId/providers/Microsoft.Storage/storageAccounts/$storageAccountName" Set-FoundryConnection -Name $searchConnectionName -Category 'CognitiveSearch' -Target "https://$searchServiceName.search.windows.net" -ResourceId "$backingResourceId/providers/Microsoft.Search/searchServices/$searchServiceName" Set-FoundryConnection -Name $cosmosConnectionName -Category 'CosmosDb' -Target "https://$cosmosAccountName.documents.azure.com:443/" -ResourceId "$backingResourceId/providers/Microsoft.DocumentDB/databaseAccounts/$cosmosAccountName"

 

Grant managed identity RBAC permissions

Before capability host provisioning can succeed, the project's system-assigned managed identity (or user assigned managed identity) must be granted the required access to Storage, AI Search, and Cosmos DB. Run below to assign the required roles.

# Step 1: Set the active context and get the managed identity object ID Set-AzContext -SubscriptionId $subscriptionId -TenantId $tenantId -ErrorAction Stop $managedIdentityObjectId = az rest --method get --uri "$($projectUri)?api-version=$apiVersion" --query identity.principalId --output tsv if ([string]::IsNullOrWhiteSpace($managedIdentityObjectId)) { throw 'Could not read the project managed identity principal ID.' } $managedIdentityObjectId # Step 2: Grant Storage blob data access New-AzRoleAssignment -ObjectId $managedIdentityObjectId -RoleDefinitionName 'Storage Blob Data Contributor' -Scope "/subscriptions/$subscriptionId/resourceGroups/$resourceGroup/providers/Microsoft.Storage/storageAccounts/$storageAccountName" # Step 3: Grant AI Search roles "Search Index Data Contributor", "Search Service Contributor" | ForEach-Object { New-AzRoleAssignment -ObjectId $managedIdentityObjectId -RoleDefinitionName $_ -Scope "/subscriptions/$subscriptionId/resourceGroups/$resourceGroup/providers/Microsoft.Search/searchServices/$searchServiceName" } #Step 4: Grant Cosmos DB roles New-AzRoleAssignment -ObjectId $managedIdentityObjectId -RoleDefinitionName 'Cosmos DB Operator' -Scope "/subscriptions/$subscriptionId/resourceGroups/$resourceGroup/providers/Microsoft.DocumentDB/databaseAccounts/$cosmosAccountName" New-AzCosmosDBSqlRoleAssignment -ResourceGroupName $resourceGroup -AccountName $cosmosAccountName -RoleDefinitionId '00000000-0000-0000-0000-000000000002' -PrincipalId $managedIdentityObjectId -Scope '/' #Step 5. Check the account-level capability host az rest --method get --uri "$accountUri/capabilityHosts?api-version=$apiVersion" --query 'value[].{name:name,kind:properties.capabilityHostKind,state:properties.provisioningState}' --output table if ($LASTEXITCODE -ne 0) { throw 'Could not list account capability hosts.' }
Account-level capability host

Check if account level capability host exists and is in failed state. If yes, delete and create using below code

# The project capability host requires an account-level host. Check whether one already exists before creating anything: az rest --method get --uri "$accountUri/capabilityHosts?api-version=$apiVersion" --query 'value[].{name:name,kind:properties.capabilityHostKind,state:properties.provisioningState}' --output table if ($LASTEXITCODE -ne 0) { throw 'Could not list account capability hosts.' } #------------------------- #Delete the account-level capability host #------------------------- $existingAccountHostName = az rest --method get --uri "$accountUri/capabilityHosts?api-version=$apiVersion" --query 'value[0].name' --output tsv az rest --method delete --uri "$accountUri/capabilityHosts/$($existingAccountHostName)?api-version=$apiVersion" #------------------------- #Create the account-level capability host #------------------------- if ($accountHostName -notmatch '^[A-Za-z0-9_-]+$') { throw "Invalid account host name: '$accountHostName'" } $accountHostBody = @{ properties = @{ capabilityHostKind = 'Agents' customerSubnet = $agentSubnetId } } | ConvertTo-Json -Depth 5 $file = [IO.Path]::GetTempFileName() [IO.File]::WriteAllText($file, $accountHostBody, [Text.UTF8Encoding]::new($false)) az rest --method put --uri "$accountUri/capabilityHosts/$($accountHostName)?api-version=$apiVersion" --headers 'Content-Type=application/json' --body "@$file" Remove-Item -LiteralPath $file #Verify the result az rest --method get --uri "$accountUri/capabilityHosts?api-version=$apiVersion" --output json if ($LASTEXITCODE -ne 0) { throw 'Account capability host verification failed.' }
Project-level capability host 

Check if project level capability host exists and is in failed state. If yes, delete and create using below code.

Also we can create project specific Cosmos, Search and Storage connections/resources.

If the Cosmos account is shared my multiple projects, each projects needs 3-5K RU's

# Check and create the project-level capability host az rest --method get --uri "$projectUri/capabilityHosts?api-version=$apiVersion" --output json if ($LASTEXITCODE -ne 0) { throw 'Could not list project capability hosts.' } # Delete the project-level capability host if ([string]::IsNullOrWhiteSpace($projectHostName)) { throw 'Set $projectHostName to the existing host name from the GET output.' } az rest --method delete --uri "$projectUri/capabilityHosts/$($projectHostName)?api-version=$apiVersion" # Create the project-level capability host # An empty host name produces '.../capabilityHosts/?api-version=...', which Azure # rejects with a misleading "UnsupportedApiVersion ... does not support HTTP method 'PUT'" error. if ([string]::IsNullOrWhiteSpace($projectHostName)) { $projectHostName = 'project-agents-host' } if ($projectHostName -notmatch '^[A-Za-z0-9_-]+$') { throw "Invalid project host name: '$projectHostName'" } if ([string]::IsNullOrWhiteSpace($projectUri) -or [string]::IsNullOrWhiteSpace($apiVersion)) { throw 'Run the variables block in step 1 first.' } $projectHostBody = @{ properties = @{ capabilityHostKind = 'Agents' storageConnections = @($storageConnectionName) vectorStoreConnections = @($searchConnectionName) threadStorageConnections = @($cosmosConnectionName) } } | ConvertTo-Json -Depth 5 $file = [IO.Path]::GetTempFileName() [IO.File]::WriteAllText($file, $projectHostBody, [Text.UTF8Encoding]::new($false)) az rest --method put --uri "$projectUri/capabilityHosts/$($projectHostName)?api-version=$apiVersion" --headers 'Content-Type=application/json' --body "@$file" Remove-Item -LiteralPath $file #Verify the result az rest --method get --uri "$projectUri/capabilityHosts?api-version=$apiVersion" --output json if ($LASTEXITCODE -ne 0) { throw 'Project capability host verification failed.' }

 

References

Capability hosts for Foundry Agent Service - Microsoft Foundry | Microsoft Learn

Use your own resources in the Foundry Agent Service - Microsoft Foundry | Microsoft Learn

foundry-samples/infrastructure/infrastructure-setup-bicep/15-private-network-standard-agent-setup at main · microsoft-foundry/foundry-samples

 

Read the whole story
alvinashcraft
1 minute ago
reply
Pennsylvania, USA
Share this story
Delete

New Capabilities for Building Digital Teammates in Microsoft Teams

1 Share

Agents are becoming part of how people work together. In Microsoft Teams, developers can build agents that do more than respond to requests. They can participate in conversations, contribute to shared work and help people move from discussion to decision and action. As part of the broader Microsoft 365 Copilot agent ecosystem, Teams brings these digital teammates into the conversations where collaboration already happens. 

New Teams capabilities support this through agent identity, conversational context, visible progress and interactive experiences. Together, they help people explore questions, evaluate recommendations and act without leaving Teams.

What’s new at a glance 

Six updates improve how teams work with agents, while a seventh makes agents easier to build and test: 

  • Agentic Users (in public preview): agents that act as themselves can join the team under their own identity, with an accountable owner and administrator controls.
  • Threaded replies (in public preview): each task in a one-to-one agent chat gets its own thread, so developers can keep its context separate.
  • Agent plans and steps (in public preview): people see what the agent is doing, and when it needs them, without extra messages. 
  • Streaming in group chats and channels (available now): answers appear as they’re written, in the conversations where teams work. 
  • Extended Markdown (available now): tables, code and checklists, with citations, so answers are easy to scan and check. 
  • HTML widgets (in public preview): interactive views inside a response, so people can explore options and act without leaving the conversation. 
  • Socket mode (in public preview): developers run and test an agent in Teams without a public endpoint or tunnel. 

To see these capabilities in practice, we follow a fictional manufacturing company, Caldova, and its agent, Supplier Analyst, which helps procurement teams evaluate suppliers. The team needs 24 batches but can cover only 8 internally. Supplier Analyst brings capacity information, supporting evidence and outstanding requirements into the conversation so the team can compare options and understand what remains before committing to a supplier. 

Bring the agent into the team 

A digital teammate needs more than a name in a chat. It needs a place on the team.  

Give an identity to agents that act as themselves. Agentic Users (in public preview) give these agents their own Microsoft Entra accounts, so their messages and actions show up under the agent’s own name, not under a person’s account or a shared app. People can find an agent by name, add it to chats, channels and meetings, and @mention it like a colleague in Teams and across Microsoft 365 apps. Its profile identifies its owner, and its actions are attributed to the agent in audit logs. Not every agent needs its own identity: application-style agents and personal assistants may use different identity models.

Image of an agent in the org chart
Supplier Analyst’s profile identifies it as an AI agent and shows its contact details and reporting relationship.

Enable proactive contributions. With its own identity and scoped access, an agent can contribute without waiting to be asked, within limits the organization sets. It can post an update, follow up on an open question or nudge work that has stalled. 

Keep administrators in control. That independence comes with oversight. Administrators approve the agent, define what it can access, review its activity in Microsoft Agent 365 down to individual tool calls, and disable it when needed.  

Build on the Teams SDK. Developers use the SDK they already know, with existing cards, reactions and API calls carrying over. On platforms that create many agents, each acting as itself, developers can maintain one Teams app while people work with distinct digital teammates. To implement this pattern, follow the build an agent factory guide.  

In our example, people find Supplier Analyst by name, add it to the capacity-planning conversation and @mention it like another colleague. They can also message it directly with a follow-up question. 

Keep the right conversation in context 

Organize ongoing work into separate threads. Threads keep related exchanges together, helping people return to a topic without mixing unrelated discussions. Threaded replies (in public preview) bring this organization to one-to-one agent conversations. Developers can use threads as task or session boundaries and choose which conversation history to bring into each follow-up.

Make the agent’s work visible and useful 

Show progress without filling the chat. With agent plans and steps (in public preview), developers can show progress on multistep tasks, completed work and requests for input without filling the conversation with extra messages. Completed steps remain available for review alongside the final response.

Stream responses as they’re generated. With streaming in group chats and channels (available now), people can see an agent’s response unfold in real time rather than waiting for the entire answer. This makes interactions feel more responsive, especially when generating longer responses. 

Present information clearly. Extended Markdown (available now) brings richer formatting to Teams messages, giving developers more ways to organize and present information—from comparison tables to syntax-highlighted code and scannable checklists—even as content streams into the conversation. Citations help readers verify the information presented.  

Make the conversation interactive. HTML widgets (in public preview)embed custom interactive views in an agent’s response. Developers can connect them to business logic and MCP tools, so people can explore options and act in the conversation instead of switching apps.

Watch the Supplier Analyst agent explain its recommendation, show its progress and bring an interactive capacity view into the Teams conversation. 

In the demo, a team member asks Supplier Analyst to explain its supplier recommendation. The agent shows its progress as it reviews capacity, compares suppliers and checks quality requirements and continuity obligations. 

In a thread, Supplier Analyst recommends shortlisting Aster, with conditions: Aster’s indicated capacity of 16 external batches could cover the shortfall, while Meridian’s 12 would leave four batches uncovered. Citations connect the recommendation to supporting evidence, with unresolved requirements clearly flagged. 

At the team’s request, Supplier Analyst adds an HTML widget to the thread. A larger canvas presents next steps, including named owners for outstanding reviews. Adjusting external capacity assumptions immediately changes the displayed coverage and remaining gap. The decision to commit remains with the team. 

Keeping the conversation, supporting evidence and interactive tools together helps people move from discussion toward a decision, with clear owners for the remaining actions and no need to switch apps. 

Build and test the experience 

Get your agent into Teams faster. Socket mode (in public preview) lets developers run and test an agent in Teams without setting up a public HTTPS messaging endpoint or development tunnel. This simplifies testing in a real Teams conversation while building locally. During public preview, socket mode supports newly created agents for development and testing only; production agents still require an HTTPS messaging endpoint. 

Go deeper at Ignite 

See how these capabilities come together to create collaborative agents in Teams. Join us at Ignite to explore what’s possible, then get hands-on with a working example. 

BRK209 | Beyond the Agent: Building Digital Teammates and Agentic Workflows in Microsoft Teams 

Explore how agent identity, conversational context, visible progress and interactive interfaces fit together in collaborative workflows. See how to design agents that contribute to shared work while keeping people in control. View the breakout session. 

LAB651 | Build AI Agents in Teams 

Put the concepts into practice with the Teams SDK. In this hands-on lab, you’ll run and explore Supplier Analyst, the same example used in this post, and learn how its interactions work in Teams. The lab runs four times during Ignite. Choose a lab time.

Ready to get started?

Head to Teams.dev to build your first agent, and check the developer release announcements for the latest capabilities and preview updates. 

The post New Capabilities for Building Digital Teammates in Microsoft Teams appeared first on Microsoft 365 Developer Blog.

Read the whole story
alvinashcraft
1 minute ago
reply
Pennsylvania, USA
Share this story
Delete

Recipe words like 'scant' and 'heaping.' Plus, the strange myth behind the cornucopia

1 Share

1238. This week, we look at why a “scant cup” and a “heaping tablespoon” survived the push for exact measurements. Then, we look at the cornucopia: a goat’s horn from Greek mythology that became a symbol of Thanksgiving abundance.


A hearty thank you to the Keepers of the Commas one mysterious Immortal on Patreon. We appreciate your support!

  • Larry Rosenblum
  • Mahala Russell
  • George Wilson
  • Laurel Paul
  • Linda Cox
  • Birna Anna Björnsdóttir
  • Kate Wade


🔗 Share your familect recording in Speakpipe or by leaving a voicemail at 833-214-GIRL (833-214-4475)

🔗 Watch my LinkedIn Learning writing courses.

🔗 Subscribe to the newsletter.

🔗 Find an edited transcript.

🔗 Get Grammar Girl books.


| HOST: Mignon Fogarty

| Grammar Girl is part of the Quick and Dirty Tips podcast network.

  • Audio Engineer: Dan Feierabend
  • Director of Podcast: Holly Hutchings
  • Advertising Operations Specialist: Morgan Christianson
  • Marketing and Video: Nat Hoopes, Rebekah Sebastian
  • Podcast Associate: Maram Elnagheeb

| Theme music by Catherine Rannus.

| Grammar Girl Social Media: YouTube. TikTok. Facebook. Threads. Instagram. LinkedIn. Mastodon. Bluesky.


Hosted on Acast. See acast.com/privacy for more information.





Download audio: https://sphinx.acast.com/p/open/s/69c1476c007cdcf83fc0964b/e/6af4b7ee3709f3cff2512d63/media.mp3
Read the whole story
alvinashcraft
1 minute ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories