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
Tools4ever UMRA
Score 9.0 out of 10
N/A
New York software company Tools4ever offers a suite of identity management and access (IAM/IdM) tools, for single sign-on (SSO), password management, access control and authorization, and more, with the User Management Resource Administrator, or UMRA.
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.
It is very well suited for tying multiple systems and services together, allowing for exchanges of information and account management. I'm not sure of instances that it is not well suited since solution was recommended by folks in education. With that being the case it suited our needs quite well.
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.
Imports students and staff into our Active Directory and email system.
It manages those same accounts, disabling accounts for folks who have left, and creating "Windows" when accounts should be enabled.
It interacts with our Microsoft AD and our student management software seamlessly. Once accounts are in our AD environment, our student management and other systems create new email accounts automatically for us.
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.
We have been attempting to get single sign on for students, so they have the ability to change their passwords on their own. The documentation of this process is very dated, and often support isn't even aware that their site issues/ references those older documents.
During the initial buildup of our server Tools4ever UMRA support was a bit hit and miss, but I will say our ongoing support has been very good.
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.
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 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.
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.
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.
We save considerable work hours by a multitude of staff having the system manage and generate accounts for us on a daily basis.
We have some peace of mind knowing accounts for staff and students who leave our district can no longer gain access to our systems because it automatically disables those accounts.
Because of the way the system interacts with input that is put in, it automatically creates logical positions which dictate different levels, meaning it automatically sets up when staff gain access and lose access depending on the position they are filling.
