All Microsoft Release Notes (214)

• Jan 13, 2026

  • Parsed from source:
    Jan 13, 2026
  • Detected by Releasebot:
    Jan 14, 2026
  

  Microsoft Copilot by Microsoft

  January 13, 2026

  Microsoft 365 Copilot rolls out a broad update with admin AI disclaimer customization, a unified Library for AI assets, GPT-5 powered agents, Dropbox and Guru integrations, richer data sources, and ServiceNow knowledge templates.

  Microsoft 365 admin center

  • Admin control to customize AI disclaimers in Copilot Chat [Windows, Web]
    We updated the AI Disclaimer experience in Microsoft Copilot Chat based on customer feedback. To address this, we introduced an admin control that allows organizations to customize how the disclaimer appears, improving user awareness and flexibility.
    Details:
    What changed: The AI disclaimer will remain visible in the user experience. Admins will gain the ability to heighten this message and to provide a link to their own documentation: The disclaimer will display bolded text for increased visibility. Admins can configure a custom URL pointing to their AI policy documentation.
    Why: Organizations asked for more control over how the disclaimer appears to improve user awareness and flexibility.
    Try this:

    • Review the new AI Disclaimer setting in the Admin Portal.
    • Decide whether you want to configure this setting for your organization.
    • If desired, prepare a custom URL to include in the UX.
    • Communicate this change to your helpdesk staff and Copilot users.
    • Update internal documentation if you reference the disclaimer experience.
      Why this matters:
      Business impact: Allows organizations to customize how the disclaimer appears.
      Personal impact: Improves user awareness of the disclaimer.

  • Microsoft 365 Copilot app

    • Access all your Copilot-generated content in one library [Android, Windows, iOS, Mac, Web]
      Use the new Library in the Microsoft 365 Copilot app to easily find and manage your Copilot-created images and pages.
      Roadmap ID: 501783
      What changed: A new centralized Library view in Copilot lets users access all their AI-generated assets in one place.
      Why: Improves organization and removes friction in retrieving past Copilot content.
      Try this:
    • Open Copilot app → go to Library
    • Filter by images or summaries
    • Share content in Teams or email
      Business impact: Boosts collaboration by making assets reusable and sharable.
      Personal impact: Saves time by avoiding re-creating previous work.
      Additional resources:
      Learn: Microsoft 365 Copilot Library

  • Microsoft 365 Copilot Chat

    • Search for meetings by organizer using Copilot Chat [Windows]
      Quickly find meetings scheduled by a specific person to review or prioritize your calendar.
      Roadmap ID: 503859
      Description: Quickly find meetings scheduled by a specific person to review or prioritize your calendar.
      What changed: Copilot Chat now lets you search your calendar for meetings organized by a specific individual.
      Why: Helps users locate calendar items and prioritize activities faster.
      Try this
    • Ask Copilot: “Find meetings organized by Alex Johnson next week.”
    • Or: “Summarize action items from last 3 meetings organized by Sarah Davis.”
      Business impact: Reduces wasted time searching for calendar details.
      Personal impact: Gives quick control and visibility over relevant scheduled events.

  • Microsoft 365 Copilot extensibility

    • Build smarter agents with GPT-5 in Agent Builder [Android, Windows, iOS, Mac, Web]
      Create more capable and context-aware Copilot agents powered by GPT-5, delivering richer responses and streamlined experiences for your users.
      Roadmap ID: 502552
      Details:
      What changed: Declarative agents built in Microsoft 365 Copilot now use GPT-5 as the underlying chat model, enabling advanced reasoning, more natural language understanding, and improved multi-step processing.
      Why: Organizations need AI-powered solutions that do not only respond accurately but anticipate user needs. GPT-5 delivers higher precision and better handling of complex queries, resulting in agents that feel more responsive and intelligent, reducing repetitive follow-ups.
      Try This:
    • Open Agent Builder in Microsoft 365 Copilot to create a new declarative agent that runs on GPT‑5 as the foundation.
    • Configure your agent with domain-specific knowledge and test its ability to handle scenario-based queries.
    • Ask your new agent: “Help me draft a Q4 performance summary with recommendations based on last quarter’s sales trends.”
      Why this matters:
      Business Impact: Smarter agents mean streamlined workflows and faster completion of complex business processes, reducing time-to-value and improving ROI on AI initiatives.
      Personal Impact: Users experience fewer frustrations when interacting with Copilot, getting precise answers and recommendations that fit their context—saving time and effort.

  • Connect Dropbox for smarter Copilot file access [Web]
    Integrate Dropbox with Copilot to access, retrieve, and manage files directly, regardless of where they are stored.
    Roadmap ID: 513282
    What Changed: A new Copilot connector allows you to integrate Dropbox into the Microsoft 365 Copilot experience. Once connected, Copilot can retrieve and manage files stored in Dropbox and use them for context in responses.
    Why: This update eliminates friction by letting Copilot work across locations, so users never waste time searching or switching services.
    Try This:

    • In Copilot settings, enable the Dropbox connector and sign in with your account.
    • Ask Copilot, “Summarize the Q4 plan from my Dropbox folder.”
    • Use Copilot in Word to insert insights from Dropbox files into a report.
      Why it Matters:
      Business Impact: Improve team efficiency by unifying data access across platforms, eliminating manual transfers.
      Personal Impact: Create and edit content with ease by letting Copilot pull in what you need, including content from Dropbox.
      Learn: Google Drive Microsoft 365 Copilot connector overview

  • Connect Microsoft 365 Copilot with Guru for enhanced insights [Web]
    Microsoft 365 Copilot can now connect with Guru to surface internal knowledge and team insights, enhancing team collaboration and decision-making.
    Roadmap ID: 513281
    Details:
    What changed: Previously, Microsoft 365 Copilot operated with its standard integrations. With this update, users can connect Microsoft 365 Copilot with Guru, allowing it to access and utilize internal knowledge bases and team insights directly within the workflow.
    Why: This feature was added to leverage the wealth of internal knowledge and insights stored in Guru. By doing so, it enhances decision-making processes and streamlines access to valuable information for team members.
    Try this:

    • Connect Microsoft 365 Copilot with Guru to start accessing your organization's internal knowledge base.
    • Use the Copilot Connector to query specific team insights and data stored in Guru.
    • Implement this connection in your workflow to improve collaboration and information retrieval during meetings or project planning.
      Why this matters:
      Business impact: Integrating Microsoft 365 Copilot with Guru enhances technological capabilities, optimizes workflow efficiency, and strengthens team collaboration by providing immediate access to critical insights.
      Personal impact: Individual users benefit from quicker access to information and insights, aiding personal productivity and informed decision-making.

  • Expand Copilot Agents with Mail, People, and Meeting Insights [Windows, Web]
    Copilot declarative agents can now integrate with richer M365 data: mail, people's data, Teams chats, and meeting transcripts.
    What Changed: Agents can now tap into richer Microsoft 365 data sources - email, Teams chats, meeting transcripts, and people data - to deliver more context-aware answers and automate tasks seamlessly.
    Why: Modern work spans inboxes, chats, calendars, and documents. Constant switching slows teams down. By grounding declarative agents in organizational data, Copilot reduces context-switching, improves accuracy, and accelerates decision-making.
    Try This:

    • Create a declarative agent that uses Meetings data to generate a project summary.
    • Sample query: “Summarize decisions and blockers from this week’s meetings relating to Project X.”
    • Create a declarative agent that uses Email data to draft emails.
    • Sample query: "Draft follow up emails for unresolved items from yesterday."
      Why This Matters:
      Business Impact: Teams work faster when Copilot agents bring context from across Microsoft 365 into one place. By reducing time spent searching through emails, chats and transcripts, organizations improve decision accuracy, accelerate workflows, and keep projects moving without delays.
      Personal Impact: Users no longer need to juggle multiple tools to gather context. Copilot agents can consolidate multiple knowledge capabilities in one place, saving time and reducing cognitive load throughout the workday.
      Additional Resources:
      Learn: Add knowledge sources to your declarative agent

  • Generate Office documents from agents in Copilot Studio lite [Windows, Web]
    Agents built with Copilot Studio lite can generate PowerPoint decks, Excel spreadsheets, and Word documents via chat, with files saved to OneDrive.
    Roadmap ID: 506753
    Details:
    What changed: Office skills are available in Copilot Studio lite. Users can chat with an agent to generate PowerPoint, Excel, and Word files. Files are saved to OneDrive to streamline organization and support retention policies. These skills are part of the “Generate code, graphs, and documents” capability (formerly known as Code Interpreter).
    Why: Automating common document tasks helps teams move faster and maintain consistency, while OneDrive storage supports governance needs.
    Try this:

    • Ask your agent to create a Word document with a project outline.
    • Request an Excel spreadsheet with labeled columns for status tracking.
    • Generate a PowerPoint deck with section titles for an upcoming review.
      Why this matters:
      Business impact: Reduces manual document creation time and supports compliant storage.
      Personal impact: Makes everyday document tasks quicker and easier.
      Additional resources
      Learn: Add capabilities

  • Simplified ServiceNow tickets setup with per-table ACL rules [Web]
    Admins can now define ACL permission rules per table for ServiceNow ticket ingestion, reducing setup complexity.
    Details:
    What changed: Previously, permissions were selected for all tables combined. Now, admins define permission rules for each selected table, improving control and clarity.
    Why: Per-table ACL rules simplify configuration and provide finer-grained access control aligned with data security practices.
    Try this:

    • Set ACL permissions for a single table that requires restricted access.
    • Review and adjust table-level rules to match ingestion needs.
    • Validate table permissions to ensure correct access during ingestion.
      Why this matters:
      Business impact: Reduces configuration complexity and improves security alignment for ticket data.
      Personal impact: Helps individuals manage permissions more clearly and confidently.
      Additional resources:
      Learn: Access permissions

  • Smart document management with Google Drive integration [Web]
    Connect Google Drive to Copilot for smooth collaboration in multiple clouds.
    What Changed: Copilot can access, reference, and combine insights from Google Drive files, allowing for richer, cross-platform collaboration.
    Why: This feature ensures Copilot brings content from different sources together, reducing complexity and improving workflow.
    Try This:

    • Add Google Drive as a connector in Copilot settings.
    • Ask Copilot in Word, “Combine insights from my Google Drive marketing plan and recent reports.”
    • Use Copilot in PowerPoint to create a slide pulling directly from Google Drive data.
      Why it Matters:
      Business Impact: Improves cross-platform workflows in hybrid environments
      Personal Impact: Minimizes context switching and increases document creation efficiency
      Additional resources
      Learn: Google Drive Microsoft 365 Copilot connector overview

  • Template-based knowledge ingestion for ServiceNow Knowledge Connector [Web]
    ServiceNow Knowledge Connector now ingests articles created using out-of-the-box and custom templates, expanding coverage and flexibility.
    Roadmap ID: 505436
    Details:
    What changed: Previously, template-based knowledge articles were not ingested. The connector now supports out-of-the-box templates such as FAQ, How to, and What is, as well as custom templates used by customers.
    Why: Supporting common and custom templates ensures more knowledge content is accessible, improving search and guidance quality.
    Try this:

    • Ingest FAQ template articles to improve self-service answers.
    • Include How to articles to guide users through procedures.
    • Add custom template articles to reflect organizational standards.
      Why this matters:
      Business impact: Broadens access to structured knowledge and improves help coverage for teams.
      Personal impact: Makes it easier for individuals to find accurate, template-based guidance.
      Additional resources:
      Learn: Connector capabilities and limitations

  Original source Report a problem

  Show more
