Automox is an endpoint management platform built for the era of autonomous operations. It provides a cloud-native foundation that unifies automation, speed, visibility, and trust.
$1
per month per endpoint
Microsoft Entra ID
Score 8.9 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.
$6
per user/per month
Pricing
Automox
Microsoft Entra ID
Editions & Modules
No answers on this topic
Premium P1
$6.00
per user/per month
Premium P2
$9.00
per user/per month
Offerings
Pricing Offerings
Automox
Microsoft Entra ID
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Automox can patch macOS, Windows, and Linux endpoints with PatchOS, an offering at $1 per endpoint/ month with an annual commitment.
The Automate Essentials or Automate Enterprise packages are for scaling IT automation, endpoint configuration, and software updates.
Modules are available with Automox Assist, a one-on-one remote endpoint control and assistance for helpdesk technicians.
Automox shines because it's compatible with all 3 major OS types (Windows, macOS, Linux). Jamf is a standard across the industry but it only covers macOS and iOS devices. If you have a mixed environment that will often leave you wondering how you cover those other devices, this …
Smaller organisations such as ourselves, who have outgrown their MSP but still need to retain control of their system and have visibility of the estate. The tool enables us to have real-time visibility and deploy or remediate as needed. We have also purchased Rapid7, which integrates natively into the product, making it a more powerful tool moving forward.
It is especially good for organizations that are otherwise in the Microsoft ecosystem (Microsoft 365 applications). Microsoft Entra ID is really well supported sign-in method in various SaaS-applications and they often have step-by-step guides how to deploy the SSO with Microsoft Entra ID. It's less suitable for organizations that might use other productivity tools than M365 or do not have Windows-based computers.
Single Sign-on helps ease the user experience, allowing users to avoid typing multiple passwords.
The identity and management are straightforward to use and easy to connect to other applications, as well as third-party applications.
The support of remote work. Nowadays, many people work from home and need to access their accounts. Microsoft Enterprise ID gives secure access to the company data.
Server patching orchestration. There is no way to patch and reboot systems in order of importance, such as database servers before application servers.
Worklets for patching .net core and similar.
Worklets for removing unwanted Java installs or other unwanted software.
Integration with Tenable Vulnerability Management.
AI script development should be included at no additional cost; GPT or Gemini can be used instead for free and pasted into Automox. Why charge when others are free?
Official worklets are slow to be added or updated.
Probably the most primary thing is just the interface itself. It's frequently changing and so oftentimes we kind of have to go back and redocument our processes for our IT staff because the steps that they would take to perform a task one month. Now it's a totally different staff, new dashboard, even a new name for the product or the feature. So it would be nice if that stuff was a little bit more consistent.
This is a software that just works. Once configured its a set and forget kind of tool that keeps things up to date and alerts me if something is wrong. I was able to work through an expansion project to deploy an additional 500 devices in almost no time and create a robust self-patching environment.
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.
It truly functions like a single pane of glass. While our use case is for EC2 instances in AWS, it can manage endpoints across all clouds, or even deployed hardware (laptops). We do manage instances in multiple AWS accounts and there is no set up required between orgs. This accomplishes our needs for real time tracking, and historical reporting for all of our in scope resources.
I mean it's pretty good. It is click, click. I mean, oftentimes I can go to the expert or layer two support to get help. Suddenly I go to them. So it has to be pretty useful to be honest. I do a lot of, and there's a lot of, you could do research quickly online to find out how to do certain things. I think that's the only thing we can improve to in terms of kind of a best practice path is setting up it. But because I'm it profess of tons of years in co-management services, I can figure it out. But for others they may not be able to figure it out. You still need an IT person of course to translate all of that. But to me pretty straightforward. I come from the days of directory from 2008, 2000, Microsoft server 2000.
I did not need to reach out to support often but when I did the answers were relatively correct and they were answered quickly. The only thing I might "ding" their support on was their lack of understanding of OS's different from Windows and especially Linux. Other than that I was satisfied
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
Implementing Automox successfully starts with a clear strategy for organizing and grouping devices based on operating systems, environments, or business criticality. This ensures that patching and configuration policies can be applied with precision. A phased rollout approach is essential—beginning with a pilot group allows teams to test patching schedules, reboot behaviors, and custom Worklets before scaling across the organization. Leveraging Worklets from the start can significantly boost automation by enforcing security baselines and performing routine system tasks. Integration with existing SOC tools, such as SIEMs, enhances visibility and response time by correlating patch compliance with threat intelligence. Additionally, aligning patching schedules with operational downtimes minimizes disruptions, and consistent monitoring and reporting helps maintain compliance and prepare for audits. Overall, Automox offers a streamlined and effective solution, but its true value is unlocked through thoughtful planning, testing, and integration with existing IT and security workflows.
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.
All of these other products are overly complicated with user interfaces that are not very friendly.. too technical, even for IT pros. They are also expensive for smaller companies or those with limited IT budgets. I've found that these other solutions are really geared for larger enterprises more than small to midsized companies, which is fine... but then they tend to market themselves as good for everyone, when they are really not.
We've used other Microsoft products and we've also used some standalone products, like each application you can have its own identity, so we've looked at some of those too, but we try to use the Entra ID as much as possible because it offers a wider range of reliability.
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.
Patches are now fully up to date and we have no longer been dinged for it from our pen testing partners.
Reduced man hours spent on maintaining an update server and the hours spent looking at each machine to ensure it patched all software both windows and third party.
Allows for us to provide a vendor with a means to connect to our systems without the use of a VPN.
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.
