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 External ID
Score 9.3 out of 10
N/A
Microsoft Entra External ID (formerly Azure Active Directory B2C, or alternately, Azure Active Directory External Identities) provides business-to-customer identity as a service. Customers can use their preferred social, enterprise, or local account identities to get single sign-on access to applications and APIs.
$0
per month per active users
Pricing
Passly by ID Agent
Microsoft Entra External ID
Editions & Modules
No answers on this topic
Premium P1 (for More than 50,000 MAU)
$0.00325
per month per active users
Premium P2 (for More than 50,000 MAU)
$0.01625
per month per active users
Offerings
Pricing Offerings
Passly by ID Agent
Microsoft Entra External ID
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
A flat fee of $0.03 is billed for each SMS/Phone-based multi-factor authentication attempt.
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 …
Google's Authenticator app is easy and streamlined, like much of Google's products. The home screen shows you the security code and how much time is left. Kaseya's AuthAnvil requires multiple clicks to even reach the security code, and only has a progress bar that lets you …
Kaseya’s products have a lot of features to them that help an MSP do their job. Accessing and getting to them is a lot easier with AuthAnvil. It’s secure and easy to use. Atera has a similar design, but overall you don’t come close to Kaseya’s products. I often found myself …
We have transitioned our Multi-Factor authentication processes to use either Authy, Duo, or Microsoft Authenticator, depending on the application use-case. We still have some clients using AuthAnvil, but it is no longer our preferred application for MFA. The other offerings in …
I am currently testing Okta as well. Okta seems to have a lot more functionality. They have integrations with mostly every SaaS around. They have a smoother Windows 2FA that includes push notifications and Yubikey integration. AuthAnvil is the only 2FA service available for …
We are pretty satisfied with the features and price of Kaseya. It's easier to deploy than say Entrust or Symantec. What really makes it stand out is the integration with the overall Kaseya environment and managing everything from one pane of glass.
For us as we already used microsoft platforms it made perfect sense to remain within one eco system rather than split external ID systems if we could. We did however look closely at AWS as a comparison and chose Microsoft Entra External ID based on our end users (familiarity) …
Microsoft Entra has much more advanced features than Amazon cognito. The access permission feature, mfa, data protection is top notch. Amazon cognito does offer MFA but the security access feature is not very great. The Microsoft Entra offers a wide selection of access …
Each one of these alternatives has pros and cons. PingOne from Ping Identity states they "help deliver the secure and seamless customer experience to win battles for customer acquisition, retention, revenue, loyalty, and trust." While that may be the case, they did not fit our …
From my experience, Kaseya made a mistake with Passly. It does not work correctly. When it does work it is very delayed causing issues for logging into the system. When Kaseya was contacted they could not find users at all. When they finally found the users they could not edit it needing them to escalate to development to fix accounts.
It is not easy to calculate the actual ROI due to the difficult quantification of all factors, but it certainly contributed a lot in protecting, monitoring and controlling access to our system. It also made it much easier to detect vulnerable external users with simple and "easy to hack" passwords they use on multiple apps.
One of the things that Microsoft Entra External ID does really well is creating user logins, accounts and profile. It is very easy to create them, manage them and delete them. It is fast and reliant.
Limit access or authorization feature. We can allow different levels of authorization and access. So that not all the employees would have access to all the data. Only some relaible employees would have access and power to change anything.
Mutli factor authentication feature is also a really good feature to secure data. Even overseas vendors need MFS to login which gives double protection to our data.
Microsoft Entra External ID is an all round solid product, and certainly delivers the solution to our needs well. Through use we found that Pupil's become 'experts in avoidance', if they can forget their login details or indeed their device used for MFA, they will and then use that as the excuse for not accessing/completing their assignments. If more MFA options were available (such as delegated MFA) this would really help iron out our entire end user experiences
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.
We have transitioned our Multi-Factor authentication processes to use either Authy, Duo, or Microsoft Authenticator, depending on the application use-case. We still have some clients using AuthAnvil, but it is no longer our preferred application for MFA. The other offerings in the market fulfill the same requirement with either lower or no additional cost and are easier to manage and more consistent in their performance.
For us as we already used microsoft platforms it made perfect sense to remain within one eco system rather than split external ID systems if we could. We did however look closely at AWS as a comparison and chose Microsoft Entra External ID based on our end users (familiarity) with microsoft authentication and deployment routines. We also found that Microsoft gave more sovereignty assurances with our data.
Using AuthAnvil to log into Kaseya VSA multiple times was definitely a loss in productivity.
AuthAnvil did provide lots of security for our products because everyone would be deterred by AuthAnvil and Kaseya VSA's labyrinth-like log in process.