Writing an Announcement post in a channel pushes the "post" button off screen and users can't scroll down to it

Question

Writing an Announcement post in a channel pushes the "post" button off screen and users can't scroll down to it

Cole Weightman 0

Normal posts are ok. This happens on the web browser and the teams app, on laptops or screens which are low resolution or smaller than approx 22". It happens in any channel, for all users. The issue we're having is specifically with the announcement post type, but I expect if someone types a long enough regular post it will eventually get pushed off the screen too.

Whenever someone creates an announcement post, with the picture banner at the top, after a few lines of space is filled in the text box the "post" button is pushed off the screen. Users are unable to scroll down using the mouse scroll wheel or the laptop touchpad. Using Tab to select the UI elements does seem to select the button, however the viewport doesn't jump down when tabbing to elements that are off-screen, so we can't actually tell if we're selecting the correct one.

Currently users are having to use their browser settings to zoom out to about 70-80%, click post, then zoom back in to make everything readable again. It's causing a lot of frustration and interrupting the workflow. I've submitted feedback in Teams

It seems like the whole posting area hasn't got flexible sizing coded in for verticals? It will resize horizontally when I drag the sides, which is fine, but if I drag the height of the app or the browser it doesn't change and just pushes the bottom of the post off the screen without giving the user a scroll bar to be able to hit "post" on their announcement... defeating the purpose of having announcements.

Any help appreciated, but especially a patch/fix for this! Users are getting sick of having to change their zoom level on their browser and the less "tech savvy" ones never remember how, so it uses up IT support's time.

0 comments

1 answer

Your answer

Answer 1

Hello @Cole Weightman,

Thank you for sharing such detailed findings. I really appreciate the effort you’ve put into documenting this.

Based on your description, I tested the scenario in my own environment and was able to reproduce the same behavior. At this time, I have not found any official communication from Microsoft confirming when a full fix will be released.

I’d also like to clarify that, as a forum moderator, I don’t have access to internal product roadmaps or official announcements. Please consider me an end user as well, providing guidance based on experience and documented processes.

Since this issue appears to occur across different users, channels, and client types, I recommend engaging Microsoft Support for a more in-depth investigation.

This type of behavior may involve backend factors that aren’t visible through standard troubleshooting steps. Microsoft Support has access to tenant-level diagnostics, service telemetry, and internal tools that can help determine whether this is related to a service regression, a configuration-specific issue, or a broader platform concern requiring escalation.

For business support:

Collect Teams diagnostic logs: To help Microsoft troubleshoot the issue, affected users should first collect Teams logs from their device. If multiple users are affected, logs from 2–3 impacted users are usually sufficient: Collect log files for monitoring and troubleshooting in Teams - Microsoft Teams | Microsoft Learn
Find your Microsoft 365 admin: If you don't know who the global admin is in your organization, you can find guidance here: How can I find my Microsoft 365 admin? - Microsoft Support
Submit a service request: The Global Administrator should create a support request with Microsoft to receive advanced technical assistance. For detailed instructions, see: Get support - Microsoft 365 admin | Microsoft Learn
If your subscription is from a partner or reseller, contact the reseller's support provider to help open a service request on behalf of you instead.

I understand it’s not ideal to be redirected, and I sincerely apologize for any inconvenience. Given the nature of this issue, support involvement is the best way to get a definitive answer and ensure it’s properly investigated.

If you come across any updates or workarounds, please feel free to share them here, as it would be very helpful for others experiencing the same issue. At the same time, please rest assured that you’re not alone in facing this. I will continue to monitor this thread and share any updates if I come across new information.

Thank you again, and please let me know if I can help further.

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.