• Jan 11, 2026

  • Parsed from source:
    Jan 11, 2026
  • Detected by Releasebot:
    Jan 13, 2026
  

  Visual Studio Code by Microsoft

  January 2026 Insiders (version 1.109)

  VS Code Insiders release brings advanced terminal features, improved chat session discovery, and new extension APIs with web browser exploration and MCP support. Enjoy timeout controls, safer npm commands, and streamlined quick input options.

  These release notes cover the Insiders build of VS Code and continue to evolve as new features are added. To try the latest updates, download Insiders. To read these release notes online, go to code.visualstudio.com/updates.

  You can still track our progress in the Commit log and our list of Closed issues.

  These release notes were generated using GitHub Copilot and might contain inaccuracies.

  Happy Coding!

  January 11, 2026

  • The terminal now supports the kitty keyboard protocol (CSI u), enabling more sophisticated keyboard input handling and providing access to previously unavailable key combinations.
  • The terminal now supports win32-input-mode, improving keyboard handling compatibility with Windows console applications.
  • The terminal now supports SGR 221 and 222 escape sequences, allowing independent control of bold and faint text attributes for more granular formatting control.
  • Improved discoverability of archived chat sessions in the Chat view, making it easier to locate and access previously archived conversations.

  January 8, 2026

  • The terminal tool now supports a timeout parameter to control how long terminal commands run before timing out, preventing unnecessary polling commands.
  • Updated the list of npm commands that are safe for automatic execution.
  • The terminal suggest toolbar no longer shows the selection mode option when quick suggestions are disabled, reducing confusion.
  • The terminal.integrated.suggest.quickSuggestions setting can now be configured in the Settings editor instead of requiring manual JSON editing.
  • Added a workbench.mcp.startServer command to start a specific or all MCP servers to discover their tools.
  • Exploration work on rich integrated web browser using WebContentsView or controlledframe to overcome limitations of the current iframe-based Simple Browser.
  • A new proposed API enables extensions to show buttons inline after the input box in quick inputs, in addition to the title bar location.

  January 7, 2026

  • You can now import a chat session into the Chat view instead of only opening it in a new editor tab.
  • Fixed an issue where auto approval information for the fetch tool was not visible when hovering over the tool call.
  • Added built-in support for MCP Apps, enabling servers to provide custom UI for tool invocation.

  December 28, 2025

  • The quick input now supports overflow buttons, enabling secondary actions to be placed in an overflow menu.

  We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.

  Original source Report a problem

  Show more
• Jan 9, 2026

  • Parsed from source:
    Jan 9, 2026
  • Detected by Releasebot:
    Sep 29, 2025
  • Modified by Releasebot:
    Jan 17, 2026
  

  Microsoft Edge by Microsoft

  Version 143.0.3650.139: January 9, 2026

  Fixed various bugs, and performance issues.

  Stable channel security updates are listed here.

  Original source Report a problem
