Azure AI Foundry and Copilot Studio agent documentation led this week’s Microsoft documentation updates.

This new documentation introduces support for using admin-connected models—models hosted behind enterprise AI gateways—in cloud evaluation scenarios within Microsoft Foundry. It details how to reference these models, the prerequisites, and the supported evaluation scenarios, marking a significant expansion in model integration capabilities.

• Introduces admin-connected models for cloud evaluation in Foundry projects
• Explains referencing models via <connection-name>/<deployment-name> format
• Lists supported scenarios: evaluator judge, model target, conversation simulation

This new documentation introduces support for configuring Microsoft Entra authentication for trace ingestion from Foundry agents to Application Insights, replacing key-based ingestion with identity-based access control. It details prerequisites, setup steps for both new and existing connections, and troubleshooting guidance, enabling more secure and manageable telemetry ingestion.

• Introduces Microsoft Entra authentication for Foundry agent trace ingestion to Application Insights
• Describes how to update existing or create new connections using project managed identity
• Explains additional permissions required for hosted agent traces using Agent Identity

This new page introduces the Agent Optimizer (preview) in Microsoft Foundry, providing step-by-step instructions for optimizing prompt agents using an interactive wizard. It details how to select agent versions, datasets, evaluators, and models, run optimizations, compare results, and promote improved agent versions, enabling users to systematically enhance prompt agent performance.

• Introduces Agent Optimizer (preview) for prompt agents in Foundry
• Describes how to optimize agent instructions, tool descriptions, and model selection
• Explains selection of datasets, evaluators, and candidate models for optimization

This new documentation introduces and explains toolbox authentication in Microsoft Foundry, detailing how authentication is centralized on project connections and how agents can use various authentication types without handling authentication logic themselves. It provides step-by-step guidance for configuring OAuth identity passthrough, enabling per-user access to downstream services while maintaining user permissions and boundaries.

• Introduces toolbox authentication as a way to centralize and simplify authentication for tools in Microsoft Foundry
• Explains the separation of agent and user identities in tool calls
• Details supported authentication types (none, custom-keys, project-managed-identity, agentic-identity, oauth2, user-entra-token)

This new documentation introduces the ability to create a private skill catalog in Microsoft Foundry using Azure API Center, enabling organizations to register, govern, and share agent skills internally. It details prerequisites, setup, governance, access control, and troubleshooting, representing a significant new capability for managing and distributing AI agent skills within an enterprise.

• Introduces private skill catalogs for internal skill discovery and use
• Describes integration with Azure API Center for skill registration and governance
• Explains how to define allowed tools for each skill to enforce security boundaries

This new documentation introduces the Toolbox feature in Microsoft Foundry, which centralizes tool management for AI agents. It describes how Toolbox enables centralized configuration, authentication, governance, and sharing of tools and skills across agents, including new preview features like tool search and skills.

• Introduction of Toolbox for centralized tool management in Foundry
• Support for sharing tools and skills across multiple agents via a single MCP-compatible endpoint
• Centralized authentication, governance, and versioning for tools

The documentation now details how to use structured outputs with the Azure OpenAI Responses API, including Python, .NET, and REST/cURL examples. This expands structured output support beyond Chat Completions and clarifies schema configuration for each API.

• Structured outputs are now supported in both Chat Completions and Responses APIs.
• Added Python (OpenAI SDK), .NET, and REST/cURL examples for using structured outputs with the Responses API.
• Clarified how to specify JSON Schema for structured outputs in each API.

The documentation introduces new controls and explanations for reasoning models in Azure OpenAI, including expanded 'reasoning_effort' levels, a new 'reasoning.mode' (standard/pro) for gpt-5.6 models, and the ability to preserve reasoning across conversation turns. These changes give developers more granular control over model behavior, cost, and continuity in multi-turn interactions.

• Expanded 'reasoning_effort' parameter with more granular levels (none, minimal, low, medium, high, xhigh, max) and guidance on their use cases
• Added 'reasoning.mode' (standard/pro) for gpt-5.6 models, allowing selection of execution mode for difficult tasks
• Introduced section explaining how reasoning tokens work, their impact on context window and billing, and how to monitor them

Page removed or relocated. The documentation page detailing the types of tools available in Microsoft Foundry Agent Service, including built-in and custom tools, toolboxes, and related management concepts, has been removed. This eliminates a comprehensive resource for understanding and implementing tool extensibility in Foundry-based Copilot agents.

• Loss of overview and guidance on built-in and custom tool types for Foundry Agent Service
• Removal of instructions for connecting, authenticating, and managing tools and toolboxes
• Missing documentation on using MCP, OpenAPI, and Agent-to-Agent (A2A) integrations

This new page introduces documentation for content provenance features in Microsoft Foundry models, detailing how C2PA manifests and invisible watermarks are used to signal the origin of AI-generated content. It also lists specific image model families that support these provenance signals, enhancing transparency and traceability for generated outputs.

• Explains the use of C2PA manifests and invisible watermarks for content provenance.
• Clarifies that provenance signals indicate origin, not content accuracy or trustworthiness.
• Lists supported image model families and versions that include provenance features.

The documentation now clarifies and expands routine action configuration, allowing either agent name or legacy endpoint ID, and updates SDK/package requirements for .NET and Python. These changes enable broader compatibility and clarify how to target agents in routines.

• Action fields now support specifying either agent_name or agent_endpoint_id, not just agent_name
• Clarifies that only one of agent_name or agent_endpoint_id should be specified
• Input field for actions now accepts JSON values, not just strings

The prerequisites and setup process for connecting agents to Microsoft 365 with Work IQ have been updated to clarify commercial requirements, licensing, and technical setup, including new details on usage-based billing, connector licensing, required software versions, and protocol support. The authentication and security section now emphasizes delegated authentication and the need for explicit admin consent for app registrations.

• Added distinction between usage-based billing (Copilot Credits) and connector licensing for different connection paths.
• Clarified that connector-backed tools may require a Microsoft 365 Copilot license for each user.
• Specified technical requirements: Node.js 22+, @azure/ai-projects 2.4.0+, and protocol versioning for A2A calls.

The documentation now requires explicit approval to use the gpt-image-1 model, updates the recommended orchestrator model to gpt-5, and provides improved setup and code sample instructions for both Python and .NET. These changes clarify prerequisites, expand supported models, and make it easier for developers to implement image generation with the latest tools.

• Explicit requirement to apply for access to gpt-image-1 before deployment
• Updated orchestrator model recommendation from gpt-4o/4.1 to gpt-5 in prerequisites and code samples
• Clarified region and model support with a new reference to a dedicated support matrix

The documentation now includes new prerequisites for using the Microsoft Fabric data agent, such as requiring a paid Fabric or Power BI Premium capacity and support for additional data sources. A new 'Usage support' section details SDK and setup compatibility, and the agent creation section is clarified with a split for 'Prompt agents.' These changes expand the documented capabilities and clarify setup requirements.

• Added requirement for paid F2 or higher Fabric capacity or Power BI Premium P1+ with Fabric enabled
• New prerequisite to configure cross-geo processing and storage tenant settings if needed
• Expanded list of supported data sources and permissions, including Mirrored database, Ontology, and Microsoft Graph

A new capability allows credentials to be sent when fetching the agent card from an A2A endpoint, addressing scenarios where the agent card path is protected and requires authentication. This is controlled by a new 'send_credentials_for_agent_card' property in the A2A tool definition.

• Added support for sending credentials on agent card fetch requests via 'send_credentials_for_agent_card' property.
• Documented the security implications and default behavior (credentials not sent unless explicitly enabled).
• Troubleshooting guidance updated for agent card authentication failures.

A new section on structured outputs has been added, describing how to make Responses API outputs conform to a JSON Schema. This enables more controlled and predictable API responses, which is important for developers integrating Copilot capabilities. Additionally, a reference link to parameter documentation was added for clarity.

• Added new 'Structured outputs' section explaining how to enforce JSON Schema on responses
• Clarified that Responses API uses 'text.format' for schema definition (distinct from Chat Completions)
• Added reference to full parameter documentation in the introduction

A new section was added explaining that tool calling with reasoning models (gpt-5.6 and later) is only supported via the Responses API, not the Chat Completions API, and provides guidance and workarounds for developers. Minor clarifications and code improvements were also made elsewhere.

• Added guidance that tool calling with reasoning_effort is not supported in Chat Completions API for gpt-5.6+ models
• Explained that such requests will fail and provided the specific error message
• Outlined two solutions: migrate to Responses API (recommended) or set reasoning_effort to 'none' in Chat Completions

A new quickstart for optimizing prompt agents using the agent optimizer in the portal has been added. This enables users to improve agent instructions, tool descriptions, and model selection, and to promote the best candidate.

• Added 'Optimize a prompt agent' quickstart
• Describes use of agent optimizer in the portal
• Covers improving instructions, tool descriptions, and model selection

The documentation now states that Model Router supports additional Claude models, specifically including 'claude-opus-4-7' and 'claude-opus-4-6', expanding the range of models that can be routed automatically. The note about unsupported models has been generalized, reflecting evolving support.

• Model Router now supports 'claude-opus-4-7' and 'claude-opus-4-6'
• The list of Claude models supported by Model Router has been updated
• The note about unsupported models is now generalized, not naming specific models

This update introduces support for custom event-based triggers (notably Microsoft Teams messages) and expands SDK and CLI options for managing routines. It also clarifies agent authentication requirements and updates supported SDK versions.

• Added 'custom' trigger type, enabling routines to fire on external events such as new Microsoft Teams messages.
• Expanded SDK and CLI support: routines can now be managed via Python, .NET, JavaScript SDKs, and Azure Developer CLI.
• Clarified that routines require agents with configured identity (not end-user delegated identity).

Page removed or relocated. The documentation page for Microsoft Foundry Canvas, a GitHub Copilot App extension for visually building and deploying Foundry hosted agents, has been removed. This eliminates official guidance on using the Canvas extension for agent development workflows.

• Loss of documentation on installing and using Microsoft Foundry Canvas with Copilot
• Missing guidance on visual agent assembly, testing, and deployment via the Canvas
• No longer provides workflow integration details between Copilot and Foundry Canvas

Two new sections were added: one provides resources for learning about responsible AI, and the other introduces a process for reporting security or safety issues related to Foundry Models. This expands the documentation to support responsible AI practices and user engagement in security.

• Added links to Microsoft AI principles, responsible AI resources, and Azure learning courses
• Introduced guidance and process for reporting security or safety issues in Foundry Models

A new instruction has been added for reporting security or safety issues related to Foundry Models sold by Azure, specifying the use of the Microsoft Security Response Center and providing examples of vulnerabilities to report.

• Added guidance for reporting security vulnerabilities or safety problems in Foundry Models
• Clarified types of issues to report (e.g., prompt injection, unsafe output, data exposure)
• Specified required information for reports (model name, version, steps, impact)

The documentation clarifies the monitoring setup by updating terminology from 'continuous evaluation' to 'recurring evaluations,' adds the Foundry portal as a supported method for setup, and adjusts prerequisites to explicitly require portal access. These changes help users understand the current recommended approach and available tools for agent monitoring.

• Terminology updated from 'continuous evaluation' to 'recurring evaluations' in monitoring settings.
• Foundry portal added as a supported method for setting up recurring evaluations, alongside SDKs.
• Prerequisites now explicitly require access to the Foundry portal.

A new section was added explaining how to improve prompt cache hit rates for Fireworks models on Microsoft Foundry, detailing which headers and parameters to use for session affinity and cache keying.

• Added guidance on setting stable user/session identifiers for prompt caching
• Explained priority order of cache key parameters
• Linked to external Fireworks AI documentation for further details

The documentation clarifies SDK and endpoint selection, updates prerequisites for RBAC roles, and specifies updated SDK package versions and requirements, especially for JavaScript/Node.js. These changes help users choose the correct SDK and ensure their environment is properly configured.

• Clarifies that the OpenAI SDK now supports Foundry Models sold by Azure through Chat Completions.
• Refines RBAC role requirements, emphasizing least-privilege assignments and just-in-time elevation for resource-group roles.
• Updates JavaScript SDK version to 2.4.0 and specifies Node.js 22+ is required.

The documentation now clarifies prerequisites for using the web search tool, especially regarding Foundry RBAC role renaming, and improves the organization and labeling of code examples for TypeScript and Java. These changes help users understand required permissions and how to implement the tool in different SDKs.

• Added details about Foundry RBAC role renaming and clarified required roles for agent creation and tool connection.
• Improved formatting and labeling of TypeScript example, explicitly introducing 'Create a toolbox-backed agent' section.
• Minor updates to Java agent example for clarity and consistency.

The documentation clarifies SDK package requirements, updates code samples for setting 'require_approval' on MCP tools, and corrects some class and method names to match current SDKs. These changes help developers use the correct packages and APIs when managing toolboxes in Foundry.

• .NET SDK prerequisites now specify coherent preview package set and exact versions
• Python and .NET code samples for 'require_approval' updated to use current class and method names
• References to example locations and method names updated for accuracy

The documentation clarifies which tools should appear in the initial tool list when tool search is enabled, specifying that only 'tool_search', 'call_tool', and any pinned tools are visible, while unpinned tools remain hidden. Verification steps and code samples were updated to reflect this behavior, and minor SDK naming corrections were made.

• Clarifies that both 'tool_search' and 'call_tool' meta-tools, plus any pinned tools, should appear in the initial tool list
• Updates verification code to check for presence of meta-tools and pinned tools, and absence of unpinned tools
• Removes requirement for 'Foundry-Features' header in verification example

The documentation clarifies required RBAC roles, updates role naming to 'Foundry' roles, and emphasizes least-privilege assignment for managed identity. It also adds instructions for downloading a maintained OpenAPI spec for code samples and clarifies authentication setup requirements.

• RBAC roles renamed from Azure AI roles to Foundry roles, with explanation of mapping and unchanged permissions.
• Clarified that only the least-privileged RBAC role should be assigned for managed identity authentication.
• Added instruction to download a maintained OpenAPI spec for code samples.

The documentation clarifies role requirements (with updated role names), expands best practices with a step-by-step 'first-success route' for MCP tool integration, and provides more explicit guidance on authentication and agent creation. These changes help users understand prerequisites, recommended workflows, and how to successfully connect agents to MCP servers.

• Updated RBAC role names and clarified required roles for agent and project connection creation
• Added a step-by-step 'first-success route' for connecting, approving, verifying, and cleaning up MCP tool usage
• Clarified authentication configuration steps and when to use project connections

The documentation now clarifies required RBAC roles for file search agents, adds detailed setup instructions for different languages and environments, and splits code examples into clearer sections for prompt agents. These changes improve guidance for developers integrating file search tools with Copilot agents.

• Clarified that 'Foundry User' role is required to create and run agents (was previously 'Foundry Owner')
• Added detailed setup instructions for C#, REST, and Java environments in code examples
• Split code samples into explicit 'Prompt agents' sections for better clarity

The documentation clarifies authentication options, identity usage, and prerequisites for connecting agents to Fabric IQ, especially for the Fabric data agent. It now specifies that requests use the configured connection identity (not always the signed-in user), and that the data agent endpoint supports direct user or service-principal tokens in addition to previous methods. Prerequisites for using the Fabric data agent are also more detailed.

• Clarifies that requests use the configured connection identity, not always the signed-in user
• Specifies that the Fabric data agent endpoint supports direct user or service-principal token authentication
• Adds detailed prerequisites for using the Fabric data agent, including capacity and data source requirements

The documentation now clarifies required prerequisites, role assignments, and environment variable mappings for deploying and running a custom code interpreter agent. It also provides more precise instructions for infrastructure output handling and troubleshooting role-based access issues.

• Added Python 3.12+ as a prerequisite for the maintained sample project.
• Clarified specific RBAC roles needed for provisioning versus day-to-day agent use, and recommended using Microsoft Entra PIM.
• Specified correct Bicep output for MCP server endpoint and warned against using the wrong endpoint.

The documentation clarifies the dependencies and structure of the code samples, explicitly noting that Python and Java samples rely on helper code and are not standalone. It also reorganizes code sample sections for better clarity, distinguishing between Prompt Agents and Hosted Agents. No new features or deprecations are introduced, but the changes help developers understand sample usage and setup requirements.

• Clarified that Python and Java code samples depend on helper files and are not standalone
• Added explanation that helpers simulate state machines and do not replace production safety checks
• Reorganized code sample sections to explicitly separate Prompt Agents and Hosted Agents

The documentation now clarifies that the sample code for using Code Interpreter in both Python and C# generates a small CSV file in the working directory, uploads it, and deletes the temporary file. The file upload step is now explicitly shown in the code samples, making the workflow clearer for users.

• Added explicit CSV file creation and cleanup steps in Python and C# code samples
• Clarified that each file-upload sample generates and deletes a temporary CSV file
• Removed mention of needing to provide your own CSV file in prerequisites

The documentation now clarifies the required Azure roles for setting up and using the Browser Automation tool, reflecting recent RBAC role renames and specifying least-privilege guidance for resource provisioning. No new features were introduced, but the prerequisites and setup steps are more precise, reducing confusion for administrators and developers.

• Clarified Azure RBAC roles needed for setup and day-to-day use, including recent role renames
• Emphasized least-privilege principle for Contributor role during Playwright workspace creation
• Added guidance on activating Contributor role just-in-time and deactivating after provisioning

The updates clarify required Azure RBAC roles for provisioning and day-to-day use of Bing Search and Bing Custom Search grounding tools, emphasizing just-in-time role activation via Microsoft Entra PIM. Some redundant or outdated environment variable requirements were removed, and guidance on network security behavior was added.

