For a few years I’m noticing more and more weird and unexplainable behaviour in Outlook. We support mostly 365 Exchange Online clients on Windows workstations or RDS environments.

The amounts of unexplainable bullshit we face is staggering. Outlook not being able to open the folder set, weird MFA glitches, weird bugs in the UI and downright weird errors coming from nowhere is some of the stuff we face weekly.

Am I alone on this?

    • HC4L@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      11 hours ago

      I’ve been doing this for 15 years daily now and it was never this bad. Not even when everyone ran Exchange on-prem with al the bullshit involved with that.

      • mesa@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 hours ago

        Ill agree. But just FYI Azure AND aws have recently had downtime which funny enough can effect a lot of things with email. Since email in itself is more html nowadays than anything else. And ive had the same issue with 2FA and timeouts from Azure/cloud exchange. Fun times.

        When I retire, im going to look forward to never touching MS product slop again. Should be fun!

      • frongt@lemmy.zip
        link
        fedilink
        arrow-up
        1
        ·
        10 hours ago

        I’m sure it’s gotten worse since Microsoft fired QA and devs and replaced them with AI, but Outlook and Exchange have always been weird and buggy.

        I personally haven’t been a mail admin for a few years so nothing comes to mind, but similarly, the recent update to the Outlook mobile app, at least on iOS, moved the reply button from its prominent location to the message three-doy menu. Like the #1 thing people do with a message, that I’m sure their analytics show, was hidden in a menu.

  • mbirth 🇬🇧@lemmy.ml
    link
    fedilink
    arrow-up
    3
    ·
    11 hours ago

    You’re not alone. We’re forced to use Classic Outlook at work.

    I’ve got a monthly recurring appointment for a Zoom call. That was due today again. There was the switch to winter time last week and Outlook decided to “adjust” the scheduled time for me.

    That meeting was originally for 11am and should continue to be at 11am during standard time. However, yesterday I’ve noticed that Outlook put it at 10am (and showed a proud message that it adjusted it due to timezone change). No way to undo it.

    Teams continued to show it at 11am where it belongs.

    Now, when trying to move it to 11 in Outlook, Teams moved it to 12.

    And when I opened Outlook this morning, the appt was at 11am where it belongs and Outlook and Teams agreed again.

    Mind you, this was only this external Zoom call. All other appointments are still correct. Very weird.

      • mbirth 🇬🇧@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 hours ago

        I thought so, too, at first. But why did Teams (using the “New Calendar” setting) show it correctly? And why did it fix itself today?

  • Brkdncr@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    11 hours ago

    Outlook classic is on life support. Next October Exchange Online drops support for it.

    It’s built on decades of code. It allows plugins to directly affect the UX. It still uses I explore at times.

    I switched to new outlook and while it has its own significant issues, at least it’s not spaghetti code. It also runs on top of Edge, which allows Outlook devs to ignore a lot of backend code, and makes the UX pretty consistent across platforms.

    • HC4L@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      11 hours ago

      Sadly I’m still bound to classic Outlooks because of a lot of clients dependent on COM add-ins.

      • Brkdncr@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        8 hours ago

        Yeah those com addins are usually the problem with outlook stability. Simply moving to modern addins improves Outlook classic significantly.