Fischer Identity as a Service (IaaS) is an identity management solution from Fischer International.
N/A
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.
Fischer is well suited for the use case scenarios where an institution has not previously used any identity management and needs to quickly provide services to meet regulatory or other deadlines. It also works well when you can implement in smaller batches of user accounts and grow over time. We have found it less appropriate for cases where we have needed to set up on-off temporary or special access. Fischer has worked with us on out-of-band provisioning but we had to pay for extra Fischer professional services to make that work.
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.
Reducing the frequency (twice a month) of scheduled outages. But I believe they are making progress toward developing a more robust cloud infrastructure that will eliminate the need for such frequent downtimes.
There are some less than intuitive administration tools, which could be improved. Fisher is always willing to help us when we don't understand the proper way to configure using the tools.
I would like a streamlined way to move changes from our test environment into our production (live) environment instead of having to duplicate the effort.
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.
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.
It does deliver as advertised, provided you do your homework and understand the expected outcome before going live. Poor planning can turn the project into a nightmare. It can save the company a good deal of man hours and money by bringing about identity management automation, a self-service portal, and customizable email notifications for all of the identity owners and other stakeholders. For example, you can inform your HR team upon successful account creation and disablement. You can proactively reach out to users informing them about their account extirpation status, etc.
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.
Fischer has had a positive impact by providing self-serve identity and password management tools that our constituents can use at their convience, not tied to our operational hours.
Fisher Identity as a Service has been a significant cost, but it is anticipated that it saves our students significant time and effort that they can better dedicate to their academic pursuits.
Negative initial reaction--as this was a new way of doing things, there was a period of confusion among our college constituent that required additional communication and instruction
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.
