Microsoft 365 Copilot app: Branded footer customization [MC1238432]

Message ID: MC1238432

[Introduction]

We’re introducing a new co-branding capability that will allow organizations to display a branded footer at the bottom of the Chat screen in the Microsoft 365 Copilot app. This update will enable admins to add their organization’s logo to their users’ Microsoft 365 Copilot app, helping users confirm they are using their trusted, work-managed Copilot experience.

This feature will begin rolling out in March 2026 and is expected to complete by late April 2026.

This message is associated with Microsoft 365 Roadmap ID 555852.

[When this will happen]

• General Availability (Worldwide): Rollout will begin in late March 2026 and is expected to complete by late April 2026.

[How this will affect your organization]

Who is affected

• All Microsoft 365 tenants using the Microsoft 365 Copilot app.

What will happen

• Admins will be able to upload a logo in the Microsoft 365 admin center to customize the footer in the Microsoft 365 Copilot app.
• The footer will display an “Approved by [Logo]” indicator to help users confirm they are in an organization-approved Copilot environment: 

  

• Only the logo from your organization’s theme configuration will be used; other theme elements will not be applied in this release.
• This feature will be off by default and will require admin configuration.
• There will be no user impact unless an admin enables the footer.

[What you can do to prepare]

No action will be required unless you want to enable the branded footer.

Admins who want to configure this feature should:

• Review and verify your organization’s theme configuration in the Microsoft 365 admin center.
• Upload the logo you want to display in the Microsoft 365 Copilot app footer once rollout begins.
• Use the existing theme management flow to apply co-branding once the feature is available.

For configuration guidance: Customize the theme for your organization | Microsoft 365 | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Source: Microsoft

Latest Posts