New Copilot Studio UI bot displays Bot ID (GUID) instead of Display Name in Teams Chat

(1) Share

Report

Posted on by TB-22061018-0

Hi everyone,

I am experiencing a strange issue with a chatbot that was developed entirely using the new Copilot Studio UI and deployed to Microsoft Teams.

The bot's display name shows up as the Bot ID (GUID) instead of its actual name in the Teams chat interface.

Here are the details and a comparison:

1. Bot developed in Copilot Studio Old UI:
Chatbots built on the older version (e.g., "Dnee DA assistant") work perfectly. The display name shows up correctly in the Teams chat list.

2. Bot developed in Copilot Studio New UI:
For the new bot built with the new UI ("Jina-DA Assistant"), the naming behavior is broken/inconsistent:
- Correct: The display name shows up correctly on the Teams App Features/Details page.
- Correct: The display name shows up correctly in Mobile Push Notifications.
- Incorrect: In the Teams Chat list, Chat Header, and Message Sender Name, it displays the long Bot ID string (GUID: 7a4967fd-706a-de1d-eb3b-362bf6bedada) instead of the actual name.

What I've tried:
- Verified that the bot name is correctly configured in the new Copilot Studio settings.
- Re-published and updated the app in Teams multiple times, but the chat canvas still insists on showing the GUID.

Since this bot was built from scratch using the new Copilot Studio UI, is there a specific setting in the new manifest or a known sync bug between the new canvas and Microsoft Teams that causes this?

Any advice or workarounds would be greatly appreciated!

Thank you!

Categories:

Bot extensibility

Bot analytics

Publish & channel management

General topics

I have the same question (5)

All responses (7)

Answers (0)

Sort by

Suggested answer

Valantis 6,939 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @TB-22061018-0,

This is a known behavior with the new Copilot Studio experience Teams deployment. <cite index="89-1">Changes to an agent's details aren't available to users who already installed the agent from a shared link.</cite> The GUID showing in the Teams chat list and header is the bot's underlying app ID, and it appears when the Teams app registration hasn't fully propagated the display name to the chat rendering layer.

Fix steps:
1. In Copilot Studio, go to Channels > Teams and Microsoft 365 Copilot
2. Select Availability options > View agent in Teams
3. This opens Teams and shows the agent's app details. Click the three dots > Update. This forces Teams to re-sync the app manifest including the display name.
4. Users who installed via a shared link need to remove and reinstall the agent in Teams to get the updated display name. Existing installations won't update automatically.

If the GUID persists after reinstall, it may be a Teams app manifest sync delay. Wait 15-30 minutes after the update step and have users clear their Teams cache or use Teams web as a test to see if the name resolves there first.

Best regards,

Valantis ✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/ 💼 LinkedIn ▶️ YouTube

Was this reply helpful? Yes No
MK-16070644-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Same issue with my agent developed in new UI.

Please provide step by step troubleshooting steps.

The provided one is not working. Thank you

Was this reply helpful? Yes No
MK-16070644-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Click the three dots > Update. --> No Update feature available here, could you please provide step by step execution.

Was this reply helpful? Yes No
FF-19071045-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

We are experiencing the same issue across all agents in the new UI. The "three-dot" menu referenced in the documentation is not available because the new UI no longer includes Channels in the same way as the classic experience. In the new UI, sharing an agent for use in Microsoft Teams is performed through the Publish function.

The same agent works correctly when accessed through the Copilot app or via Microsoft 365 in a browser, which suggests that the issue is specific to Microsoft Teams.

We would appreciate your guidance on a possible solution or any known workarounds for this behavior. Thank you for your support.

Was this reply helpful? Yes No
RC-22071608-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

we are also facing the same issue how can we resolve this issue.

Was this reply helpful? Yes No
RC-22071608-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

@Valantis any idea on this how this can be fixed !
thanks

Was this reply helpful? Yes No
AP-22071416-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi everyone,

I am experiencing this exact same issue and could use some architectural insight.

The Setup:
I am building an internal Support Co-Pilot using Copilot Studio and deploying it to Microsoft Teams for a restricted pilot group.

The Issue:
In Copilot Studio, the bot is correctly named (e.g., "SABA") under Settings and within the Channels > Microsoft Teams > Edit Details menu. However, when my test users open the bot in Teams, the Display Name shows up as the raw bot/environment GUID (e.g., a90216a4-ab7d-cb25-cd40-b1522b1dc216) instead of the actual name.

Troubleshooting Done:

I have updated the details in the Teams Channel configuration.

I have republished the bot multiple times.

I have cleared the Teams cache and tried the Teams Web App.

My Question:
Is there a known workaround to force Teams to recognize the Display Name when side-loading or sharing directly from Copilot Studio for a pilot test?

Or is the only way to bypass this Microsoft caching bug to download the App Manifest (.zip) and have our global IT admins formally deploy it as a Custom App via the Teams Admin Center?

Any advice from others who have navigated this deployment quirk would be hugely appreciated! Thanks in advance.

Was this reply helpful? Yes No