The initial setup for Microsoft Identity Manager is quite straightforward. It comes with a default configuration, and you can start using it right away. You don't have to implement anything from scratch. Instead, you can enhance it by defining new policies to meet your organization's specific needs. It is a user-friendly process, and you can get it up and running without a lot of complex implementation steps. Setting up Microsoft Identity Manager usually takes a few hours for the basics. However, the total time can vary a lot. If your company already has clear policies, it's quick. But if you need to create new policies, it can take longer. The time needed depends on how well your company's policies are defined and how fast you can integrate the solution with them.

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.

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.

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

The initial setup is quite straightforward. It took us about a month. Our internal team was responsible for the implementation ourselves.

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.

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.

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 didn't participate in its implementation.

The setup is not difficult, although in my experience sometimes I ran into situations where I had to deal with a number of bugs. With five being difficult and one being easy, I would rate this solution a two point five in terms of setup, configuration, and implementation difficulty. The solution requires patching or tweaking right away, and configuration requires some level of experience.

The initial setup is simple because a lot of the configuration comes from the on-premises Active Directory. It connects to various other components. If your device has to be enrolled then it is a bit complex, and you need expertise on that.

If we compare Microsoft Identity Manager to a cloud-based identity management solution, the initial setup is complex. 

If you compare Microsoft Identity Manager with Okta or OneLogin and the direct cloud solutions, these are all fast solutions awaiting only minimal configuration. The number of companies for which we uniquely install Microsoft Identity Manager is a little more than what we allocate fact-based IDM solutions for overall. 

Deployment depends on if the customer requires high availability and disaster recovery strategy, or the number of applications that we need to integrate.

The time that it takes to deploy the solution, integrate applications, and configure the dynamic overflow typically takes around three months. 

The deployment requires a minimum of three months and sometimes it can go up to six months. 

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

Its setup is straightforward.

The initial setup was straightforward.

The difficulty of the initial setup is always different. It depends on which application you deploy. Some are complex, some are straightforward. If you're deploying Microsoft XG, it's quite straight forward. If you're deploying something like MGM it's a little more confusing, and you always need somebody to help you to be able to do that. SharePoint is also a little bit confusing to handle. 

Likewise Identity Manager looks a little more confusing in terms of its implementation process. There are other products from Microsoft that are more straightforward to implement or deploy, however.