• Clarified that Contributor role is only needed for provisioning Bing resources, not for daily agent development or use
• Recommended using Microsoft Entra Privileged Identity Management (PIM) for just-in-time role activation
• Removed some environment variable requirements for REST samples

The documentation clarifies required Azure roles for A2A connections, adds details about agent card credential handling, and expands code samples to distinguish between prompt and hosted agents. These changes help users correctly configure permissions and understand authentication nuances when connecting agents.

• Clarified Azure role requirements: Foundry Project Manager is needed to create A2A connections, Foundry User to create/test agents.
• Added guidance on agent card credential requirements and the 'send_credentials_for_agent_card' field.
• Expanded code samples to separately cover prompt agents and hosted agents, improving implementation guidance.

The page now provides a clearer migration path table for different starting points and clarifies minimum migration steps. It also updates troubleshooting guidance, notably specifying a newer required JavaScript package version. These changes help developers better understand migration requirements and avoid common pitfalls.

• Added a migration path table mapping starting points to migration steps
• Outlined four minimum required migration steps for all users
• Updated JavaScript troubleshooting to require @azure/ai-projects version 2.4.0 or later (was 2.3.0)

The updates clarify recommended workflows for using memory in Foundry Agent Service, specify Node.js version requirements for the JavaScript SDK, and update Python code samples to use timedelta for TTL. These changes improve guidance and accuracy for developers integrating memory features.

• Added step-by-step workflow guidance for first-time memory usage
• Clarified when to use different memory workflows (administration vs. commands)
• Specified Node.js 22+ requirement for JavaScript SDK usage

The documentation now provides detailed guidance on configuring the base URL for model connections and choosing the correct API key and header, as well as expanded troubleshooting steps including how to enable and use Application Insights and Log Analytics for diagnostics. These clarifications help users avoid common misconfigurations and improve troubleshooting effectiveness.

• Added section explaining how to correctly set the base URL for different protocol styles
• Added section detailing which API key and header to use for various connection patterns
• Expanded troubleshooting section with step-by-step instructions for enabling and querying Application Insights and Log Analytics in API Management

The introduction was expanded to clarify when and why to use agents, conversations, and responses, including a new comparison table and a more detailed example of their lifecycle. The previous 'How runtime components work together' section was removed, with its content largely integrated into the expanded introduction.

• Added a table comparing agents, conversations, and responses with guidance on when to use each
• Expanded explanation of component lifecycle with a concrete support assistant example
• Clarified that streaming and background mode affect response delivery, not component relationships

The section clarifies and expands on how hosted agents access Foundry-managed tools, listing additional supported tools and emphasizing the use of the Toolbox MCP endpoint for consolidated authentication. It removes the previous warning about not adding tools directly and provides a clearer overview of tool integration.

• Expanded list of Foundry-managed tools accessible to hosted agents (including Skills and more)
• Clarified that tools are connected via the Toolbox MCP endpoint, not by direct addition to agent definition
• Emphasized consolidated authentication options through the toolbox

A new note clarifies that reasoning models like GPT-5 series behave differently on the Chat Completions API, including changes to supported parameters and tool calling behavior. This helps developers avoid errors and choose the right API for their use case.

• Reasoning models use `max_completion_tokens` instead of `max_tokens`
• Reasoning models do not support `temperature`, `top_p`, or penalty parameters
• On `gpt-5.6` and later, tool calls require `reasoning_effort` set to `none` or will fail

The documentation now references support for Entra-authenticated trace ingestion, providing a link to configuration instructions for this preview feature. This adds a new authentication option for trace ingestion in Foundry projects.

• Added reference and link to configuring Microsoft Entra authentication for Foundry Agent trace ingestion (preview)

The documentation now clarifies that GPT-5.6 models support the Chat Completions API and function tools, but not simultaneously unless 'reasoning_effort' is set to 'none'. It also advises using the Responses API for tool calling, providing important operational guidance for developers.

• Clarified API and tool support limitations for GPT-5.6 models
• Added guidance on using 'reasoning_effort' and the Responses API for tool calling

The documentation now clarifies the distinction between deployment types and instant access, introduces the batch deployment type and developer tier, and provides more precise guidance on data residency, billing, and SLA guarantees for each deployment type. These changes help users better understand which deployment options are available, their compliance implications, and how to select the right type for their needs.

• Clarified that deployment types apply only to Serverless API, not managed compute for open-source/custom models
• Added 'batch' (discounted asynchronous processing) and 'developer' (fine-tuned model evaluation) as deployment categories
• Separated instant access from deployment types and clarified its use case

The documentation clarifies procedures and requirements for configuring, monitoring, and managing AI Gateway in Foundry resources, including more precise instructions for log collection, clearer requirements for using existing API Management instances, and updated governance scenarios. These changes help users better understand how to set up, verify, and govern AI Gateway usage.

• Clarified requirements for selecting existing API Management instances and improved explanation of permissions and network access.
• Expanded instructions for verifying gateway operation, including detailed steps for collecting and querying diagnostic logs.
• Updated governance scenarios to specify registering custom agents and preview support for governing MCP tools.

The documentation updates clarify and rename deployment options in Microsoft Foundry Models, replacing 'Standard deployment in Foundry resources' with 'Serverless API', and provide more precise descriptions of which models use each deployment type. The changes also introduce 'instant access (preview)' as a way to try models without deployment, and update the list of models and capabilities for managed compute deployments.

• Renamed 'Standard deployment in Foundry resources' to 'Serverless API' and clarified its capabilities
• Added 'instant access (preview)' as a way to use models without deployment
• Updated which models are supported by managed compute, with specific examples

The documentation clarifies prompt caching controls and billing for GPT-5.6 and later models, introduces new API parameters, and updates how cache reads and writes are reported. These changes help users understand how to configure and monitor prompt caching with the latest model families.

• Clarifies that on GPT-5.6 and later, prompt_cache_options.ttl sets minimum cache lifetime, replacing prompt_cache_retention
• Explains that cache writes can now incur charges on GPT-5.6 and later, and how to monitor them via cache_write_tokens
• Updates API usage examples to show new reporting fields for cache reads and writes

The retirement status and replacement for the Anthropic 'claude-opus-4-1' model have changed: it is now marked as 'Retired' with a new replacement listed as 'claude-opus-5'. This provides users with updated lifecycle information and a clear migration path.

• 'claude-opus-4-1' Anthropic model status changed from 'Preview' to 'Retired'
• Replacement for 'claude-opus-4-1' updated from 'claude-opus-4-8' to 'claude-opus-5'

The prerequisites section now requires a newer version of the Azure Developer CLI (azd 1.27.1+ instead of 1.25.3+). The cleanup instructions clarify how 'azd down' behaves differently depending on whether the Foundry project was newly created or reused, helping users avoid unintended deletions.

• Updated minimum required azd version from 1.25.3 to 1.27.1
• Clarified that 'azd down' deletes all resources only if the Foundry project was created in the current environment
• Explained that if an existing Foundry project was reused, 'azd down' does not delete the project or its resources

The regional availability table for Claude models in Microsoft Foundry was updated, specifically removing the listing for 'claude-opus-4-1' and its associated version and region data. This change affects which Claude model versions are available for deployment in specific Azure regions.

• Removed 'claude-opus-4-1' from the regional availability table
• No other model additions or removals detected in the visible table excerpt

Germany West Central has been added as a supported region for risk and safety evaluators, expanding regional availability for these Copilot evaluation features.

• Germany West Central added to supported regions for risk and safety evaluators

The cleanup instructions now clarify how 'azd down' behaves differently depending on whether the Foundry project was created by the current environment or was pre-existing. This helps users avoid unintentionally deleting important resources.

• 'azd down' now described as deleting the entire resource group only if it was created by the current environment
• If an existing project was used, 'azd down' leaves the project and its resources intact, requiring manual deletion of unneeded resources

The deployment step now clarifies that 'azd deploy' uploads source code as a ZIP and builds the hosted agent remotely, and the cleanup section explains how 'azd down' behaves differently depending on whether the Foundry project was newly created or pre-existing. These clarifications help users better understand deployment mechanics and avoid accidental deletion of shared resources.

• 'azd deploy' is clarified to package and upload source code as a ZIP for remote build.
• Cleanup instructions now specify that 'azd down' deletes the resource group only if the Foundry project was created by the current environment.
• Users are warned that existing projects and resources are not deleted by 'azd down' and must be removed separately.

The documentation clarifies deployment and cleanup behaviors for hosted agents, updates required tool versions, and improves troubleshooting guidance. These changes help users avoid accidental resource deletion and ensure they use compatible CLI versions.

• Clarified that 'azd down' only deletes resources if the environment created the Foundry project; otherwise, resources remain and must be deleted manually.
• Updated Azure Developer CLI (azd) minimum version requirement from 1.25.3 to 1.27.1.
• Clarified deployment process: 'azd deploy' now packages and uploads source code as a ZIP, with remote build and deployment handled by Foundry.

The deployment and cleanup instructions were clarified to better explain how the 'azd deploy' and 'azd down' commands work, especially regarding resource deletion depending on how the environment was set up. This helps users avoid accidental deletion of important resources.

• 'azd deploy' now described as packaging and uploading source for remote build by Foundry
• Cleanup section clarifies that 'azd down' deletes all resources only if the environment created the Foundry project, otherwise leaves existing resources intact

The prerequisites now clarify that an authenticated azd session is required, and the cleanup section explains how azd down behaves differently depending on whether the Foundry project was newly created or pre-existing. Troubleshooting steps now specify updated minimum version requirements for azd and its extension.

• Added requirement for authenticated azd session in prerequisites
• Clarified azd down deletes resources only if the project was created in the current environment
• Updated troubleshooting to require azd version 1.27.1+ and azure.ai.agents extension 1.0.0-beta.4+

The documentation clarifies the behavior of the 'azd deploy' and 'azd down' commands for hosted agents, specifying deployment steps and resource deletion conditions. This helps users better understand deployment workflows and resource management.

• 'azd deploy' now explicitly describes packaging, remote build, container image publishing, and prebuilt image deployment steps
• 'azd down' now clarifies that it deletes the resource group only if the current environment created the Foundry project, otherwise leaves existing resources intact

The documentation now clarifies the differences in agent optimizer capabilities and workflow between prompt agents and hosted agents, specifying which optimization targets and integration steps apply to each. This helps users understand what is supported for their agent type and how to prepare for optimization.

• Clarifies that agent optimizer supports both prompt agents and hosted agents, with differences in configuration and workflow.
• Specifies which optimization targets (instructions, skills, tools, model selection) are available for each agent type.
• Details that hosted agents require code integration for optimization, while prompt agents do not.

The documentation now requires Python SDK version 2.4.0 or later (previously 2.2.0), and the example code for generating evaluation datasets from agent traces has been updated to reflect changes in the SDK, including the removal of the JobStatus and TERMINAL_STATUSES logic and the addition of a poll interval variable.

• Minimum required Python SDK version increased from 2.2.0 to 2.4.0
• Example code updated: removed JobStatus/TERMINAL_STATUSES, added poll_interval_seconds variable
• Reflects changes in SDK usage for dataset generation from agent traces

The documentation now clarifies that billing for Microsoft Purview data security policies in Foundry can be based on either pay-as-you-go meters or an Agent 365 subscription. If neither is present, only Purview Audit is supported. This helps organizations understand licensing and billing requirements for full feature access.

• Clarified billing options: pay-as-you-go meters or Agent 365 subscription
• Specified that only Purview Audit is supported without these billing setups

The documentation clarifies how to configure guardrails for hosted agents using the Azure Developer CLI, specifying a new approach via the 'policies' list in 'azure.yaml' instead of directly setting 'rai_config'. It also updates the required CLI extension version and explains the mapping between 'policies' and 'rai_config'. This matters for users deploying guardrails, as the configuration steps have changed.

• Azure Developer CLI extension version requirement updated to 1.0.0-beta.1 or later
• Clarified that 'rai_config' is not set directly in 'azure.yaml' for CLI deployments; use 'policies' list instead
• Added explanation of how 'policies' entries are mapped to 'rai_config' during deployment

This new documentation introduces preview Copilot agent capabilities for working with Microsoft Word documents, including creating documents, retrieving content, and managing comments via API tools. It details required parameters, expected outputs, and usage notes for each tool, enabling automation and integration scenarios.

• Introduces WordCreateNewDocument tool to create Word files in OneDrive with HTML or plain text content
• Describes WordGetDocumentContent tool for retrieving DOCX content, metadata, and comments via sharing URL
• Documents WordCreateNewComment and WordReplyToComment tools for adding and replying to comments in Word documents

This new documentation introduces the Windows 365 for Agents MCP server, detailing its capabilities for full operational control of a Windows 365 cloud PC. It outlines available tools for desktop interaction, browser automation (primarily via Edge), UI inspection, and provides practical usage notes and common automation scenarios.

• Describes the Windows 365 for Agents MCP server and its operational scope
• Lists and explains tools for mouse, keyboard, screen, window, and browser automation
• Clarifies browser automation support (full DOM tools only on Edge)

This new documentation introduces the 'User reference (preview)' page, detailing a set of Copilot agent tools for accessing user profiles, managers, direct reports, and organizational hierarchy within a tenant. It describes endpoints, parameters, and usage scenarios for querying user and organizational data, supporting advanced OData queries and search.

• Introduces endpoints for retrieving user profiles, managers, and direct reports
• Describes advanced query capabilities including OData $select, $filter, $expand, $orderby, and $search
• Explains how to list and search users within an organization

This new documentation introduces a comprehensive set of Microsoft Copilot (MCP) Teams server APIs, detailing preview features for managing Teams chats, channels, messages, members, and teams via the standard harness. It outlines endpoints, required parameters, error handling, and supported operations, enabling advanced automation and integration scenarios for Teams within Copilot-powered solutions.

• New MCP Teams server with endpoints for chat, channel, message, member, and team management
• Detailed API reference for creating, updating, deleting, and retrieving Teams entities
• Support for private, shared, and standard channels, including member role management

This new documentation introduces a comprehensive set of Copilot-powered SharePoint management capabilities, including site, document library, file, folder, list, and column operations, as well as sharing, permissions, and security features. It details the available tools, parameters, and limitations for automating and managing SharePoint resources via Copilot agents.

• New Copilot agent tools for SharePoint site, document library, file, folder, and list management
• Support for creating, reading, updating, and deleting SharePoint lists, items, and columns
• File and folder operations (create, read, rename, delete, move, copy) with 5 MB size limit

This new documentation introduces a preview set of Copilot-powered tools for managing files and folders in a user's personal OneDrive, including file operations, sharing, sensitivity labeling, and asynchronous copy/move. It details the available API-like methods, their parameters, and operational constraints, enabling automation and integration scenarios for OneDrive within Copilot workflows.

• New Copilot-powered OneDrive management tools documented
• Supports file/folder creation, reading, renaming, deletion, copy, and move (≤5MB files)
• Enables sharing with role-based permissions and custom messages

This new documentation introduces a preview set of Copilot-powered tools for Microsoft Graph mail operations, enabling automated email creation, sending, management, and search within tenant environments. It details available API endpoints, required and optional parameters, and key capabilities such as HTML support, message search, and concurrency control.

• New Copilot agent tools for creating, sending, replying, and managing emails via Microsoft Graph
• Support for HTML and plain text email composition, including To, CC, and BCC fields
• APIs for searching messages using KQL and OData queries

This new documentation introduces the Fabric IQ Ontology MCP (preview), detailing how to connect Microsoft Copilot Studio agents to Fabric Ontology data using new MCP server endpoints and tools. It describes setup, prerequisites, and step-by-step integration with Copilot Studio, enabling natural language queries over organizational ontologies.

• Announces preview availability of Fabric IQ Ontology MCP server endpoints for AI assistants and agents
• Describes two new tools: list_ontology_entity_types and search_ontology for schema exploration and natural language querying
• Provides detailed setup instructions for connecting the MCP server in VS Code and Copilot Studio

This new documentation introduces the Copilot reference (preview), detailing the capabilities, usage, and integration of a Microsoft 365 Copilot agent for searching and discovering organizational content across Microsoft 365. It outlines how to invoke the tool, required and optional parameters, and key features such as multiturn chat, context retention, and file grounding.

• Describes a new Copilot agent for searching Microsoft 365 content (documents, emails, sites, etc.)
• Explains fallback behavior when workload-specific tools are unavailable
• Lists required and optional parameters for Copilot Chat API usage

This new documentation introduces the Calendar MCP toolset for Copilot, detailing a comprehensive set of preview features for programmatically managing calendar events, availability, attendees, and online meetings via agent flows. It outlines available operations, required and optional parameters, and key capabilities, enabling advanced calendar automation and integration scenarios.

• New preview documentation for Calendar MCP tools in Copilot
• Supports creating, updating, deleting, accepting, declining, and canceling calendar events
• Includes tools for finding meeting times, checking free/busy schedules, and managing attendees

This new page introduces and explains the concept of 'harnesses' in Microsoft Copilot Studio, detailing the three available harness types (GitHub Copilot harness, standard harness, Copilot chat harness), their capabilities, use cases, and billing models. It provides essential guidance for builders on selecting the appropriate harness for their agents or workflows.

• Defines what a harness is and its role in Copilot Studio
• Describes three harness types: GitHub Copilot harness, standard harness, Copilot chat harness
• Explains differences in capabilities, automation, and supported experiences for each harness

This new page introduces and explains the concept of 'agents' in Microsoft Copilot Studio, detailing three distinct harness types (GitHub Copilot, standard, and Copilot chat), their capabilities, deployment options, and billing models. It provides foundational knowledge for users to understand, select, and implement AI-powered agents tailored to various business scenarios.