• Jan 8, 2026

  • Parsed from source:
    Jan 8, 2026
  • Detected by Releasebot:
    Jan 15, 2026
  

  Visual Studio Code by Microsoft

  December 2025 (version 1.108)

  VS Code’s December 2025 release brings broad feature updates across editor, terminal and collaboration tools plus major stability fixes. It adds Agent Skills, enhanced Agent Sessions, new snippet transforms, Go to Symbol improvements and improved accessibility for a smoother, more productive coding experience.

  December 2025 (version 1.108)
  Release date: January 08, 2026
  Update 1.108.1: The update addresses these issues
  Downloads: Windows: x64 Arm64 | Mac: Universal Intel silicon | Linux: deb rpm tarball Arm snap
  Welcome to the December 2025 release of Visual Studio Code.
  Traditionally, the month of December is a time where our team focuses on cleaning up GitHub issues and pull requests across our repositories. This year, we managed to reduce our open issues by nearly 6,000 and triaged over a thousand more.
  In addition to our housekeeping efforts, we have also made several improvements and feature updates across various areas of VS Code.
  Happy Coding!

  If you'd like to read these release notes online, go to Updates on code.visualstudio.com.

  Insiders: Want to try new features as soon as possible?
  You can download the nightly Insiders build and try the latest updates as soon as they are available.

  Agents
  Agent Skills (Experimental)
  Setting: chat.useAgentSkills
  VS Code now supports Agent Skills, allowing you to teach the coding agent new capabilities and provide domain-specific knowledge. Agent Skills are folders of instructions, scripts, and resources that GitHub Copilot can load when relevant to perform specialized tasks.
  Skills are stored in directories with a SKILL.md file that defines the skill's behavior. VS Code automatically detects skills from the .github/skills folder in your workspace (or .claude/skills/ for backwards compatibility). They are then loaded on-demand into the chat context when relevant for your request.
  Enable support for Agent Skills by enabling the chat.useAgentSkills setting.
  Learn more about creating and using skills in the Agent Skills documentation.

  Improvements to Agent Sessions view
  This iteration, we further improved the Agent Sessions view with several enhancements:
  • Keyboard access support for actions such as archive, read state, opening a session
  • Grouping of sessions based on state and age when showing side-by-side
  • Provide information on changed files and associated PRs for a session
  • Support for archiving multiple sessions at once from the new group sections
  • General accessibility improvements

  Note: chat.viewSessions.orientation no longer provides the auto option. Use sideBySide as alternative.

  Chat
  Chat picker is based on agent sessions
  The Quick Pick for chat sessions is now based on the same information that drives the Agent Sessions view. You can access any previous chat session from there and perform actions like archiving, renaming or deletion.

  Note: Agent sessions can also be accessed by typing agent in the Quick Open control (Ctrl+P).

  Chat title improvements
  The Chat view title control is now showing up, irrespective of how the Activity Bar is configured. Previously, it only showed up in the default Activity Bar configuration.
  To quickly jump from one session to another, select the chat title to open the sessions Quick Pick and choose another session.

  Open empty Chat on restart
  Setting: chat.restoreLastPanelSession
  From now on, previous chat sessions are not automatically restored when VS Code is restarted. Instead, an empty Chat view is shown where you can then access previous sessions from the Agent Sessions control.
  Modify this behavior with the chat.restoreLastPanelSession setting.

  Terminal tool auto approve default rules
  Settings: chat.tools.terminal.enableAutoApprove ORG, chat.tools.terminal.autoApproveWorkspaceNpmScripts
  The following commands are now auto approved by default when terminal auto approve is enabled (chat.tools.terminal.enableAutoApprove ORG):
  • git ls-files
  • git --no-pager
  • git -C
  • rg (excluding --pre and --hostname-bin)
  • sed (excluding some args and usage patterns)
  • Out-String
  In addition, npm scripts run through npm, pnpm, or yarn are now auto approved by default when they are included within the package.json. We do this because using agents already requires Workspace Trust, and we protect agents from editing sensitive files like package.json. This can be disabled with chat.tools.terminal.autoApproveWorkspaceNpmScripts.
  To improve transparency around auto approve, there is now an informational message when a rule was explicitly denied by either default or custom rules:

  Add session and workspace rules for future terminal tool commands
  The allowed commands or command line entries in the Allow dropdown now have options a corresponding action to allow them for the current session or for the workspace.

  Terminal tool preventing adding to shell history
  Setting: chat.tools.terminal.preventShellHistory
  When shell integration is enabled and working, commands that are run by the terminal tool are no longer included in shell history for bash, zsh, pwsh and fish. The method this uses differs for each shell, for bash for example HISTCONTROL=ignorespace is set and a space is added to the start of the command being run.
  If you prefer to keep terminal tool commands in the shell history, configure this with the chat.tools.terminal.preventShellHistory setting.

  Accessibility
  Streaming chat responses in Accessible View
  The Accessible View now dynamically streams chat responses as they are generated. Previously, you needed to close and reopen the Accessible View to see updated content. Now, you can stay in the Accessible View and monitor output as it comes in, making it much easier to follow along with AI responses in real-time.

  MCP server output excluded from Accessible View
  To reduce noise, MCP (Model Context Protocol) server output is now excluded from the Accessible View by default. The standard chat output remains fully accessible, as it's presented in a text area that works well with screen readers.

  Language ID variable in window title
  A new ${activeEditorLanguageId} variable is now available for the window.title setting. This variable displays the language identifier of the currently active editor, which is useful for accessibility tools like Talon that need to determine the current programming language to enable appropriate voice commands.

  Editor Experience
  Import profile by drag and drop
  You can now import a settings profile by dragging and dropping a .code-profile file into VS Code. This makes it easier to share profiles with teammates or quickly set up a new environment.
  When you drop the file, the Profiles editor opens and lets you preview and import the profile. This provides a similar experience to dragging and dropping a .code-workspace file to open a workspace.

  Copy breadcrumbs path
  Setting: breadcrumbs.symbolPathSeparator
  You can now copy the breadcrumbs path to the clipboard by using the Copy Breadcrumbs Path command. This is useful when you need to share the exact location of a symbol with your team or for documentation purposes.
  The breadcrumbs.symbolPathSeparator setting enables you to customize the separator character used to join breadcrumb segments.

  Go to Symbol in Workspace supports special characters in query
  The Go to Symbol in Workspace (Ctrl+T) feature no longer incorrectly filters out all results when the search query contains a # character.
  This fix enables language extensions like rust-analyzer to use # as a modifier in symbol searches. For example, in rust-analyzer, appending # to a query like main# searches for functions in current workspace only.

  Code Editing
  New snippet tranformations
  There are two new snippet transformations available: snakecase and kebabcase. This is how you can use them:
  For snake_case transformation:
  ${TM_FILENAME/(.*)/${1:/snakecase}/}
  This transforms the filename to snake-case format. For example, from MyFileName.txt it makes my_file_name.txt. The kebab-case transformation would be my-file-name.txt.

  Source Control
  Git blame information settings
  Settings: git.blame.ignoreWhitespace, git.blame.editorDecoration.disableHover
  The new git.blame.ignoreWhitespace setting enables you to configure Git blame to ignore whitespace changes when determining which commit last modified a line. This is particularly useful when working with code that has been reformatted, as it helps you identify the commit that made the actual functional change rather than just whitespace adjustments.
  Additionally, the git.blame.editorDecoration.disableHover setting lets you disable the hover tooltip that appears when you hover over a Git blame editor decoration. This can be useful if you prefer a cleaner editing experience and only want to see the inline blame annotations without the additional hover information.

  Authoring commit messages using the editor
  Some time ago we added the capability to use the full editor to author a commit message but the actions to commit or cancel were difficult to discover in the editor title toolbar. We improved the editor overlay control in the lower right-hand corner of the editor and moved these actions there to make them easier to use.

  Worktrees in the Source Control Repositories view (Experimental)
  Settings: scm.repositories.explorer, scm.repositories.selectionMode
  This milestone, we have added a Worktrees node to the Source Control Repositories view. Under this node, you can see the list of the repository worktrees with an inline action to open the worktree in a new window. The context menu also contains an action to open the worktree in the current window, as well as an action to delete the worktree.
  You can enable the experimental repository explorer by setting the scm.repositories.selectionMode and scm.repositories.explorer settings. Give it a try and let us know what other repository artifacts you would like to see in the Repositories explorer.
  Learn more about using source control in VS Code.

  Terminal
  Terminal IntelliSense default UX rework
  During the past two releases, we rolled out terminal IntelliSense to all VS Code Stable users. While much of the feedback was positive, there was a segment of users (mostly terminal power users) that did not like the feature breaking their muscle memory. After a lot of discussion, we decided to switch some defaults, improve discoverability and allow easier inline configuration of the feature.
  The feature itself is still enabled by default, but instead of showing the control automatically when typing (quick suggestions and suggest on trigger characters), it now needs to be explicitly triggered via Ctrl+Space.
  We also improved the "status bar" on the bottom. Previously, it showed insert on the left and Learn more/Configure on the right with their associated keybindings. We got feedback that it's not clear that these can be interacted with, so we now show icons on the right and no longer show the keybindings. The left action now allows rotating through the options for "selection mode", which determines how Tab and Enter react when it's brought up. There's a new eye icon on the right, which enables quick suggestions and suggest on trigger characters again.
  Finally, to still make this powerful feature relatively discoverable without being overbearing, a hint shows when opening a terminal that explains how to show suggestions. The lifecycle of the hint is simplified and it's as easy as clicking "don't show" to get rid of it permanently, just like the similar feature in the editor.
  Beyond this UX rework, these improvements were also done to terminal IntelliSense:
  • We now show files with the executable bit on macOS/Linux
  • Improved completions for npm and git
  • Several fixes to the feature

  Performance and stability improvements
  The terminal saw several important performance and stability improvements this release:
  • node-pty#831: On macOS and Linux, pasting more than 50 characters at once or having Copilot run a large command is no longer throttled and should apply essentially instantly, scaling similarly to other terminals with KBs/MBs of data. This also fixed a crash that could happen on macOS when doing the same thing.
  • vscode#285031, vscode#285032, xterm.js#5548: Fixed several layout thrashing issues that could cause the editor to get laggy.
  • vscode#239541: Fixed a crash that could occur when fonts such as CommitMono were configured in the terminal.

  More comprehensive custom glyphs
  The terminal's GPU accelerated renderer (on by default) has supported custom glyphs for some time for box drawing, block element, and a subset of powerline symbols. This means that you can see these characters without needing to configure a font and they also scale with line height, letter spacing, and should align with each other perfectly.
  In this release, we expanded the number of characters supported to almost 800 by including the majority of custom glyphs supported by any other terminal. This includes ranges that are generally useful in a terminal, specifically these ranges:
  • Box Drawing (U+2500 - U+257F)
  • Block Elements (U+2580 - U+259F)
  • Braille Patterns (U+2800 - U+28FF)
  • Powerline Symbols (U+E0A0 - U+E0D4, Private Use Area)
  • Progress Indicators (U+EE00 - U+EE0B, Private Use Area)
  • Git Branch Symbols (U+F5D0 - U+F60D, Private Use Area)
  • Symbols for Legacy Computing (U+1FB00 - U+1FBFF)
  Here's a visual of the complete set of glyphs:

  Improved rendering of curly underlines
  VS Code has been able to parse and display colored and styled underlines for some time now, but the curly underline's rendering always left something to be desired. The curly underlines should now look very close to how they look in the editor.
  You can try this out for yourself by running this command in bash:
  echo -e '\x1b[4:3mCurly\x1b[0m \x1b[4:3m\x1b[58;5;1mRed\x1b[0m'

  Dimensions visual overlay on resize
  Inspired by a feature in ghostty, we added a brief overlay that shows the current terminal dimensions (columns x rows) when you resize the terminal. This is useful if you want to resize your terminal to a specific size for testing or other purposes.

  New VT features
  The terminal now supports the follow VT features/sequences:
  • Synchronized output: can be used by applications to pause rendering and batch updates in the terminal, which is particularly useful to prevent tearing when rewriting the buffer.
  ◦ DECRQM (CSI ? 2026 $ p)
  ◦ BSU (CSI ? 2026 h)
  ◦ ESU (CSI ? 2026 l)
  • XTVERSION (CSI > 0 q): allows applications to query details about the terminal, the response VS Code will give currently is the "xterm.js" and its version

  Debug
  Organize breakpoints by file
  Setting: debug.breakpointsView.presentation
  Breakpoints can now be shown as a tree, grouped by their file. Enable this by setting debug.breakpointsView.presentation to tree.

  Testing
  Navigate to uncovered regions
  We've added navigation buttons to the test coverage toolbar that allow you to easily jump between regions of uncovered code. You can toggle the test coverage toolbar using the Test: Show Coverage Toolbar command in the Command Palette.

  Contributions to extensions
  GitHub Pull Requests
  There has been more progress on the GitHub Pull Requests extension, which enables you to work on, create, and manage pull requests and issues. New features include:
  • Change a pull request's base branch from the pull request description webview.
  • Convert open pull requests to draft from the pull request description webview.
  • Generate a pull request description for an existing PR, not just new ones.
  Review the changelog for the 0.126.0 release of the extension to learn about everything in the release.

  Extension Authoring
  New Quick Pick properties for prompts and resource URIs
  The Quick Pick API includes two new properties for creating interactive selection interfaces.
  Use the prompt property on QuickPick to display persistent instructional text beneath the input box. The text remains visible while users type, which helps provide guidance or context.
  Use the resourceUri property on QuickPickItem to automatically derive item properties from a resource URI. When provided, VS Code derives:
  • The label from the file name (when set to an empty string)
  • The description from the file path (when set to undefined or an empty string)
  • The icon from the current file icon theme (when iconPath is set to ThemeIcon.File or ThemeIcon.Folder)
  This is useful when building file or folder selection interfaces.

  Engineering
  Housekeeping
  As part of our annual December housekeeping, we spent a majority of time cleaning up GitHub issues and pull requests across all our maintained repositories. This year, we managed to reduce our open issues by 5,951 and triaged another 1,203 issues.
  By using improved triage tooling and deduplication processes, we were able to close a significant number of stale and resolved issues. This has left us with a more manageble project, enabling us to move forward and develop the features that have the most impact for our users. In our core VS Code repository alone, we closed 2,872 issues and triaged another 1,697!
  In June of 2025, we also announced that Copilot had become Open Source! This meant that all related issues would also be filed in the microsoft/vscode repo, and that we had a backlog of issues remaining in microsoft/vscode-copilot-release to take care of. This month, we triaged every issue in the repository and closed 1,659 issues, leaving only 175 open to be migrated.
  Below is a graph that shows how our core vscode repository has grown over the years, and how many issues our amazing community has contributed over time. We appreciate everyone who has contributed issues to our repositories over the years and continued to engage with us. Your feedback is what has made VS Code the product that it is today! 🚀

  Authoring extensions in TypeScript (Experimental)
  It is now possible to author VS Code extensions directly in TypeScript without requiring a build step. This works... but there is still a bit of adventure involved! Many aspects are still untested, such as how to write and run tests, how to publish extensions, and other workflow considerations.
  Learn more about this experimental approach in this GitHub comment.

  Notable fixes
  • vscode#283356 - Fixed regression causing jumping around while scrolling past some chat output

  Thank you
  Contributions to vscode:
  • @abhijit-chikane (Abhijit Chikane): fix: hover focus border cutting at the corners PR #259548
  • @alievilshat (Ilshat Aliyev): Fixed wrong negation in the _shouldRenderHint logic. PR #242479
  • @Andarist (Mateusz Burzyński): Simplify TestInstantiationService#stub overloads PR #282223
  • @anki-code (Andy Kipp): Added Xonsh shell type PR #284044
  • @aryla (Arttu Ylä-Outinen): Fix sticky scroll hover listeners piling up PR #260020
  • @AviVahl (Avi Vahl): fix: ensure fallback to default system monospace font PR #282747
  • @BartolHrg: fix copy with multiple cursors and empty selections PR #256083
  • @Beace (Beace): fix: fix terminal webgl context memory leak PR #279579
  • @bibaswan-bhawal (Bibaswan Bhawal): fix(extensions): allow extensionButton.prominentBackground to take effect PR #276788
  • @chaitanyamedidar (Chaitanya Medidar): Fix Swipe to navigate setting missing description #281997 PR #282220
  • @CyMad7001 (Cyril Madigan): #196344 - Fix installer hang issue PR #228233
  • @daiyam (Baptiste Augrain): fix: correctly pass extension's id when version is also provided PR #279630
  • @eidriahn (Adrian Luca): fix: fixes icons not showing when hovering quick pick checkboxes PR #285250
  • @erezak (Erez Korn): Chat: hide Apply in Editor from Command Palette PR #283486
  • @flying-sheep (Philipp A.): fix: set LANGUAGE for Git PR #285410
  • @gjsjohnmurray (John Murray): Standardize the breadcrumb toggle option label (fix #257550) PR #284486
  • @hickford (M Hickford): Reverse lines: apply to whole document when selection is single line PR #257031
  • @irengrig (Irina Chernushina): Fix memory leak with installing cursor change position listener PR #267799
  • @isksss (isksss): Update: Fixed so that MARK can be used in vue files etc. PR #283583
  • @izolotarev (Igor): Fix color detection in hsl saturation PR #266720
  • @jakebailey (Jake Bailey): Replace old-style TS modules with namespaces PR #282862
  • @jcpetruzza (Daniel Gorin): debug: Fix UI freezing on "continue" with high number of threads PR #283635
  • @JeffreyCA: Update Fig spec for Azure Developer CLI (azd) PR #281127
  • @joeriddles (Joe Riddle): Add snakecase to snippets syntax PR #237110
  • @josephxiao8 (Joseph Xiao): Expected Final Selection After Running Delete Duplicate Lines PR #234799
  • @junhaoliao (Junhao Liao): Suppress unhandled errors in WordHighlighter's runDelayer triggers. PR #285887
  • @kheif (Mehmet Ege Aydın): workbench: add commands to move editor to start and end PR #284999
  • @kortin99 (Kortin Zhou): feat(snippets): add support for kebab-case in snippets tmLanguage syntax PR #222319
  • @maynkxx (mayank choudhary): docs: update Twitter branding to X in README PR #280235
  • @milanchahar (MILAN CHAHAR): Fix terminal icon picker placement PR #281275
  • @mizdra (mizdra): Fix tests that failed in environments where XDG_DATA_HOME is set PR #285402
  • @MohamedEmirHajji (Mohamed Emir HAJJI):
  ◦ Add more git log options to completions PR #282311
  ◦ Markdown preview: filter hidden elements from scroll sync (fix #281247) PR #282506
  • @murataslan1 (Murat Aslan):
  ◦ fix: avoid jumpy scrolling when navigating next/prev problem PR #285634
  ◦ Fix: Replace terminal tabbed view lifecycle hack with Event.once PR #285657
  ◦ Fix: Replace terminal view lifecycle hack with Event.once PR #285661
  • @NriotHrreion (Norcleeh): fix: Latest input is not stored to the history when sending message to a new chat PR #282633
  • @odinGitGmail (odinsam): fix(debug): support C# stack trace format in debug console links PR #281536
  • @przpl: fix(runSubagent): collect computed attachments PR #283750
  • @rducom (Raphael DUCOM): Fix ReDoS in PowerShell prompt detection PR #279853
  • @RedCMD (RedCMD):
  ◦ Add TS/JS Template surrounding brackets PR #255972
  ◦ Fix php indenting #248229 PR #258016
  ◦ Fix FormatOnSave when modificationsIfAvailable PR #283726
  ◦ Support # pragma folding markers in C PR #284927
  • @remcohaszing (Remco Haszing): Fix editor edge clicking PR #262964
  • @Riya-chandra (RIYA_CHANDRA): Show command descriptions as tooltips in Command Palette PR #284609
  • @SalerSimo (Simone Salerno):
  ◦ Exclude terminal editors from recently closed editors history PR #282009
  ◦ Refactor virtual model creation logic in MoveLinesCommand PR #284785
  • @SimonSiefke (Simon Siefke):
  ◦ fix: memory leak in terminal editor PR #279088
  ◦ fix: memory leak in terminal process PR #279167
  ◦ fix: memory leak in terminal process PR #279172
  ◦ fix: memory leak in accessibility signal PR #279242
  ◦ fix: memory leak in local process extension host PR #279351
  ◦ fix: memory leak in extension icon widget PR #280566
  ◦ fix: memory leak in markdown hover PR #280745
  ◦ fix: memory leak in debug session PR #281767
  ◦ fix: memory leak in status bar PR #282246
  ◦ fix: memory leak in ipc PR #282253
  ◦ fix: memory leak in chat list renderer PR #282560
  ◦ fix: memory leak in notebook code scrolling PR #283452
  ◦ fix: memory leak in terminal find widget PR #283466
  ◦ fix: memory leak in mainThreadLanguages PR #283498
  ◦ fix: memory leak in chat widget PR #284288
  ◦ fix: memory leak in terminal chat widget PR #284325
  ◦ fix: memory leak call stack widget PR #286246
  • @sudip-kumar-prasad (Sudip Kumar Prasad): Fix: use codicon id for Command Prompt default profile icon PR #280967
  • @tamuratak (Takashi Tamura):
  ◦ fix: ensure finishedEditing is called in ChatWidget PR #281763
  ◦ include uppercase -I in sed in-place option detection PR #284645
  ◦ Fix context handling in ChatWidget while re-editing PR #285099
  • @ThanhNguyxn (Thanh Nguyen): fix: Panel doesn't close when maximized and center-aligned (fixes #281772) PR #281773
  • @tharani-2006: Terminal: show dimensions overlay while resizing PR #284244
  • @tt0mmy (Tommy): Fix duplicate description in terminal suggestion config PR #279730
  • @yavanosta (Dmitry Guketlev):
  ◦ Fix backward selection when EditContext is off PR #273150
  ◦ InlineEditsView: remove redeclaration of textModel PR #281501
  ◦ SingleUpdatedNextEdit: Correctly apply insertion changes PR #281519

  Contributions to vscode-copilot-chat:
  • @AbdelrahmanAbouelenin (ababouelenin): Update system prompt for VSCModelB. PR #2727
  • @bharatvansh (Ayush Singh): fix(byok): improve Gemini provider error handling and add tests PR #2686

  Contributions to vscode-js-profile-visualizer:
  • @xiaoxiangmoe (ZHAO Jin-Xiang): chore: remove useless package-lock.json files PR #216

  Issue tracking
  Contributions to our issue tracking:
  • @gjsjohnmurray (John Murray)
  • @RedCMD (RedCMD)
  • @tamuratak (Takashi Tamura)
  • @IllusionMH (Andrii Dieiev)
  • @albertosantini (Alberto Santini)

  We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.
  If you'd like to read release notes for previous VS Code versions, go to Updates on code.visualstudio.com.

  Original source Report a problem

  Show more
• Jan 8, 2026

  • Parsed from source:
    Jan 8, 2026
  • Detected by Releasebot:
    Jan 8, 2026
  

  Visual Studio Code by Microsoft

  December 2025 (version 1.108)

  VS Code December 2025 ships new capabilities like Agent Skills and richer Agent Sessions, plus big terminal and accessibility upgrades, editor and source control refinements, and broader glyphs. It pairs user-facing features with performance fixes and behind‑the‑scenes housekeeping that tidy the project.

  Welcome to the December 2025 release of Visual Studio Code.
  Traditionally, the month of December is a time where our team focuses on cleaning up GitHub issues and pull requests across our repositories. This year, we managed to reduce our open issues by nearly 6,000 and triaged over a thousand more.
  In addition to our housekeeping efforts, we have also made several improvements and feature updates across various areas of VS Code.
  Happy Coding!

  If you'd like to read these release notes online, go to Updates on code.visualstudio.com.

  Insiders: Want to try new features as soon as possible?
  You can download the nightly Insiders build and try the latest updates as soon as they are available.

  Agents
  Agent Skills (Experimental)
  Setting: chat.useAgentSkills
  VS Code now supports Agent Skills, allowing you to teach the coding agent new capabilities and provide domain-specific knowledge. Agent Skills are folders of instructions, scripts, and resources that GitHub Copilot can load when relevant to perform specialized tasks.
  Skills are stored in directories with a SKILL.md file that defines the skill's behavior. VS Code automatically detects skills from the .github/skills folder in your workspace (or .claude/skills/ for backwards compatibility). They are then loaded on-demand into the chat context when relevant for your request.
  Enable support for Agent Skills by enabling the chat.useAgentSkills setting.
  Learn more about creating and using skills in the Agent Skills documentation.

  Improvements to Agent Sessions view
  This iteration, we further improved the Agent Sessions view with several enhancements:
  • Keyboard access support for actions such as archive, read state, opening a session
  • Grouping of sessions based on state and age when showing side-by-side
  • Provide information on changed files and associated PRs for a session
  • Support for archiving multiple sessions at once from the new group sections
  • General accessibility improvements

  Note: chat.viewSessions.orientation no longer provides the auto option. Use sideBySide as alternative.

  Chat
  Chat picker is based on agent sessions
  The Quick Pick for chat sessions is now based on the same information that drives the Agent Sessions view. You can access any previous chat session from there and perform actions like archiving, renaming or deletion.

  Note: Agent sessions can also be accessed by typing agent in the Quick Open control (Ctrl+P).

  Chat title improvements
  The Chat view title control is now showing up, irrespective of how the Activity Bar is configured. Previously, it only showed up in the default Activity Bar configuration.
  To quickly jump from one session to another, select the chat title to open the sessions Quick Pick and choose another session.

  Open empty Chat on restart
  Setting: chat.viewRestorePreviousSession
  From now on, previous chat sessions are not automatically restored when VS Code is restarted. Instead, an empty Chat view is shown where you can then access previous sessions from the Agent Sessions control.
  Modify this behavior with the chat.viewRestorePreviousSession setting.

  Terminal tool auto approve default rules
  Settings: chat.tools.terminal.enableAutoApprove, chat.tools.terminal.autoApproveWorkspaceNpmScripts
  The following commands are now auto approved by default when terminal auto approve is enabled (chat.tools.terminal.enableAutoApprove):
  • git ls-files
  • git --no-pager
  • git -C
  • rg (excluding --pre and --hostname-bin)
  • sed (excluding some args and usage patterns)
  • Out-String
  In addition, npm scripts run through npm, pnpm or yarn are now auto approved by default when they are included within the package.json. We do this because using agents already requires Workspace Trust, and we protect agents from editing sensitive files like package.json. This can be disabled with chat.tools.terminal.autoApproveWorkspaceNpmScripts.
  To improve transparency around auto approve, there is now an informational message when a rule was explicitly denied by either default or custom rules.

  Add session and workspace rules for future terminal tool commands
  The allowed commands or command line entries in the Allow dropdown now have options a corresponding action to allow them for the current session or for the workspace.

  Terminal tool preventing adding to shell history
  Setting: chat.tools.terminal.preventShellHistory
  When shell integration is enabled and working, commands that are run by the terminal tool are no longer included in shell history for bash, zsh, pwsh and fish. The method this uses differs for each shell, for bash for example HISTCONTROL=ignorespace is set and a space is added to the start of the command being run.
  If you prefer to keep terminal tool commands in the shell history, configure this with the chat.tools.terminal.preventShellHistory setting.

  Accessibility
  Streaming chat responses in Accessible View
  The Accessible View now dynamically streams chat responses as they are generated. Previously, you needed to close and reopen the Accessible View to see updated content. Now, you can stay in the Accessible View and monitor output as it comes in, making it much easier to follow along with AI responses in real-time.

  MCP server output excluded from Accessible View
  To reduce noise, MCP (Model Context Protocol) server output is now excluded from the Accessible View by default. The standard chat output remains fully accessible, as it's presented in a text area that works well with screen readers.

  Language ID variable in window title
  A new ${activeEditorLanguageId} variable is now available for the window.title setting. This variable displays the language identifier of the currently active editor, which is useful for accessibility tools like Talon that need to determine the current programming language to enable appropriate voice commands.

  Editor Experience
  Import profile by drag and drop
  You can now import a settings profile by dragging and dropping a .code-profile file into VS Code. This makes it easier to share profiles with teammates or quickly set up a new environment.
  When you drop the file, the Profiles editor opens and lets you preview and import the profile. This provides a similar experience to dragging and dropping a .code-workspace file to open a workspace.

  Copy breadcrumbs path
  Setting: breadcrumbs.symbolPathSeparator
  You can now copy the breadcrumbs path to the clipboard by using the Copy Breadcrumbs Path command. This is useful when you need to share the exact location of a symbol with your team or for documentation purposes.
  The breadcrumbs.symbolPathSeparator setting enables you to customize the separator character used to join breadcrumb segments.

  Go to Symbol in Workspace supports special characters in query
  The Go to Symbol in Workspace (Ctrl+T) feature no longer incorrectly filters out all results when the search query contains a # character.
  This fix enables language extensions like rust-analyzer to use # as a modifier in symbol searches. For example, in rust-analyzer, appending # to a query like main# searches for functions in current workspace only.

  Code Editing
  New snippet tranformations
  There are two new snippet transformations available: snakecase and kebabcase. This is how you can use them:
  For snake_case transformation:
  ${TM_FILENAME/(.*)/${1:/snakecase}/}
  This transforms the filename to snake-case format. For example, from MyFileName.txt it makes my_file_name.txt. The kebab-case transformation would be my-file-name.txt.

  Source Control
  Git blame information settings
  Settings: git.blame.ignoreWhitespace, git.blame.editorDecoration.disableHover
  The new git.blame.ignoreWhitespace setting enables you to configure Git blame to ignore whitespace changes when determining which commit last modified a line. This is particularly useful when working with code that has been reformatted, as it helps you identify the commit that made the actual functional change rather than just whitespace adjustments.
  Additionally, the git.blame.editorDecoration.disableHover setting lets you disable the hover tooltip that appears when you hover over a Git blame editor decoration. This can be useful if you prefer a cleaner editing experience and only want to see the inline blame annotations without the additional hover information.

  Authoring commit messages using the editor
  Some time ago we added the capability to use the full editor to author a commit message but the actions to commit or cancel were difficult to discover in the editor title toolbar. We improved the editor overlay control in the lower right-hand corner of the editor and moved these actions there to make them easier to use.

  Worktrees in the Source Control Repositories view (Experimental)
  Settings: scm.repositories.explorer, scm.repositories.selectionMode
  This milestone, we have added a Worktrees node to the Source Control Repositories view. Under this node, you can see the list of the repository worktrees with an inline action to open the worktree in a new window. The context menu also contains an action to open the worktree in the current window, as well as an action to delete the worktree.
  You can enable the experimental repository explorer by setting the scm.repositories.selectionMode and scm.repositories.explorer settings. Give it a try and let us know what other repository artifacts you would like to see in the Repositories explorer.
  Learn more about using source control in VS Code.

  Terminal
  Terminal IntelliSense default UX rework
  During the past two releases, we rolled out terminal IntelliSense to all VS Code Stable users. While much of the feedback was positive, there was a segment of users (mostly terminal power users) that did not like the feature breaking their muscle memory. After a lot of discussion, we decided to switch some defaults, improve discoverability and allow easier inline configuration of the feature.
  The feature itself is still enabled by default, but instead of showing the control automatically when typing (quick suggestions and suggest on trigger characters), it now needs to be explicitly triggered via Ctrl+Space.
  We also improved the "status bar" on the bottom. Previously, it showed insert on the left and Learn more/Configure on the right with their associated keybindings. We got feedback that it's not clear that these can be interacted with, so we now show icons on the right and no longer show the keybindings. The left action now allows rotating through the options for "selection mode", which determines how Tab and Enter react when it's brought up. There's a new eye icon on the right, which enables quick suggestions and suggest on trigger characters again.
  Finally, to still make this powerful feature relatively discoverable without being overbearing, a hint shows when opening a terminal that explains how to show suggestions. The lifecycle of the hint is simplified and it's as easy as clicking "don't show" to get rid of it permanently, just like the similar feature in the editor.
  Beyond this UX rework, these improvements were also done to terminal IntelliSense:
  • We now show files with the executable bit on macOS/Linux
  • Improved completions for npm and git
  • Several fixes to the feature

  Performance and stability improvements
  The terminal saw several important performance and stability improvements this release:
  • node-pty#831: On macOS and Linux, pasting more than 50 characters at once or having Copilot run a large command is no longer throttled and should apply essentially instantly, scaling similarly to other terminals with KBs/MBs of data. This also fixed a crash that could happen on macOS when doing the same thing.
  • vscode#285031, vscode#285032, xterm.js#5548: Fixed several layout thrashing issues that could cause the editor to get laggy.
  • vscode#239541: Fixed a crash that could occur when fonts such as CommitMono were configured in the terminal.

  More comprehensive custom glyphs
  The terminal's GPU accelerated renderer (on by default) has supported custom glyphs for some time for box drawing, block element, and a subset of powerline symbols. This means that you can see these characters without needing to configure a font and they also scale with line height, letter spacing, and should align with each other perfectly.
  In this release, we expanded the number of characters supported to almost 800 by including the majority of custom glyphs supported by any other terminal. This includes ranges that are generally useful in a terminal, specifically these ranges:
  • Box Drawing (U+2500 - U+257F)
  • Block Elements (U+2580 - U+259F)
  • Braille Patterns (U+2800 - U+28FF)
  • Powerline Symbols (U+E0A0 - U+E0D4, Private Use Area)
  • Progress Indicators (U+EE00 - U+EE0B, Private Use Area)
  • Git Branch Symbols (U+F5D0 - U+F60D, Private Use Area)
  • Symbols for Legacy Computing (U+1FB00 - U+1FBFF)
  Here's a visual of the complete set of glyphs:

  Improved rendering of curly underlines
  VS Code has been able to parse and display colored and styled underlines for some time now, but the curly underline's rendering always left something to be desired. The curly underlines should now look very close to how they look in the editor.
  You can try this out for yourself by running this command in bash:
  echo -e '\x1b[4:3mCurly\x1b[0m \x1b[4:3m\x1b[58;5;1mRed\x1b[0m'

  Dimensions visual overlay on resize
  Inspired by a feature in ghostty, we added a brief overlay that shows the current terminal dimensions (columns x rows) when you resize the terminal. This is useful if you want to resize your terminal to a specific size for testing or other purposes.

  New VT features
  The terminal now supports the follow VT features/sequences:
  • Synchronized output: can be used by applications to pause rendering and batch updates in the terminal, which is particularly useful to prevent tearing when rewriting the buffer.
  ◦ DECRQM (CSI ? 2026 $ p)
  ◦ BSU (CSI ? 2026 h)
  ◦ ESU (CSI ? 2026 l)
  • XTVERSION (CSI > 0 q): allows applications to query details about the terminal, the response VS Code will give currently is the "xterm.js" and its version

  Debug
  Organize Breakpoints by File
  Breakpoints can now be shown as a tree, group by their file, using the setting debug.breakpointsView.presentation.

  Testing
  Navigate to uncovered regions
  We've added navigation buttons to the test coverage toolbar that allow you to easily jump between regions of uncovered code.
  You can toggle the test coverage toolbar using the Test: Show Coverage Toolbar command.

  Contributions to extensions
  GitHub Pull Requests
  There has been more progress on the GitHub Pull Requests extension, which enables you to work on, create, and manage pull requests and issues. New features include:
  • Change a pull request's base branch from the pull request description webview.
  • Convert open pull requests to draft from the pull request description webview.
  • Generate a pull request description for an existing PR, not just new ones.
  Review the changelog for the 0.126.0 release of the extension to learn about everything in the release.

  Extension Authoring
  New Quick Pick properties for prompts and resource URIs
  The Quick Pick API includes two new properties for creating interactive selection interfaces.
  Use the prompt property on QuickPick to display persistent instructional text beneath the input box. The text remains visible while users type, which helps provide guidance or context.
  Use the resourceUri property on QuickPickItem to automatically derive item properties from a resource URI. When provided, VS Code derives:
  • The label from the file name (when set to an empty string)
  • The description from the file path (when set to undefined or an empty string)
  • The icon from the current file icon theme (when iconPath is set to ThemeIcon.File or ThemeIcon.Folder)
  This is useful when building file or folder selection interfaces.

  Engineering
  Housekeeping
  As part of our annual December housekeeping, we spent a majority of time cleaning up GitHub issues and pull requests across all our maintained repositories. This year, we managed to reduce our open issues by 5,951 and triaged another 1,203 issues.
  By using improved triage tooling and deduplication processes, we were able to close a significant number of stale and resolved issues. This has left us with a more manageble project, enabling us to move forward and develop the features that have the most impact for our users. In our core VS Code repository alone, we closed 2,872 issues and triaged another 1,697!
  In June of 2025, we also announced that Copilot had become Open Source! This meant that all related issues would also be filed in the microsoft/vscode repo, and that we had a backlog of issues remaining in microsoft/vscode-copilot-release to take care of. This month, we triaged every issue in the repository and closed 1,659 issues, leaving only 175 open to be migrated.
  Below is a graph that shows how our core vscode repository has grown over the years, and how many issues our amazing community has contributed over time. We appreciate everyone who has contributed issues to our repositories over the years and continued to engage with us. Your feedback is what has made VS Code the product that it is today! 🚀

  Authoring extensions in TypeScript (Experimental)
  It is now possible to author VS Code extensions directly in TypeScript without requiring a build step. This works... but there is still a bit of adventure involved! Many aspects are still untested, such as how to write and run tests, how to publish extensions, and other workflow considerations.
  Learn more about this experimental approach in this GitHub comment.

  Notable fixes
  • vscode#283356 - Fixed regression causing jumping around while scrolling past some chat output

  Thank you
  Contributions to vscode:
  • @abhijit-chikane (Abhijit Chikane): fix: hover focus border cutting at the corners PR #259548
  • @alievilshat (Ilshat Aliyev): Fixed wrong negation in the _shouldRenderHint logic. PR #242479
  • @Andarist (Mateusz Burzyński): Simplify TestInstantiationService#stub overloads PR #282223
  • @anki-code (Andy Kipp): Added Xonsh shell type PR #284044
  • @aryla (Arttu Ylä-Outinen): Fix sticky scroll hover listeners piling up PR #260020
  • @AviVahl (Avi Vahl): fix: ensure fallback to default system monospace font PR #282747
  • @BartolHrg: fix copy with multiple cursors and empty selections PR #256083
  • @Beace (Beace): fix: fix terminal webgl context memory leak PR #279579
  • @bibaswan-bhawal (Bibaswan Bhawal): fix(extensions): allow extensionButton.prominentBackground to take effect PR #276788
  • @chaitanyamedidar (Chaitanya Medidar): Fix Swipe to navigate setting missing description #281997 PR #282220
  • @CyMad7001 (Cyril Madigan): #196344 - Fix installer hang issue PR #228233
  • @daiyam (Baptiste Augrain): fix: correctly pass extension's id when version is also provided PR #279630
  • @eidriahn (Adrian Luca): fix: fixes icons not showing when hovering quick pick checkboxes PR #285250
  • @erezak (Erez Korn): Chat: hide Apply in Editor from Command Palette PR #283486
  • @flying-sheep (Philipp A.): fix: set LANGUAGE for Git PR #285410
  • @gjsjohnmurray (John Murray): Standardize the breadcrumb toggle option label (fix #257550) PR #284486
  • @hickford (M Hickford): Reverse lines: apply to whole document when selection is single line PR #257031
  • @irengrig (Irina Chernushina): Fix memory leak with installing cursor change position listener PR #267799
  • @isksss (isksss): Update: Fixed so that MARK can be used in vue files etc. PR #283583
  • @izolotarev (Igor): Fix color detection in hsl saturation PR #266720
  • @jakebailey (Jake Bailey): Replace old-style TS modules with namespaces PR #282862
  • @jcpetruzza (Daniel Gorin): debug: Fix UI freezing on "continue" with high number of threads PR #283635
  • @JeffreyCA: Update Fig spec for Azure Developer CLI (azd) PR #281127
  • @joeriddles (Joe Riddle): Add snakecase to snippets syntax PR #237110
  • @josephxiao8 (Joseph Xiao): Expected Final Selection After Running Delete Duplicate Lines PR #234799
  • @junhaoliao (Junhao Liao): Suppress unhandled errors in WordHighlighter's runDelayer triggers. PR #285887
  • @kheif (Mehmet Ege Aydın): workbench: add commands to move editor to start and end PR #284999
  • @kortin99 (Kortin Zhou): feat(snippets): add support for kebab-case in snippets tmLanguage syntax PR #222319
  • @maynkxx (mayank choudhary): docs: update Twitter branding to X in README PR #280235
  • @milanchahar (MILAN CHAHAR): Fix terminal icon picker placement PR #281275
  • @mizdra (mizdra): Fix tests that failed in environments where XDG_DATA_HOME is set PR #285402
  • @MohamedEmirHajji (Mohamed Emir HAJJI):
  ◦ Add more git log options to completions PR #282311
  ◦ Markdown preview: filter hidden elements from scroll sync (fix #281247) PR #282506
  • @murataslan1 (Murat Aslan):
  ◦ fix: avoid jumpy scrolling when navigating next/prev problem PR #285634
  ◦ Fix: Replace terminal tabbed view lifecycle hack with Event.once PR #285657
  ◦ Fix: Replace terminal view lifecycle hack with Event.once PR #285661
  • @NriotHrreion (Norcleeh): fix: Latest input is not stored to the history when sending message to a new chat PR #282633
  • @odinGitGmail (odinsam): fix(debug): support C# stack trace format in debug console links PR #281536
  • @przpl: fix(runSubagent): collect computed attachments PR #283750
  • @rducom (Raphael DUCOM): Fix ReDoS in PowerShell prompt detection PR #279853
  • @RedCMD (RedCMD):
  ◦ Add TS/JS Template surrounding brackets PR #255972
  ◦ Fix php indenting #248229 PR #258016
  ◦ Fix FormatOnSave when modificationsIfAvailable PR #283726
  ◦ Support # pragma folding markers in C PR #284927
  • @remcohaszing (Remco Haszing): Fix editor edge clicking PR #262964
  • @Riya-chandra (RIYA_CHANDRA): Show command descriptions as tooltips in Command Palette PR #284609
  • @SalerSimo (Simone Salerno):
  ◦ Exclude terminal editors from recently closed editors history PR #282009
  ◦ Refactor virtual model creation logic in MoveLinesCommand PR #284785
  • @SimonSiefke (Simon Siefke):
  ◦ fix: memory leak in terminal editor PR #279088
  ◦ fix: memory leak in terminal process PR #279167
  ◦ fix: memory leak in terminal process PR #279172
  ◦ fix: memory leak in accessibility signal PR #279242
  ◦ fix: memory leak in local process extension host PR #279351
  ◦ fix: memory leak in extension icon widget PR #280566
  ◦ fix: memory leak in markdown hover PR #280745
  ◦ fix: memory leak in debug session PR #281767
  ◦ fix: memory leak in status bar PR #282246
  ◦ fix: memory leak in ipc PR #282253
  ◦ fix: memory leak in chat list renderer PR #282560
  ◦ fix: memory leak in notebook code scrolling PR #283452
  ◦ fix: memory leak in terminal find widget PR #283466
  ◦ fix: memory leak in mainThreadLanguages PR #283498
  ◦ fix: memory leak in chat widget PR #284288
  ◦ fix: memory leak in terminal chat widget PR #284325
  ◦ fix: memory leak call stack widget PR #286246
  • @sudip-kumar-prasad (Sudip Kumar Prasad): Fix: use codicon id for Command Prompt default profile icon PR #280967
  • @tamuratak (Takashi Tamura):
  ◦ fix: ensure finishedEditing is called in ChatWidget PR #281763
  ◦ include uppercase -I in sed in-place option detection PR #284645
  ◦ Fix context handling in ChatWidget while re-editing PR #285099
  • @ThanhNguyxn (Thanh Nguyen): fix: Panel doesn't close when maximized and center-aligned (fixes #281772) PR #281773
  • @tharani-2006: Terminal: show dimensions overlay while resizing PR #284244
  • @tt0mmy (Tommy): Fix duplicate description in terminal suggestion config PR #279730
  • @yavanosta (Dmitry Guketlev):
  ◦ Fix backward selection when EditContext is off PR #273150
  ◦ InlineEditsView: remove redeclaration of textModel PR #281501
  ◦ SingleUpdatedNextEdit: Correctly apply insertion changes PR #281519

  Contributions to vscode-copilot-chat:
  • @AbdelrahmanAbouelenin (ababouelenin): Update system prompt for VSCModelB. PR #2727
  • @bharatvansh (Ayush Singh): fix(byok): improve Gemini provider error handling and add tests PR #2686

  Contributions to vscode-js-profile-visualizer:
  • @xiaoxiangmoe (ZHAO Jin-Xiang): chore: remove useless package-lock.json files PR #216

  Issue tracking
  Contributions to our issue tracking:
  • @gjsjohnmurray (John Murray)
  • @RedCMD (RedCMD)
  • @tamuratak (Takashi Tamura)
  • @IllusionMH (Andrii Dieiev)
  • @albertosantini (Alberto Santini)

  We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.
  If you'd like to read release notes for previous VS Code versions, go to Updates on code.visualstudio.com.

  Original source Report a problem

  Show more
• Dec 30, 2025

  • Parsed from source:
    Dec 30, 2025
  • Detected by Releasebot:
    Jan 18, 2026
  

  Excel by Microsoft

  Excel in 2025: A Year of Culture, Craft, and Copilot

  Excel closes 2025 with bold AI powered updates and a strong cultural moment. Agent Mode, Copilot in cells, and smarter formula completion redefine workflows while celebrating 40 years of impact.

  As 2025 comes to a close, one thing feels clearer than ever: Excel is no longer just something you use. It’s something you belong to.
  This year brought major product innovations, many powered by AI, but it also delivered something just as meaningful: cultural moments that reminded us how deeply Excel is woven into work, learning, creativity, and even competition around the world.
  From celebrating a milestone birthday, to watching spreadsheets light up arenas and streaming platforms, to shipping some of our most ambitious product updates yet, 2025 was a year we’re incredibly proud of. And none of it would have happened without you.
  Let’s take a look back.

  A Cultural Year for Excel

  Excel Turns 40!

  In 2025, Excel celebrated its 40th birthday —four decades of helping people think, analyze, build, and decide more effectively.
  What began as a simple spreadsheet application in 1985 has evolved into a foundational tool used by hundreds of millions of people across industries, roles, and continents. Over the years, Excel has adapted to new technologies, new ways of working, and entirely new audiences, without losing the core flexibility that made it so powerful in the first place.
  We marked this milestone by reflecting on Excel’s past and, more importantly, its future: one where data literacy, accessibility, and creativity continue to expand.
  👉 Read more in Excel Turns 40: Join the Celebration!

  The Excel World Championship Goes Mainstream

  If you needed proof that spreadsheets have officially entered pop culture, look no further than the Excel World Championship (EWC).
  In 2025, the competition reached new heights with larger audiences, more global participation, and unprecedented attention. What began as a niche idea has grown into a true esports-style event that proves how dynamic, fast-paced and thrilling Excel can be in expert hands.
  Watching competitors solve complex problems live under pressure and at speed was both entertaining and inspiring. It showed that Excel mastery is a real skill built through practice, creativity and deep understanding.
  👉 Read more in Congrats to the Winners of the 2025 MECC & MEWC!

  Spreadsheet Champions Brings Excel to the Big Screen

  This year also saw the release of Spreadsheet Champions, a documentary that follows six students from different countries on their unique journeys to achieve excellence in competitive Excel.
  More than just a story about formulas and grids, the film is about community, curiosity, and the joy of solving problems together. It captured something we see every day across forums, classrooms, livestreams, and workplaces: Excel brings people together.
  For many of us on the Excel team, seeing these stories told so thoughtfully was deeply moving—and a powerful reminder of who we’re building for.
  👉 Read more in Celebrating the Premiere of “Spreadsheet Champions” at the Melbourne International Film Festival

  A Breakthrough Year for the Product

  While Excel’s cultural presence grew, 2025 was also one of the most ambitious product years in recent memory.

  Agent Mode in Excel

  One of the biggest shifts came with Agent Mode in Excel —a new way to approach work that moves beyond asking for help, to delegating outcomes.
  Instead of manually building step-by-step solutions, users can now describe goals and let Excel reason through the steps: gathering data, applying transformations, and explaining results along the way. It’s a meaningful step toward making Excel not just reactive, but proactive.
  Agent Mode doesn’t replace expertise; it amplifies it.
  👉 Read more in Building Agent Mode in Excel

  The COPILOT Function Arrives

  In 2025, Copilot became more deeply embedded directly into the Excel grid with the introduction of the COPILOT function.
  For the first time, users can call Copilot like a formula, bringing AI-powered reasoning directly into cells alongside traditional Excel functions. This bridges the gap between natural language requests and structured spreadsheet logic, unlocking entirely new workflows.
  It’s one of the clearest examples yet of how AI and spreadsheets can work together seamlessly.
  👉 Read more in Bring AI to your formulas with the COPILOT function in Excel

  Formula Completion Gets Smarter

  Excel has always been about speed and precision, and in 2025 we made writing formulas easier than ever with improved formula completion.
  Smarter suggestions, better context awareness, and faster recommendations mean less time remembering syntax, and more time focusing on insights. Whether you’re learning Excel or pushing it to its limits, formula completion now meets you where you are.
  Small improvements like this matter. They add up to a smoother, more confident experience for everyone.
  👉 Read more in Introducing formula completion - A new way to write formulas in Excel using Copilot

  Thank You for an Incredible Year 💚

  If there’s one theme that defines Excel in 2025, it’s this: progress powered by community.
  Every feature we shipped and every moment we celebrated was shaped by customer feedback, creator experimentation, MVP insight, and everyday use in the real world. You pushed us, inspired us, and reminded us why Excel continues to matter—40 years on.
  As we head into 2026, we’re excited to keep building with you.
  Thank you for being part of the Excel story.

  Original source Report a problem

  Show more
• Dec 23, 2025

  • Parsed from source:
    Dec 23, 2025
  • Detected by Releasebot:
    Dec 24, 2025
  

  Microsoft Copilot by Microsoft

  December 23, 2025

  Microsoft 365 Copilot now runs GPT-5 by default across Chat and apps, delivering faster, smarter results. New extensibility, asset sharing, and governance updates include Freshservice docs, 512 MB file uploads, SDKs for .NET/Python/TypeScript, and Word citations.

  Updates released between December 10, 2025, and December 23, 2025.

  Microsoft 365 Copilot app

  • GPT-5 powers Copilot Chat by default [Android, Windows, iOS, Mac, Web]
    Copilot Chat delivers faster, smarter results using GPT-5 as the default model.
    Details:
    What Changed: All Copilot Chat experiences run on GPT-5 by default. Copilot automatically routes prompts to the best-performing models for each task, using fast models for basic tasks and specialized reasoning models for multi-step requests.
    Why: Users want speed, accuracy, and minimal friction. This update helps to ensure consistent, high-quality AI interactions in Copilot Chat.
    Try This:
  • “Get me up to speed on the latest plans related to [project/initiative]. Help me think through what to do next.”
  • “Use the attached spreadsheet with customer feedback to create a polished executive report that helps upper management decide where to prioritize resources in our next cycle.”
    Why this matters:
    Business Impact: Increases accuracy and productivity, helping teams make strong decisions and complete complex work faster.
    Personal Impact: Removes friction by letting Copilot choose the best model--fast or reasoning--for the prompt.
    Additional Resources:
    Blog:
    Available today: GPT-5 in Microsoft 365 Copilot

  Microsoft 365 Copilot Chat

  • Streamlined Copilot chat navigation with expanded history [Windows, Web]
    A redesigned navigation pane provides a cleaner layout and expanded chat history, making it easier to switch between conversations. This allows you to switch between conversations and pick up where you left off, perfect great for fast-paced projects and multitasking.
    Roadmap ID:
    516570
    Details:
    What Changed: The Copilot navigation pane highlights key agents, removes clutter, and expands visible chat history beyond the previous limit of five recent chats. Chat search is also more prominent for faster access to specific threads. This reduces interface clutter.
    Why: Users wanted an interface that feels organized and speeds up workflow. This redesign lets you quickly return to prior conversations without digging through menus.
    Try This:
  • Open the navigation pane in Copilot to see the improved design.
  • Search for a previous project conversation using the updated chat search bar.
  • Pin your most important chats to keep them accessible during critical work sessions.
    Why this matters:
    Business Impact: Standard, simplified navigation UI to help reduce downtime from searching old threads.
    Personal Impact: Enjoy a simpler, less cluttered workspace with easier access to past chats.

  Microsoft 365 Copilot extensibility

  • Access IT service documentation with Freshservice integration [Web]
    Let Copilot retrieve IT documentation and troubleshooting instructions directly from Freshservice with this integration.
    Roadmap ID:
    513280
    Details:
    What Changed: Freshservice connector gives access to IT procedures and knowledge articles
    Why: IT teams and employees often struggle with finding the right documentation. With Copilot pulling service details in real time, response times and productivity benefit.
    Try This:
  • Connect Freshservice in Copilot settings.
  • Ask Copilot, “What’s the procedure for resetting passwords from Freshservice?”
  • Insert a troubleshooting guide directly into a Teams post for your team.
    Why this matters:
    Business Impact: Faster issue resolution reduces downtime and keeps employees productive.
    Personal Impact: Remove frustration, solve issues, and prevent delays caused by searching for documentation.
    Additional resources:
    Learn:
    Freshservice Microsoft 365 Copilot connector overview
  • Upload Larger Files in Copilot Studio Agent Builder [Android, Windows, iOS, Web]
    Agent Builder now supports file uploads up to 512 MB when creating agents, ideal for larger files.
    Roadmap ID:
    500375
    Details:
    What Changed: This increases the upload size limit in Agent Builder to 512 MB, enabling use of larger files as grounding data.
    Why: Users requested more flexibility for grounding agents. Larger files improve reduce the need to split or compress documents.
    Try This:
  • Drag and drop large documents such as training manuals into your agent project.
  • Create the agent and ask it to summarize information from uploaded files.
    Why this matters:
    Business Impact: Allows enterprises to build agents with richer, domain-specific knowledge.
    Personal Impact: Complete your work without the need to split files or compress data.
    Additional resources:
    Learn:
    Embedded file content
  • Use .NET client libraries to integrate Microsoft 365 Copilot APIs [Web]
    Offers official .NET SDKs for integrating with Microsoft 365 Copilot APIs.
    Details:
    What changed: Released a .NET SDK for Copilot API calls, making integration easier.
    Why: Meets enterprise developers’ need for secure .NET integration options.
    Try This:
  • Install NuGet package
  • Authenticate and initiate Copilot prompt calls
  • Process responses in your .NET app
    Why this matters:
    Business Impact: Improves developer productivity and project speed.
    Personal Impact: Gives .NET teams direct hooks into Copilot capabilities.
    Additional Resources:
    Learn:
    Microsoft 365 Copilot APIs client libraries
  • Use Python client libraries to integrate Microsoft 365 Copilot APIs [Web]
    Adds official Python libraries for secure integration with Microsoft 365 Copilot APIs.
    Details:
    What changed: Developers can now leverage Microsoft 365 Copilot APIs using Python SDKs.
    Why: Opens opportunities for AI workflows in Python-based applications.
    Try This:
  • Install Python SDK
  • Authenticate using OAuth
  • Send prompts and parse results
    Why this matters:
    Business Impact: Expands Copilot customization for enterprise developers.
    Personal Impact: Python devs gain first-class access to Copilot APIs.
    Additional Resources:
    Learn:
    Microsoft 365 Copilot APIs client libraries
  • Use TypeScript client libraries to integrate Microsoft 365 Copilot APIs [Web]
    Build custom integrations with Microsoft 365 Copilot APIs using official TypeScript SDK libraries.
    Roadmap ID:
    501574
    Details:
    What changed: Official TypeScript SDK released for Copilot API integration in web apps.
    Why: Standardizes developer integration with Microsoft 365 Copilot features.
    Try This:
  • Install SDK via npm
  • Authenticate using Microsoft Identity
  • Test API calls for Copilot prompts
    Why this matters:
    Business Impact: Enables custom enterprise apps with AI-powered features.
    Personal Impact: Developers have a secure, documented method for advanced builds.
    Additional Resources:
    Learn:
    Microsoft 365 Copilot APIs client libraries
  • View and Manage SharePoint Agents with Greater Control [Web]
    Admins can now see all SharePoint agents in a single unified view and manage them more intuitively with a streamlined delete action.
    Details:
    What Changed: The enhanced Copilot Control System UI introduces a centralized SharePoint agent inventory and replaces the previous block/unblock workflow with a clear, simplified delete option.
    Why: Admins requested more transparent oversight of deployed agents, and this update delivers easier tracking, review, and lifecycle management.
    Try This:
  • Go to Agents and Connectors in the Copilot Control System.
  • Review all existing SharePoint agents and delete those that are outdated, unused, or no longer compliant.
    Why this matters:
    Business Impact: Strengthens governance and operational hygiene by reducing risk from stale or misconfigured agents.
    Personal Impact: Saves time with straightforward, intuitive controls instead of complex, multi-step administration.

  Microsoft 365 Copilot Studio

  • Build Copilot agents using organizational People data [Windows, Web]
    Developers can build agents in Copilot Studio that deliver personalized, context-aware responses using organizational People data.
    Details:
    What changed: Added the ability for agent builders to access and use People data from your directory in responses.
    Why: Makes interactions more contextual and human-centric for better relevance.
    Try This:
  • Enable People data in Agent Builder
  • Create an agent to answer org-specific directory questions
  • Test in Microsoft Teams
    Why this matters:
    Business Impact: Improves accuracy and personalization in enterprise workflows.
    Personal Impact: Users get tailored answers courtesy of context-rich data.
    Additional Resources:
    Learn:
    Add knowledge sources to your declarative agent in Microsoft 365 Copilot

  PowerPoint

  • Use your organization’s approved assets in Copilot presentations [Mac, Windows, Web]
    Create branded PowerPoint slides by pulling images and templates from your company’s SharePoint asset library or Templafy integration.
    Roadmap ID:
    496366
    Details:
    What changed: PowerPoint Copilot integrates with SharePoint Organization Asset Library and Templafy for approved, compliant visuals.
    Why: Ensures quality designs aligned with corporate branding guidelines.
    Try This:
  • Configure SharePoint OAL or Templafy in Microsoft 365
  • Ask Copilot: “Create a marketing update deck using brand imagery.”
    Why this matters:
    Business Impact: Maintains brand identity across all content.
    Personal Impact: Saves design time by eliminating manual asset searching.
    Additional Resources:
    Learn:
    Create an organization assets library

  Word

  • Referenced sources cited in drafted content [Windows]
    Draft content with confidence as Copilot automatically includes citations, referencing the information in your text. This feature ensures accuracy and credibility, saving time on manual citation.
    Roadmap ID:
    380842
    Details:
    What changed: Copilot in Word now automatically generates citations when incorporating external information into your drafts. This process highlights references directly within the text, eliminating the need for manual citation entry.
    Why: Proper attribution is vital for maintaining credibility and avoiding plagiarism. This enhancement simplifies the citation process, ensuring academic and professional integrity without added effort.
    Try This:
  • While drafting in Word, ask Copilot: "Include citations for referenced content."
  • Use Copilot commands to review the generated citations for completeness and accuracy.
  • Compare the citation style used with your preferred or required academic formatting.
    Why this matters:
    Business Impact: Enhances the reliability of professional documents by ensuring proper attribution without a complex citation process.
    Personal Impact: Save time creating references, allowing more focus on content quality and creativity.

  Original source Report a problem

  Show more
• Dec 17, 2025

  • Parsed from source:
    Dec 17, 2025
  • Detected by Releasebot:
    Jan 18, 2026
  

  Dynamics 365 Finance by Microsoft

  What's new or changed in Dynamics 365 Finance 10.0.46 (December 2025)

  Dynamics 365 Finance 10.0.46 brings broad updates across cash and bank management, fixed assets, regulatory reporting and subscription billing with previews and GA timelines. Highlights include QR‑Bill structured addresses, batch posting improvements, and new transfer data entities.

  Note

  Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.

  Important

  Some or all of the functionality noted in this article is available as part of a preview release. The content and the functionality are subject to change. For more information about preview releases, see Service update availability.
  This article lists the features that are new or changed for Microsoft Dynamics 365 Finance version 10.0.46. This version has a build number of 10.0.2428 and is available on the following schedule:

  • Preview of release: October 2025
  • General availability of release (self-update): December 2025
  • General availability of release (auto-update): February 2026

  Features included in this release

  This section contains a table that lists the features that are included in this release when available. We might update this article to include features that were added to the build after this article was originally published.

  • Accounts receivable

    • (Switzerland) Structured addresses in QR-Bill
    • This feature enables structured addresses (address type “S”) for both biller and debtor, with each address broken into its individual components.
    • Feature management

  • Accounts receivable

    • Performance issue on the Global transaction page with huge volume of data
    • This feature improves performance issue in Global transaction page by changing the join type dynamically to inner.
    • On by default

  • Cash and bank management

    • Display payee name for customer/vendor payment information
    • This feature enables the retrieval and display of the payee name defined on the customer and vendor bank account details. The payee name will be visible in customer and vendor payment journals, payment proposals, and outbound payment files. The payee name can be different from the name of the customer/vendor defined on the master data, and should align with banking requirements, ensuring accurate identification of payment recipients.
    • Feature management

  • Cash and bank management

    • Enable batch mode for Bank CODA transfer to ledger
    • When the feature is enabled, users can transfer Bank CODA account statements to ledger journals in batch.
    • Feature management

  • Cash and bank management

    • Automatic bank reconciliation matching results (Preview)
    • This feature is released in private preview allowing its usage in nonproduction environments. The Preview automatic bank reconciliation matching results feature enables users to preview matching results during the bank reconciliation matching process before transactions are posted. By allowing users to select rules that require review and user checks, the feature ensures accurate matching and minimizes errors. To enable this feature, contact support.
    • Feature management

  • Cash and bank management

    • Delay invoice settlement (Preview)
    • This feature is released in private preview without the ability to enable it in production environments. The feature controls the Delayed settlement parameter in General Ledger journal names. When the feature and parameter are enabled, the settlement is delayed and is executed separately from posting the customer and vendor payment journals. To enable this feature, contact support.
    • Feature management

  • Fixed assets

    • Create acquisition proposal through recurrence batch job throws error in batch tasks when the created journal is deleted
    • This update addresses a scenario where the recurrence batch job for creating acquisition proposals fails with an error in batch tasks if the journal created by a previous run is manually deleted. Validation has been added to detect missing journals and handle the error gracefully, ensuring the batch job continues to run without interruption.
    • On by default

  • Fixed assets

    • Retain fixed asset name when acquired through Accounts payable invoice
    • This feature ensures that the text defined in the Text field of a purchase order line for a fixed asset is stored in the Information 3 field during asset creation and remains unchanged. If the asset is later acquired through additional purchase orders with new text, the new values are appended to the Information 3 field without removing the existing ones.
    • On by default

  • Fixed assets

    • Correct inventory sold transaction behavior when Allow asset acquisition from purchasing is disabled
    • When acquiring the same fixed asset ID from multiple purchase lines, the Inventory sold transaction is now created when posting the fixed asset acquisition proposal journal. This ensures transactions are generated at the correct stage of the process and prevents premature entries.
    • On by default

  • Fixed assets

    • Data entity for transfer worksheet (preview)
    • This feature introduces a data entity that supports the fixed asset transfer between legal entities worksheet process. It enables users to programmatically manage asset transfers between legal entities by importing transfer data, including source asset details, financial values, and destination asset data.
    • Flight

  • Subscription billing

    • Reduce chattiness in SubBillDeferralRecognitionProcessing and SubBillDeferralRecognitionProcessingBatch
    • This change successfully reduced a significant amount of chattiness in the batch process. This is controlled by SubBillDeferralRecogProcChattinessReductionFlight
    • On by default

  • Subscription billing

    • Fix generate invoice with sales order performance problems
    • This introduced a posting sales order batch job for billing schedule invoicing batch processing for the sales order posting process. This enables multithreaded posting resulting in parallelism and faster execution time. This is controlled by SubBillGenerateInvoiceMultiThreadedPostingFlight
    • On by default

  • Subscription billing

    • Performance improvements for deferral recognition batch (preview)
    • This feature enhances the subscription billing deferral recognition batch process by processing deferral data in parallel, allowing each run to complete more efficiently.
    • Feature management

  • Subscription billing

    • Performance improvement in deferral processing
    • Key performance improvements are introduced in Subscription Billing deferral processing. These enhancements are designed to address critical business challenges observed in high-volume deferral scenarios and to improve overall reliability and scalability of the batch process.
    • On by default

  • Regulatory reporting

    • Withholding tax report for Indonesia
    • Support generating the e-Bupot file for reporting periods starting from 2025 based on the withholding tax transactions.
    • Electronic Reporting configurations

  • Regulatory reporting

    • VAT (Pajak Pertambahan Nilai) declaration for Indonesia
    • Support generating the SPT Masa PPN (Pajak Pertambahan Nilai) in Excel format for reporting periods starting from 2025.
    • Electronic Reporting configurations

  • Regulatory reporting

    • VAT declaration for Estonia - KMD5, KMD6
    • Support generating the VAT declaration for Estonia - KMD5 for reporting periods from January to June 2025, KMD6 for reporting periods starting from July 2025.
    • Electronic Reporting configurations

  Feature enhancements included in this release

  This section contains a table that lists the enhancements that are included in this release when available. We might update this article to include features that were added to the build after this article was originally published.

  • Cash and bank management

    • Bank account lifecycle management
    • As of Dynamics 365 Finance version 10.0.46, this feature isn't in Preview. Bank account lifecycle management feature enables approval workflow for bank account opening, modification and closing, adds additional signer information in the bank account data model, and provides bank account change history for auditing purpose.
    • Feature management

  • Cash and bank management

    • Modern bank reconciliation
    • When the feature is enabled, sales tax direction is considered when the general ledger voucher is generated during bank reconciliation process.
    • Feature management

  • Credit and collections

    • Customer interest note creation – top picking optimization
    • This feature uses top picking to improve the performance when creating customer interest notes. This helps avoid long-running transactions and ensures faster and more efficient processing when handling large transaction volumes.
    • Feature management

  • General ledger

    • Account reconciliation agent (Production ready preview)
    • The Account reconciliation agent functionality has been improved to provide suggested actions for In ledger not in subledger and In subledger not in ledger exception types.
    • Feature management

  • General ledger

    • User ID added to the Ledger settlement inquiry page for full visibility.
    • The user ID that did the ledger settlement is now displayed in the Ledger settlement inquiry page.
    • Default

  • General ledger

    • Performance improvements in Ledger settlements when the Enable advanced awareness option feature isn't enabled.
    • The Ledger settlements page has been updated to improve the performance when doing ledger settlements. Customizations may need to be updated to work with the new page.
    • Default

  • Subscription billing

    • Billing schedule
    • The discount group setup in the trade agreement for item prices should automatically apply to the billing schedule when it is created for the corresponding customer record.
    • Feature management

  • Subscription billing

    • Subscription billing deferral COGS adjustment-enhancement (preview)
    • A dedicated dashboard monitors and provides visibility into errors that had occurred during the adjustment process. This dashboard offers actionable insights and a user-friendly interface, allowing users to conveniently reprocess failed adjustments through a rerun batch job—reducing manual effort and enhancing the overall reliability of the deferral.
    • Feature management

  • Subscription billing

    • Subscription billing deferral COGS adjustment-enhancement (preview)
    • A notification message is displayed when the asynchronous process finishes so that the user is notified.
    • Feature management

  • Regulatory reporting

    • [Sweden] Standard Import and Export (SIE) modernization in Electronic Reporting
    • This feature replaces the legacy SIE export format (SE) format with the new Standard Import and Export SIE TXT (SE) format under the Ledger accounting reports model in Electronic Reporting. This new format enables the export of key financial data, including balances and transactions, in accordance with SIE Types 1 through 4. It supports larger datasets and introduces a redesigned export process that ensures faster generation, reduced system load, and a simplified workflow. By adopting this feature, Swedish entities can efficiently meet statutory reporting obligations while benefiting from a more scalable, performant, and maintainable export solution.
    • Export financial information (SIE) in Sweden
    • Feature management

  • Regulatory reporting

    • (Preview) [Italy] Fiscal Journal modernization in Electronic Reporting
    • This feature replaces the legacy SSRS-based report with a modern, PDF-based solution built on Electronic Reporting. It offers improved performance, enhances the ability to process large volumes of data across extended reporting periods, including up to a full fiscal year, while ensuring compliance with Italian fiscal requirements.
    • Feature management

  • Regulatory reporting

    • Enhancement of Calculate statistics for Payment terms in commercial transactions report for Poland
    • As of version 10.0.46 of Finance, the Payment transaction type parameter is available in the Calculate statistics dialog of Statistics on invoices process. This parameter allows selection of types of payment transactions to include in the statistics.
    • Default

  • Regulatory reporting

    • Define application of exchange rates in Intrastat reporting
    • This feature introduces flexibility in how amounts are calculated for Intrastat, enabling alignment with tax calculation logic.
    • Intrastat overview - Foreign trade parameters
    • Default

  More information

  • Platform updates for finance and operations apps

    • Dynamics 365 Finance version 10.0.46 includes platform updates. To learn more, see Platform updates for version 10.0.46 of finance and operations apps.

  • Bug fixes

    • For information about the bug fixes that are included in this update, sign in to Microsoft Dynamics 365 Lifecycle Services, and view the KB article.

  • Regulatory updates

    • For information about regulatory updates for finance and operations apps, see Regulatory updates. Another way to learn about regulatory updates is to sign in to Lifecycle Services and view the planned regulatory updates using the issue search tool. Issue search lets you search by country/region, type of feature, and release.

  • Dynamics 365 and industry clouds: 2025 release wave 2 plan

    • Wondering about upcoming and recently released capabilities in any of our business apps or platform?
    • Check out Dynamics 365 and industry clouds: 2025 release wave 2 plan. We've captured all the details, end to end, top to bottom, that you can use for planning.

  Original source Report a problem

  Show more
• Dec 11, 2025

  • Parsed from source:
    Dec 11, 2025
  • Detected by Releasebot:
    Dec 12, 2025
  

  Microsoft Teams by Microsoft

  December 11, 2025

  A new multi window experience lets you pop core apps into separate windows. Interpreter upgrades bring auto language detection, a preparing status, clearer settings, and improved multilingual meeting accuracy, plus stronger impersonation protection in Teams messages.

  Pop out your core apps into a new window

  • Users can now open their core applications, such as Chat, Teams, and more, in separate windows by selecting "Open in new window" from the app's context menu.

  Interpreter agent improvements

  • We're enhancing the Interpreter experience to deliver more accurate and consistent multilingual meeting experiences across interpretation, captions, and transcripts.
    • Auto-detect & auto-update spoken language:
      Previously, Interpreter automatically detected and updated spoken language for Interpreter agent, but Live Captions and Live Transcripts required users to manually configure their spoken language, even in the same meeting. With this improvement, spoken language is now autodetected and autoupdated consistently across Interpreter, Live Captions, and Live Transcripts. This ensures all speech features stay aligned with the actual language being spoken without manual setup.
    • Preparing status indicator:
      A new preparing status gives users clearer visual feedback when Interpreter is initializing, helping them understand when the system is ready. This is critical for those who rely on visual cues in multilingual meetings.
    • Interpreter settings optimization:
      Concise explanations are added in Interpreter settings to clarify how each configuration and field works, reducing setup friction and user confusion.

  Impersonation protection of tenant-owned domains for Teams messaging

  • This feature lets users identify if an external user comes from a domain that's impersonating the recipient tenant's own domains, during their initial contact with an enterprise user via Teams messages.

  Original source Report a problem

  Show more
• Dec 11, 2025

  • Parsed from source:
    Dec 11, 2025
  • Detected by Releasebot:
    Jan 18, 2026
  

  Dynamics 365 Sales by Microsoft

  Dynamics 365 sets the bar for agentic sales qualification on new benchmark

  Microsoft announces GA of Sales Qualification Agent in Dynamics 365 Sales, enabling autonomous lead research and outreach to boost pipeline and cut costs. It also introduces the Microsoft Sales Bench to measure AI sales agent quality and drive ongoing improvements.

  Release Notes: Sales Qualification Agent (SQA) — Dynamics 365 Sales

  In October 2025, we announced the general availability of the Sales Qualification Agent (SQA) in Dynamics 365 Sales —a breakthrough in autonomous lead qualification. Sales Qualification Agent empowers sellers by helping build higher quality opportunity while eliminating tedious, repetitive work. Sales Qualification Agent autonomously researches every lead, initiates personalized outreach, and engages prospects to understand purchase intent, ensuring that sellers spend their time meeting prospects who are ready to take the next step. With modes enabling both seller-driven and fully autonomous qualification, the agent supports a key goal for sales organizations—increasing revenue per seller.

  Customers are using Sales Qualification Agent in two ways

  • Helping boost revenue beyond current sales capacity
    • Responding to inbound leads within minutes instead of days, increasing response rates and in turn, qualified opportunities.
    • Engaging leads that sellers are unable to follow up on due to capacity constraints, or those deemed economically unviable to pursue.
    • Increasing pipeline quality by focusing the seller’s time on a handful of high intent, engaged leads recommended by the agent.
  • Helping reduce sales costs
    • Reducing back-office costs related to lead research and validation, using Sales Qualification Agent in “Research only” mode to hand-off only the leads that meet the ideal customer profile criteria.
    • Automatically disqualifying low-quality leads, saving hours of seller time during the week.

  Continuing benchmarking the quality of sales AI agents

  Microsoft is building the future of agentic Sales technology with prebuilt AI agents, such as Sales Qualification Agent, the Sales Research Agent, and the Sales Close Agent available in Dynamics 365.

  At Microsoft, we’re committed to delivering quality, trust, and transparency with our agents, and that requires rigorous evaluation. As we continue to build new agents and improve existing ones for critical sales workflows, evaluation benchmarks provide a structured and transparent way for our customers to measure quality for the jobs the agent does.

  Today, we’re announcing the Microsoft Sales Bench —a new collection of evaluation benchmarks designed to assess the performance of AI-powered sales agents across real-world scenarios. This framework brings together purpose-built metrics, hundreds of sales-specific scenarios, and composite scoring validated by both human and AI judges.

  The Sales Bench isn’t starting from scratch. It now formalizes and expands what began with the Sales Research Bench, published on October 21, 2025, which evaluates how AI solutions answer business research questions for sales leaders.

  Today, we’re extending the Microsoft Sales Bench with a second benchmark: the Microsoft Sales Qualification Bench, focused on measuring how effectively AI agents qualify leads and generate high-quality pipeline.

  Introducing the Sales Qualification Bench for lead qualification

  This Microsoft Sales Qualification Bench evolved from rigorous evaluations we conducted since the Sales Qualification Agent’s public preview in April, with the goal of objectively measuring quality as we further developed the agent, partnering with customers from a diverse set of industries. Since the preview, we measured every update against these standards, ensuring improvements are real and repeatable.

  We generated a synthetic dataset modeled after companies from three different industries, with 300 leads, with attributes such as name, company, and email ID—representative of what sales teams typically work with before any enrichment or hygiene is performed. In addition to these typical attributes, we also added key knowledge inputs such as value proposition of the products being sold, customer case studies, and documentation for answering customer questions.

  In addition to Sales Qualification Agent, we used the evaluation framework to measure ChatGPT by OpenAI on the same dataset. Since we didn’t have access to an autonomous agent from OpenAI, we mimicked how a human seller would use ChatGPT to recreate the three key jobs SQA performs. We provided each system—Sales Qualification Agent and ChatGPT—the exact same lead inputs, knowledge sources, and contextual signals under controlled evaluation configurations. We used a ChatGPT Pro license with GPT-4.1. This model is the closest match (and slightly better) to Sales Qualification Agent’s GPT-4.1 mini, which we intentionally chose to deliver optimal quality at lower cost per lead than newer models. Additionally, Pro license was chosen to optimize for quality: ChatGPT’s pricing page describes Pro as “full access to the best of ChatGPT.”

  The framework evaluates outputs from the three jobs across Sales Qualification Agent and ChatGPT:

  • Research: Company research for the lead—background, strategic priorities, financial health, and latest news.
  • Outreach: A personalized email generated based on research, to make initial contact with the lead.
  • Engagement: The agent’s conversation with a lead until it’s qualified or dispositioned.

  Our scoring metrics span core quality (accuracy, relevance, completeness), trustworthiness (grounding and citations), and business-specific success criteria (e.g., relevancy of company research to highlight interest in the seller’s offerings, personalization of the initial outreach emails sent to catch the lead’s attention, accuracy of responses to the lead’s questions to drive purchase intent, and the timing of handoff to a seller when the lead is ready to engage).

  Outputs were scored independently by both human reviewers and an LLM judge built with GPT-5.1, using a 1–10 scale for each metric. These metric-specific scores were then rolled up using a simple average to produce a composite quality score. The result is a rigorous benchmark presenting a composite score and dimension-specific scores to reveal where agents excel or need improvement. Our methodology, metrics, and their definitions are described in this technical blog.

  Results

  In evaluations completed on December 4, 2025, using the Sales Qualification Bench, Sales Qualification Agent outperformed ChatGPT on each of the three jobs required for sales qualification:

  • Research: The Sales Qualification Agent outperformed ChatGPT with 6% higher aggregate scores, leading on relevancy and completeness in research results that highlighted the lead company’s interest in the seller’s offerings.
  • Outreach: Sales Qualification Agent demonstrated 20% better results compared to ChatGPT, generating email drafts with accurate personalization and mentions of relevant recent events that will resonate with the lead.
  • Engagement: Sales Qualification Agent’s email responses to engage a lead over a multi-turn conversation scored 16% higher than ChatGPT’s. SQA generated emails that responded to the lead’s questions with accurate answers that develop their purchase interest and with precise discovery questions that qualify the lead before handing off to a seller.

  In addition to performing better on these metrics, Sales Qualification Agent has the ability to run autonomously, which can help significantly reduce the time spent generating pipeline while helping sales teams build better quality pipeline.

  Sales Qualification Agent scores well on these three jobs as its optimized for sales-specific scenarios and uses the following techniques to get great results:

  • It uses agentic Retrieval Augmented Generation (RAG) to relentlessly research each lead, ensuring greater completeness. More on this in the following section.
  • With knowledge of what the company sells, it can contextualize every workflow to increase relevancy for both the seller and the lead.
  • It can retrieve organizational knowledge from attached documents and internal repositories like SharePoint with greater precision, boosting accuracy of its responses when engaging with the lead.

  The technical blog details which metrics SQA excels at relative to ChatGPT, where it falls short, and why.

  Translating evals to real-world impact

  Running evals led to major Sales Qualification Agent improvements during its six-month preview. Early results prompted us to try agentic AI design patterns, especially agentic RAG, which improved our company research by allowing iterative web searches and real-time reasoning. They also led us to enhance data coverage by auto-linking existing CRM records to each lead and inferring company names from lead emails. These updates provided sellers with deeper insights, revealing strategic opportunities and risks beyond basic facts.

  For instance, when researching leads for a security company, Sales Qualification Agent can link news on recent cyberattacks to increased demand for its software. As highlighted in the technical blog, research synthesized by the agent makes such inferences more consistently than ChatGPT. Enhancing the agent’s research also improved the relevance and personalization of outreach emails, helping agents better engage leads and clarify their ability and intent to purchase before handing them off to sellers.

  Sandvik Coromant, a leader in precision cutting tools, partnered with us to pilot Sales Qualification Agent for their Digital Commerce program. After the updates, Pia Cedendahl, Global Sales Manager for Strategic Channels/Partners and Online Sales, noted, “Sales Qualification Agent’s answers became far more on-point to our business—it’s like having a research assistant that already understands what we care about.” Sandvik Coromant saw improved lead conversion and higher engagement from their Digital Account Managers, validating the impact of our evaluation-driven approach. Pia joined Microsoft leaders at the Microsoft Ignite 2025 session, “Accelerate revenue and seller productivity with agentic CRM,” where she shared how the team saved more than 120 hours and $19,000 in just the first three weeks since launching a pilot, and forecasted a 5% increase in revenue with full rollout.

  Better insights, more personalization, proven value

  Equipped with agentic AI design and backed by data-driven evaluation, customers can confidently use the Sales Qualification Agents so that:

  • Sellers receive comprehensive company overviews, timely news highlights, and actionable recommendations that are consistently delivered with high quality—drawing a clear line from insight to action.
  • Sales leaders can expand their qualified pipeline cost efficiently, with the agent ensuring high lead quality.
  • Prospects benefit from more personalized outreach, enhancing their experience and supporting increased conversion rates.

  What’s next

  We’ll continue to refine Sales Qualification Agent using agentic design patterns, aiming to make every improvement measurable and meaningful. Stay tuned for the full evaluation results and methodology for the Sales Qualification Bench, which will be published for transparency and reproducibility. We also intend to add more evaluation frameworks and benchmarks to the Microsoft Sales Bench collection including benchmarks that cover future sales agent capabilities.

  Get started with the Sales Qualification Agent

  Original source Report a problem

  Show more