Microsoft has announced they are taking action to force organizations to improve security posture by deprecating basic authentication in Exchange Online effective October 1st, 2022.
Have you heard the news? Windows Virtual Desktop (colloquially known as WVD) is now Azure Virtual Desktop (AVD). Microsoft announced the rebranding on June 7, 2021, about 21 months after making WVD generally available at the end of September 2019 (uncanny timing, given the start of the COVID-19 outbreak and the corresponding shift to remote […]
Microsoft is adding extra security and management functionality into their Intune and Enterprise Mobility + Security E3 (EMS E3) offerings and will increases prices starting July 1st, 2021.
A new wave of funding has been approved for the federal Paycheck Protection Program (PPP-2). This new program includes a provision that increases flexibility with non-payroll expenses, such as cloud investments and software upgrades.
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?
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.
For our customers under 300 employees, Azure Active Directory Plan 1 is coming to M365 Business Premium.
Licensing for MFA, Conditional Access, and Risk-Based Conditional Access has been coming up in many of our conversations.
Previously when creating queries for dynamic membership rules in Azure AD, you would have to create the group, then provide the syntax, and then wait anywhere from 5-10 minutes while Azure AD evaluates the group members. When first starting out, this can add up to hours of timing waiting for results.