Forum Discussion

Diego_GM_Room_Mate's avatar
Diego_GM_Room_Mate
Copper Contributor
Apr 09, 2026

Suggestion: Allow users to customize the UI name of MS Copilot (with “Powered by Microsoft 365”)

Background

Microsoft Copilot is an extremely capable assistant, but its current visual identity is completely fixed (the name “Copilot” is always shown), even though users interact with it daily as a personal or team assistant.

From a user experience perspective, this creates a small but important gap between using a tool and working with an assistant.

Proposal

Allow users to customize the visible name of their Copilot assistant, while maintaining a clear and consistent Microsoft branding indicator, for example:

Holiday (name that the user creates for calling Microsoft Copilot 365 IA) Powered by Microsoft 365 Copilot (Text that Microsoft uses to reflect that it's already Microsoft Copilot).

This proposal does not aim to change the underlying model, security, governance, or responsibility.
It only affects the identity/presentation layer of the assistant.

Why this matters (UX & adoption)

Allowing users to name their assistant creates:

  • Psychological ownership (“my assistant” instead of “the assistant”)
  • Higher trust and willingness to delegate complex tasks
  • Stronger long-term adoption and recurring usage

In daily work, users naturally refer to assistants by name (“Ask Friday to review this document”), which helps integrate Copilot into real workflows instead of keeping it as an external tool.

Enterprise perspective

In organizational environments, a named assistant feels like part of the team rather than a generic external service.
This improves internal communication, clarity, and acceptance of AI-assisted workflows.

Importantly, the “Powered by Microsoft 365 Copilot” label keeps:

  • brand visibility
  • transparency
  • technical and legal responsibility clearly with Microsoft

This follows well-established patterns such as “Powered by Azure” or “Powered by Microsoft Security”.

Strategic fit

Microsoft already enables named and branded assistants through Copilot Studio.
Extending this concept to the core Copilot experience feels like a natural next step with:

  • Low technical risk (presentation-level feature)
  • High UX impact
  • No compromise on governance or brand integrity

Closing

Naming the assistant transforms the relationship from using AI to collaborating with AI.
This small change could have a disproportionally positive effect on trust, adoption, and everyday productivity.

Thanks for considering this feedback.

No RepliesBe the first to reply