• Defines three agent harness types: GitHub Copilot, standard, and Copilot chat
• Explains deployment across multiple channels and integration with business systems
• Details billing models for each harness type

This new documentation introduces the ability to connect agents to Microsoft Fabric IQ, enabling agents to access business data and analytics from Fabric for generating insights. It details prerequisites, setup, and removal steps, and notes usage-based billing via Copilot Credits.

• Describes how to add Fabric IQ as a tool to an agent in Copilot Studio
• Explains prerequisites including agent creation and Fabric access
• Outlines usage-based billing with Copilot Credits for agent actions

This new page introduces a usage-based billing model for agents powered by the GitHub Copilot harness, detailing how Copilot Credits are consumed, managed, and monitored. It marks a significant shift from previous billing approaches, impacting how organizations plan and pay for agent usage.

• Usage-based billing now applies to agents using the GitHub Copilot harness
• Copilot Credits are consumed for building, testing, and using agents—not just after publishing
• Credits are charged for LLM tokens, tools, and the harness itself

This new documentation introduces Work IQ (preview) in Copilot Studio, a feature that enhances agents with real-time, contextual understanding across Microsoft 365 and business systems. It details the architecture, key capabilities, governance, and step-by-step instructions for enabling and connecting agents to Work IQ.

• Introduction of Work IQ as an intelligence layer for Copilot and agents
• Description of Data, Memory, and Inference layers powering Work IQ
• Details on centralized governance, security, and evaluation processes

The Monitor tab documentation for Copilot Studio agents has been significantly expanded and restructured, introducing new analytics features such as KPI overviews, billing, savings estimation, user reactions, and tool usage metrics, while removing previous sections focused on recent tasks and file access. This represents a major shift in the monitoring and analysis capabilities available to users.

• Added Overview panel with key performance indicators (KPIs) including conversation sessions, reactions, active users, run durations, and success rate
• Introduced billing analytics showing Copilot Credits usage and trends
• Added Savings panel for estimating time and cost savings per run or per tool

The page has been significantly restructured and expanded to introduce new concepts such as harnesses, workflows, and natural language-based building, while providing more detailed guidance on Copilot Studio's capabilities, billing, and management. Several new sections clarify how to build, operate, and extend solutions, and the previous sections on agents, flows, and conversations have been replaced with more comprehensive and up-to-date explanations.

• Added detailed explanations of building blocks: agents, workflows, and agent flows
• Introduced the concept of harnesses (GitHub Copilot, standard, Copilot chat) and their impact on reasoning, capabilities, and billing
• Added section on building with natural language (preview feature)

Page removed or relocated. The documentation page detailing the Windows 365 for Agents MCP server and its extensive automation and control capabilities for Windows 365 Cloud PCs has been removed. This eliminates official reference material for a wide range of Copilot automation tools and use cases related to Windows 365 for Agents.

• Loss of detailed reference for the Windows 365 for Agents MCP server and its operational control features
• Removal of tool documentation for desktop interaction, browser automation, UI inspection, and session management
• No longer provides official guidance on automating Windows 365 Cloud PCs via Copilot

Page removed or relocated. The documentation page detailing the Work IQ Teams reference (preview) has been removed. This page described the MCP server endpoints and operations for managing Teams chats, channels, messages, and members, including supported parameters and error codes. The removal means that detailed reference information for these Copilot-related Teams automation capabilities is no longer available, which could significantly impact developers and admins relying on these APIs.

• Loss of endpoint documentation for Teams chat, channel, and team management via MCP server
• Missing details on required/optional parameters, error codes, and operation behaviors
• No longer provides reference for preview features and their limitations

Page removed or relocated. The documentation page detailing the Work IQ SharePoint reference (preview) for Copilot has been removed. This page described a wide range of SharePoint management capabilities available via Copilot, including site, document library, file, folder, list, and column operations, as well as sharing, permissions, and compliance features. The removal means users no longer have official documentation for these preview capabilities, which may impact adoption, integration, or troubleshooting.

• Loss of documentation for Copilot's SharePoint management preview features
• Missing reference for site, document library, file, folder, list, and column operations via Copilot
• No longer available: details on sharing, permissions, security, and compliance features in preview

Page removed or relocated. The documentation for the Work IQ OneDrive reference (preview) has been removed. This page described a set of Copilot-integrated tools for managing, searching, and sharing files and folders in a user's personal OneDrive, including file operations, folder management, sharing, and sensitivity labeling. The removal means detailed guidance on these preview Copilot OneDrive capabilities is no longer available, though it is unclear if the feature itself is deprecated or if the documentation has been relocated.

• Loss of documentation for Copilot's OneDrive file and folder management tools
• No longer available: details on file search, creation, deletion, sharing, and sensitivity labeling via Copilot
• Uncertainty whether the feature is deprecated or documentation has moved

Page removed or relocated. The documentation for the Fabric IQ Ontology MCP (preview) feature has been removed. This page described how to connect Microsoft Copilot Studio agents to Fabric IQ Ontology via MCP endpoints, including setup, prerequisites, and tool usage. The removal means that guidance for integrating Copilot with Fabric IQ Ontology via MCP is now missing, which could impact users seeking to leverage this capability.

• Loss of documentation on MCP server endpoints for Fabric IQ Ontology integration
• Missing setup instructions for connecting Copilot Studio agents to Fabric IQ Ontology
• No longer available: details on required scopes, tool definitions, and VS Code integration

Page removed or relocated. The documentation page for the Work IQ Calendar reference (preview) has been removed, resulting in the loss of detailed guidance on using Copilot's calendar management MCP tools. This removal means users no longer have access to official documentation for creating, updating, retrieving, and managing calendar events and availability via Copilot's MCP server, which may impact development and integration efforts.

• Loss of reference for all mcp_CalendarTools_* operations (create, update, delete, accept, decline, etc.)
• No longer documents parameters and usage for calendar event and scheduling tools in Copilot
• Missing feature descriptions for online meeting integration, attendee management, and recurrence patterns

Page removed or relocated. The documentation page introducing and explaining Microsoft IQ for agents in Copilot Studio (preview) has been removed. This page described a major new capability that enables Copilot agents to access and act on organizational data from Microsoft 365, Fabric, and Azure AI Foundry sources.

• Loss of overview and conceptual explanation of Microsoft IQ as a context layer for Copilot agents
• Removal of details on Work IQ, Fabric IQ, and Foundry IQ data sources and their capabilities
• Missing comparison between Microsoft IQ and traditional knowledge sources for agents

A new enforcement policy page explains what happens when Copilot Credits are exhausted in an environment, detailing the impact on both end users and makers, and outlining available options for restoring service. This is important for administrators and users to understand service continuity and credit management.

• Describes service interruption for both end users and makers when Copilot Credits run out
• Explains the concept of overage and Microsoft's grace period policy
• Lists options for restoring Copilot Credit capacity, including reallocation, purchase, or pay-as-you-go setup

This new page documents how to build a new agent in Microsoft Copilot Studio using the GitHub Copilot harness, including steps for naming, configuring, and saving agents, as well as details on usage-based billing with Copilot Credits.

• Introduces step-by-step instructions for creating a new agent in Copilot Studio
• Explains usage-based billing via Copilot Credits for agent-related actions
• Describes how to set or change the agent's primary language, solution, and schema name

This new page introduces documentation on how to purchase and manage Copilot credits, detailing both pay-as-you-go and prepurchase options. It provides guidance on linking environments to Azure subscriptions for billing and managing credits in the Power Platform admin center.

• Explains pay-as-you-go Copilot Studio billing via Azure subscription
• Describes a one-year prepurchase plan for Copilot Credits (CCCUs)
• Details how to link/unlink environments to Azure for billing

The documentation introduces Microsoft Agent 365 as a new central control plane for Copilot Studio agent governance, enabling features like centralized observability, identity management, and policy enforcement. Additional governance controls such as usage visibility, Copilot credit management, connector dependency insights, and GitHub integration with audit trails are now described. The Customer Lockbox section is clarified to specify which outbound data is not covered, including Agent 365 governance events.

• Microsoft Agent 365 added as a central governance and security control plane for Copilot Studio agents
• Copilot Studio agents can now be represented as identities in Microsoft Entra for advanced access controls
• New controls: usage visibility, Copilot credit governance, connector dependency insights, and GitHub-backed deployment with audit trails

The documentation now describes a new capability to block only 'untrusted' images and URLs that are not contextually related to the agent's conversation, in addition to the previous options to allow or block all images/URLs. This provides more granular control for administrators to balance security and usability.

• Added option to block only untrusted images and URLs, not just all or none
• Clarified what constitutes a contextually related (trusted) image or URL
• Detailed how nested or Markdown-embedded images/URLs are handled as untrusted

The documentation now introduces 'Memory' as a core component and configurable option for agents powered by the GitHub Copilot harness, allowing agents to remember details from interactions for future context. This is a significant new capability for agent behavior and context retention.

• Added 'Memory' as a core component in the Key concepts section
• Described the ability to turn Memory on for agents to remember interaction details
• Updated the Build tab description to include configuration of memory

The introduction now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, affecting how users are charged for using, building, testing, and evaluating agents.

• Added information about GitHub Copilot harness powering these features
• Introduced Copilot Credits and usage-based billing for agent-related actions
• Removed previous preview and experience comparison notes

The introduction now clarifies that features described in the article are powered by the GitHub Copilot harness and are subject to usage-based billing via Copilot Credits, impacting how users are charged for using, building, testing, and evaluating agents.

• Added information about GitHub Copilot harness powering the features
• Introduced Copilot Credits usage-based billing for relevant actions
• Linked to billing overview for agents powered by the GitHub Copilot harness

The introduction now specifies that features are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous preview/disclaimer notes. This is a significant update as it introduces billing implications for users.

• Added information about GitHub Copilot harness powering features
• Introduced usage-based billing with Copilot Credits
• Removed previous preview and production-readiness disclaimers

The introduction now states that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, affecting users' cost considerations when building or using agents and workflows.

• Added information about GitHub Copilot harness powering these features
• Introduced Copilot Credits and usage-based billing for agent-related actions
• Removed preview/disclaimer notes about new agent and workflow experiences

The documentation now clarifies that features described in this article are powered by the GitHub Copilot harness and are subject to usage-based billing via Copilot Credits. This impacts how users are charged for using, building, testing, and evaluating agents with classify nodes.

• Added information about GitHub Copilot harness powering these features
• Introduced Copilot Credits usage-based billing for relevant actions
• Removed previous preview and experience-specific disclaimers

The introduction now states that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, affecting how users are charged for using, building, and testing agents. This is a significant update as it introduces new billing implications for users.

• Features now powered by GitHub Copilot harness
• Usage-based billing with Copilot Credits applies to agent-related actions
• Reference to Copilot Credits billing overview added

The documentation now specifies that the quickstart and its features are powered by the GitHub Copilot harness, introduces usage-based billing with Copilot Credits, and clarifies that the natural language chat is only compatible with agents built in the GitHub Copilot harness. This impacts how users access, build, and are billed for solutions in Copilot Studio.

• GitHub Copilot harness is now explicitly identified as powering these features
• Usage-based billing with Copilot Credits is introduced and explained
• Clarifies compatibility: natural language chat only works with agents/artifacts in the GitHub Copilot harness

The introduction now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, affecting how users are charged for building and using agents and workflows.

• Added information about GitHub Copilot harness powering these features
• Introduced Copilot Credits as the billing mechanism for usage
• Specified that building, testing, and evaluating agents may consume credits

The documentation now focuses on the distinction between the standard harness and GitHub Copilot harness, replacing previous guidance about classic and new agent experiences. It introduces new instructions for accessing and building agents and flows with the standard harness, and removes sections about switching between classic and new experiences.

• Replaces 'classic vs. new experience' with 'standard harness vs. GitHub Copilot harness' terminology.
• Adds a new section detailing how to build and access agents and flows using the standard harness.
• Removes guidance on switching between classic and new experiences.

The documentation now clarifies that features described are powered by the GitHub Copilot harness and introduces usage-based billing via Copilot Credits for building, testing, and using agents. This is a significant update as it impacts cost and billing considerations for users.

• Added information about GitHub Copilot harness powering the features
• Introduced Copilot Credits as the billing mechanism for agent usage
• Clarified that building, testing, and evaluating agents may consume credits

The documentation now specifies that publishing agents is powered by the GitHub Copilot harness, introduces usage-based billing via Copilot Credits, and removes references to Microsoft IQ configuration. This clarifies both the technical backend and the billing model for Copilot Studio agents.

• Agents now explicitly powered by the GitHub Copilot harness
• Usage-based billing with Copilot Credits applies to agent activities
• References to Microsoft IQ configuration removed from prerequisites and published content

The documentation has shifted from describing a generic 'new agent experience' to specifically focusing on agents powered by the GitHub Copilot harness. This introduces usage-based billing with Copilot Credits and clarifies the distinction between the GitHub Copilot harness and the standard harness, including their capabilities and migration limitations.

• Introduction of the GitHub Copilot harness as a distinct, enhanced orchestration runtime for agents
• Usage-based billing with Copilot Credits now applies to building and using these agents
• Clarified that agents cannot be transferred between the GitHub Copilot harness and the standard harness

The documentation now specifies that features described are powered by the GitHub Copilot harness and are subject to usage-based billing via Copilot Credits. This introduces important billing implications for users building or using agents with SharePoint lists.

• Removed prerelease and preview disclaimers about agent and workflow experiences
• Added information about GitHub Copilot harness powering these features
• Introduced usage-based billing via Copilot Credits for building, testing, and using agents

The documentation now specifies that features described are powered by the GitHub Copilot harness and introduces usage-based billing via Copilot Credits for agent-related actions. This is a significant update as it impacts how users are billed for using, building, and testing agents.

• Features are now explicitly stated to be powered by the GitHub Copilot harness.
• Usage-based billing with Copilot Credits is introduced for agent actions.
• Clarifies that web search toggle applies to agents powered by the GitHub Copilot harness.

The documentation now specifies that knowledge features are powered by the GitHub Copilot harness and introduces usage-based billing via Copilot Credits for agent activities. The section comparing Knowledge sources and Microsoft IQ has been removed, reducing clarity on their differences.

• Knowledge features are now explicitly tied to the GitHub Copilot harness.
• Usage-based billing with Copilot Credits applies to building, testing, and using agents.
• Removed explanation of the distinction between Knowledge sources and Microsoft IQ.

The documentation now focuses on agents powered by the GitHub Copilot harness, introducing usage-based billing with Copilot Credits and clarifying knowledge source management for this harness. References to Microsoft IQ and Work IQ for M365 data have been removed, and the guidance now distinguishes between the standard and GitHub Copilot harnesses.

• Added information about usage-based billing with Copilot Credits for agents powered by the GitHub Copilot harness
• Clarified that knowledge source configuration and behavior differ between the standard and GitHub Copilot harnesses
• Removed references to Microsoft IQ and Work IQ for accessing M365 organizational data

The documentation now clarifies that Foundry IQ integration is available only for agents created with the GitHub Copilot harness, and that usage is billed via Copilot Credits. The process for adding and managing Foundry IQ connections has shifted from the 'Microsoft IQ' section to the 'Tools' section in Copilot Studio.

• Foundry IQ is now added as a tool from the Tools panel, not Microsoft IQ
• Integration requires agents created with the GitHub Copilot harness
• Usage of Foundry IQ features is billed via Copilot Credits

The documentation now clarifies that sharing and using agents in Copilot Studio may consume Copilot Credits due to usage-based billing powered by the GitHub Copilot harness. It also updates instructions for enabling editing rights to reference the GitHub Copilot harness instead of the previous 'new experience' terminology.

• Introduced usage-based billing for agent actions via Copilot Credits
• Clarified that features are powered by the GitHub Copilot harness
• Updated instructions for enabling editing rights to reference the GitHub Copilot harness

The documentation now clarifies that features described are powered by the GitHub Copilot harness and introduces usage-based billing via Copilot Credits for building, testing, and using agents. It also updates terminology to distinguish between the GitHub Copilot harness and the standard harness.

• Added explanation that features use the GitHub Copilot harness and are billed via Copilot Credits
• Clarified that usage-based billing applies to building, testing, and using agents
• Updated terminology from 'classic experience' to 'standard harness' and referenced the GitHub Copilot harness

The documentation now introduces a new natural language-based agent creation feature (preview) powered by the GitHub Copilot harness, and removes detailed step-by-step instructions for creating agents with the previous 'new experience.' Billing information for different harnesses is also clarified.

• Added section describing agent and workflow creation using natural language input (preview) via GitHub Copilot harness
• Removed detailed instructions for creating agents with the previous 'new experience'
• Removed prerequisites and next steps sections related to the previous agent creation process

The documentation now clarifies that features described are powered by the GitHub Copilot harness and introduces usage-based billing via Copilot Credits for using, building, testing, and evaluating agents. This is a significant update as it impacts how organizations plan and budget for Copilot Studio agent usage.

• Introduction of GitHub Copilot harness as the powering technology for connected agents
• Announcement of usage-based billing with Copilot Credits for agent-related activities
• Reference to new billing documentation for further details

The page now documents several new monitoring features for Copilot agents, including AI-generated analytics summaries, detailed cost and billing metrics, user reaction tracking, and transcript download options. It also clarifies that monitoring features are powered by the GitHub Copilot harness and subject to usage-based billing.

• Added AI-powered Summary section for analytics insights
• Introduced Cost and billing metrics with Copilot Credit tracking
• Documented Reactions section for user feedback (thumbs up/down)

