Additional features, settings, or issues not covered by specific Microsoft Teams categories
Hi Kris,
Thank you for the update and thank you again for taking the time to perform all of these additional tests.
I truly appreciate the effort you've put into investigating this issue and the level of detail you've provided throughout the discussion. Your willingness to test different scenarios, share recordings, involve a colleague, and follow up on the results has been extremely helpful.
Your latest findings are particularly valuable because they help rule out several possibilities. Since:
- the behavior occurs in both Teams Desktop and Teams Web,
- another user in your organization is experiencing the same issue,
- the behavior affects all Loop tables you've tested,
- and the issue is not limited to Loop-to-Loop pasting but also occurs when copying from Loop into applications such as Excel, Word, and Notepad,
The issue now appears broader than a problem with a single Loop component, browser session, or individual user profile.
On my side, I have continued testing this behavior in multiple environments, including personal environments, work environments, test environments, and additional tests with colleagues' accounts. At this time, I have not been able to reproduce the issue. In my testing, Loop continues to copy and paste multiple rows and table content as expected.
Because of the difference between your results and mine and given that the issue is occurring across multiple users and clients in your organization, I am concerned that further investigation may be required beyond what we can reasonably verify from the user side.
At this stage**, I recommend contacting your Microsoft 365 administrator and asking them to open a support ticket with Microsoft.** The support engineers have access to diagnostic and backend tools that are not available to either you or me through the community. They may be able to determine whether this is related to a tenant-specific issue, a service-side behavior, or another underlying condition that cannot be identified through normal client-side troubleshooting.
You can raise support ticket from Microsoft 365 Admin Center>Support>Help & Support.
For reference: Get support | Microsoft Docs
Thank you again for your patience, cooperation, and all the testing you've done so far. I hope you're able to get this in front of the appropriate support team quickly and that your Loop workflows return to normal as soon as possible.
Please feel free to continue updating this thread if you learn anything new. I'd be very interested to hear what Microsoft Support finds, as it may help other community members who encounter similar behavior in the future.
Wishing you all the best and thank you again for working through this with me.
Kind regards,
Liora