• HeyJoe@lemmy.world
    link
    fedilink
    English
    arrow-up
    25
    ·
    2 days ago

    Saw this in our all IT Teams chat today with people complaining. I just laughed and said oh well that’s what you get when you moved from on prem to cloud. At least it was a Saturday, although I think that was by design since it appeared to be due to a change they implemented and reversed so that makes sense.

    We recently had a huge outage almost a month ago with RingCentral as well. Our entire call center was down for almost 8 hours due to that crazy outage. I have been with this company 19 years and it was Avaya on prem and never had a single outage, last year we moved to RingCentral and boom less than a year later that happened. The funny thing is they also said they never had that happen that bad ever before either. Thankfully our VP has been around the block and knew to tell the company when we shifted to cloud that we needed to lower our expectations from what we previously had because there’s no way you will have 100% uptime with a cloud solution. 8 hours was never expected, though, lol.

    • LedgeDrop@lemm.ee
      link
      fedilink
      English
      arrow-up
      10
      ·
      2 days ago

      I just laughed and said oh well that’s what you get when you moved from on prem to cloud.

      Our Techs said that you couldn’t buy on-perm exchange anymore. You needed to go with the cloud subscription, which “includes” all the crap you don’t want: like Teams.

      Atleast, they said didn’t make financial sense to pay for Google Workspace + Slack + Cloud Exchange, when MS offered their (lesser) services as a bundle (but the human suffering is real) :(

  • catloaf@lemm.ee
    link
    fedilink
    English
    arrow-up
    40
    ·
    2 days ago

    365’s OWA, not Outlook. I assume desktop Outlook still works with their Exchange backend because it’s just a redirect loop error. They should have it fixed pretty quick.

    • malios@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      2 days ago

      Desktop Outlook stopped working too, it’d show a send/receive error or “disconnected”. Seemed to be resolved around 3:36PM Central.

    • corsicanguppy@lemmy.ca
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      2
      ·
      edit-2
      22 hours ago

      365’s OWA, not Outlook

      You don’t need to split that hair. No one’s gonna tell the two nearly-identically-named products apart later. While they intentionally named them nearly the same thing so consumers would get confused, I bet they didn’t mean like this. But that’s where we are.

      • the_crotch@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 day ago

        Outlook is a client, OWA is a web based version of that client. Microsoft is bad at names but I don’t see a problem with these tbh

        • Scrollone
          link
          fedilink
          English
          arrow-up
          2
          ·
          22 hours ago

          The new Outlook for Windows, however, is just the OWA inside of a glorified Electron app.

  • Singletona082@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    3
    ·
    2 days ago

    Thus the weakness of 365. No online? No office.

    I love the concept. I have for the past twenty five years, but for that same twenty five years we haven’t been THERE yet no matter the screeching about ‘boradband’

    If we were Japan or Korea… Maybe? But give me local within my personal network if not that device any day.

    • Xanza@lemm.ee
      link
      fedilink
      English
      arrow-up
      11
      ·
      2 days ago

      Microsoft would do _much better by offering a self-hosted enterprise model for businesses. They wouldn’t have to run all this fucking cloud infrastructure, and they wouldn’t be responsible for their cloud being down and stopping multi-billion dollar businesses from functioning.

      Business X can simply self-host their office suite and incorporate a VPN to allow tenants to connect to their sanitized local instance of office and access it through the browser. Realistically they’re half way there. They already have the application designed. lol

    • Squizzy@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      4
      ·
      2 days ago

      Their desktop apps suck though. Opening two ecels requires a fucking IT qualification. As in IT had to change admin settings to allow it to happen in our company.

  • ryper@lemmy.ca
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    2 days ago

    I guess that explains why the iOS Mail app asked me to sign into my Outlook.com account again. I switched away from the Outlook app last week and I was thinking the Mail app must only be able to stay logged in for a few days at a time.

  • Dempf@lemmy.zip
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    2 days ago

    I see a lot of comments in here against the cloud and saying that on-prem is better. My question is, why would on-prem uptime would be any better? Or is it more about a loss of control in moving to the cloud?

    • Clent@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 day ago

      On-prem allows you 100% control on the downtime. You build internal trust by deciding when to upgrade, availability of hot swap, rollback, etc.

      Cloud is just trust and it’s out of your control if they break that trust.

      • Dashi@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        1 day ago

        “Allows you to control the downtime”

        *unless your company infrastructure was designed by a 2 year old, you don’t have infrastructure admins that believe is still the wild wild west, and your Security team knows how to manage it’s av and doesn’t block the file servers

        • Clent@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 day ago

          All of that can be equally true for cloud infrastructure. There is argument that the cloud company is more incentivizing to use 2 year olds to save labor costs.

          In the cloud admin world, no one knows you’re a toddler.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 days ago

      The problem with cloud services is that you put all your eggs in one basket. Even if outages are less frequent, impacting more people at a time isn’t good. If most people use a handful of centralized services, those services become a larger target for hacking and DOS attacks.

      That’s why I like on-prem, generally speaking. It localizes the risk and prevents a cascading effect.

      • thanksforallthefish@literature.cafe
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 day ago

        Theoretically the major cloud providers like MS have redundant geographically dispersed servers that mean there should only be an outage if the individual user can’t reach the internet.

        In practise however those promises are hollow for a number of reasons, cost usually. Legal issues like GDPR also impinge (EU data being allowed to be in the US has been blocked by the courts the other day for example). In addition there’s a long list of other configuration reasons which almost always come back to cost indirectly.

        Theoretically an ideally configured cloud solution is far superior to on-prem.

        In the real world, not so much: corners cut, pennies saved by non technical managers not understanding the ramifications of their choices & etc

        On prem is certainly better in the real world if you’re big enough to afford proper redundancy and to hire and keep good techs.

        Many many firms can’t tick those boxes though and so you get to imperfect world optimisation where what is good for coy. A is bad for coy. B

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 day ago

          Sums up my thoughts pretty succintly.

          I’ll add one more: privacy. The more people rely on a given service, the more juicy it is to attack. On prem limits the attractiveness of your data, so you’re hiding in a crowd instead of trying to protect a single golden goose.