Page removed or relocated. The documentation page describing the Work IQ MCP (Model Context Protocol) preview feature for Microsoft Copilot Studio has been removed. This page detailed how to extend Copilot agents with Work IQ MCP tools, including setup, governance, security, and integration steps.

• Loss of overview and setup instructions for Work IQ MCP in Copilot Studio
• Missing documentation on governance, security, and compliance for Work IQ MCP tools
• No longer available: step-by-step guide to connecting agents to Work IQ MCP servers (Mail, Calendar, Teams, etc.)

Page removed or relocated. The documentation for the Work IQ Word reference (preview) page has been removed, eliminating guidance on Copilot's preview tools for Word document creation, retrieval, and comment management via MCP. It is unclear if this reflects feature deprecation or a documentation restructure, but users now lack official reference for these capabilities.

• Loss of documentation for creating Word documents in OneDrive via Copilot MCP tools
• No longer available: instructions for retrieving Word document content and metadata using sharing URLs
• Comment management features (add, reply) for Word documents are undocumented

Page removed or relocated. The documentation for the Work IQ User reference (preview) page has been removed. This page described preview MCP server endpoints for accessing user profiles, managers, direct reports, and organizational hierarchy in Copilot scenarios. The removal means users and developers lose official guidance on these preview capabilities, though it is unclear if the feature itself is deprecated or if the documentation has been relocated.

• Loss of documentation for MCP server endpoints enabling user profile and organizational hierarchy queries
• No longer provides details on parameters, usage, and supported query options for endpoints like getMyProfile, getUserProfile, getUsersManager, getDirectReports, and listUsers
• Missing guidance on preview feature limitations, best practices, and common use cases

Page removed or relocated. The documentation for the Work IQ Mail reference (preview), which described a set of Copilot MCP tools for Microsoft Graph mail operations, has been removed. This eliminates official guidance on using these preview mail-related automation features in Copilot, though it is unclear if the feature itself is deprecated or the documentation was relocated.

• Loss of documentation for creating, sending, updating, deleting, and searching emails via Copilot MCP tools
• No longer available: parameter details and usage for mail-related automation endpoints
• Missing guidance on preview limitations, supported scenarios, and API behaviors

Page removed or relocated. The documentation for the Work IQ Copilot (preview) feature has been removed, leaving a gap in official guidance on how to use this tool for searching and discovering information across Microsoft 365 content. It is unclear if the feature itself is deprecated or if the documentation has been relocated.

• Loss of reference details for Work IQ Copilot's capabilities and usage
• No longer available: tool parameters, use cases, and integration guidance
• Missing information on fallback search scenarios and conversation management

Page removed or relocated. The documentation page describing Microsoft IQ sources for agents, specifically the Work IQ sources that enable Copilot agents to access various Microsoft 365 data types, has been removed. This leaves a gap in official guidance on which M365 data sources are available to Copilot agents and their capabilities, especially for preview users.

• Loss of documentation on Work IQ sources (Mail, Calendar, Teams, OneDrive, SharePoint, User profile, Copilot Search, SharePoint Lists)
• No longer describes which sources are enabled by default and how to enable others
• Missing table outlining read and action capabilities per source

Page removed or relocated. The documentation page explaining how to manage Microsoft IQ sources in a Copilot agent (preview) has been removed. This eliminates guidance on enabling, disabling, and configuring individual IQ sources, as well as managing scoped knowledge and understanding source behavior. It is unclear if this reflects a feature deprecation or a documentation restructure.

• Loss of step-by-step instructions for enabling/disabling Microsoft IQ sources in Copilot Studio
• No longer documents how to manage scoped knowledge for each source
• Removes explanation of source details, including knowledge and tools available per source

Page removed or relocated. The documentation page explaining how to enable Microsoft IQ for an agent in Copilot Studio (preview) has been removed. This removes guidance on connecting agents to Microsoft 365 organizational data and configuring data sources, which may impact users seeking to leverage these preview capabilities.

• Loss of instructions for enabling Microsoft IQ in Copilot Studio agents
• Missing details on connecting agents to Work IQ, Fabric IQ, and Foundry IQ sources
• No longer documents how to configure individual Microsoft 365 data sources and scoped knowledge

Page removed or relocated. The documentation comparing the classic and new agent experiences in Microsoft Copilot Studio has been removed. This eliminates official guidance on the differences, feature gaps, and migration limitations between the two experiences, which is important for users deciding which experience to adopt.

• Loss of detailed comparison between classic and new agent experiences
• No longer documents feature gaps or migration limitations
• Removes guidance on choosing between experiences based on use case

The documentation clarifies the differences between the new and classic agent sharing experiences, adds prerequisites for sharing agents, and provides more detailed instructions for sharing and stopping sharing of agents, including editing rights and publishing requirements.

• Clarifies that instructions apply to the new agent experience and links to classic experience documentation
• Explains how to grant editing rights by turning off the new experience or assigning security roles
• Adds prerequisites: agents must be published to Teams + Microsoft 365 with the appropriate setting enabled

The documentation clarifies how root agent invocations are now emitted as 'dependencies' instead of 'requests' in Application Insights, and provides guidance on evaluating the preview feature using the Early release cycle. It also removes some details about sub-agent trace reconstruction.

• Root agent invocations (`invoke_agent`) are now emitted as `dependencies` rather than `requests`.
• Guidance added for testing the preview feature in non-production environments with Early release cycle enabled.
• Removed detailed explanation about sub-agent trace reconstruction using conversation IDs.

A new section was added to guide users on planning for throughput and rate limits, emphasizing the importance of considering peak traffic and providing a link to further guidance on managing and requesting limit increases.

• Added guidance on planning for throughput and rate limits
• Explains risks of exceeding limits in high-volume deployments
• Provides a link to detailed planning and mitigation strategies

The documentation now clarifies how SharePoint sensitivity labels and encryption affect agent access, specifies the scope of folder/site crawling, and adds a new section detailing limitations such as hyperlink crawling and site type support. These changes help users better understand what content Copilot agents can and cannot access or ground on when using SharePoint as a knowledge source.

• Clarified that encrypted or password-protected files (including those with certain sensitivity labels or Double Key Encryption) cannot be accessed or grounded on by the agent.
• Specified that agents only search within registered folders/sites and their subfolders, not parent or sibling folders/sites.
• Added a new section explaining that hyperlinks within documents are not crawled unless the target is separately registered.

A new note clarifies that code interpreter should be used instead of semantic search for searching over Excel file content, due to semantic search limitations with cell indexing. This guidance helps users choose the correct tool for Excel data tasks.

• Added note recommending code interpreter over semantic search for Excel file content search
• Explains semantic search limitations with cell indexing

The documentation now clarifies that the 'delete' API operation only supports Agent Builder agents, which is important for administrators to avoid attempting unsupported deletions.

• Added explicit note that 'delete' API operation supports only Agent Builder agents

The documentation now clarifies that workflows in Copilot Studio are powered by the GitHub Copilot harness and introduces distinctions in billing methods between different harnesses. This helps users understand which harness powers their workflows and how billing is applied.

• Clarified that workflows use the GitHub Copilot harness
• Added details about usage-based billing with Copilot Credits for GitHub Copilot harness
• Specified licensing differences for agents powered by other harnesses

The introduction now clarifies that features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand billing implications and how to access these features.

• Added note that features are powered by the standard harness
• Linked to licensing information for agents powered by the standard harness
• Provided guidance on accessing standard agents and agent flows

The introduction now clarifies that real-time agent features are powered by the 'standard harness' and provides links to licensing and access information. This helps users understand the billing model and how to enable these features.

• Added note specifying features are powered by the standard harness
• Included references to licensing and access documentation for standard agents

The introduction now clarifies that the features discussed are powered by the standard harness, with references to licensing and access documentation. This helps users understand billing implications and how to access these features.

• Added note about standard harness powering the features
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features discussed are powered by the 'standard harness' and provides references to licensing and access documentation. This helps users understand billing implications and how to access these features.

• Added note about features being powered by the standard harness
• Linked to licensing information for standard harness agents
• Linked to documentation on accessing standard agents and agent flows

The introduction now clarifies that the features discussed are powered by the 'standard harness' and references licensing and access documentation, providing important context for users regarding billing and feature access.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features discussed are powered by the standard harness, with references to licensing and access documentation. This helps users understand billing implications and how to access these features.

• Added note about standard harness powering the features
• Linked to licensing information for standard harness agents
• Linked to documentation on accessing standard agents and agent flows

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using IVR capabilities in Copilot Studio.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the Hold and resume feature is powered by the standard harness and references related licensing and access documentation. This helps readers understand prerequisites and billing implications for using this feature.

• Added note that Hold and resume is powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand the billing model and feature availability for agent templates in Copilot Studio.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the described features are powered by the 'standard harness' and references related licensing and access documentation, helping users understand prerequisites and billing implications.

• Added explanation that features use the 'standard harness'
• Linked to licensing information for standard harness-powered agents
• Provided guidance on accessing standard agents and agent flows

The introduction now clarifies that Cloud PC pool features are powered by the 'standard harness' and references specific licensing and access documentation. This helps users understand the billing model and how to access these features.

• Added note that features are powered by the standard harness
• Linked to licensing details for agents powered by the standard harness
• Linked to instructions for accessing standard agents and agent flows

The introduction and upgrade guidance were clarified to focus on the cloning and migration process from classic Power Virtual Agents bots to Copilot Studio, with more explicit details on what is and isn't cloned. The section promoting structured learning and training was removed, narrowing the page's focus to technical migration steps.

• Intro now emphasizes cloning and migration eligibility, process, and testing, rather than general product improvements.
• Cloning process details updated to specify creation of a 'standard agent' and clarify what is cloned.
• Explicit note that cloning creates a new agent and does not modify the original classic bot.

The introduction now clarifies that Website Q&A agents are powered by the 'standard harness' and references related billing and access documentation. This helps users understand licensing and feature access implications.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the Weather agent template uses the standard harness, with implications for licensing and feature access. This helps users understand billing and access requirements for these features.

• Added note specifying that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that Sustainability Insights features are powered by the standard harness, with references to related licensing and access documentation. This helps users understand billing and access implications.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard harness agents

The introduction now clarifies that Store Operations agent features are powered by the 'standard harness' and provides references to licensing and access documentation. This helps readers understand billing implications and how to access these features.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the Safe Travels agent template uses the standard harness, with associated billing and licensing details, and provides links to relevant documentation. This helps users understand the technical and licensing context for deploying the agent.

• Added note specifying features are powered by the standard harness
• Included reference to billing options and licensing for standard harness agents
• Provided links to documentation on accessing standard agents and agent flows

The introduction now clarifies that the IT Helpdesk agent features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand the underlying technology and billing model.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references licensing and access documentation for these standard features. This helps users understand the billing model and feature availability for agent templates.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that Citizen Services agent features are powered by the standard harness, with links to licensing and access information. This helps users understand billing and feature access implications.

• Added note that features are powered by the standard harness
• Included references to licensing and access documentation

The introduction now clarifies that the features discussed are powered by the 'standard harness' and provides links to related licensing and access documentation. This helps users understand which billing model applies and how to access standard features.

• Added clarification about features being powered by the 'standard harness'
• Linked to licensing for agents powered by the standard harness
• Linked to guidance on accessing standard agents and agent flows

The introduction now clarifies that the features discussed are powered by the 'standard harness' and references specific billing and access documentation for standard agents and agent flows. This helps readers understand which licensing model applies to the described features.

• Added clarification that features are powered by the standard harness
• Linked to documentation on licensing for agents powered by the standard harness
• Added reference to accessing standard agents and agent flows

A clarification was added that the features discussed are powered by the 'standard harness' and subject to specific licensing and access requirements. This helps users understand which Copilot Studio features and billing models apply when creating privacy statements and terms of use for Teams agents.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references associated licensing and access documentation. This helps readers understand prerequisites and billing implications for using these integration features.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the publishing and deployment features described are specific to agents powered by the 'standard harness,' and provides references to licensing and access documentation. This helps users understand feature applicability and billing implications.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references licensing and access documentation, helping readers understand prerequisites and billing implications.

• Added note that features use the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the standard harness, with references to licensing and access documentation. This helps readers understand prerequisites and billing implications before proceeding.

• Added note that features use the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the Agents Client SDK features are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand billing implications and how to access these features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the display name suffix feature is powered by the 'standard harness' and references relevant licensing and access documentation. This helps readers understand prerequisites and billing implications.

• Added note that the feature uses the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand prerequisites and billing implications for using these agent features in Teams and Microsoft 365 Copilot.

• Added note that features are powered by the standard harness
• Linked to licensing information for standard harness agents
• Linked to guidance on accessing standard agents and agent flows

The introduction now clarifies that the features described are powered by the 'standard harness' and references licensing and access documentation for these features. This helps readers understand prerequisites and billing implications.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents

The documentation clarifies that the prompt node is not available in workflows powered by the GitHub Copilot harness, but remains available in standard agent flows. This distinction helps users understand where the prompt node can be used.

• Clarified that prompt node is unavailable in GitHub Copilot harness workflows
• Confirmed prompt node remains available in standard agent flows

The introduction now clarifies that the prompt library features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand billing implications and how to access these features.

• Added explanation that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that features described are powered by the 'standard harness' and references related licensing and access documentation. This provides important context for users regarding billing and feature access.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that NLU+ features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand the underlying platform and billing implications for NLU+ capabilities.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the described generative AI features are powered by the 'standard harness' and references related billing and access documentation. This helps users understand licensing implications and how to access these features.

• Added note specifying features are powered by the 'standard harness'
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that the described features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using generative answers with SharePoint content.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references licensing and access documentation, helping users understand prerequisites and billing implications.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references specific licensing and access documentation. This helps users understand billing implications and how to access these features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the described features are powered by the 'standard harness' and references relevant licensing and access documentation. This helps users understand prerequisites and billing implications for using uploaded files with generative answers nodes.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using Copilot to create and edit topics.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the multilingual agent features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these features.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features discussed are powered by the Copilot chat harness and references specific licensing and billing options. This helps readers understand the underlying technology and potential costs associated with using these extensibility features.

• Added note that features are powered by the Copilot chat harness
• Referenced licensing and billing options for agents using the standard harness

The introduction now clarifies that the features discussed are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand the billing model and how to access standard features for agents and agent flows.

• Added note that features are powered by the standard harness
• Linked to licensing information for agents using the standard harness
• Provided guidance on accessing standard agents and agent flows

The introduction now clarifies that features on the Tools page are powered by the standard harness, with references to related licensing and access documentation. This helps users understand prerequisites and billing implications.

• Added note that Tools page features use the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the described features are powered by the 'standard harness' and references licensing and access documentation. This helps users understand prerequisites and billing implications for using unstructured data as a knowledge source in Copilot Studio.

• Added explicit note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand billing implications and how to access these features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features discussed are powered by the 'standard harness' and references relevant licensing and access documentation. This helps readers understand prerequisites and billing implications for using these connector features in Copilot Studio.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the described knowledge source features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand prerequisites and billing implications for using Copilot connectors as a knowledge source.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the code interpreter features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these preview features.

• Added note that features are powered by the 'standard harness'
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the SharePoint knowledge source features are powered by the 'standard harness' and references specific licensing and access documentation. This helps users understand prerequisites and billing implications for using these features.

• Added note that features are powered by the 'standard harness'
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the file upload features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these Copilot capabilities.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

A new note clarifies that features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using Dataverse tables as a knowledge source in Copilot Studio.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the Document (preview) feature is powered by the standard harness, with references to billing and licensing details, and provides links to learn more about accessing standard features. This helps users understand the underlying infrastructure and licensing implications.

• Added note that features are powered by the standard harness
• Referenced billing options and licensing for agents using the standard harness
• Provided links to documentation on accessing standard agents and agent flows

The introduction now clarifies that the features described are powered by the 'standard harness' and provides links to licensing and access information for standard agents. This helps readers understand prerequisites and billing implications.

• Added clarification that features use the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the standard harness and references relevant licensing and access documentation. This helps readers understand prerequisites and billing implications for using these capabilities.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The documentation now clarifies that agent flows are part of the 'standard harness' experience in Copilot Studio, with references to related licensing and access documentation. It also distinguishes between the standard harness and the GitHub Copilot harness when creating or editing agent flows.

• Agent flows are now described as part of the standard harness, not just the classic experience.
• Added references to licensing and access documentation for standard harness features.
• Clarified workflow for users of the GitHub Copilot harness versus the standard harness.

The introduction now clarifies that the multistage and AI approvals features are powered by the 'standard harness' and references related billing and access documentation. This helps users understand licensing and access requirements for these preview features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that the features described are powered by the 'standard harness' and references licensing and access documentation for standard agents and agent flows. This helps readers understand the billing model and feature availability context.

• Added note that features are powered by the standard harness
• Linked to licensing information for agents powered by the standard harness
• Linked to documentation on accessing standard agents and agent flows

The introduction now clarifies that the features discussed are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand prerequisites and billing implications for using these features.

• Clarifies that features are powered by the standard harness
• Adds references to licensing and access documentation for standard agents and flows

The introduction now clarifies that the described features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using agent flows as tools.

• Clarifies that features use the 'standard harness'
• Adds links to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the features discussed are powered by the 'standard harness' and references licensing and access documentation, helping readers understand prerequisites and billing implications.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the customization features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these customization options.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand prerequisites and billing implications for using these capabilities.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the integration features are powered by the 'standard harness' and references licensing and access documentation for standard agents and agent flows. This helps readers understand prerequisites and billing implications.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the described features are powered by the 'standard harness' and references licensing and access documentation. This helps users understand prerequisites and billing implications for using these Copilot agent capabilities.

• Added note specifying features are powered by the standard harness
• References to licensing and access documentation for standard agents

