Teams missing GIF option in messaging
This morning we noticed the GIF option in Teams messaging is missing org wide. Desktop and Web client. Old messages that were sent with a GIF display as a link now instead of the image Our global org policy in the Admin porta is set to On Anyone else seeing this?
Teams drag-and-drop upload fails only from macOS screenshot thumbnail / markup window
I’m encountering a reproducible issue with Microsoft Teams file uploads that appears to be specific to the drag-and-drop source on macOS. Steps to reproduce On macOS, take a screenshot using: Cmd + Shift + 4 or Cmd + Shift + 5 When the floating screenshot thumbnail / markup window appears (bottom-right of screen), do not save the file manually Drag the screenshot directly from the floating thumbnail or markup window Drop it into the Teams message compose box in: a 1:1 chat, or a group chat Result Upload gets stuck on Uploading Environment macOS Teams Web (Chrome) Teams macOS desktop app
Teams email notifications of missed chats coming from wrong email address?
For the past several days, when some users have missed a chat message in teams and they are setup to receive an email notification, the sending email address of the notification is incorrect. It has always been that these notification emails appear to be sent from the person who sent the original chat message, but now, they are being sent from our global administrator account email. Obviously creating lots of confusion and has broken these users' ability to reply via email. Has something changed, or is this a bug?Teams Messaging Gets Autocorrect
The addition of Autocorrect for messaging is a small but important change for Teams messaging brings Teams up to speed with the other Office applications. It’s taken Teams a little longer than it perhaps should have to support Autocorrect and the implementation is not as functional as it is in Outlook, but that’s not a reason to overlook the update. https://office365itpros.com/2025/12/10/teams-autocorrect-messaging/
Require approval from IT to join a Team and/or Shared Channels
My company has two sides to its business. Both sides are under the same Microsoft 365 tenant. They can be called Group A and Group B. Group A should not be able to add those from Group B into teams and channels on their own. Likewise, Group B should not be able to add those from Group A. If either side wants to add the other to a team or channels, they should have to get approval from IT, with IT making the additions to the team or channel. We would rather not have this just done over emails. This has to be done while still allowing members of Group A and members of Group B the ability to have 1 on 1 and group chats. Does anyone have any suggestion how to do this?Teams Messaging Gains New Protections
Teams now includes weaponized file protection and malicious URL protection to make sure that people don’t share bad files or URLs in chats or channel conversations. Given that a user can post a message to up to 50 channels at one time, it obviously makes a heap of sense to check that any files or URLs that people share in chat or channel conversations are safe and not malicious. https://office365itpros.com/2025/11/24/weaponized-file-protection-teams/Announcing the General Availability of the RabbitMQ Connector
We are pleased to announce the general availability of the RabbitMQ Connector in Logic Apps (Standard) which allows you to both send and receive messages between Logic Apps and RabbitMQ. RabbitMQ is a robust, open-source message broker widely used for building reliable, scalable, and flexible messaging solutions. It is trusted across industries such as financial services, e-commerce, IoT, telecommunications, and cloud-native microservices. Our RabbitMQ connector allows messaging scenarios on-premises using Logic Apps hybrid. Benefits of Using RabbitMQ Reliability: RabbitMQ ensures message delivery with strong durability and acknowledgment mechanisms. Flexible Routing: Supports complex routing logic via exchanges (direct, topic, fanout, headers). Clustering & High Availability: Offers clustering and mirrored queues for fault tolerance. Management & Monitoring: Provides a user-friendly management UI and extensive monitoring capabilities. Extensibility: Supports plugins for authentication, federation, and more. Our current connector offering supports both triggers (receive) and sending (publish) within Logic Apps. Receiving Messages To enable a trigger, we need to search for the RabbitMQ connector within our designer. We will discover an operation called When the queue has messages from RabbitMQ show up as a built-in connector. We also have a peek lock operation for non-destructive reads. Search for Trigger and click on this operation to add the trigger to your design surface. Configure the trigger by providing the Queue Name. You can use the payload from your trigger in downstream actions. For example, you might place the payload within a Compose action for further processing. Publishing Messages To send a message, search for the RabbitMQ connector in your design experience. You’ll find an operation called Send a message. Add this operation to your design surface and Provide the following: Queue Name Message Body Exchange Name (if routing is required) Routing Key Once configured, you can run messages through your solution. To see this in action, refer to the demonstration video below. Completing Messages To Complete messages, in scenarios using peek-lock, search for the RabbitMQ connector within the Logic Apps designer. You’ll find an operation called Complete message as a built-in connector. Search for the action and click on this operation to add the action to your design surface. Provide: Delivery tag Consumer tag Acknowledgment (Complete or Reject) You can use the payload from your trigger in downstream actions. For example, you might place the payload within a Compose action for further processing. You can also create queues as well, with the Create a queue action. Please see the following video with further details on the configuration of this connector: Supported Regions We are rolling out this connector worldwide, with some regions receiving it before others.Teams Gains Ability to Start Chat with Email Address
A new Teams feature allows users to initiate chats with any email address. This caused some commotion in the security community, but it’s not that bad. In fact, it’s an extension of existing functionality that allows Teams users to chat with guest accounts. All that’s happening is that initiating a chat causes a new guest account to be created in the tenant, and there’s lots of controls to make sure that guests are controlled. https://office365itpros.com/2025/11/10/chat-with-email-address-teams/
