Built-in Teams “Submit feedback” dialog renders all text bold

Question

Problem summary

• The built-in Teams feedback dialogue (Created using this) (the “Submit feedback” modal shown when using Teams’ thumbs-up/down feedback loop) displays most text in bold. DevTools shows the rule coming from an inline <style> tag generated at runtime by Fluent UI (style tag has attribute data-make-styles-bucket).
• The rule is like: .f16wzh4i { font-weight: bold; } and is injected by the Teams client (not a static CSS file in my app).

Expected behavior

• Teams’ own feedback dialog should use normal-weight text for labels/body unless intentionally bolded. Built-in dialog styling should not apply a global class that forces bold on many elements.

DevTools evidence (what I saw)

• The rule originates from an inline style element (no external href), ownerNode = <style data-make-styles-bucket="d" data-priority="0">…</style>
• Running a small script in Console found that stylesheet and showed its cssRules; disabling the rule removes the bold.
• Because the style is injected at runtime by Fluent UI / make-styles, there is no file in my repo to edit.

Environment

• Microsoft 365 Agents Playground (dev host), bot runs from local dev server.
• Building Custom Chatbot via code

Is there something that can be done to fix this issue or is it something that I am doing wrong?

Answer 1

Dear @Ronit,

Welcome to Microsoft Q&A Forum!

Based on your description and the evidence you shared (DevTools showing an inline <style> tag with data-make-styles-bucket), this behavior may not cause by your bot or feedback implementation.

The built‑in Microsoft Teams “Submit feedback” dialog is owned and styled entirely by the Teams client itself. Internally, Teams may use Fluent UI React (v9), which applies styles at runtime using makeStyles. This mechanism dynamically injects atomic CSS rules into the DOM, and the insertion order is controlled by the host application (Teams), not by embedded apps or bots.

Fluent UI explicitly documents that:

• makeStyles generates atomic CSS classes that are injected dynamically
• When multiple rules target the same CSS property, the rule injected later wins
• Host applications control style injection order, so embedded apps cannot reliably override those styles

Also, I found the Fluent UI makeStyles specification on GitHub, you can take a look: https://github.com/microsoft/fluentui/blob/master/specs/makeStyles.md

Besides that, I saw a case that there may be also clear precedent for this type of issue on the Fluent UI GitHub repo, where Teams‑side overrides cause unexpected typography and font behavior in embedded surfaces. For example, Fluent UI issue #33392 documents Teams overriding typography tokens at runtime, resulting in inconsistent font rendering that required a Teams / Fluent UI product fix, not an application‑level workaround: https://github.com/microsoft/fluentui/issues/33392

So, in this case, here are several points that you may see:

• The bold text is coming from runtime‑injected Fluent UI styles applied by the Teams client
• The built‑in feedback dialog is not customizable by developers
• There is no supported workaround to override these styles from app or bot code
• This may be a Teams / Fluent UI product behavior, not an implementation error on your side

In the meantime, as I really want to help you to improve some aspects in this case, you can try these suggestions to see if they can help:

• In Windows Settings > Accessibility > check and disable any bold text or high-contrast options.
• In Teams Settings > Appearance, try switching themes (e.g., from Dark to Light) to see if it resets the dialog styling.
• Clear Cache: Close Teams, delete the cache folder (typically at %appdata%\Microsoft\Teams), and restart the app. This may help to resolve rendering glitches.

However, from my perspective view and research, there is no confirmations, configuration, or code change available to address this.

Since this behavior comes from the Teams client itself (host‑injected Fluent UI styles) and there is no supported way for developers to override the built‑in feedback dialog styling, the recommended next step is to submit this as product feedback directly from Microsoft Teams.

You can do this via Settings and more (…) > Feedback > Report a problem and include the DevTools observation that a runtime‑injected Fluent UI makeStyles rule is forcing font-weight: bold in the built‑in feedback dialog. This sends diagnostics directly to the Teams engineering team for investigation. Reference: Give feedback in Microsoft Teams

Additionally, I understand this may impact your workflows, but we should wait for Microsoft’s answers at this time. If this issue causes the uncomfortable situation to you, I recommend opening a new thread in the Microsoft Community Hub or on GitHub, there are many developers and SDK contributors there who can give you more targeted help. This may help you get the most accurate guidance, and I also don’t want to accidentally give you misleading instructions at this current behavior of your concern.

I hope this information can give you some insights in this case.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.