The introduction now clarifies that the described features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using computer use in Copilot Studio.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand prerequisites and billing implications for using suggested prompts.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand prerequisites and billing implications for using automatic agent conversation start.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references specific licensing and access requirements. This helps readers understand prerequisites and billing implications for using Azure Bot Service skills in Copilot Studio.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the standalone computer use tool is powered by the standard harness, and provides references to licensing and access documentation. This helps users understand prerequisites and billing implications for using these features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the 'computer use' feature is powered by the standard harness, with references to licensing and access documentation. This helps users understand prerequisites and billing implications for using the feature.

• Added note specifying the feature is powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that the code interpreter features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the features described are powered by the 'standard harness' and references licensing and access documentation for standard agents and agent flows. This helps users understand billing implications and how to access these features.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that batch testing for prompts is powered by the 'standard harness' and references related billing and access documentation. This helps users understand the underlying infrastructure and licensing implications.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the testing features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features discussed are powered by the 'standard harness' and provides references to licensing and access documentation. This helps users understand the underlying technology and billing model for these chatbot features.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features discussed are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these solution management features.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The documentation now clarifies that the export/import features are powered by the 'standard harness' and references related licensing and access information. It also updates guidance for exporting agents with many components to use the standard harness instead of the classic experience.

• Added note that export/import features use the standard harness and are subject to specific licensing.
• Provided links to learn more about accessing standard features and billing.
• Changed export guidance for large agents to reference the standard harness instead of the classic experience.

The introduction now clarifies that features described are powered by the 'standard harness' and references related billing and access documentation. This helps users understand licensing implications and how to access these features.

• Added explanation that features use the 'standard harness' with specific billing options
• Provided links to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the described features are powered by the 'standard harness' and references licensing and access documentation. This helps users understand prerequisites and billing implications for using activity tracking features.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that deep reasoning features are powered by the 'standard harness' and references licensing and access documentation for standard agents. This helps users understand billing and access implications for using deep reasoning models.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related billing and access documentation. This helps users understand licensing implications and how to access these features.

• Added explanation that features use the 'standard harness'
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references licensing and access documentation. This helps users understand prerequisites and billing implications for using component collections.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the features described are powered by the 'standard harness' and references licensing and access documentation. This helps users understand prerequisites and billing implications for using Adaptive Cards in Copilot Studio.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the described features are powered by the standard harness, with references to licensing and access documentation. This helps users understand prerequisites and billing implications for using these Copilot Studio preview features.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand prerequisites and billing implications for using these agent-connecting features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand the scope and prerequisites for using these features.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and the scope of the described capabilities.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the features described are powered by the 'standard harness' and references related billing and access documentation. This helps users understand licensing implications and how to access these features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the analytics features discussed are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these analytics capabilities.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the analytics features are powered by the standard harness, with references to licensing and access documentation. This helps users understand prerequisites and billing implications for using analytics.

• Added note specifying analytics features are powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that the analytics features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these analytics capabilities.

• Added note specifying analytics features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the standard harness and references licensing and access documentation for standard agents and agent flows. This helps users understand prerequisites and the scope of features.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the custom metrics feature is powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the described analytics features are specific to agents powered by the standard harness, and provides links to related licensing and access documentation. This helps users understand the scope and applicability of the billing analytics features.

• Clarifies that analytics features apply to agents using the standard harness
• References licensing details for standard harness agents
• Adds link to instructions for accessing standard agents and agent flows

The introduction now clarifies that the evaluation features discussed are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the automated agent evaluation features are powered by the 'standard harness' and references licensing and access documentation. This helps users understand prerequisites and billing implications.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and provides links to information about licensing and access for standard agents and agent flows. This helps users understand prerequisites and billing implications.

• Added note specifying features are powered by the standard harness
• Included references to licensing and access documentation for standard agents

The introduction now clarifies that the described agent evaluation features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these evaluation features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The documentation now clarifies that the error codes and related features apply specifically to agents powered by the GitHub Copilot harness, and introduces information about usage-based billing with Copilot Credits. This helps users understand the scope of applicability and potential billing implications.

• Clarified that error codes and features are for agents powered by the GitHub Copilot harness
• Removed prerelease and preview disclaimers for the new agent experience
• Added information about Copilot Credits and usage-based billing for agent actions

The documentation now clarifies that features described are specifically powered by the GitHub Copilot harness and introduces Copilot Credits as the billing mechanism for usage, building, and testing of agents. It also specifies that enhanced orchestration and certain tool behaviors apply to agents using the GitHub Copilot harness.

• Introduced Copilot Credits as the billing model for agent usage and development
• Clarified that enhanced orchestration and tool invocation features are specific to agents powered by the GitHub Copilot harness
• Removed references to preview status and classic/new experience comparison in the introduction

The introduction now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous prerelease and preview status notes.

• Added explanation that features use the GitHub Copilot harness
• Introduced Copilot Credits and usage-based billing details
• Removed notes about preview status and experience differences

The introduction now clarifies that features discussed are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous notes about preview status and feature parity.

• Added information about GitHub Copilot harness powering features
• Introduced Copilot Credits and usage-based billing for agent-related actions
• Removed prior notes about preview status, feature availability, and experience conversion

The introduction now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, affecting users' cost considerations when using, building, or testing agents.

• Added information about GitHub Copilot harness powering the features
• Introduced Copilot Credits and usage-based billing details
• Removed previous notes about preview status and experience differences

The introduction now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous notes about preview status and experience differences.

• Added information about GitHub Copilot harness powering features
• Introduced Copilot Credits and usage-based billing for agent-related actions
• Removed notes about preview status and differences between classic and new agent experiences

The introduction now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous notes about preview status and feature parity.

• Added explanation of Copilot Credits and usage-based billing for agent-related actions
• Removed information about preview status, feature availability differences, and conversion limitations between classic and new experiences

The documentation now clarifies that features described are powered by the GitHub Copilot harness and introduces usage-based billing via Copilot Credits for building, testing, and using agents. The prerequisite for creating a skill is also updated to require an agent created with the GitHub Copilot harness.

• Added information about GitHub Copilot harness powering the features
• Introduced Copilot Credits and usage-based billing for agent activities
• Updated prerequisite to specify agents must be created with the GitHub Copilot harness

The documentation now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits. It also updates prerequisites to specify agents must be created with the GitHub Copilot harness.

• Added information about usage-based billing with Copilot Credits for using, building, and testing agents
• Clarified that features are powered by the GitHub Copilot harness
• Updated prerequisite to specify agents must be created with the GitHub Copilot harness

The introduction now clarifies that the documented settings apply specifically to agents powered by the GitHub Copilot harness, and introduces usage-based billing with Copilot Credits. This is important for users to understand billing implications and the scope of the documentation.

• Specifies that settings are for agents powered by the GitHub Copilot harness
• Introduces Copilot Credits and usage-based billing for agent actions
• Removes references to preview status and classic vs. new agent experiences

The introduction now clarifies that features discussed are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous notes about preview status and experience differences.

• Added information about GitHub Copilot harness powering features
• Introduced Copilot Credits and usage-based billing for agent activities
• Removed details about preview status and differences between classic and new agent experiences

The introduction now clarifies that the Preview tab and features described are specifically for agents powered by the GitHub Copilot harness, and introduces information about usage-based billing with Copilot Credits.

• Specifies that the Preview tab applies to agents using the GitHub Copilot harness
• Introduces Copilot Credits and usage-based billing for building, testing, and evaluating agents
• Removes references to classic vs. new agent experiences and public preview status

The documentation now clarifies that the Preview conversation history feature is specific to agents powered by the GitHub Copilot harness and introduces information about usage-based billing with Copilot Credits. This is important for users to understand feature availability and potential costs.

• Specifies that the Preview tab and conversation history apply to agents using the GitHub Copilot harness
• Introduces Copilot Credits and usage-based billing for building, testing, and evaluating agents
• Removes references to classic vs. new agent experiences and preview disclaimers

The documentation clarifies how Memory works in Copilot Studio, including privacy details, billing implications, and user control. It now specifies that user memories are private, not visible to makers, and are disabled in group chats and Teams channels. It also introduces usage-based billing via Copilot Credits and provides more detail on how users can manage their memories.

• Clarifies that user memories are private and not accessible to makers or other users
• Specifies that user memory is disabled in group chats and Teams channels
• Introduces usage-based billing for Memory features via Copilot Credits

The introduction now clarifies that features discussed are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous preview and experience-related notes.

• Added explanation that features use the GitHub Copilot harness and Copilot Credits for billing
• Removed notes about preview status, experience differences, and feature availability between classic and new experiences

The introduction now clarifies that features described are powered by the GitHub Copilot harness and are subject to usage-based billing via Copilot Credits, affecting both agent creation and use. Previous prerelease and preview status notes have been removed.

• Added explanation that features use the GitHub Copilot harness and Copilot Credits for billing
• Clarified that usage-based billing applies to building, testing, and using agents
• Removed notes about preview status and feature availability differences between classic and new experiences

The introduction now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous preview and experience-related notes. This matters for users tracking licensing, billing, and deployment implications.

• Added explanation that features use the GitHub Copilot harness
• Introduced Copilot Credits as the billing mechanism for usage
• Removed details about preview status and differences between classic and new agent/workflow experiences

The documentation now clarifies that the Build tab and its features are specific to agents powered by the GitHub Copilot harness, introduces usage-based billing with Copilot Credits, and removes references to Microsoft IQ in the Build tab's components. These changes help users understand harness-specific capabilities and billing implications.

• Clarifies that the Build tab applies to agents using the GitHub Copilot harness
• Introduces Copilot Credits and usage-based billing for building and using agents
• Removes Microsoft IQ as a selectable component in the Build tab

The documentation now clarifies that testing agents uses the GitHub Copilot harness and is subject to usage-based billing via Copilot Credits. Prerequisites and feature descriptions have been updated to reflect this harness-specific context.

• Explicitly states that the Preview tab and features are powered by the GitHub Copilot harness
• Introduces Copilot Credits and usage-based billing for building, testing, and evaluating agents
• Updates prerequisites to require agents created with the GitHub Copilot harness

The introduction now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous notes about preview status and experience differences.

• Added explanation that GitHub Copilot harness powers the features
• Introduced Copilot Credits and usage-based billing for agent activities
• Removed details about preview status and differences between classic and new agent experiences

The documentation now clarifies that the activity trace and related features are specific to agents powered by the GitHub Copilot harness, and introduces information about usage-based billing with Copilot Credits. This helps users understand prerequisites and potential costs.

• Clarified that the activity trace applies to agents using the GitHub Copilot harness
• Added information about Copilot Credits and usage-based billing for these features
• Updated prerequisites to specify agents must use the GitHub Copilot harness

The introduction now clarifies that features described are powered by the GitHub Copilot harness and subject to usage-based billing via Copilot Credits, replacing previous preview and experience-related notes. This matters for users tracking licensing, billing, and technical dependencies.

• Added explanation that features use the GitHub Copilot harness
• Introduced Copilot Credits as the billing mechanism for usage
• Removed prior notes about preview status and differences between classic and new agent/workflow experiences

The documentation clarifies that the evaluation feature is a production-ready preview and updates prerequisites to specify that agents must be created with the GitHub Copilot harness. Some preview disclaimers and process instructions have been streamlined for clarity.

• Clarifies that the evaluation feature is a production-ready preview, not just a public preview.
• Prerequisite now specifies agents must be created with the GitHub Copilot harness.
• Removes references to classic vs. new agent experiences and public preview limitations.

The documentation now clarifies that adding tools to agents and related features are specifically available for agents powered by the GitHub Copilot harness, and introduces information about usage-based billing with Copilot Credits.

• Removed prerelease and preview disclaimers about agent experiences.
• Added details about Copilot Credits and usage-based billing for agents using the GitHub Copilot harness.
• Clarified that prerequisites and custom tool support apply to agents created with the GitHub Copilot harness.

The documentation now clarifies that the features described are specifically powered by the GitHub Copilot harness and that usage is subject to Copilot Credits and usage-based billing. Prerequisites have also been updated to specify agents must use the GitHub Copilot harness.

• Added explicit note about GitHub Copilot harness powering the features
• Introduced information about Copilot Credits and usage-based billing for agent actions
• Prerequisites now specify agents must be created with the GitHub Copilot harness

The introduction now clarifies that the features described are powered by the 'standard harness' and references related billing and access documentation. This helps users understand licensing implications and how to access these features.

• Added note that features use the 'standard harness' with specific billing options
• Linked to documentation on licensing and accessing standard agents and flows

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This provides important context about billing and feature availability for users planning to use these capabilities.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that proactive messaging features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using Power Fx in Copilot Studio.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the described features are powered by the 'standard harness' and references licensing and access documentation, providing important context about feature availability and billing.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the features described are powered by the 'standard harness' and provides links to licensing and access information for standard agents and agent flows. This helps users understand prerequisites and billing implications.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the described features are powered by the 'standard harness' and references specific licensing and access documentation. This helps users understand prerequisites and billing implications for using agent flows.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the features described are specific to agents powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand prerequisites and scope for using entities and slot filling.

• Added note specifying features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using connectors in Copilot Studio.

• Added explanation that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the CLU integration features are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications for using these features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard harness features

The introduction now clarifies that the described features are powered by the 'standard harness' and references licensing and access documentation for standard agents and agent flows. This helps readers understand prerequisites and billing implications for using these features.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the sharing features described are specific to agents powered by the 'standard harness' and references related licensing and access documentation. This helps users understand the scope and prerequisites for sharing agents.

• Added note specifying features are for agents powered by the standard harness
• Linked to licensing and access documentation for standard harness agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps users understand prerequisites and billing implications.

• Added note that features are powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

The introduction now clarifies that the features described are powered by the 'standard harness' and references related billing and access documentation. This helps users understand licensing implications and how to access these features.

• Added note that features use the 'standard harness' with specific billing options
• Linked to licensing and access documentation for standard agents and agent flows

A new note clarifies that features in this article are powered by the standard harness, with links to licensing and access information. This helps users understand billing implications and how to access these features.

• Added note about standard harness powering these features
• Linked to licensing and access documentation for standard agents

A new note clarifies that features in this article are powered by the standard harness, with references to licensing and access documentation. This helps users understand billing implications and how to access standard agent features.

• Added note about standard harness powering these features
• Linked to licensing and access documentation for standard agents

The introduction now clarifies that the features described are powered by the 'standard harness' and references licensing and access documentation for standard agents and agent flows. This helps users understand prerequisites and billing implications.

• Added note that features use the standard harness
• Linked to licensing and access documentation for standard agents

A new note clarifies that the features described are powered by the 'standard harness' and references related licensing and access documentation. This helps readers understand prerequisites and billing implications for using Adaptive Cards in Copilot Studio.

• Added note about features being powered by the standard harness
• Linked to licensing and access documentation for standard agents and agent flows

Page removed or relocated. The documentation explaining the behavioral and architectural changes from GPT 5.0 to GPT 5.1 has been removed. This leaves a gap for users and developers seeking guidance on adapting prompts, workflows, and agent instructions for the new model's intent-first, adaptive reasoning approach.

• Loss of detailed comparison between GPT 5.0 and GPT 5.1 behaviors
• Missing guidance on adapting prompts and agent instructions for GPT 5.1
• No longer documents new output style profiles and adaptive reasoning features

This new page introduces and documents the credit usage system for Microsoft Copilot Cowork tasks, including the `/cost` command for tracking credit consumption. It explains how credits are allocated, tracked, and managed, and clarifies the distinction between individual and group credit limits.

• Introduces the concept of credits for Copilot Cowork tasks, set by organizations
• Documents the `/cost` command to check approximate credit usage and remaining balance
• Explains group vs. individual credit limits and their impact on usage

The documentation now describes support for multiple owners per agent in Microsoft 365 Copilot Agent Builder, clarifies the distinction between owner and chat user roles, and updates management permissions accordingly. This enables collaborative agent management and editing, not just single-author control.

• Agents now support multiple owners, allowing shared editing and management rights.
• The share dialog distinguishes between 'Can edit' (owner) and 'Can chat' (chat user) roles.
• Only individuals (not groups) can be assigned as owners; groups can be chat users only.

The documentation now states that Copilot Cowork uses the ChatGPT Images 2.0 model for image generation instead of the previously listed Imagen 2 model. This change affects both the description of Cowork's capabilities and the technical explanation of model routing, indicating a significant update to the underlying image generation technology.

• Image generation model changed from Imagen 2 to ChatGPT Images 2.0
• All references to Imagen 2 replaced with ChatGPT Images 2.0 in capabilities and model routing sections

The documentation now states that Copilot Cowork uses the ChatGPT Images 2.0 model for image generation instead of Imagen 2, clarifying the underlying technology. There are also minor clarifications to approval options, specifying that 'Always allow' applies only to the current session. These changes impact user understanding of image generation capabilities and approval workflows.

• Image generation model changed from Imagen 2 to ChatGPT Images 2.0
• Clarified that 'Always allow' approval applies only to the current session
• Minor rewording for clarity in approval options

The documentation now lists 'ChatGPT Images 2.0' as the image generation model available in Copilot Cowork, replacing the previous reference to 'Imagen 2.' This signals a change in the underlying image generation capability offered to users.

• Replaced 'Imagen 2' with 'ChatGPT Images 2.0' as the image generation model
• No other model changes or admin controls were introduced

A new feature allows users to check their approximate Copilot Credit usage directly within Microsoft Copilot Cowork using the `/cost` command. This empowers end users to monitor their own credit consumption in real time.

