4.2 Renaming and Deleting Chats

4.2 Renaming and Deleting Chats

Quick Answer: Both actions live on the ... (more options) menu beside a conversation in the Copilot chat history list. Rename changes the display label only. Delete removes the conversation from your history but does not erase the records retained for enterprise compliance. AB-730 tests the second half of that sentence far more often than the first.

These are deliberately mundane features, and that is precisely why they appear on the blueprint as their own bullets. The exam is checking that you know where the commands are and, more importantly, that you do not mistake a tidy chat list for a cleared data trail.

1. Renaming Chats & Enterprise Taxonomy Best Practices

By default, Microsoft 365 Copilot generates a title based on the first few words of the opening prompt (e.g., "Draft an email", "Summarize document", or "Help with spreadsheet"). In an active enterprise workday, this leads to a sidebar filled with dozens of indistinguishable, unsearchable entries.

+-------------------------------------------------------------------------+
|                        CHAT RENAMING WORKFLOW                           |
+-------------------------------------------------------------------------+
|  1. Locate conversation in sidebar list.                                |
|  2. Click the three-dot ellipsis menu [...] next to the chat title.     |
|  3. Select 'Rename' from the dropdown menu.                             |
|  4. Apply standardized organizational naming convention.                |
|  5. Press Enter or click Checkmark to save.                             |
+-------------------------------------------------------------------------+

Recommended Enterprise Naming Taxonomies

Organizations should train business users to adopt standardized naming schemas for Copilot conversations:

Benefits of Disciplined Renaming

• Instant Context Re-engagement: Team members can return to a complex thread weeks later and immediately understand its scope.
• Audit & Governance Transparency: When reviewing chat history during internal audits or handover sessions, clear titles establish exact provenance.
• Clean Promotion to Notebooks & Pages: When promoting chat outputs into Copilot Pages or Notebooks, the structured title is inherited as the default artifact name.

---

2. Deleting Chats: User Experience vs. Enterprise Purview Governance

A critical domain tested on the AB-730 certification is the distinction between User-Level Deletion in the client interface and Tenant-Level Data Retention enforced by enterprise security policies.

+-------------------------------------------------------------------------+
|                 USER DELETION VS. PURVIEW COMPLIANCE                    |
+-------------------------------------------------------------------------+
|                                                                         |
|  USER ACTION: Click [...] -> 'Delete Chat'                              |
|       │                                                                 |
|       ├──► USER INTERFACE: Thread removed from sidebar immediately      |
|       ├──► LLM WORKING MEMORY: Context window reset to zero             |
|       │                                                                 |
|       ▼                                                                 |
|  ENTERPRISE BACKEND (Microsoft Purview & Substrate Storage):            |
|       │                                                                 |
|       ├──► Copilot Interaction Store (Exchange Online Substrate)        |
|       ├──► Purview Retention Policies (e.g., Retain for 3–7 Years)      |
|       ├──► Litigation / Legal Hold (Preserved for discovery)            |
|       └──► Unified Audit Log (UAL: 'CopilotInteraction' event logged)   |
|                                                                         |
+-------------------------------------------------------------------------+

User-Level Deletion Mechanics

When an individual user clicks the ellipsis menu (...) and selects Delete Chat:

• UI Removal: The conversation thread is immediately deleted from the user's sidebar history.
• Context Flushing: The active conversational state is severed; the LLM will no longer access or reference any tokens from that conversation in future prompts.
• Device Sync: The deletion synchronizes across all client endpoints (Teams, Edge, Web, Mobile).

Backend Enterprise Compliance: Microsoft Purview & Substrate Storage

Many business users mistakenly assume that deleting a chat destroys all traces of the interaction. In enterprise Microsoft 365 tenants, this is not the case:

1. Substrate Data Storage: Copilot interactions—comprising the user's original prompt, the retrieved Microsoft Graph grounding metadata, and the AI-generated response—are stored as compliance records in a hidden folder within the user's Exchange Online mailbox (specifically within the Substrate store under TeamsMessagesData / Copilot interaction storage).
2. Microsoft Purview Retention Policies: Administrators can establish global or group-level retention rules (e.g., "Retain all Copilot interactions for 5 years for financial compliance"). Even if a user deletes the chat five seconds after creation, the compliance copy is retained in the backend until the retention period expires.
3. Litigation Hold & Legal Discovery: If a custodian is placed on a Litigation Hold or eDiscovery Hold, deleted Copilot conversations are preserved in the non-editable Recoverable Items store and can be searched, reviewed, and exported using Microsoft Purview eDiscovery (Standard and Premium).
4. Audit Logging (Unified Audit Log): Every prompt and response generates an immutable audit record in the Microsoft 365 Unified Audit Log under the CopilotInteraction record type, capturing timestamps, user Entra ID, accessed file IDs, and sensitivity labels.

---

Comparison: User Chat Actions vs. Enterprise Compliance State

---