Does US Cloud Support Every Microsoft Technology?

Reality Summary

• Wide Ticket Technology Resolution: US Cloud resolves issues for all Microsoft products
• Senior-Level Expert Staff at First Interaction: Every technical point of contact at US Cloud including TAMs, engineers, and DSEs have an average of 15+ years of experience
• Eliminate Issue Repetition: Talk to senior-level experts who understand your Microsoft environment and issues the first time

Evidence: US Cloud Expertly Supports Any Microsoft Technology You’re Using

What makes US Cloud different is this: senior-level Microsoft-certified experts who become familiar with your IT infrastructure. This combination of expertise paired with long-term relationships means fewer interruptions and more uptime, even when one of your Microsoft products experiences an issue.

The best part? We won’t try to sell you more Microsoft products to solve your tickets. Our wealth of expertise allows us to focus on actual support for all Microsoft technologies—not sales. Check out the evidence below to see more about everything we cover.

Client Validation

 

US Cloud’s Critical Incident Response Team mobilized within hours of the CrowdStrike outage, delivering fixes up to two days faster than Microsoft and helping clients restore operations amid chaos.

See How US Cloud Led Clients Through the CrowdStrike Outage

When the client, a state-level governmental institution, encountered a critical application issue, their expectation was quick resolution. What they got from US Cloud was far more: a relentless, all-hands-on-deck approach that didn’t stop—even when the problem turned out to be outside Microsoft’s domain.

See Case Study: When Every Minute Matters, US Cloud Stays Until the End

For my team, the proactive work from US Cloud has been key. One of my admins manages SCCM but isn’t an expert, so he relies on US Cloud’s SCCM experts when updates roll out. That proactive support prevents issues before they happen, which could otherwise be very disruptive.

See Client Conversation: Amedisys (Revisited)

As for the experience of opening up cases through US Cloud, I haven’t heard a single negative thing from any of the members on our team or anyone else who we provided the service to within the University. It’s all been positive feedback.

See Client Conversation: Brown University

I just had a case the other day. I turned off a server that we all thought wasn’t doing anything, and it had a small role that got missed. Unfortunately, it wasn’t something that was easy for me to recreate and there was a little bit of documentation, but it was woefully out of date. So, I called US Cloud…I got a call back in 15 minutes…So he starts that ball rolling. I get another call back 20 minutes later from US Cloud with an idea they want to test. Then, less than an hour later, I got a call saying that it’s all successful. They’ve tested it. Everything’s good.

So, we knocked it out together and it worked perfectly. Six hours later, I got a call from Microsoft. I could barely hear the guy. He was asking for my permission to close the ticket because he couldn’t get permission from his manager to close it. Then he said that we needed to sit down and have a conversation around it. I just hung up on the guy, because, you know, I didn’t care about it.

He then called me back three separate times, before finally calling me from a working phone. He brought the manager into the loop and at that point we were able to successfully close the ticket, that they didn’t have anything to do with, which was solved by US Cloud five hours previously.

See Client Conversation: Aegion

We had an outage with our Azure tenant that was affecting a host, impacting several of our healthcare customers that we provide services to. And it just so happened that when the outage occurred the traditional people who would jump on it, what we call a SEV, weren’t there (we’re an ITIL framework kind of company so we follow incident management response which we have on-call rotations and people jump on bridges and we get the problem remediated)…I went on the portal and popped a ticket for a critical customer outage.

And within an hour, within an hour, US Cloud responded with four engineers. So not only did they bring the right guys to the call, but they brought the cavalry. And it was great because we needed that diversity because it was a unique problem, in the end, and the root cause was a combination of like a firewall rule change and a load balancer that sat in the cloud combined with some ACLs. So we needed a couple of different subject matter experts and they got to it, remediated it, and the service was up.

And I just felt like, wow, that was amazing. That was unlike anything I had experienced with Microsoft in my eight years of being with Premiere, so I was like…we made the right choice.

See Client Conversation: Bottomline Technologies

We use SharePoint, originally SharePoint 2010, and we migrated our 2010 environment to SharePoint Online. And along with that came all of the workflows and everything else. In 2019, Microsoft started warning us about the end of support for those SharePoint 2010 workflows, so we immediately called them. I don’t have a SharePoint person on staff, so I called Microsoft and I said ‘I’m gonna need some help’.

Microsoft spent three years on this. And we used all of our support hours before they were able to fix it. I basically ran out of hours and then they gave me grief about this wasn’t break-fix.

So we moved on to US Cloud. With their support, when Microsoft finally shut down access to that 2010 workflow we had one, just one, e-mail that wasn’t getting sent out and that was just a bug in the code, but everything else worked seamlessly. Approvals were there, the sites were created, the permissions were created, everything was phenomenal.

So it was a phenomenal experience. I can’t tell you how great it was to feel like somebody was putting me first. You just don’t get that from support these days.

See Client Conversation: Parkland Health Hospital System

I remember the US Cloud engineer at the time. All of our domain controllers were built on something with no GUI, no graphical user interface. So, it’s a lot harder to troubleshoot on that, and he was able to get in there and work in core. He was able to get in there and resolve the problem using basically PowerShell commands and get us back in working order.

See Client Conversation: Saint Louis University

At one point, we had some operational problems with the Windows Server, but it also involved Cisco, and our US Cloud engineer was able to work with the Cisco engineer. There was no problem having multiple companies on the phone. Nobody said, “well, it’s Cisco’s problem.”

See Client Conversation: Saint Louis University

It has been so helpful to be able to talk to the technicians and work with them from the beginning. And one of the other things, too, was that everything’s based on hours, so we could get training out of our hours. It’s nice to know that we don’t have to go spend additional money if we just need some assistance and training.

We just did a security assessment on our Office 365 platform that just came out of our hours. So, things like that, it’s just definitely been a benefit with the switch to US Cloud.

See Client Conversation: TrueBlue