Microsoft Identity Manager Reviews

We use Microsoft Identity Manager for application identification and single sign-on processes for different applications.

The product allows us to track the logins easily. We can find out if someone is trying to attack Boot Guard.

The product's pricing and integration features could be improved.

We have been using Microsoft Identity Manager for a couple of years.

The product is 99.9% stable. Although, sometimes, internal configurations or improvements made in the vendor's system may cause an impact on our systems as well.

I rate the product’s scalability a ten out of ten.

I rate the product’s initial setup process an eight out of ten. We encounter difficulties integrating legacy systems with the product in Azure environment. It takes a few weeks to complete the process.

It is an expensive tool.

Microsoft Identity Manager has good functionality, but its pricing is too high. I rate it an eight out of ten.

We are currently using a hybrid identity access management solution. We've got an on-premise ADFS that is running a Server 2016 ADFS farm. That is coupled to a Microsoft Identity Management Server 2016, which is then coupled to Azure Active Directory as the cloud-based identity and access management solution.

We're a partner and a reseller. We're a Microsoft Gold Partner and Cloud Platform, and we have achieved the Microsoft competency at the highest level due to our commitment to delivering successful solutions in both on-premises and cloud-based environments. So we are a Microsoft delivery partner and a Tier 2 reseller. In other words, we're reselling Microsoft licenses. 

We're also a deployment partner for Microsoft services, meaning that we can deploy services and migrate customers and design solutions and be involved in adoption and innovation programs on behalf of Microsoft. So we're a big partner in Microsoft solutions.

The feature that I find most valuable is the security layer of the identity and access management solution. The ability to secure on-premise and cloud-based workloads and to provide seamless authentication into hybrid workloads. In addition to cloud-based authentication, we've also got advanced adaptive authentication with a privileged identity management feature for protecting identities.

In terms of the identity and access management solution for an on-premise environment, I think Microsoft needs to eliminate or minimize the number of workloads for the solution to run in an on-premise environment.

For example, you need more instances, more servers on-premise for the whole solution to completely function. You need ADFS servers, farms application proxies, a MIM server, SQL databases, and Cluster databases, which leads to more costs in running and maintaining the solution.

I think Microsoft should minimize the number of instances in terms of hardware and software.

In the next edition, I prefer that Microsoft would start looking at giving the solution the ability to integrate on-premise workloads, specifically Linux on-premise workloads, with the cloud-based identity and access management solution, which is Microsoft Azure Active Directory. Currently, the provided Microsoft identity and access management solution does not have the capability to integrate with a Linux or Unix environment and the cloud-based Azure Active Directory.

I'm satisfied with the stability. It is quite stable these days because Microsoft updates all of its identity management solution technologies monthly. In terms of stability, I'm quite impressed.

I'm not quite impressed with the scalability of the solution, because you need more workloads in terms of scalability. For small businesses, I wouldn't recommend the Microsoft identity and management solution for on-premises environments for SMBs, because they won't see any return on investment since they will still need to invest in hardware, which is quite costly, and also in software. Maintaining the solution in general also requires more workload and instances to operate, so I wouldn't recommend on-premises environment for small businesses.

That is why most of my customers are enterprise customers. They will be best with a complex environment. Specifically, they will have hybrid environments that are running the on-premises MIM, Microsoft Identity Management.

For cloud-based identity and access management solution for Microsoft, specifically the Microsoft Azure Active Directory, it's an excellent solution for small businesses. It's excellent and it's easy to scale because you don't need to be an enterprise business to protect your applications with Azure Active Directory. It's quite good for cloud-based environments.

They provide excellent support. Now when you log a call with them they engage with you until they resolve the solution. They give you a dedicated engineer, a PSE specifically, to come and correct any issues.

To be honest, the on-premise configuration is complex. You need to know what you are doing to successfully deploy the solution. You need components such as an SSL certificate. Also, you can't use a self-signed certificate. You need a certificate with a publicly known CA, such as GoDaddy or DigiCert. Additionally, you need to configure your application proxies, all your ADFS and MIM servers, and also the database servers correctly. It's quite complex, you need to know what you're doing in terms of getting the solution up to speed.

My advice to someone implementing this solution would be to implement the on-premise identity and access management solution if they've got more than 1,000 identities on-premise. I strongly recommend implementing an on-premise environment in that case, or if they are a financial institution, such as a bank or underwriting institution. They also should implement the hybrid deployment, which means there would be an integration of the identity management solution sitting on-premises and a combination of the Azure Active Directory as an identity and access management in the cloud-based environment.

For small businesses, I would recommend that they implement the cloud-based identity and access management solution, leveraging the provided Azure Active Directory by Microsoft.

