Forum Widgets
Latest Discussions
Teams for Mac retains deleted personal Microsoft account in account picker after alias change
I’m hoping someone can point me to the location where Teams for Mac stores remembered accounts, or confirm whether this is a bug. Environment Teams Version: 26163.407.4839.8659 macOS: 27.0 Problem I previously had both: a work account using email address removed for privacy reasons a personal Microsoft account that also used email address removed for privacy reasons I successfully migrated the personal Microsoft account to a new primary alias (email address removed for privacy reasons) and removed email address removed for privacy reasons from the personal account. The work account remains unchanged. However, Teams for Mac still displays the old personal account in the account picker as a second “Sherry Serdikoff” account (purple icon). When I click that account, Microsoft correctly responds: “That Microsoft account doesn’t exist. Enter a different account or get a new one.” So the account no longer exists, but Teams continues to display it. What I have already verified The personal account now signs in only as email address removed for privacy reasons. email address removed for privacy reasons has been removed as a personal account alias. Microsoft confirms that no personal Microsoft account exists for email address removed for privacy reasons. My work account continues to function normally. Troubleshooting already performed Signed out of all Teams accounts. Restarted Teams and macOS. Cleared the traditional Teams cache. Renamed the Teams Group Container (UBF8T346G9.com.microsoft.teams) so Teams recreated it. Searched Keychain (all keychains/all items) for Teams, OneAuth, ADAL, MSAL, OneAuthAccount, authority_map, login.windows.net, etc. No relevant cached identity entries were found. Verified the stale account is not present in Microsoft account settings. Created a brand-new macOS user profile and launched Teams before signing into any Microsoft account. Important observation In the brand-new macOS user profile, Teams starts with only Sign In and Join a Meeting. No remembered accounts are displayed. This suggests the stale account is stored somewhere within my original macOS user profile rather than in Microsoft’s cloud or the Teams installation itself. Question Has anyone identified where the current Teams for Mac client stores these remembered account identities, or is this a known bug in the current Teams/OneAuth implementation? I’d appreciate any suggestions before I resort to deleting additional Microsoft authentication data.
Don't expire attached chat files | Show a warning.
Teams allows users to upload files to share with others in a chat. These files inherit the organization's sharing policy. So whether you use Share or Copy Link in SharePoint or OneDrive or you use Attach File in Teams, the same default policy is applied. The issue, what makes the Teams experience different from SharePoint / OneDrive, is that the message with the attached file persists in the chat. A file that was attached to a conversation two months ago appears to still be in the chat. However, the default policy blocks access to the file that appears present. Moreover, there is no method for the sender to alter the sharing policy using the Attach function. When this an issue, this is a HUGE issue. Suggestions: Actually attach the attached file and store in the recipient's Attachments folder. Don't use a paperclip icon that says "Attach file" for files that aren't actually attachments. Warn the sender that the attached file inherits the organization's 'Share with anyone' policy and may expire. Prompt the sender to alter the sharing link before sending. Put a timer on the attachment showing the countdown to expiration. After the expiration date, the file should be labeled "Your organization's sharing policy has expired access to this file". Add a button for the recipient to request access to the file again.
Mirror My Video Apparently Means Mirror Everything?
Most users expect Mirror My Video to mirror only their camera video, while leaving the virtual background exactly as they uploaded it. However, when Mirror My Video is enabled, Microsoft Teams also mirrors uploaded background image. So someone on MS Teams Team really thought: "The user will anticipate this and manually reverse their background images, then upload the backwards image so Teams can reverse it again!" We wait in earnest to find out if the next Teams patch will drop all pretenses and just mirror the entire display, including on screen text, menus, and the Windows Start bar.Teams for iOS (MAM only Call Identification)
In order of the implementation of O365/M365 and with it Microsoft Intune, Teams and Outlook for iOS has become the standard collaboration and mail clients on iOS devices for many customers today. This is due to the excellent user experience and the constant stream of new features implemented by Microsoft. From a security perspective, in addition to the provision on managed devices (managed by Intune), the secure use on unmanaged devices with MAM or App Protection Policies (APP) is a big argument for using Teams and Outlook for iOS. A big pain point for many users who use Teams and Outlook for iOS in an MAM-only setup (and for MDM setup with Intune too) is the missing caller identification of Exchange Online (EXO) contacts, when someone is calling via a cellular connection. Outlook for iOS supports a one-way contact export process whereby contacts from within Outlook for iOS can be exported into the personal (unmanaged) part of the native iOS Contacts app. This means a contact must first be imported into the users personal contacts directory of EXO and then exported from Outlook for iOS to the native (unmanaged) iOS Contact app in order to see who is calling. This functionality enables Caller-ID, iMessage, and FaceTime integration for users’ Outlook contacts. The exported Outlook contacts are considered unmanaged and are accessible by unmanaged, personal apps. Especially for European customers who are subject to GDPR compliance, this is a no go, as personal data and company data must not be mixed. The unintentional outflow of contact data worthy of protection to commercial platforms, such as WhatsApp or Google, and the unintentional synchronization of address books with social media apps, represents a significant GDPR risk. Although the user's personal EXO contacts can be synchronized, there is currently no option to synchronize the GAL. Furthermore, there is currently no provision in Teams and Outlook for iOS to synchronize the GAL cyclically. The user has to add a GAL contact to his personal contacts as described above and then within the Outlook for iOS app export the contact to his native iOS contacts app to be able to see who is calling. To meet the GDPR compliance, we need to prevent the contact export. So this is not a solution. The question to ask is: Why does a user need to export a GAL/personal contact to their native iOS Contact app? There are already several paid app solutions that close exactly this gap (ebf Contacts, Secure Contacts, etc.) which offer more or less the same range of functions. The app builds a container and downloads the managed address books (GAL, personal) of the user and then enables the resolution of the CallerID or identification of the caller via the so-called Apple CallKit integration. Apple has been offering the so-called CallKit integration for years. With CallKit you can integrate your calling services with other call-related apps on the system. CallKit provides the calling interface, and you handle the back-end communication with your VoIP service. For incoming and outgoing calls, CallKit displays the same interfaces as the Phone app, giving your app a more native look and feel. CallKit also responds appropriately to system-level behaviors such as Do Not Disturb. In addition to handling calls, you can provide a Call Directory app extension to provide caller ID information and a list of blocked numbers associated with your service. When a phone receives an incoming call, the system first consults the user’s contacts to find a matching phone number. If no match is found, the system then consults your app’s Call Directory extension to find a matching entry to identify the phone number. This is useful for applications that maintain a contact list for a user that’s separate from the system contacts, such as Teams and Outlook for iOS. For example, consider a user who is a colleague to Jane, but doesn’t have her phone number in their contacts. If the Teams or Outlook for iOS app has a Call Directory app extension, which downloads and adds the phone numbers of all of the user´s colleagues. When the user gets an incoming call from Jane, the system displays something like “(App Name, e.g. Outlook) Caller ID: Jane Appleseed” rather than “Unknown Caller”. The effort to integrate the Call Directory Extension is minimal and would solve many pain points from both a security and user experience perspective. Apple has documented CallKit excellently on the developer site: https://developer.apple.com/documentation/callkit With the possibility of using Apple CallKit in combination with Teams and Outlook for iOS and the contact synchronization (personal/GAL) of a managed EXO mailbox, the use of M365 in a BYOD scenario for customers Blue Collar workers will massively increase. Furthermore, the use of contact synchronization is then also possible for devices managed by Intune. This creates an outstanding user experience while increasing user adoption! This article was also published as feedback in the Outlook Forum for iOS: https://feedbackportal.microsoft.com/feedback/idea/a80414f4-9598-ed11-a81b-000d3ae32cd0 There are already other requests within the Microsoft community that I would like to link here: @PatrickF11 : Outlook for iOS + Caller Identification - Microsoft Community Hub Daniel Huttenlocher: https://feedbackportal.microsoft.com/feedback/idea/bbfc8763-da97-ed11-a81b-000d3ae32cd0How to Record Snapshots for Teams Memberships
A lawyer asked if it is possible to take a snapshot of Teams memberships (people who were members at a certain point). This isn’t something that every Microsoft 365 tenant will want to do, but good reasons no doubt exist for the request. In any case, PowerShell makes it easy to find the team membership data and record it in a CSV file or XLS spreadsheet. https://office365itpros.com/2026/07/03/teams-membership-snapshot/
Speaker diarisation help!
Hi! Is there a way to get speaker diarisation in Microsoft Teams meetings? This is a situation where all speakers are in the same room, and the meeting is joined through a Teams enabled device. I am aware of programs like WhisperX, however I do not know how to do any coding-based stuff, and would prefer to have as much as possible within the Copilot 'universe'Anyone Else Having Issues?
Hello! My company uses Teams as our main communication channel. For the past two or three weeks we have had significantly more issues than usual with Teams. Messages will sit and not send for sometimes over an hour. We have tried the standard troubleshooting methods and are still facing this problem. Is it just us or is this a bug? If so, is Microsoft working on a solution? Thank you!Microsoft Teams File Permissions: Why Can't I Remove Direct Access?
While working with files stored in Microsoft Teams, I recently encountered an issue related to file permissions that may affect other users as well. A file was uploaded to a Microsoft Teams channel, which means it is physically stored in the SharePoint document library connected to the Team. At some point, direct access permissions were granted to an individual user using the Manage Access feature. Later, when attempting to remove this direct permission, the option was no longer available. What Happened? The file's permission overview shows that the user has Direct Access (View Only) permissions. However, when opening the permission details, SharePoint displays the following message: "Grant access is unavailable because you are not the owner of this item." Although the file was originally uploaded by the user attempting to manage permissions, SharePoint does not recognize that user as the owner of the item for permission management purposes. As a result: The granted permission remains visible. Permission levels (View, Edit, Block Download) can be selected. The Remove Access option is missing. Changes cannot be applied because the user is not considered the owner.
Our remote managers are struggling with giving regular feedback in Teams
We’re a mostly remote team and one issue we keep running into is that feedback only happens during formal reviews. Managers use Teams every day, but feedback tends to get buried in chats or not documented at all. Has anyone found a simple way to make regular employee feedback part of the Teams workflow without adding a lot of admin work?
