Formal Complaint: The UX Failure of Microsoft Authenticator and Teams Guest Access
To the Microsoft Product & Engineering Teams, I am writing this not just as a frustrated user, but as a systems engineer and developer who has just spent several hours navigating the Kafkaesque labyrinth that is your current authentication ecosystem. The transition to a new mobile device while maintaining "Guest" access to an external organization (Rihter d.o.o.) has been an exercise in systemic failure. Specifically, I would like to highlight the following critical UX flaws: The Identity Paradox: Your system’s inability to gracefully handle a personal Outlook account acting as a Guest in an Entra ID tenant is baffling. Receiving the error "You can't sign in here with a personal account" while trying to access a tenant I am already a member of is a fundamental logic failure. Visual Inconsistency (The "Briefcase" vs. "Initials"): The fact that an account can appear in Authenticator as a "One-time password" nalog with initials, yet be completely non-functional for Teams until it is manually re-added as a "Work/School" nalog with a briefcase icon, is a UI disaster. The "Action Required" Loop: I was trapped in a cycle where the app demanded action but provided no path to resolution within the mobile environment. I had to resort to using a desktop browser in Incognito mode just to force the system to generate a valid QR code for the new hardware. Mandatory Hardware Security (Passwordless): Forcing users to implement device-wide PINs or biometrics on their private hardware just to use the "Approve" notification feature is overreach. There should be a clear, frictionless fallback to TOTP codes within Teams without degrading the entire app's functionality. App vs. Web Desynchronization: It is unacceptable that a web browser (in Desktop mode) can successfully authenticate a session while the native Teams app on the same device remains stuck with stale tokens and cached AADSTS90023 errors. As someone who designs low-level architectural specifications (DREL), I find the lack of interoperability and the "black box" nature of these errors (like AADSTS90023) to be a significant step backward for professional productivity. I hope this feedback reaches someone who prioritizes user flow over bureaucratic security layers. Best regards, Milan Lakatoš Petrović Systems Engineer & Freelance Programmer
Document Library Settings
Many times when someone opens a document from a teams document library, it shows the document as modified even though no actual changes were made to the document. The default at my company is that documents open in edit mode and they auto save so one solution would be to set it to open in view only mode, but my company doesn't want to change that at the company wide level. Is there any way to do this at the SharePoint library level? I also don't want to make document checkout mandatory.Multi-app camera - Stops Teams from detecting webcams
Hi. We have a load of shared meeting rooms that are setup with Jabra panacast webcams. When you open Teams it shows that no devices are connected but if you open the camera app or any other app like zoom the camera works fine. The only way to get it to work is to enable this setting. This settings for Multi-app camera cannot be enabled by Intune or powershell/regedit. There are some posts on reddit that suggest I am not alone and there are others having this issues too. So.. its either a bug with the Teams app itself or the windows OS Thanks, Cam
Shared Number Group Channel Operator Options Missing in Microsoft Teams 260043.403
After updating to Microsoft Teams version 260043.403, options in Group Channels related to shared number / calling queue operator availability appear to have changed. Previously, when selecting a channel associated with a calling queue, operators could: View a list of all queue operators See each operator’s availability for that specific calling queue (not general Teams presence) Change their own availability for that queue With this update, the ability for operators to change their availability now appears to be located under Settings → Calls. However, the channel-level view that displayed the availability of other operators seems to have been removed entirely. Can someone confirm whether the operator availability view within Group Channels has been deprecated, or if it is now accessible elsewhere in Teams?
StarLeaf + Teams integration
Hi all, I have a user that wants to integrate StarLeaf into one of his Microsoft Teams group. He is not the owner of the group. The issue he reported: "Currently, Starleaf for Teams is installed, but when there is any attempt to setup using the integration token generated from our systems admin in Starleaf, an error occurs." The link for instructions he used: https://support.starleaf.com/integrating/starleaf-for-microsoft-teams/#3-Install+StarLeaf+for One of the errors he gets: "Something went wrong. Reinstall StarLeaf for Teams." Any idea of what to do? Kind regards, Dino
Microsoft Teams – “You need a paid subscription to use Microsoft Teams”
Hi everyone, I’m currently unable to sign in to Microsoft Teams using my work account. When I launch the Teams desktop app, I receive the following message: "You need a paid subscription to use Microsoft Teams. To continue using Teams, you’ll need a license. You’re currently signed in as [my account]. Please click Request License to ask your admin for access or sign in with a different account." However, according to our admin, a Microsoft Teams Premium license (or equivalent Microsoft 365 license) has already been assigned to my account. I can also see Teams listed under My Apps in the Microsoft 365 portal. I have tried the following steps: Signed out and signed back in Tried Teams web app (teams.microsoft.com) in an InPrivate or Incognito browser Cleared Teams cache from %appdata%\Microsoft\Teams Reinstalled the Teams desktop client Unfortunately, the same message still appears. Could someone please advise: Is this a known sync or license propagation issue? Should the admin reassign the license or refresh it from the Microsoft 365 Admin Center? Are there any other steps to force Teams license validation? Any guidance would be greatly appreciated. Thank you, SavinduApps notification settings missing in Teams settings
Hello Teams Community, I'm facing a strange issue with App notifications in Microsoft Teams. I've already researched this and found nothing. I've opened a Microsoft case and I'm waiting for an answer but it's taking longer than expected. So, I'm turning to you for expedited help! Scenario: You're an administrator in Teams. You've applied a setup policy for a pinned app like Viva Engage. After the policy is applied and the tool is launched, users complain that notifications are either too frequent or not frequent enough. You direct them to the Teams Notification and activity settings to control app notifications. The users go to Teams notification settings but report back to you that the App section of Teams settings doesn't exist. Problem Statement: Microsoft explicitly states in their documentation that in order for the App notifications section to appear, you must first add an app yourself within Teams and get at least one notification. But relying on users to add an app, somehow create a notification, and then remove it, just to access App notifications is impractical and would never work. Desired Outcome: I'm looking for a way to bypass this prerequisite and force the Apps section to appear in the Notifications and activity section without any user action whenever an app is pinned in the Teams admin center with a setup policy. I'm hoping this can work with any app, not just Viva Engage. Any help is appreciated. Thanks, Teams experts! -RobTeams Webinars: Org name vs brand name – how are people handling this?
Has anyone else hit this with Teams webinars? Microsoft recently changed how webinar emails are sent, and the sender name now seems to come from the tenant Organisation Name. You can change that in M365 admin, but that’s where the problem starts. In a lot of companies, the organisation name is a legal/billing entity, not the public-facing brand. Example: Legal / tenant name: FedEx Corporate Services, Inc. Brand: FedEx Teams webinar emails now go out showing the legal entity, which isn’t great for external, customer-facing events. Changing the org name just to fix webinar emails can have knock-on effects for billing, contracts, and governance. As far as I can see: No way to set a brand-specific sender name No per-webinar or per-mailbox sender identity Org name is global and used across multiple services The only real workaround seems to be not using Teams-generated emails at all, and sending custom emails via Power Automate / Graph / a marketing platform, while still using Teams for the actual event. Curious how others are dealing with this: Are you just living with it? Changing the org name with legal sign-off? Or bypassing Teams emails completely? Feels like a gap for larger, multi-brand orgs.
Teams admin centre - add the ability to setup a team completely (shared channels and/or groups)
I think the current teams setup workflow in admin centre is a bit flawed. We're trying out to create a team for every project that we do, but since these projects are done by many different departments it makes sense to use Shared Channels within each project and divide the data in such a way that it is stored in the site library of the channel that is the most fitting. For example creative documents in the channel for the creative department, and business documents in the business channel. To make things clearer to the end user we would like to structure each project the same. So it would be logical if an admin could create these shared channels while creating the project and not have to trust that a project manager is able to set things up correctly after they get assigned. (so being able to create a template would be nice...) So IMHO what is missing from admin centre: -ability to add shared channels. -ability to add teams (in this case department teams) to these shared channels. -ability to create a template with shared channels configured (is a little bit complex, because channel names need to be unique, so some sort of variables need to be taken into account... maybe these can be distilled from the main project team name...which is basically what we also intend) (maybe this could be done with Power automate if the ability to create shared channels is being added to an admin's abilities...) Another option, which would actually be much sweeter would be to skip Shared Channels altogether and add the ability to add Office 365 groups to the main Team, now we can only add members... I would like to work with Team groups, as it's much easier to manage and remove a user from a group than to have this user have to be removed from each project individually. But actually I think both options are a necessity...
