Initially, the setup was complex because there was a learning curve, so the team did hit some issues with the integrations and making it work seamlessly. It was not simple but not complicated either. The solution was deployed in a week.

The initial setup is easy. It took 15 minutes to activate the account.

The product’s installation is straightforward.

The initial setup was quite complex, mostly because we have 32,000 users worldwide. Deployment took us about two years.

The solution's initial setup wasn't very easy.

The product's initial setup phase was very simple.

The solution is deployed on the public cloud.

Google Cloud Identity's setup phase is just a part of a larger setup process of Google, which doesn't take more than 30 minutes.

The initial setup of the instance was straightforward.

The initial setup is simple. You need a verified domain. I would rate my experience with the initial setup an eight out of ten, where one is difficult and ten is easy. 

The initial setup is straightforward and simple.

It took less than a month to deploy and only requires one person to deploy and maintain.

I can't recall how long the Cloud Identity takes to set up, but it wasn't cumbersome. 

It is cloud-based Software as a Service model, so you don't need to provision anything on your own. You sign up like any G Suite service. Once you sign up for Cloud Identity using your domain, you must verify that you own the domain. It's straightforward after that. One person is enough to manage Cloud Identity, but you can have two or three people for availability purposes. It took one or two hours to get it deployed. I just had to coordinate with the domain admin guy. Aside from managing the end-users, there isn't much maintenance. It's SaaS, so Google manages all the infrastructure for you.

For a completely new user and setup, the initial implementation is very straightforward.

It is easy to install. However, it could be easier. For the Windows device management agent, there isn't an easy way to install it and push it into the devices. We would prefer a better way of managing Windows or pushing that agent.

The time for deployment depends on the number of users. Generally, for a 10,000-user base, it takes about ninety days. Moreover, maintenance is easier because of the way Google has integrated everything into a single console. It's simpler to maintain. One person should be enough for 10,000 users.

The initial setup of Google Cloud Identity is not difficult. You have to create the groups and users and give them a link to the applications that you want them to access. You need to add all the permission. It's something that can be implemented easily. The time it takes depends on the complexity. For example, if you have a lot of users and the access and tools that they will have access to are high then it will add to the time.

I would not say that the setup was simple or complex. Rather, it was of medium complexity. It is, however, far better when compared to the other cloud providers.

The configuration involves setting up the roles and figuring out which roles to assign to which users. It is not difficult and very quick.

The initial setup is really okay. We do these third-party system integrations a lot with this and other products, so I think it is no harder than with any other systems to do. For the deployment of Google Cloud Identity to all departments, it took maybe half-an-hour.  

Creating accounts is simple, but further deployment is moderate. Maintenance is all administrative to control accounts.

The initial setup is straightforward. We were able to deploy 25 VMs and we had it done within two hours.

The initial setup is quite easy and simple. If you know the product well it won't take you a long time to deploy. We have done it for a few of our customers and we have got good results.