• Users can now enter `/cost` in Copilot Cowork to view their credit usage for the current task
• Provides transparency and self-service for users to track Copilot Credit consumption

The introduction now clarifies that Microsoft's Customer Copyright Commitment applies to OpenAI models used within products covered by that commitment, such as Microsoft 365 Copilot and Copilot Studio. This provides important legal assurance for organizations considering these models.

• Added statement that Microsoft's Customer Copyright Commitment applies to OpenAI models in covered products
• Specifically mentions Microsoft 365 Copilot and Copilot Studio as examples

The image generation capability in Copilot Cowork has changed from using Imagen 2 to ChatGPT Images 2.0. This affects which underlying model is used for generating images in chat, which may impact image quality, style, or compliance.

• Image generation model changed from Imagen 2 to ChatGPT Images 2.0

The documentation now specifies the exact minimum version of Microsoft Edge required (Edge 150 Stable 2, Build 150.0.4078.83) for using the local browser with Copilot Cowork, providing clearer guidance for users and admins.

• Added explicit minimum Edge version required for browser tasks
• Clarified that Cowork will guide users to update if Edge is outdated
• Improved reference to more information for non-Edge browsers

The documentation now clarifies that Copilot Cowork uses ChatGPT Images 2.0 for image generation instead of Imagen 2, and softens the language about Anthropic Claude models from a definite to a possible subprocessor.

• Replaces 'Imagen 2' with 'ChatGPT Images 2.0' as the image generation model
• Changes language from 'uses Anthropic Claude models' to 'can use Anthropic Claude models'

The introduction now clarifies that Work IQ MCP uses Microsoft Entra authentication and enforces tenant policy controls, blocking mutation operations by default unless enabled by administrators. This provides important context for security and access management.

• Added explanation of Microsoft Entra authentication usage
• Clarified that Microsoft 365 permissions are used for Graph access
• Described tenant policy layer blocking mutations by default

Page removed or relocated. The documentation page explaining how to rewrite text with Copilot in Word has been removed. It is unclear if this indicates feature deprecation or a restructuring of documentation, but users now lack official guidance on this specific Copilot capability.

• Loss of instructions for rewriting text with Copilot in Word
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. Documentation for generating images with Copilot in Word has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page covering image generation with Copilot in Word is no longer available
• Uncertainty whether feature is deprecated or documentation was moved

Page removed or relocated. The documentation page explaining how to draft and add content with Copilot in Word has been removed. It is unclear if this indicates feature deprecation or a documentation restructure, but users now lack official guidance on using Copilot for content creation in Word.

• Loss of official instructions for drafting and adding content with Copilot in Word
• Uncertainty whether the feature is deprecated or documentation was relocated

Page removed or relocated. The documentation page explaining how to use Copilot in Word to create a summary of a document has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but guidance for this specific Copilot capability is now missing.

• Instructions for generating document summaries with Copilot in Word are no longer available
• Potential loss of user guidance for a key Copilot feature

Page removed or relocated. The documentation page for using Copilot in Word on mobile devices has been removed. It is unclear whether this indicates deprecation of the feature or a relocation of the documentation, but users now lack official guidance on Copilot's mobile Word capabilities.

• Official documentation for Copilot in Word on mobile devices is no longer available
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page for using Copilot in PowerPoint on mobile devices has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on Copilot's mobile PowerPoint capabilities.

• Official documentation for Copilot in PowerPoint on mobile devices is no longer available
• Uncertainty whether this signals feature removal or just a documentation move

Page removed or relocated. The FAQ page for the Office Agent in Copilot for Office Frontier has been removed. This means users no longer have access to official answers to common questions about this capability, which could impact understanding and troubleshooting unless the content has been relocated.

• FAQ documentation for Copilot Office Agent is no longer available
• Potential loss of guidance on common issues and usage scenarios

Page removed or relocated. The documentation page for visualizing data with Copilot in Excel has been removed. It is unclear whether this indicates feature deprecation or a restructuring of documentation, but users now lack official guidance on using Copilot for data visualization in Excel.

• Official documentation for using Copilot to visualize data in Excel is no longer available
• Uncertainty remains whether the feature is deprecated or the documentation was relocated

Page removed or relocated. Documentation for importing data from the web and internal sources into Excel using Copilot is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users lose official guidance on this capability.

• Page covering Copilot-assisted data import into Excel is no longer available
• Uncertainty whether the feature is deprecated or documentation was relocated

Page removed or relocated. The documentation page for Copilot in Excel skills is no longer available. It is unclear if this indicates deprecation of the feature or a relocation of the documentation, but users now lack direct access to information about Copilot's capabilities in Excel.

• Copilot in Excel skills documentation is missing
• Uncertainty whether this is due to deprecation or restructuring

Page removed or relocated. Documentation for Copilot in Excel and Power BI is no longer available at this URL. It is unclear whether the feature has been deprecated or if the documentation has been moved or consolidated elsewhere.

• Copilot in Excel and Power BI documentation is missing
• Potential loss of guidance on using Copilot features in these products

Page removed or relocated. The documentation page for Copilot in Excel (Microsoft Skills) has been removed. It is unclear if this indicates deprecation of the feature or a restructuring of documentation, but users now lack direct guidance on Copilot's Excel integration and capabilities.

• Copilot in Excel (Microsoft Skills) documentation is no longer available at this URL
• Uncertainty whether this reflects feature removal or documentation reorganization

Page removed or relocated. Documentation about Copilot in Excel data sources is now missing. It is unclear if this reflects a feature deprecation or a restructuring of the documentation, but users now lack official guidance on how Copilot in Excel interacts with data sources.

• Page covering Copilot in Excel data sources has been removed
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. Documentation for using Copilot in the SharePoint rich text editor is now missing. It is unclear if this reflects a feature deprecation, a move, or a restructure, but users now lack official guidance on this capability.

• Loss of documentation on Copilot integration with SharePoint's rich text editor
• Uncertainty whether feature is deprecated or documentation was relocated

Page removed or relocated. The documentation page for creating pages with AI in SharePoint is no longer available. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this Copilot capability.

• Official documentation for AI-powered page creation in SharePoint is missing
• Uncertainty whether the feature is deprecated or the content was relocated

Page removed or relocated. The documentation page for generating images with Copilot in Word has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page detailing how to generate images in Word with Copilot is no longer available
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page for drafting and adding content with Copilot in Word has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on using Copilot for content creation in Word.

• Page explaining how to draft and add content with Copilot in Word is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page explaining how to use Copilot in Word to create a summary of your document has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Loss of instructions for generating document summaries with Copilot in Word
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for using Copilot in Word on mobile devices has been removed. It is unclear whether this reflects a deprecation of the feature or a relocation/restructuring of the documentation, but users now lack official guidance on Copilot capabilities in Word for mobile.

• Official documentation for Copilot in Word on mobile devices is no longer available
• Uncertainty whether this is due to feature deprecation or documentation restructuring

Page removed or relocated. The FAQ page for Copilot in PowerPoint has been removed. This means users no longer have access to a centralized set of frequently asked questions and answers about Copilot's features and usage in PowerPoint, which could impact their ability to quickly resolve common issues or understand capabilities. It is unclear if this information has been relocated or consolidated elsewhere.

• FAQ documentation for Copilot in PowerPoint is no longer available
• Potential loss of quick reference for common user questions and troubleshooting

Page removed or relocated. The documentation page for using Copilot in PowerPoint on mobile devices has been removed. It is unclear whether this indicates a deprecation of the feature or a relocation of the documentation, but users now lack official guidance on Copilot capabilities in PowerPoint for mobile.

• Official documentation for Copilot in PowerPoint on mobile devices is no longer available
• Uncertainty whether the feature is deprecated or the documentation has moved

Page removed or relocated. The documentation page for 'Chat with Copilot in Outlook' has been removed. It is unclear whether this indicates feature deprecation or a restructuring/relocation of the documentation. Users now lack official guidance on using Copilot's chat capabilities within Outlook.

• Documentation for using Copilot's chat feature in Outlook is no longer available
• Uncertainty whether the feature is deprecated or the documentation has moved

Page removed or relocated. The documentation page for visualizing data with Copilot in Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack official guidance on using Copilot for data visualization in Excel.

• Documentation for Copilot's data visualization capabilities in Excel is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. Documentation for importing data from the web and internal sources into Excel using Copilot is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page covering data import with Copilot in Excel is no longer available
• Uncertainty whether the feature is deprecated or documentation was moved

Page removed or relocated. Documentation for using Copilot in Excel to import data from another Excel file is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page explaining how to import data from another Excel file using Copilot is no longer available
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page for getting started with Copilot in Excel has been removed. It is unclear if this indicates deprecation of the feature or a relocation of the documentation, but users now lack official guidance on how to begin using Copilot in Excel.

• Removal of 'Get started with Copilot in Excel' guidance
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. The documentation page for using Copilot to gain data insights in Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack official guidance on this capability.

• Page on 'Data insights with Copilot in Excel' is no longer available
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. The documentation page detailing Copilot's skills in Excel has been removed. It is unclear whether this indicates a deprecation of features or a restructuring of documentation, but users now lack direct reference material for Copilot's Excel-specific capabilities.

• Loss of documentation outlining Copilot's skills in Excel
• Uncertainty whether features are deprecated or documentation is relocated

Page removed or relocated. The documentation page for Copilot in Excel and Power BI is no longer available. It is unclear whether this indicates a deprecation of the feature or a relocation of the documentation, but users now lack official guidance on using Copilot with Excel and Power BI.

• Documentation for Copilot integration with Excel and Power BI is missing
• Uncertainty whether this is due to deprecation or restructuring

Page removed or relocated. The documentation page for Copilot in Excel (Microsoft Skills) has been removed. It is unclear if this reflects a deprecation of the feature or a restructuring of documentation, but users now lack official guidance on this capability.

• Copilot in Excel (Microsoft Skills) documentation is no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. Documentation about Copilot in Excel data sources is now missing. It is unclear if this is due to deprecation, relocation, or restructuring, but users now lack official guidance on how Copilot in Excel interacts with data sources.

• Page covering Copilot in Excel data sources has been removed
• Uncertainty whether this reflects a feature deprecation or documentation reorganization

Page removed or relocated. Documentation for using Copilot in the SharePoint rich text editor is no longer available at this URL. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Official instructions for using Copilot in SharePoint's rich text editor are missing
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page for creating pages with AI in SharePoint is no longer available. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this Copilot capability.

• Official documentation for using AI to create pages in SharePoint is missing
• Uncertainty whether the feature is deprecated or the content was relocated

Page removed or relocated. The documentation page for generating images with Copilot in Word has been removed. It is unclear whether this indicates feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page describing how to generate images with Copilot in Word is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page explaining how to draft and add content with Copilot in Word has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on using Copilot for content creation in Word.

• Loss of instructions for drafting and adding content with Copilot in Word
• Uncertainty whether this signals feature removal or documentation reorganization

Page removed or relocated. The documentation page explaining how to use Copilot in Word to create a summary of a document has been removed. It is unclear if this indicates feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Official instructions for generating document summaries with Copilot in Word are no longer available
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page for using Copilot in Word on mobile devices has been removed. It is unclear whether this indicates deprecation of the feature or a relocation of the documentation, but users now lack official guidance on Copilot's mobile Word capabilities.

• Official documentation for Copilot in Word on mobile devices is no longer available
• Uncertainty whether the feature is deprecated or the content has been moved

Page removed or relocated. The documentation page for using Copilot in PowerPoint on mobile devices has been removed. It is unclear whether this indicates a deprecation of the feature or a restructuring of documentation, but information about Copilot's mobile capabilities in PowerPoint is now missing.

• Loss of guidance for Copilot in PowerPoint on mobile devices
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. The documentation page for 'Chat with Copilot in Outlook' has been removed. It is unclear whether this indicates feature deprecation or a restructuring/relocation of the documentation, but users now lack official guidance on using Copilot's chat capabilities within Outlook.

• Loss of documentation for Copilot chat functionality in Outlook
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. The documentation page explaining how to use Copilot in Excel to import data from the web and internal sources is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Loss of instructions for importing data from web/internal sources using Copilot in Excel
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page for using Copilot to gain data insights in Excel has been removed. It is unclear if this reflects a deprecation of the feature or a restructuring of documentation, but guidance on this specific Copilot capability is now missing.

• Page detailing how to use Copilot for data insights in Excel is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page detailing Copilot skills in Excel has been removed. It is unclear whether this reflects a deprecation of features or a restructuring of documentation, but users now lack direct reference material for Copilot's Excel-specific capabilities.

• Loss of documentation outlining Copilot's skills in Excel
• Uncertainty whether features are deprecated or documentation is relocated

Page removed or relocated. Documentation for Copilot integration between Excel and Power BI is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users lose access to guidance on this integration.

• Copilot in Excel and Power BI integration documentation removed
• Uncertainty whether feature is deprecated or documentation was relocated

Page removed or relocated. The documentation page about Copilot in Excel personalization is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on personalizing Copilot in Excel.

• Loss of documentation on how to personalize Copilot in Excel
• Uncertainty whether the feature is deprecated or the content was moved

Page removed or relocated. The documentation page for Copilot in Excel (Microsoft Skills) has been removed. It is unclear if this reflects a deprecation of the feature or a restructuring of documentation, but users now lack official guidance on this capability.

• Copilot in Excel (Microsoft Skills) documentation is no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. Documentation about Copilot in Excel data sources is now missing. It is unclear if this reflects a feature deprecation or a restructuring of the documentation, but users now lack official guidance on how Copilot in Excel interacts with data sources.

• Page covering Copilot in Excel data sources is no longer available
• Potential loss of information on supported data sources, configuration, or limitations

Page removed or relocated. Documentation for using Copilot to write in the SharePoint rich text editor is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page describing Copilot integration with SharePoint rich text editor is no longer available
• Uncertainty whether the feature is deprecated or documentation was relocated

Page removed or relocated. The documentation page for creating pages with AI in SharePoint is no longer available. It is unclear whether this reflects a deprecation of the feature or a relocation of the documentation, but users now lack official guidance on using AI to create SharePoint pages.

• Documentation for AI-powered page creation in SharePoint is missing
• Uncertainty whether feature is deprecated or documentation is moved

Page removed or relocated. The documentation page for drafting and adding content with Copilot in Word has been removed. This means users no longer have access to official guidance on how to use Copilot's content generation features in Word, though it is unclear if the feature itself is deprecated or if the documentation was relocated.

• Loss of official instructions for using Copilot to draft and add content in Word
• Uncertainty about whether the feature is deprecated or documentation is reorganized

Page removed or relocated. The documentation page explaining how to use Copilot in Word to create a summary of your document has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Guidance for generating document summaries with Copilot in Word is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for using Copilot in Word on mobile devices has been removed. It is unclear if this indicates deprecation of the feature or a relocation of the documentation, but users now lack official guidance on Copilot's mobile Word capabilities.

• Loss of official documentation for Copilot in Word on mobile devices
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. Documentation for using Copilot in PowerPoint on mobile devices is no longer available at this URL. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack official guidance for Copilot's mobile PowerPoint capabilities.

• Loss of documentation specific to Copilot in PowerPoint for mobile devices
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page for 'Chat with Copilot in Outlook' has been removed. It is unclear if this indicates feature deprecation or a restructuring/relocation of the documentation, but users now lack official guidance on using Copilot's chat capabilities within Outlook.

• Loss of documentation for using Copilot chat in Outlook
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. The documentation page for visualizing data with Copilot in Excel has been removed. It is unclear whether this indicates feature deprecation or a restructuring of documentation, but users now lack official guidance on using Copilot for data visualization in Excel.

• Official documentation for using Copilot to visualize data in Excel is no longer available
• Uncertainty remains whether the feature is deprecated or the content has been relocated

Page removed or relocated. The documentation page for importing data from the web and internal sources with Copilot in Excel has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page covering data import with Copilot in Excel is no longer available
• Uncertainty whether feature is deprecated or documentation was moved

Page removed or relocated. The documentation page for getting started with Copilot in Excel has been removed. It is unclear if this indicates deprecation of the feature or a relocation of the documentation, but users now lack official guidance on initial setup and use of Copilot in Excel.

• Removal of official 'getting started' instructions for Copilot in Excel
• Potential loss of onboarding and setup guidance for new users

Page removed or relocated. Documentation for Copilot integration between Excel and Power BI has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack official guidance on this integration.

• Loss of documentation on Copilot capabilities spanning Excel and Power BI
• Uncertainty whether the feature is deprecated or the content was relocated

Page removed or relocated. The documentation page for Copilot in Excel (Microsoft Skills) has been removed. It is unclear if this reflects a deprecation of the feature or a restructuring of documentation, but users now lack direct guidance on this capability.

• Copilot in Excel (Microsoft Skills) documentation is no longer accessible
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. Documentation about Copilot in Excel data sources is now missing. It is unclear if this reflects a feature deprecation or a relocation/restructure of the content, but users lose access to guidance on how Copilot interacts with data sources in Excel.

• Page covering Copilot in Excel data sources is no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. Documentation for using Copilot in the SharePoint rich text editor has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Guidance for using Copilot in SharePoint's rich text editor is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for creating pages with AI in SharePoint is no longer available. It is unclear whether this indicates feature deprecation or a restructuring of documentation, but users now lack official guidance on this Copilot capability.

• Official documentation for AI-powered page creation in SharePoint is missing
• Uncertainty whether the feature is deprecated or the content was moved

Page removed or relocated. The documentation page for generating images with Copilot in Word has been removed. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page detailing how to generate images for documents with Copilot in Word is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for drafting and adding content with Copilot in Word has been removed. It is unclear if this indicates feature deprecation or a restructuring of documentation, but users now lack official guidance on using Copilot for content creation in Word.

