Passly from ID Agent, a Kaseya company and the service that replaces the former AuthAnvil, is an identity and access management (IAM) platform providing two-factor authentication, single sign-on (SSO) and password management.
N/A
Microsoft Entra ID
Score 9.0 out of 10
N/A
Microsoft Entra ID (formerly Microsoft Azure Active Directory or Azure AD) is a cloud-based identity and access management (IAM) solution supporting restricted access to applications with Azure Multi-Factor Authentication (MFA) built-in, single sign-on (SSO), B2B collaboration controls, self-service password, and integration with Microsoft productivity and cloud storage (Office 365, OneDrive, etc) as well as 3rd party services.
If you have a skilled IT support team (whether in-house or outsourced) that is familiar with Kaseya's applications and has a good relationship with the vendor, it may be a good fit. It "checks the box" for 2FA, but there are much simpler solutions out there today that can get the same job done with less complexity and, in many cases, at a lower cost.
Definitely well suited for enterprise identity management. Just makes sense to use that tool because it's been the standard for so many years. Businesses that may not be ready for an enterprise level product might not be for them just due to cost. So there might be some more cost efficient and effective ways to perform the same tasks.
It addresses the issue of identity management very well with respect to putting in that multi authentication.
It can also support with respect to we can push these policies into another product that is not Microsoft, but it needs that SSO so we can have one account going into multi different accounts. I think that's the biggest pros and the easy use of Microsoft 365 also is one of those pros also in terms of administration.
Well, I'm an active ad admin, so there's a lot of features in active directory that Entra ID seems to be just adding now. We're kind of figuring out that the policies are different than Entra ID that they were in active directory and we're finding other products to do that, like Azure policy. Some things I'm used to seeing in identity products or like active directory aren't in Entra iID, but are doing good job of managing stuff that it does so far.
MSFT Entra ID has been essential for managing our geographically dispersed team. We're confident that it will scale with us as grow, and we'll be able to take advantage of additional security and ID management features as they become necessary. Being able to centrally manage our user access from anywhere with a small support team is such a relief.
Very easily usable. It could be easier to use. Implementation was kind of tricky. We do run a hybrid environment, so we're syncing a local active directory instance with Entra ID, so that could be a little tricky. But outside of that, if you're not running a hybrid deployment or a version of Entra ID usually, it's pretty straightforward.
They are very helpful with helping us with any issues. There are a lot of helpful guides online if you get lost. Kaseya is also good about not bugging you with notifications. Kaseya offers easy to access to support options. Overall I have not had to contact them over a lot of issues. The software rarely broke or was down for maintenance.
I have not needed to engage support for anything at this time. I have been able to find the answers either online or in a knowledgebase. I tried to skip the question but it would not let me, so I rated a 9 based on other interactions with Microsoft support I have had
Make sure you use a good partner. Our implementation was a bit longer and more problematic than we expected. Our partner got it done, but, in my opinion, some of their inexperience and staffing issues were evident.
I selected Passly at first as it would allow for a single sign on with azure to Kaseya VSA. Kaseya has made access to different products very different. VSA does not have single sign on with Azure where as Vorex/BMS does. This is a feature that Kaseya should make unified accross all applications.
For us, it was a natural evolution of our use of active directory. As we went from on-premises to the cloud, this was an easy extension of our authentication infrastructure. We looked at other products from Oracle, so Oracle ID, Oracle Identity Management. We looked at pink credit for single sign-on. It was just everything was built into Entra ID. Both internal use cases and external ones.
Microsoft Professional Services' technical knowledge is appreciable as consultants design the solution as per customer requirements. Mapping of features per user specifications and assisting Customer IT engineers to implement so they can manage and administer the services.
I think it's had positive. It's enabled us to make authentication easier and more streamlined across the organization from frontline workers to back office workers.
It's allowed us to really adopt authentication policies and methods that suit that user and their work environment.