CloudServus is very proud to announce that they have attained Microsoft Gold Partner status in Cloud Platform, yet another milestone for the company to go along with their recent Gold Partner achievement in Cloud Productivity.
In the last blog post, we enabled FIDO2 security key logins with Windows 10 on our AADJ Windows machines, but users are still able to login with username/password. What if we want to enforce a FIDO2 Security Key or Windows Hello for Business login?
CloudServus is very proud to announce that they have attained Microsoft Gold Partner status in Cloud Productivity, yet another milestone for the company to go along with competencies in Cloud Platform and Small and Midmarket Cloud Solutions.
As you’ve probably heard, cyber attacks are up this year. But while big-name breaches tend to get the most attention, it isn’t just enterprise companies that are at risk. In fact, some hackers specifically target SMBs and mid-market companies, due to the lax security that many have.
Consider this: while many business owners rate cybersecurity as a top concern, only 57% have actually implemented any type of security plan.
2020 has challenged our customers to find new ways to reduce their IT spend. Cost optimization is at the forefront of our customers’ minds. Fortunately, there are many simple (and unrealized) ways to optimize your spend in Azure, and reduce the overall burden of costs in the cloud. See below for 4 easy ways to optimize your Azure Costs.
As companies like Yubico announce the next generation of YubiKeys with biometrics, let’s take a look at what is actually possible today with Azure AD Joined Windows 10 devices. Microsoft pushes us closer and closer to passwordless login options, but without a domain and GPOs available, some of our clients are left wanting. In this series of blog posts, I am going to walk through the setup of a FIDO2 device in Azure AD and Windows 10, and later apply Intune policies to alter login options.