• Page explaining how to draft and add content with Copilot in Word is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page explaining how to use Copilot in Word to create a summary of your document has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Guidance for generating document summaries with Copilot in Word is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for using Copilot in Word on mobile devices has been removed. It is unclear whether this indicates a feature deprecation or a restructuring of documentation, but users now lack official guidance on Copilot's mobile Word capabilities.

• Official documentation for Copilot in Word on mobile devices is no longer available
• Uncertainty whether this reflects feature removal or documentation reorganization

Page removed or relocated. The documentation page for using Copilot in PowerPoint on mobile devices has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but information about Copilot's mobile capabilities is now missing.

• Page detailing Copilot in PowerPoint for mobile devices is no longer available
• Uncertainty whether this signals feature removal or documentation reorganization

Page removed or relocated. The documentation page for 'Chat with Copilot in Outlook' has been removed. It is unclear if this indicates feature deprecation or a restructuring of documentation, but users now lack official guidance on using Copilot's chat capabilities within Outlook.

• Loss of documentation for Copilot chat features in Outlook
• Uncertainty whether the feature is deprecated or the content was relocated

Page removed or relocated. The FAQ page for the Office Agent in Copilot is no longer available. This removes a resource that addressed common questions about the Office Agent's features, usage, and troubleshooting, which may impact users seeking self-service information.

• FAQ documentation for Copilot Office Agent is missing
• Users lose access to self-help and troubleshooting guidance

Page removed or relocated. Documentation for using Copilot in Excel to import data from the web and internal sources is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users lose guidance on this specific capability.

• Page detailing how to import data from web/internal sources with Copilot in Excel is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page for using Copilot to gain data insights in Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack official guidance on this capability.

• Page detailing Copilot's data insights features in Excel is no longer available
• Uncertainty whether the feature is deprecated or documentation is relocated

Page removed or relocated. Documentation for Copilot in Excel rules is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users lose access to guidance on this capability.

• Page covering Copilot in Excel rules has been removed
• Uncertainty whether this is a deprecation or a documentation move

Page removed or relocated. The documentation page for Copilot in Excel (Microsoft Skills) has been removed. It is unclear whether this indicates a deprecation of the feature or a relocation/restructuring of the documentation. Users now lack direct access to guidance or information about Copilot's capabilities within Excel under the Microsoft Skills context.

• Entire page on Copilot in Excel (Microsoft Skills) is missing
• Uncertainty whether this is a deprecation or a documentation move

Page removed or relocated. A documentation page about Copilot in Excel data sources has been removed. It is unclear if this indicates a feature deprecation or a restructuring of documentation, but information about how Copilot in Excel interacts with data sources is now missing.

• Documentation for Copilot in Excel data sources is no longer available
• Uncertainty whether this is due to deprecation or doc reorganization

Page removed or relocated. Documentation for using Copilot in the SharePoint rich text editor has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Guidance for using Copilot in SharePoint's rich text editor is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for creating pages with AI in SharePoint is no longer available. It is unclear whether this indicates feature deprecation or a documentation restructure, but users now lack official guidance on using AI to create SharePoint pages.

• Official documentation for AI-powered page creation in SharePoint is missing
• Uncertainty whether the feature is deprecated or the content was moved

Page removed or relocated. The documentation page for generating images with Copilot in Word has been removed. It is unclear whether this indicates deprecation of the feature or a relocation of the documentation, but users now lack official guidance on using Copilot to generate images in Word.

• Page detailing how to generate images with Copilot in Word is no longer available
• Uncertainty whether the feature is deprecated or documentation is moved

Page removed or relocated. The documentation page explaining how to draft and add content with Copilot in Word has been removed. It is unclear whether this indicates feature deprecation or a restructuring of documentation, but users now lack official guidance on this capability.

• Loss of instructions for drafting and adding content with Copilot in Word
• Uncertainty whether the feature is deprecated or documentation is relocated

Page removed or relocated. The documentation page explaining how to use Copilot in Word to create a summary of your document has been removed. It is unclear if this indicates feature deprecation or a documentation restructure, but users now lack official guidance on this Copilot capability.

• Loss of instructions for generating document summaries with Copilot in Word
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for using Copilot in Word on mobile devices has been removed. It is unclear whether this indicates a deprecation of the feature or a relocation of the documentation, but users now lack official guidance on Copilot's mobile Word capabilities.

• Official documentation for Copilot in Word on mobile devices is no longer available
• Uncertainty whether this reflects feature removal or documentation restructuring

Page removed or relocated. The FAQ page for Copilot in PowerPoint has been removed, resulting in the loss of documentation that addressed common questions about Copilot's features and usage in PowerPoint. It is unclear whether this indicates a deprecation, relocation, or restructuring of the content.

• FAQ content for Copilot in PowerPoint is no longer available at this URL
• Users lose access to answers about Copilot's capabilities, limitations, and troubleshooting in PowerPoint

Page removed or relocated. The documentation page for using Copilot in PowerPoint on mobile devices has been removed. It is unclear whether this indicates a deprecation of the feature or a relocation of the documentation, but users now lack official guidance on Copilot's mobile PowerPoint capabilities.

• Official documentation for Copilot in PowerPoint on mobile devices is no longer available
• Uncertainty whether the feature is deprecated or the documentation has moved

Page removed or relocated. The documentation page for 'Chat with Copilot in Outlook' has been removed. It is unclear whether this indicates feature deprecation or a restructuring/relocation of the documentation. Users now lack official guidance on how to use Copilot's chat capabilities within Outlook.

• Loss of documentation for using Copilot chat in Outlook
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. The documentation page for visualizing data with Copilot in Excel has been removed. It is unclear whether this indicates feature deprecation or a restructuring of documentation, but users now lack official guidance on using Copilot for data visualization in Excel.

• Official documentation for using Copilot to visualize data in Excel is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page explaining how to use Copilot in Excel to import data from the web and internal sources is no longer available. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Guidance on importing data from web/internal sources with Copilot in Excel is missing
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page explaining how to use Copilot in Excel to import data from another Excel file is now missing. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page detailing Copilot-assisted data import between Excel files is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for getting started with Copilot in Excel has been removed. It is unclear if this indicates deprecation of the feature or a relocation of the documentation, but users now lack official guidance on how to begin using Copilot in Excel.

• Removal of official 'getting started' instructions for Copilot in Excel
• Potential gap in onboarding information for new users

Page removed or relocated. The documentation page for using Copilot in Excel to gain data insights has been removed. It is unclear whether this indicates a deprecation of the feature or a relocation of the documentation, but users now lack official guidance on this capability.

• Documentation for Copilot's data insights features in Excel is no longer available
• Uncertainty whether this is due to deprecation or restructuring

Page removed or relocated. The documentation page detailing Copilot's skills in Excel has been removed. It is unclear whether this indicates a deprecation of features or a restructuring of documentation, but users now lack direct guidance on Copilot's Excel capabilities.

• Loss of documentation outlining Copilot's skills in Excel
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. Documentation for Copilot in Excel rules is now missing. It is unclear if this is due to feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page on Copilot in Excel rules no longer accessible
• Uncertainty whether feature is deprecated or documentation was moved

Page removed or relocated. Documentation for Copilot integration between Excel and Power BI is now missing. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users lose access to guidance on this integration.

• Page covering Copilot in Excel and Power BI integration is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page about Copilot in Excel personalization is no longer available. It is unclear whether this reflects a feature deprecation, a move, or a consolidation, but users now lack official guidance on personalizing Copilot in Excel.

• Documentation on Copilot in Excel personalization is missing
• Uncertainty whether the feature is deprecated or the content was relocated

Page removed or relocated. The documentation page for Copilot in Excel (Microsoft Skills) has been removed. It is unclear if this indicates deprecation of the feature or a relocation of the documentation, but users now lack official guidance on this capability.

• Loss of documentation for Copilot in Excel (Microsoft Skills)
• Uncertainty whether the feature is deprecated or the doc was moved

Page removed or relocated. The documentation page covering Copilot in Excel data sources is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users currently lack official guidance on how Copilot in Excel interacts with data sources.

• Loss of documentation about Copilot in Excel data sources
• Uncertainty whether this is a deprecation or a relocation

Page removed or relocated. The documentation page explaining how to use Copilot to write in the SharePoint rich text editor has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but guidance for this specific Copilot capability is now missing.

• Loss of instructions for using Copilot in SharePoint's rich text editor
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for creating pages with AI in SharePoint is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on using AI to create SharePoint pages.

• Official documentation for AI-powered page creation in SharePoint is missing
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page 'Welcome to Copilot in Word' has been removed. It is unclear whether this indicates a deprecation of the feature, a relocation of the content, or a restructuring of the documentation. Users may temporarily lose access to introductory or onboarding information about Copilot in Word.

• Removal of the 'Welcome to Copilot in Word' page
• Potential loss of introductory guidance for Copilot in Word

Page removed or relocated. A documentation page introducing Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but introductory information about Copilot's capabilities in PowerPoint is now missing from this location.

• Removal of the 'Welcome to Copilot in PowerPoint' page
• Potential loss of overview or onboarding information for Copilot in PowerPoint

Page removed or relocated. The documentation page explaining how to use Copilot in PowerPoint to summarize presentations has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page describing Copilot's presentation summarization in PowerPoint is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The FAQ page for Copilot in PowerPoint has been removed. It is unclear if this indicates deprecation, relocation, or restructuring of the documentation. Users now lack a centralized resource for common questions about Copilot in PowerPoint.

• FAQ content for Copilot in PowerPoint is no longer available at this URL
• Potential loss of answers to common user questions and troubleshooting guidance

Page removed or relocated. The documentation page explaining how to create a new presentation with Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Step-by-step instructions for creating presentations with Copilot in PowerPoint are no longer available
• Potential gap in user guidance for leveraging Copilot's presentation creation features

Page removed or relocated. A documentation page about Copilot skills in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack direct access to information about Copilot's capabilities in PowerPoint.

• Page detailing Copilot skills in PowerPoint is no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. The documentation page explaining how to add an image to a PowerPoint presentation using Copilot is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Step-by-step instructions for adding images with Copilot in PowerPoint are missing
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page explaining how to add a slide from a file using Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Missing instructions for adding a slide from a file with Copilot in PowerPoint
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for creating a meeting agenda with Copilot in Outlook has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page explaining how to create a meeting agenda with Copilot in Outlook is no longer available
• Uncertainty whether the feature is deprecated or documentation was relocated

Page removed or relocated. The documentation page for 'Chat with Copilot in Outlook' has been removed. It is unclear if this indicates feature deprecation or a restructuring of documentation, but information about using Copilot's chat capabilities within Outlook is now missing.

• Page detailing how to chat with Copilot in Outlook is no longer available
• Uncertainty whether this reflects feature removal or documentation reorganization

Page removed or relocated. The documentation page explaining how to use Copilot in Excel to import data from another Excel file has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Missing instructions for importing data from another Excel file using Copilot
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for getting started with Copilot in Excel has been removed. It is unclear whether this indicates deprecation of the feature or a restructuring of the documentation. Users now lack direct guidance on how to begin using Copilot in Excel.

• Removal of 'Get started with Copilot in Excel' documentation
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. The FAQ page for Copilot in Excel has been removed. It is unclear whether this indicates deprecation, relocation, or restructuring of the documentation, but users now lack a dedicated source for common questions and answers about Copilot in Excel.

• FAQ content for Copilot in Excel is no longer available at this URL
• Potential loss of troubleshooting and usage guidance for Excel Copilot users

Page removed or relocated. The documentation page for using Copilot to gain data insights in Excel has been removed. It is unclear if this reflects a deprecation of the feature or a restructuring of documentation, but users now lack official guidance on this capability.

• Page covering Copilot's data insights features in Excel is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. A documentation page providing tips for using Copilot in Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack direct access to these usage tips.

• Removal of a page dedicated to Copilot in Excel tips
• Potential loss of guidance for effective Copilot usage in Excel

Page removed or relocated. A documentation page about Copilot in Excel rules has been removed. It is unclear if this indicates feature deprecation or a restructuring of documentation, but information about rules for using Copilot in Excel is now missing.

• Documentation for Copilot in Excel rules is no longer available at this URL
• Uncertainty whether this is due to deprecation or doc reorganization

Page removed or relocated. The documentation page for Copilot in Excel personalization is no longer available. It is unclear whether this indicates feature deprecation or a restructuring of documentation, but users now lack official guidance on personalizing Copilot in Excel.

• Copilot in Excel personalization documentation is missing
• Uncertainty if this is due to deprecation or doc reorganization

Page removed or relocated. A documentation page about getting started with editing prompts in Copilot for Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack direct guidance on this topic.

• Page on getting started with editing prompts in Copilot for Excel is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page for refining SharePoint pages with AI is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but information about using AI in SharePoint page refinement is now missing.

• Documentation for AI-powered refinement of SharePoint pages is no longer accessible
• Uncertainty remains whether the feature is deprecated or the content was relocated

Page removed or relocated. The documentation page 'Welcome to Copilot in Word' has been removed. It is unclear whether this indicates a deprecation of the feature, a relocation of the content, or a restructuring of the documentation. Users may temporarily lose access to introductory or onboarding information about Copilot in Word.

• Removal of introductory documentation for Copilot in Word
• Potential loss of onboarding or overview information for new users

Page removed or relocated. The documentation page explaining how to rewrite text with Copilot in Word has been removed. It is unclear if this indicates feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page detailing how to use Copilot to rewrite text in Word is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The introductory documentation page for Copilot in PowerPoint has been removed. It is unclear if this indicates deprecation, relocation, or restructuring of the documentation, but users now lack a central overview or welcome guide for Copilot in PowerPoint.

• Removal of the welcome/overview page for Copilot in PowerPoint
• Potential loss of introductory guidance for new users

Page removed or relocated. The documentation page for summarizing presentations with Copilot in PowerPoint has been removed. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page detailing how to summarize presentations with Copilot in PowerPoint is no longer available
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page explaining how to create a new presentation with Copilot in PowerPoint has been removed. It is unclear if this indicates a feature deprecation or a restructuring of documentation, but users now lack direct guidance on this capability.

• Step-by-step instructions for creating presentations with Copilot in PowerPoint are no longer available
• Potential loss of onboarding or usage guidance for new Copilot users in PowerPoint

Page removed or relocated. A documentation page about Copilot in PowerPoint skills has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but information about Copilot's capabilities in PowerPoint is now missing from this location.

• Page covering Copilot skills in PowerPoint is no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. The documentation page explaining how to add an image to a PowerPoint presentation using Copilot is no longer available. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance for this specific Copilot capability.

• Step-by-step instructions for adding images with Copilot in PowerPoint are missing
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page explaining how to add a slide from a file using Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Guidance for adding a slide from a file with Copilot in PowerPoint is no longer available
• Uncertainty remains whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page explaining how to create a meeting agenda with Copilot in Outlook has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page detailing Copilot's meeting agenda creation in Outlook is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The FAQ page for the Office Agent (Copilot for Office Frontier) is no longer available. It is unclear whether this indicates a deprecation of the feature or a relocation of the documentation, but users now lack access to official answers to common questions about this capability.

• FAQ documentation for Copilot Office Agent is missing
• Potential loss of guidance on usage, troubleshooting, or feature details

Page removed or relocated. The FAQ page for Copilot in Excel has been removed. It is unclear if this indicates feature deprecation or a documentation restructure, but users now lack a dedicated resource for common questions about Copilot in Excel.

• FAQ content for Copilot in Excel is no longer available at this URL
• Potential loss of answers to common user questions and troubleshooting guidance

Page removed or relocated. A page providing tips for using Copilot in Excel has been removed. It is unclear if this reflects a deprecation of features, a relocation of content, or a documentation restructure, but users now lack access to these specific tips.

• Removal of Copilot in Excel tips documentation
• Potential loss of guidance for effective Copilot use in Excel

Page removed or relocated. The documentation page for Copilot in Excel rules is no longer available. It is unclear whether this indicates a feature deprecation or a relocation/restructuring of the content, but users currently lack official guidance on Copilot rules in Excel.

• Copilot in Excel rules documentation is missing
• Uncertainty whether the feature is deprecated or the content was moved

Page removed or relocated. The documentation page about Copilot in Excel personalization is no longer available. It is unclear if this reflects a deprecation of the feature or a restructuring of the documentation, but information about personalizing Copilot in Excel is now missing.

• Page covering Copilot in Excel personalization has been removed
• Uncertainty whether this is due to feature deprecation or documentation reorganization

Page removed or relocated. A documentation page about getting started with editing prompts in Copilot for Excel has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack direct guidance on this topic.

• Page on getting started with editing prompts in Copilot for Excel is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page about refining SharePoint pages with AI is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but information about using AI in SharePoint page refinement is now missing.

• Page describing AI-powered refinement of SharePoint pages has been removed
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page 'Welcome to Copilot in Word' has been removed. It is unclear whether this indicates a deprecation of the feature, a relocation of the content, or a restructuring of the documentation. Users may temporarily lose access to introductory or onboarding information about Copilot in Word.

• Removal of the 'Welcome to Copilot in Word' page
• Potential loss of introductory guidance for Copilot in Word

Page removed or relocated. The documentation page explaining how to rewrite text with Copilot in Word has been removed. It is unclear whether this indicates a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page detailing how to use Copilot to rewrite text in Word is no longer available
• Uncertainty whether the feature is deprecated or documentation was relocated

Page removed or relocated. The documentation page 'Welcome to Copilot in PowerPoint' has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but introductory or onboarding information for Copilot in PowerPoint is now missing from this location.

