OneDrive won't sign in until I log into an external account in Teams
OneDrive gets stuck on "Signing in" after every restart – Sign-in only works when I log into a second organization in Teams I've noticed that OneDrive consistently gets stuck at the "Signing in" stage every time I restart my Mac. I have tried several troubleshooting steps to resolve this issue, including: Quitting OneDrive completely and restarting the Mac. Running the ResetOneDriveApp.command reset procedure. Running the standalone version of the OneDrive reset procedure (ResetOneDriveAppStandalone.command). Removing the "OneDrive Cached Credential" entry from macOS Keychain Access. Testing the sign-in process through a web browser. Testing the connection using a mobile hotspot to rule out potential network-related issues. Updating the standalone OneDrive application to the latest available version. Unfortunately, none of these steps has permanently resolved the issue. Even when OneDrive starts working again, it gets stuck at the sign-in stage after a subsequent restart. However, I have discovered something quite interesting. Recently, while preparing for a Teams meeting, I signed in to one of my two accounts in Microsoft Teams. At that exact moment, I noticed that OneDrive suddenly completed its sign-in process and started working normally, even though it had previously been stuck at the "Signing in" screen. Here is how my account setup is configured: OneDrive is currently syncing folders belonging to my primary organization, as well as one shared folder from an external organization. I have two accounts configured in Microsoft Teams, representing my primary organization and the external organization. Both accounts are essentially associated with the same email address and my primary organization's Exchange account. The external organization's shared access also uses the same email address, but with some additional characters appended to the email address. The interesting part is that OneDrive only manages to complete its sign-in process when I sign in to the external organization's account in Teams. Otherwise, it remains stuck in an endless sign-in loop. This makes me wonder whether there is some kind of authentication dependency or token-sharing mechanism between Teams and OneDrive that is causing this behaviour. What I would like to understand is: Is it possible to make OneDrive authenticate independently, without relying on signing in to the external organization's account in Teams? Is this expected behaviour when using multiple organizational accounts and shared folders across different Microsoft 365 tenants? Could a recent update to OneDrive, Teams, or macOS have introduced a change in how authentication tokens are handled? What's particularly confusing is that I have been using exactly the same account configuration and setup for quite some time without any issues. This behaviour only started appearing after recent updates. I'd really appreciate any insights or suggestions on how to resolve this permanently, rather than having to sign in to the external organization's Teams account every time I restart my Mac just to get OneDrive working. Thank you in advance!
Has anyone noticed a recent change in outbound PSTN ringing behavior in Microsoft Teams?
Previously, when dialing an E.164 number, Teams would play its internal ringing tone and then switch to the PSTN ringback tone once the call reached the carrier. Recently, the internal Teams ringing tone continues all the way until the far end answers. I haven't seen any Microsoft notices about this. Has anyone else noticed the change?
Meeting chats visible for only one month in Microsoft Teams
Hi Community, In Microsoft Teams, under Chat > Meeting chats, I am currently able to see meeting chats from only the last one month. Is there any way or setting to extend this so that I can see meeting chats from the last two months (60 days) in the Meeting chats section? Please let me know if this can be configured through Teams settings or the Teams Admin Center. Please find the below screenshot: Thanks!
Speed dial in new Teams call history layout
Hello all, I have a query which I am hoping someone can help me out with. The new Teams desktop client layout has launched, but I am experiencing an issue with the layout of the call history section. Previously, speed dials that I add myself within the client would be ordered alphabetically, as well as being able to create my personal groups for the contacts in my speed dial. In the new layout, both of these features appear to be missing. Am I missing something here, or is anyone else noticing these two features are no longer available in the new layout?Can I use forms inside Teams to automate surveys at intervals?
I’m trying to set up a few recurring surveys for things like monthly pulse checks and occasional employee feedback, ideally without someone from HR having to remember to send them out every time. I know Forms works inside Teams, but I’m not sure how far the automation goes. Can you schedule the same survey to go out every month or quarter, send reminders to non-responders, and keep the results together so you can compare them over time? Has anyone built a decent setup for this?
Teams co-organizers can’t access meeting engagement data: a gap for centrally managed meetings
Hi everyone, We’ve run into what seems to be a gap in the Microsoft Teams co-organizer model while working on moving our enterprise virtual learning delivery from a dedicated virtual-classroom platform to Teams. Our requirement is fairly straightforward: we run a large number of centrally administered learning sessions, with multiple facilitators who need to be able to step in and deliver a session when required. The model we’d ideally use is: A shared calendar/mailbox for central visibility and administration. The relevant facilitator group automatically added as co-organizers. Facilitators can run the session, manage participants, breakout rooms, recordings, etc. Co-organizers can access the standard attendance report after the session. This gets us almost everything we need. The gap is the richer meeting engagement data. Teams provides engagement information such as reactions, raised hands, camera usage and other engagement measures, but this appears to remain restricted to the meeting organizer, rather than being available to co-organizers. That creates an awkward problem for centrally administered meeting scenarios. A co-organizer can be trusted to run the meeting and access its attendance reporting, but not access all of the post-meeting engagement reporting. It becomes particularly problematic if a shared mailbox is the meeting organizer, because there may be no actual person able to retrieve that organizer-only data. What I’d love to see I’d like Microsoft to allow explicitly assigned co-organizers to access the same post-meeting engagement data as the organizer. I’ve submitted this as a feature request here, which I'd love for you to vote for at the link below please if you think it would help you too: https://feedbackportal.microsoft.com/feedback/idea/28182268-f7d9-f111-bda3-6045bd78a526 I’d be really interested to hear: Is anyone else running centrally managed Teams meetings at scale and hitting this same limitation? Have you found another supported way of retrieving this engagement data? If this would be useful for your organization too, would you consider voting/commenting on the feature request? It feels like a relatively small permissions gap in an otherwise very capable co-organizer model, but closing it would make a big difference for centrally managed training, events and similar enterprise scenarios. Thanks!Bot not receiving message events in shared channels (RSC)
Hi folks, Running into an issue with a bot in Microsoft Teams shared channels. I've configured RSC permissions to listen for new messages. This works as expected in standard channels - I receive events for every new message. However, in shared channels, the behavior is different: I only receive events when the bot is explicitly tagged Regular messages in the channel don’t trigger any events Permissions currently granted: Channel.ReadBasic.All (Application) ChannelMember.Read.All (Application) ChannelMessage.Read.All (Application) Has anyone faced this with shared channels? Is this expected behavior or am I missing something in setup? Thanks!