I'd give Microsoft Identity Manager a rating of nine out of ten. I'm giving it a nine because I'm looking at the hybrid scenario and more strongly on the cloud-based identity and access management solution for Microsoft. It has a lot of features; it has all the bells and whistles of identity and access management, such as adaptive MFA, intelligent graph security API, and being powered by Microsoft Graph API. Also, the multi-factor authentication is easy to set up, with a single button. For Windows environments, you just install one application API, called AD Connect, to sync all the on-premises identity to the Microsoft Azure Active Directory.

The reason why I'm not giving it a ten is that they still need to upgrade their solution to enable a new feature to accommodate Linux and Unix identity directory specifically to integrate with Microsoft Azure Active Directory. It seems as if the company does not want to provide that capability because now they are focusing on growing their own Microsoft Azure cloud, which means they are forcing all those customers that are running the Linux or Unix environment to come and migrate or lift and shift all their Linux or Unix workloads into Microsoft Azure. I think they are focusing on growing their own environment, which is why they are not providing this capability.

MIM allows for easier provisioning of Outlook mailboxes.

MIM's most valuable feature is its connectivity with Exchange.

MIM's reliability could be improved.

I've been using this solution for ten years.

MIM's stability is excellent.

MIM's scalability is excellent.

Microsoft's technical support is excellent.

Positive

We used SailPoint previously, but MIM is cheaper and easier to administer.

The initial setup was complex - I would rate the setup experience as two out of five.

We deployed using an in-house team, which took six months.

MIM gives a high return on investment.

MIM is free with a Microsoft Azure license.

We evaluated SailPoint and NetIQ.

I would give MIM a rating of ten out of ten.

We use the solution for authentication management.

The product’s simplicity and integration are valuable. All the accounts are linked to Microsoft.

The security could be slightly improved.

I have been using the solution for two years.

I rate the tool’s stability an eight out of ten.

There are more than 100 users in our organization. I rate the tool’s scalability an eight out of ten.

The support team is quite knowledgeable. Getting a support person is quite challenging, though.

Neutral

I rate the ease of setup a seven out of ten. The solution is deployed on the cloud. It took us a few days to deploy it. Multiple business, technical, and security teams are involved in the deployment process.

The product helps us save 10 to 20% of our time.

The solution is expensive. I rate the pricing an eight out of ten.

I recommend the tool to others. Overall, I rate the solution an eight out of ten.

I have an ongoing project with my clients that encompasses research.

Hypbrid cloud is the major case, also some on Mobile Application developing.

Customer point of view, MIM work as / or together with SSO to extend the authentication, empowers orgnization agility by adopting new apps faster 

Identity 
Security 
Access Managment is the three I can think of. why? they transpass the hybrid barrier, and it's from Microsoft, fits in M365 applicaiton well

The product could be more friendly for non-native English speakers. It would also be better if it were more intuitive and visually attractive.

Microsoft Identity Manager was designed for the on-premise environment. If you want to implement a cloud-based application, so you will run into some problems, including the transport of the token from the applicant, the application side, the mobile application side through the firewall, and the transfer to the backend for authentication. That part is not quite convenient. It is very slow.

I have been using this solution for a few years. 

It is a stable product. You will experience some issues with it, but it's a good product. Identity is a complex thing, multifactor authentication is yet another, what add on this complexity is the wild Internet, if you focus enough，MIM or AAD will be you best choice. 

Microsoft Identity Manager is a scalable product. It allows for multiple users that can work together.

The primary use case is for the single migration of the user from on-premises to Azure Active Directory in the cloud. It is also used for the Microsoft authentication application for mobile devices.

We authenticate on the smart device back to back so they can access their emails and other applications.

We are planning to use this for the Windows 10 authentication as well as directly from the Azure Active Directory.

The most valuable and most interesting feature is the conditional access. 

It can provide a low formulation combination based on the extra files that we can work on to verify the solution.

The information that is available for the Active Directory portal is segregated here and there. It's not in one single location where you can see, for example, all of the security features and maybe the customization feature.

In the next release of this solution, I would like to see the manageability, the web-based access to the portal, and the reconfiguration of things to be made simpler and more straightforward.

We have been selling this solution for the last five years.

It's stable, but it's maybe a bit more challenging than I have seen in the last five years.

This solution is scalable. We have plans to increase our usage in the future.

The number of users varies. There can be anywhere from 10,000 to maybe more than 100,000 users, who are made up of IT, administrators, managers, and architects.

We have been in touch with technical support. They are good. Normally they are available to assist and they are knowledgable.

Our previous system was based on an on-premises solution. Now, the on-premises products are integrated with the cloud, which is what made the difference.

The initial setup is straightforward and can be deployed in one week.