• Removal of introductory or overview content for Copilot in PowerPoint
• Potential loss of onboarding guidance for new users

Page removed or relocated. The documentation page for summarizing presentations with Copilot in PowerPoint has been removed. It is unclear whether this indicates feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Official instructions for using Copilot to summarize PowerPoint presentations are no longer available
• Uncertainty whether the feature is deprecated or the documentation has been relocated

Page removed or relocated. The FAQ page for Copilot in PowerPoint has been removed. It is unclear whether this indicates deprecation, relocation, or restructuring of the documentation. Users now lack a centralized resource for common questions about Copilot in PowerPoint.

• FAQ content for Copilot in PowerPoint is no longer available at this URL
• Potential loss of quick-reference answers for users

Page removed or relocated. The documentation page explaining how to create a new presentation with Copilot in PowerPoint has been removed. It is unclear if this indicates a feature deprecation or a restructuring of documentation, but users now lack direct guidance on this capability.

• Step-by-step instructions for creating presentations with Copilot in PowerPoint are no longer available
• Potential loss of onboarding or feature discovery information for new users

Page removed or relocated. A documentation page about Copilot skills in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack direct access to information about Copilot's capabilities in PowerPoint.

• Page detailing Copilot skills in PowerPoint is no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. The documentation page explaining how to add an image to a PowerPoint presentation using Copilot is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page detailing how to add images to PowerPoint with Copilot has been removed
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page explaining how to add a slide from a file using Copilot in PowerPoint has been removed. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page detailing how to add a slide from a file with Copilot in PowerPoint is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for creating a meeting agenda with Copilot in Outlook has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page detailing how to create a meeting agenda with Copilot in Outlook is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The FAQ page for the Office Agent in Copilot for Office Frontier has been removed. It is unclear whether this indicates a deprecation of the feature, a relocation of the documentation, or a restructuring of content. Users now lack direct access to frequently asked questions about the Office Agent capability.

• FAQ documentation for Office Agent is no longer available at this URL
• Uncertainty whether the feature is deprecated or the content has moved

Page removed or relocated. The documentation page for visualizing data with Copilot in Excel has been removed. It is unclear whether this indicates feature deprecation or a restructuring of documentation, but users now lack direct guidance on using Copilot for data visualization in Excel.

• Page explaining how to visualize data with Copilot in Excel is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page explaining how to use Copilot in Excel to import data from another Excel file has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Guidance for importing data from another Excel file with Copilot is no longer available
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page for getting started with Copilot in Excel has been removed. It is unclear if this indicates a deprecation of the feature or a restructuring of the documentation, but users now lack direct guidance on how to begin using Copilot in Excel.

• Removal of introductory/getting started guidance for Copilot in Excel
• Potential loss of onboarding information for new users

Page removed or relocated. The FAQ page for Copilot in Excel has been removed. It is unclear whether the content has been relocated, consolidated, or deprecated, but users now lack direct access to frequently asked questions and answers about Copilot in Excel.

• FAQ documentation for Copilot in Excel is no longer available at this URL
• Potential loss of quick reference for common Copilot in Excel questions

Page removed or relocated. A page offering tips for using Copilot in Excel has been removed. It is unclear if this content has been relocated, consolidated, or deprecated, but users now lack access to this specific guidance.

• Removal of documentation providing tips for Copilot in Excel
• Potential loss of best practices or usage advice for Excel users

Page removed or relocated. Documentation for Copilot in Excel rules is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users lose access to guidance on this capability.

• Page covering Copilot in Excel rules is no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. A documentation page about getting started with editing prompts in Copilot for Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of the documentation.

• Page covering 'Copilot in Excel: Get started editing prompt' is no longer available
• Potential loss of guidance for users on how to edit prompts in Copilot for Excel

Page removed or relocated. The documentation page describing how to refine SharePoint pages with AI is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but guidance on using AI in SharePoint is now missing.

• Page on refining SharePoint pages with AI has been removed
• Uncertainty whether feature is deprecated or documentation was relocated

Page removed or relocated. The documentation page for rewriting text with Copilot in Word has been removed. It is unclear whether this indicates feature deprecation or a relocation of the documentation, but users now lack official guidance on this specific Copilot capability in Word.

• Page explaining how to rewrite text with Copilot in Word is no longer available
• Uncertainty whether the feature is deprecated or documentation is moved

Page removed or relocated. The documentation page for generating images with Copilot in Word has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page detailing how to generate images for documents with Copilot in Word is no longer available
• Uncertainty whether the feature is deprecated or the documentation has moved

Page removed or relocated. The introductory documentation page for Copilot in PowerPoint has been removed. It is unclear if this indicates a deprecation, relocation, or restructuring of the documentation, but users now lack a central overview or welcome guide for Copilot in PowerPoint.

• Removal of the welcome/overview page for Copilot in PowerPoint
• Potential loss of introductory guidance for new users

Page removed or relocated. The documentation page explaining how to summarize presentations with Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page detailing Copilot's presentation summarization in PowerPoint is no longer available
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The FAQ page for Copilot in PowerPoint has been removed. It is unclear if this indicates deprecation, relocation, or restructuring of the documentation, but users now lack a centralized resource for common questions about Copilot in PowerPoint.

• FAQ content for Copilot in PowerPoint is no longer available at this URL
• Potential loss of answers to common user questions and troubleshooting guidance

Page removed or relocated. The documentation page explaining how to create a new presentation with Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack direct guidance on this capability.

• Step-by-step instructions for creating presentations with Copilot in PowerPoint are no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. A documentation page about Copilot in PowerPoint skills has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but information about Copilot's capabilities in PowerPoint is now missing from this location.

• Page covering Copilot in PowerPoint skills is no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. The documentation page explaining how to add an image to a PowerPoint presentation using Copilot is no longer available. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Step-by-step instructions for adding images with Copilot in PowerPoint are missing
• Potential loss of clarity for users seeking to use Copilot for image insertion

Page removed or relocated. The documentation page explaining how to add a slide from a file using Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Loss of instructions for adding a slide from a file with Copilot in PowerPoint
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for creating a meeting agenda with Copilot in Outlook has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page detailing how to create a meeting agenda with Copilot in Outlook is no longer available
• Uncertainty whether the feature is deprecated or documentation has been relocated

Page removed or relocated. The FAQ page for the Office Copilot agent is no longer available. It is unclear whether this indicates deprecation of the feature or a relocation of the documentation, but users now lack access to commonly asked questions and answers about the Office Copilot agent.

• FAQ documentation for Office Copilot agent is missing
• Potential loss of guidance on common issues and usage

Page removed or relocated. The documentation page explaining how to use Copilot in Excel to import data from another Excel file is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Missing instructions for importing data from another Excel file using Copilot
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The FAQ page for Copilot in Excel has been removed. This means users no longer have access to a centralized set of frequently asked questions and answers about Copilot's features and usage in Excel, but it is unclear if this is due to deprecation or documentation restructuring.

• Loss of a dedicated FAQ resource for Copilot in Excel
• Potential gap in user self-service support and clarification

Page removed or relocated. The documentation page for using Copilot to gain data insights in Excel has been removed. It is unclear whether this indicates a feature deprecation or a restructuring of documentation, but users now lack official guidance on this capability.

• Page on data insights with Copilot in Excel is no longer available
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. A documentation page providing tips for using Copilot in Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack access to these specific usage tips.

• Removal of Copilot in Excel tips documentation
• Potential loss of guidance for effective Copilot use in Excel

Page removed or relocated. A documentation page about Copilot in Excel skills has been removed. It is unclear if this reflects a deprecation, a move, or a consolidation of content, but readers now lack direct access to this information.

• Page detailing Copilot in Excel skills is no longer available
• Uncertainty whether this is due to deprecation or restructuring

Page removed or relocated. A documentation page about Copilot in Excel rules is now missing. It is unclear if this indicates feature deprecation or a documentation restructure, but users now lack guidance on rules for Copilot in Excel.

• Page on Copilot in Excel rules no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. The documentation page about Copilot in Excel personalization is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but information about personalizing Copilot in Excel is now missing.

• Page covering Copilot in Excel personalization has been removed
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. A documentation page about getting started with editing prompts in Copilot for Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack direct guidance on this topic.

• Page on 'getting started with editing prompts' in Copilot for Excel is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page about refining SharePoint pages with AI is now missing. It is unclear if this indicates a feature deprecation or a relocation of the documentation, but users currently lack official guidance on using AI capabilities in SharePoint for page refinement.

• Documentation for AI-powered refinement of SharePoint pages is no longer accessible
• Uncertainty whether the feature is deprecated or the content has been moved

Page removed or relocated. The documentation page introducing Copilot in Word is no longer available at this URL. It is unclear whether the feature has been deprecated or if the documentation has been moved or consolidated elsewhere.

• Removal of introductory information about Copilot in Word
• Potential loss of onboarding or overview content for new users

Page removed or relocated. Documentation for using Copilot to rewrite text in Word is now missing. It is unclear if this reflects a feature deprecation or a documentation restructure, but users currently lack official guidance on this capability.

• Page explaining how to rewrite text with Copilot in Word is no longer available
• Uncertainty whether the feature is deprecated or documentation has moved

Page removed or relocated. The introductory documentation page for Copilot in PowerPoint has been removed. It is unclear if this reflects a deprecation, a move, or a restructuring of the documentation. Users may temporarily lose access to basic onboarding or overview information for Copilot in PowerPoint.

• Removal of the welcome/introductory page for Copilot in PowerPoint
• Potential loss of onboarding or overview guidance for new users

Page removed or relocated. The documentation page explaining how to use Copilot in PowerPoint to summarize presentations has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page detailing Copilot's presentation summarization in PowerPoint is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The FAQ page for Copilot in PowerPoint has been removed. It is unclear if this indicates deprecation, relocation, or restructuring of the documentation. Users now lack a centralized resource for common questions about Copilot in PowerPoint.

• FAQ content for Copilot in PowerPoint is no longer available at this URL
• Potential loss of answers to common user questions and troubleshooting guidance

Page removed or relocated. The documentation page explaining how to create a new presentation with Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Step-by-step instructions for creating presentations with Copilot in PowerPoint are no longer available
• Potential loss of clarity for users seeking to leverage Copilot for new presentations

Page removed or relocated. A documentation page about Copilot in PowerPoint skills has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but information about Copilot's capabilities in PowerPoint is now missing from this location.

• Documentation for Copilot in PowerPoint skills is no longer available at this URL
• Uncertainty whether this is due to deprecation or doc reorganization

Page removed or relocated. The documentation page explaining how to add an image to a PowerPoint presentation using Copilot is no longer available. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Step-by-step instructions for adding images with Copilot in PowerPoint are missing
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page explaining how to add a slide from a file using Copilot in PowerPoint has been removed. It is unclear whether this indicates feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page detailing how to add a slide from a file with Copilot in PowerPoint is no longer available
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The documentation page for creating a meeting agenda with Copilot in Outlook has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page explaining how to create a meeting agenda with Copilot in Outlook is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for visualizing data with Copilot in Excel has been removed. It is unclear whether this indicates feature deprecation or a restructuring of documentation, but users now lack direct guidance on using Copilot for data visualization in Excel.

• Page on visualizing data with Copilot in Excel is no longer available
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. The documentation page explaining how to use Copilot in Excel to import data from another Excel file has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Missing instructions for importing data from another Excel file using Copilot
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for getting started with Copilot in Excel has been removed. It is unclear if this indicates deprecation of the feature or a restructuring of the documentation. Users now lack a dedicated guide for initial setup and use of Copilot in Excel.

• Removal of the 'Get started with Copilot in Excel' guide
• Uncertainty whether feature is deprecated or documentation is relocated

Page removed or relocated. The FAQ page for Copilot in Excel has been removed. It is unclear if this indicates deprecation, relocation, or restructuring of the documentation, but users now lack a centralized resource for common questions about Copilot in Excel.

• FAQ content for Copilot in Excel is no longer available at this URL
• Potential loss of answers to common user questions and troubleshooting guidance

Page removed or relocated. A documentation page offering tips for using Copilot in Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack direct access to these usage tips.

• Removal of Copilot in Excel tips documentation
• Potential loss of guidance for effective Copilot usage in Excel

Page removed or relocated. A documentation page about Copilot in Excel skills has been removed. It is unclear if this reflects a deprecation, relocation, or restructuring of the content, but users now lack direct access to this information at the previous URL.

• Documentation for Copilot in Excel skills is no longer available at this location
• Uncertainty remains whether the feature is deprecated or the content has moved

Page removed or relocated. The documentation page for Copilot in Excel and Power BI is no longer available at this URL. It is unclear if the content has been deprecated, relocated, or consolidated elsewhere, but users currently lack access to guidance on Copilot capabilities in these products from this page.

• Documentation for Copilot in Excel and Power BI is missing
• Uncertainty whether this reflects deprecation or restructuring

Page removed or relocated. The documentation page about Copilot in Excel personalization is no longer available. It is unclear if this reflects a feature deprecation or a documentation restructure, but information about personalizing Copilot in Excel is now missing.

• Page covering Copilot in Excel personalization has been removed
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. A documentation page about getting started with editing prompts in Copilot for Excel has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack direct guidance on this topic.

• Page on getting started with editing prompts in Copilot for Excel is no longer available
• Potential loss of onboarding or instructional content for prompt editing

Page removed or relocated. The documentation page describing how to refine SharePoint pages with AI is no longer available. It is unclear whether this reflects a feature deprecation or a restructuring of documentation, but guidance on using AI in SharePoint is now missing.

• Page detailing AI refinement features for SharePoint pages has been removed
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The introductory documentation page for Copilot in Word has been removed. It is unclear if this indicates a deprecation, relocation, or restructuring of the documentation, but users now lack a central overview or welcome guide for Copilot in Word.

• Removal of the welcome/overview page for Copilot in Word
• Potential loss of introductory guidance for new users

Page removed or relocated. The documentation page explaining how to rewrite text with Copilot in Word has been removed. It is unclear whether this indicates feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Loss of instructions for rewriting text with Copilot in Word
• Uncertainty whether the feature is deprecated or documentation was relocated

Page removed or relocated. The introductory documentation page for Copilot in PowerPoint has been removed. It is unclear if this reflects a deprecation, a move, or a restructuring of the documentation, but users now lack a central overview or welcome page for this capability.

• Removal of the main welcome/overview page for Copilot in PowerPoint
• Potential loss of introductory guidance for new users

Page removed or relocated. The documentation page for summarizing presentations with Copilot in PowerPoint has been removed. It is unclear whether this indicates feature deprecation or a documentation restructure, but users now lack official guidance on this capability.

• Page explaining how to summarize presentations with Copilot in PowerPoint is no longer available
• Uncertainty whether the feature is deprecated or documentation was relocated

Page removed or relocated. The documentation page explaining how to create a new presentation with Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a restructuring of documentation, but users now lack direct guidance on this capability.

• Step-by-step instructions for creating new presentations with Copilot in PowerPoint are no longer available
• Potential loss of onboarding or feature discovery information for new users

Page removed or relocated. A documentation page about Copilot in PowerPoint skills is now missing. It is unclear if this indicates feature deprecation or simply a restructuring or relocation of the documentation, but users currently lose access to information about Copilot's capabilities in PowerPoint.

• Documentation for Copilot in PowerPoint skills is no longer available at this URL
• Uncertainty whether this is due to deprecation or documentation reorganization

Page removed or relocated. The documentation page explaining how to add an image to a PowerPoint presentation using Copilot is no longer available. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Step-by-step instructions for adding images with Copilot in PowerPoint are missing
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page explaining how to add a slide from a file using Copilot in PowerPoint has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Guidance for adding a slide from a file with Copilot in PowerPoint is no longer available
• Uncertainty whether the feature is deprecated or the documentation was relocated

Page removed or relocated. The documentation page for creating a meeting agenda with Copilot in Outlook has been removed. It is unclear whether this reflects a feature deprecation or a documentation restructure, but users now lack official guidance on this specific Copilot capability.

• Page detailing how to create a meeting agenda with Copilot in Outlook is no longer available
• Uncertainty whether the feature is deprecated or the documentation was moved

Page removed or relocated. The FAQ page for the Office Copilot Agent is no longer available. It is unclear whether this indicates a deprecation of the feature or a relocation of the documentation, but users now lack access to official answers to common questions about the Office Copilot Agent.

• FAQ content for Office Copilot Agent is missing
• Potential loss of guidance on common issues and usage

Page removed or relocated. The FAQ page for Copilot in Excel has been removed, resulting in the loss of a resource that addressed common user questions. It is unclear if this indicates deprecation, relocation, or restructuring of the documentation.

• FAQ content about Copilot in Excel is no longer available at this URL
• Users lose access to previously documented answers to common questions

Page removed or relocated. A documentation page providing tips for using Copilot in Excel has been removed. It is unclear if this reflects a deprecation, relocation, or restructuring of the content, but users now lack direct access to these usage tips.

• Removal of a page dedicated to Copilot in Excel tips
• Potential loss of guidance for effective Copilot usage in Excel

Page removed or relocated. A documentation page about getting started with editing prompts in Copilot for Excel has been removed. It is unclear if this reflects a feature deprecation or a documentation restructure, but users now lack guidance on this specific aspect.

• Page on 'getting started editing prompts' in Copilot for Excel is no longer available
• Uncertainty whether this is due to feature removal or documentation reorganization

Page removed or relocated. The documentation page about refining SharePoint pages with AI is no longer available. It is unclear whether this reflects a feature deprecation or simply a documentation move or restructure, but information about using AI in SharePoint page refinement is now missing.

• Page describing AI-powered refinement of SharePoint pages is gone
• Uncertainty whether the feature is deprecated or documentation was relocated