Update…Per Microsoft’s instructions, disabled all tracking protections in Safari and requested desktop mode and it works. Their instructions say turn protections back on after using teams… 😐

Funny enough it works in Safari and not Edge…tho that may be Apple’s fault since all browsers are somewhat just versions of Safari, last I heard…

  • nogooduser@lemmy.worldEnglish
    2·
    1 year ago

    We use it where I work and it does have its problems but I’ve not experienced anything major. The biggest issue is that it frequently can’t access the camera or mic without a reboot.

    I’ve never used anything else so I’m wondering what these critical features that it’s missing are. Our company only has about 25 employees so I wonder if it’ll get more difficult as we grow more. Having said that, almost all of our European customers use Teams and many of them have thousands of employees and seem to be managing ok (although they wouldn’t tell me if they weren’t - it’s the kind of thing that you complain about among yourselves).

    • lemmylommy@lemmy.worldEnglish
      4·
      1 year ago

      How is camera and mic not working until reboot not a major issue for you? That would drive me insane.

      • nogooduser@lemmy.worldEnglish
        1·
        1 year ago

        It’s because “frequently” is a bit vague. When I say frequently I mean maybe once per month per user (although I get it less often than that and another guy in my office gets it more often).

        It’s more frequent than it should be but not enough to annoy too much.

    • Dandroid@dandroid.appEnglish
      2·
      1 year ago

      The only time I have had it not be able to use my mic was when I had some issue with my whole computer and no app could use my mic. It could have been a driver crash or something. But other than that, I haven’t had that issue. Slack ALWAYS has that issue for me, though.

      For missing features, you can’t add custom emojis, you can’t have bots, searching chat history is horrible (almost to the point where it’s not usable), there’s no markdown for spoilers, code blocks, italics, etc. so you have to click the buttons for it (not sure if spoilers even exist in Teams), code blocks are really clunky, you can’t link other conversations.

      When my work briefly used Slack, it was really nice for text chat. But some teams just didn’t switch, and there’s just so much value having everyone on one platform. Fragmenting users was very counterproductive, so we went back to Teams.

      • nogooduser@lemmy.worldEnglish
        1·
        1 year ago

        Searching chat history is pretty shit. There’s no way to actually see the chat bubble that you found in the context of its conversation that I can see.

        You can have bots in Teams although I haven’t found any particularly useful ones yet. I know Azure DevOps has one that I haven’t tried yet and so does our support desk software but I don’t see why I’d use that over using the support desk app directly.

        The reason why we’re using Teams is that it was the default option for Office 365 and I haven’t seen a reason to switch to anything else when Teams has text chat, voice and video chat, SharePoint file browser, todo list, power apps, SharePoint pages etc.

        I wouldn’t want to go to a system where I’m using different apps for all that or one where we have to move our documentation to view it in the app.