It was installed by my internal team.

I would say that it's the best solution on the market and I would go ahead with it.

I would rate this solution a nine out of ten.

There have been only two, maybe three projects related to this product. The challenge with obtaining information about these projects is that we focused mainly on designing the solution. 

The customers did not want continuous involvement in the operations because they couldn't see immediate results. So, we started with initial contact and face-to-face interviews to understand the organization's structure. Then, we began integrating the solution, including the site-based aspects and the schema for the metadata directory, which is essential for working with other components. 

However, the time spent designing and integrating the identity solution is a challenge. The deployment process is not quick. In the best-case scenario, it may take around six months before you see some tangible results at the beginning of the implementation of the identity solution.

The concept is primarily for the people in the business. In business, you can discuss how integrating all the services and resources within the company can bring numerous benefits. It involves having an integrated persona in the organization, not just in technology but throughout the company, including resources, printing, Salesforce, and office.

The problem lies in how to convey these ideas within each department. For example, the technology department might say, "No, this is an accounting problem because it's related to the accounting system." And the same goes for other departments like human resources. These are the kind of challenges we face when trying to integrate all the components within the company. We need to communicate with individuals about the benefits of identity, which are clear to project managers. We have executive support internally, but the challenge lies with the employees who don't see the benefits because they might be long-term or not immediately apparent.

I always appreciate products that provide technical information. It would be helpful to understand what's happening behind the scenes, such as log information. It doesn't need to be extensive, but it should show the process and provide insights. For example, in any Identity Manager software, having a console that displays the ongoing process helps identify any issues. Once you stop the process, you can refer to the problem and determine which system it's related to. This is very useful.

In the case of Microsoft Identity Manager, it would be beneficial to have a similar process where each stage of the process is clearly documented. For example, if there's a problem with communication between the identity manager and the human resource services when requesting a new account or adding a profile, having visibility into the systems involved helps identify the root cause. It could be a problem with the sales system, even if the product itself is not the Active Directory server solution. Understanding the connection and how to resolve the issue is crucial.

It takes a considerable amount of time to reach the right person and truly understand the problem. Especially in different regions, the problem may appear different but actually be related to another underlying issue. Support personnel with experience can identify such cases and provide effective solutions, but it can be time-consuming to reach these individuals, sometimes taking two or three hours on the phone. This can be challenging when the issue is affecting production. Reaching out to the support can be complex. For example, when dealing with Active Directory, there are ways to gather information and create reports, but they may not always be effective in certain scenarios. You often need to gather information from different sources, compile it into a document, and explain the problem, its identification, the solution, and so on. It's an ongoing process with multiple steps.

The setup was difficult. The deployment process is not quick. This is the case not just with identity solutions from Microsoft but also in general. There haven't been many implementations or opportunities for identity solutions in Mexico. The projects haven't been successful as they want to see quick resolution and benefits from the solution. Implementing identity solutions involves understanding the organization, integrating various systems, validating security components, and addressing other challenges.  People often feel frustrated because it takes a significant amount of time during the planning phase. There are no significant issues. The main problem with Microsoft Identity Manager is related to identity requests or similar matters.

Moreover, maintenance depends on how the project is initiated because I don't provide extensive support after the implementation. But initially, around five individuals are involved in a company with items, persons, and employees. In the beginning, there were only five products published in the shopping cart, and users can request services or access to systems such as accounting or similar programs. I don't recall the other programs, but there were only five initially. The problem arises when it comes to budget constraints. We publish five products internally and integrate with three systems—human resources, accounting, and IP directory— but there are more systems in existence. We try to create and extend the solution, but the customer needs to assign dedicated personnel to ensure the continuity and smooth operation of the solution. This becomes problematic because they usually reach out to us when they encounter issues like communication problems or misconfigurations. Maintenance or system upgrades are not the primary reasons for their calls.

I have experience with Microsoft Identity Manager as well as the Identity Manager from Quest Software, which was previously owned by VMware.

Overall, I would rate the solution an eight out of ten. However, my experience is based on the planning stage because we haven't had the opportunity to implement it.

We use the product for identity management. It stores organizational data, including contracts we generate using Active Directory.

The product’s most valuable feature is stability.

Microsoft Identity Manager could be more intuitive in terms of interface. Also, the product’s life cycle is very short. It is going to expire soon. It becomes tough to manage projects in this case.

We have been using Microsoft Identity Manager since 2016.

It is a stable product.

It is a scalable product.

The technical support services are average. They should improve the response time.

Neutral

The initial setup is complicated. It doesn’t have a modern GUI, making the process difficult. It takes one and a half years to complete. It requires one executive for maintenance.

I rate Microsoft Identity Manager a six out of ten.