The initial setup is straightforward. Once we have subscribed to the license, we will receive our tenant ID and organization ID. We can then access the portal and configure whatever we want. To save the configuration, we must enable it from the portal itself. The Azure Ready Connect GUI console makes it easy to join devices to Azure and to create and deploy conditional access policies.

We have four or five global administrator access levels in our organization. The most limited level is for the global administrator, who can be limited to one person. We need to involve them to enter the password while configuring the CMG, and then the Microsoft support in case we are missing any configuration during the installation or managing Microsoft Intune.

We deployed across more than 10 to 15 countries. The solution is used in India, the US, and England.

The implementation of every Microsoft solution is very easy, if you are already using Microsoft solutions. There are no issues with that.

In terms of maintenance, the services are fully managed by Microsoft, including all the upgrades, updates, and security patches, without any customer involvement.

Microsoft documentation has traditionally been criticized for its complexity and search difficulty. While some improvements have been made, many users still rely on online forums and YouTube videos for basic setup and troubleshooting. As a result, the onboarding experience can feel less polished compared to competitors like Malwarebytes, which offer more hand-holding during installation and configuration. Unfortunately, navigating Microsoft products often requires independent research and trial and error, which can be a barrier for new users.

Setting up Intune was initially complex because we need to migrate everything from SCCM to Intune. If you already have your policies and configurations worked out on-prem, it will be the same once you move to Intune, and you'll see a massive improvement in configuration, compliance, reporting, and mobile device management.

Once we create our tenants, the migration and synchronization of the users to the cloud services is straightforward.

We deployed the solution in phases and it took around three months to complete. Three people from our end were involved in the deployment.

The initial setup was easy, but we had lots of time during the pandemic. I had that all set up in my living room that first summer, working on it remotely. There were some pains because it wasn't all there yet. It wasn't until about July 2020 that most of the pieces were in place. It took another year before the rest was solid. However, to be fair, people adopting Intune now will get a mostly finished product.

I would rate the complexity of the initial setup as a seven out of ten. However, if you have prior experience with MDM solutions or other MDM platforms like MobileIron, AirWatch, or IBM's MaaS360, the process may be more straightforward. Intune deployment typically takes a few weeks. The deployment involved a team of over 35 people to cater to a user base of around 30,000 in an automobile company based in Canada. The process began with testing and policy configuration over a month, focusing on aspects like data restrictions and copy limitations. After the pilot phase, Microsoft provided a pricing model, and a migration process took place over two to three months. This involved transitioning users from BlackBerry to iOS and Android and incorporating Windows Autopilot for Windows laptops, both new and existing. The onboarding process also extended to HP and other vendors.

The initial setup was straightforward. The deployment required two people from the third party and two of our architects, one for security and one for the network.

Setting up Intune is pretty straightforward. There may be a few bumps in the road, but you shouldn't have much trouble if you're a system administrator or a pure IT guy. I did it by myself, and it took about two hours. You have to do the basic configuration. 

For that, you need a bit of reading to understand how your configuration is working within your overall setup. Once you do the necessary tweaking, Intune is up and running. After that, you create policies and do a test run on one or two machines. Once you verify that everything is working fine, you deploy it all. 

If you're not a techie, I could guide you step by step. It's as simple as that. After deployment, Intune doesn't require maintenance because it's a cloud product. 

My deployment model for Intune is gradual and cautious. It is like navigating through a vast ocean, where I test on a few devices first, slowly deploying one thing at a time. I learned the hard way that rushing impacts users, so it is a step-by-step process, taking a month or two, testing, deploying, and making adjustments as needed. Patience is the key to Intune deployment.
Deploying Intune wasn't a walk in the park, but it wasn't overly complex either. I would say it is moderate—needing time, experience, and knowledge. Testing is crucial.

Microsoft takes care of updates and maintenance. I just need to stay on top of deploying new patches that come from vendors, ensuring our machines are up-to-date and secure.

Deploying Intune is pretty straightforward. It doesn't matter whether you use autopilot or manual deployment. Each machine is enrolled in Intune automatically if it's connected to Azure AD with the correct user licensing. It's a relatively painless enrollment process.

Intune involves some maintenance, like any solution. You must ensure it's still working correctly and helping you achieve your business goals for compliance and configuration of your endpoints.

For some customers, it is a hybrid deployment, and for some customers, it is a pure cloud deployment. Our customers are medium and large enterprises. They are not small businesses.

Its deployment is of medium complexity. If it is a hybrid environment, it is fairly complex. If it is a pure cloud environment, it is easy.

The deployment duration depends on the number of users we have or the number of computers we have. For a setup with 100 users or 100 computers, it takes about two weeks. It may require some troubleshooting and tweaking.

The initial setup was quite straightforward.

The time it takes to implement Intune depends on two factors: the features we want to enable and the size of our organization. Enabling basic management features for common devices like iOS, Android, Mac, and Windows typically takes one to two weeks. This includes enrolling devices and setting up core functionalities. For a full Intune implementation with all its capabilities, the timeline can vary depending on the organization's size. However, simply enrolling devices and exploring basic features can be done in a couple of days.

While the step-by-step guided scenarios make the initial deployment process easier, it still requires familiarity with Intune and some experience using it.

The initial deployment was complex until we understood the process. We went through a simple dev test and then prod methodology. 

Two to three people were required for the deployment.

The initial deployment process is very straightforward. It's software as a service. You just buy the subscription and start using it. It's not the case that there are very complex configurations or prerequisites to start off.

It does not require any maintenance on the customer's side. Microsoft takes care of all the maintenance.

The initial setup is quite easy because it is a cloud-based, managed service. There is nothing complex about it.

The initial setup was complex.

The initial setup of Intune was straightforward, taking just one day to deploy. Our implementation strategy focused on identifying and securing all available assets, including desktops and mobiles. The setup was managed by one person.

Essentially, the way it was set up, it wasn't set up as a hybrid model. At the moment, we have got on-premises, and we have a cloud, but they're not joined. There is no passthrough, which is interesting. A lot of the on-premise has been copied over to the cloud. We are now taking the cloud to default, and the overall plan is to mothball the servers and reuse those as very high-powered desktops wherever possible. I just predominantly use the cloud.

I was not involved in its deployment, but in terms of maintenance, typically, our MSP makes the changes, but I've got GA rights to make anything that is critical. Generally, there are about 20 people at the Microsoft solution partner, and there are four of us on the IT team. There are less than 30 people in total.

The initial deployment of Microsoft Intune was complex as fine-tuning policies took time. We ran a POC for three to six months before deploying to production. Our implementation strategy involved evaluating vendors, cost comparison and prioritizing security features. We opted for Microsoft Intune for its ability to consolidate security telemetry into the Defender portal. Deployment followed a phased approach: POC, small pilot group, then rollout to production. 

The solution requires maintenance from our side. This includes change management and configuration management to prevent unauthorized changes to policies, as well as constant review of threats from mobile devices. A team of four people is involved in maintaining the solution.

The deployment model for Intune is cloud basically, but for other MDM solutions, it's on-prem because the government and healthcare sectors prefer to use the on-prem solution.

The deployment duration depends on the project timeline and the complexity of the deployment. A fresh Intune deployment is straightforward. We just need to do the configuration and create configuration profiles. For example, for Windows OS, we can enroll 1,000 devices in a month or something like that depending on the availability of the machine. Everything is configured in the backend, so they just need to power on the device, and everything works as expected, and everything is pushed down.

The number of people required depends on how many machines need to be deployed and users' availability. The model that we're having right now is that for a new device, it's straightaway delivered to the user. So, there is no involvement of IT because it's an autopilot deployment. When a user powers on a device, the configuration kicks in. The users just log in using their user accounts, and that's all. So, one IT person is enough to configure the backend.

It was pretty straightforward. It was not a very long, complex, and involved process. It was fairly easy to set up.

I rate Intune a nine out of ten for ease of setup. I have a lot of experience with Microsoft, so it was straightforward. We have a hybrid environment with an on-prem 2019 Windows Server and Google Workspace. We're slowly transitioning from Google Workspace to Microsoft 365 and shifting from an on-prem Windows Server to a hybrid environment on Azure.

Our deployment is still in progress, but it's expected to take six months. The deployment includes not only our Philippines office but also branch locations throughout Asia. 

We started by evaluating the solution to see how user-friendly and compatible it was with our organization. Next, we created a training program with the help of the partner and vendor to introduce our users to the Microsoft platform. From there, we are face-to-face training in each country. The deployment team consists of eight people from our company and three from the vendor. 

Setting up Intune wasn't straightforward. It took us about three or four months. We did a test phase and rollout then collected feedback. Based on that feedback, we did another test phase and rollout. Initially, we did it in-house, but we got stuck, so we reached out to Intune support. 

It would be easier with one person, but the person doing the deployment needs to work with various teams, like cybersecurity, infrastructure, and IT.

The initial setup is straightforward. I am an architect and completed the deployment on my own within two months.

The solution's deployment is both complex and intuitive. 

Intune's initial setup is straightforward. Microsoft provided us with some documentation on how to implement the basic setup, and we went through that. There is also a lot of documentation available on the Microsoft portal. We can easily find whatever we are looking for by searching. The Microsoft support team is also very helpful.

The initial setup was somewhat complex. We encountered some issues with the security group, which prevented us from enrolling some of the devices. Our strategy was to onboard all the new users first. The deployment involved around eight people.

The initial setup was very easy, not at all complex.

The initial setup is a bit complex. Initially, we deployed for the executives of the organization. We deployed Microsoft Intune for one hundred users in the first year. After receiving positive feedback, we expanded our model and provided security for all the major executive users of our organization, protecting their data, devices, and applications. We had two administrators and six service desk screen engineers deploy the solution. In addition, our two administrators were verifying the policies and implemented the solutions on end users' devices.

The initial deployment of Intune can be complex because it is linked to Microsoft Entra, which itself is a complex product. This complexity depends on the desired outcome. Intune's deployment complexity hinges on whether users will enroll their devices themselves or if the IT team will enroll them and grant access. A proper pre-assessment is crucial to determine if Intune's complexity aligns with our desired outcome.

Our deployment took two months to complete because of the internal security approvals we required.

Three administrators were required for the deployment.

It is easy. It is not difficult.

It is easy.

Intune was easy to set up. Everything goes quickly once you have all the documentation. It isn't that complicated and took about four or five days in our test environment. We had to synchronize the users with the cloud environment. Once all the identities are replicated in the cloud, we started to duplicate the groups and endpoints. After this was finished, we cut the links to the on-premise installation.

If you've got the right skills, the initial setup is not that difficult. It is very quick to set up. It doesn't take long. 

We have not yet implemented the solution but the app deployment is a bit complex.

When we add a device to the Azure domain, the activation process for Intune is simple and straightforward with no added complexity.

I wasn't involved in the initial deployment. Now that it's set up, deployment to devices requires turning the phone on, and the device will automatically pull up the profile if the client is linked to our Apple Business Manager tool. We currently have one staff member involved with the maintenance, but we're looking into distributing it to others on the same team.  

Now that I'm starting to be familiar with the profiles, it's starting to get easier. A few weeks ago, there was a very odd issue that happened also related to MDM devices where we were using the manage home screen application to lock down the apps that we wanted to allow only the users to use, like the kiosk application.

We have configured the profile and have deployed to 200 or 300 devices. Some of our users called and said suddenly all the mobile devices were flashing. I don't know what happened, but it happened at the same time. The workaround that I had to do was to remove the manage home screen from the profile. Then all of the devices were kicked out and went back to the home screen of the devices. That was the only way they could resume the mobile devices. I don't know what happened, but something was wrong with the manage home screen app on that day because a few days after, I pushed back and everything resumed.

The implementation of Intune follows a structured process, starting with a change activity managed by a dedicated team. This involves creating a ServiceNow ticket detailing the implementation plan, rollback options, and involvement of various teams. After approval, testing is conducted, followed by deployment in a phased manner, typically at the beginning of the month to avoid interfering with critical month-end activities.

It is a cloud solution. Its deployment took about 40 minutes.

It does require maintenance.

Initial setup is a simple process. It is a cloud solution. It is easy to deploy and easy to integrate with other tools as well. If we have to integrate with on-prem or Azure-ready through an AD connector, it is easy. Also, it is capable of integrating with other tools.

In terms of deployment, having things in the VM or physical VM or physical system in place and the ports enabled, as the main infrastructure is all in the cloud, is only part of connecting with the Azure already and the AD connectors, and does not take much time. With full testing, it takes one day if all things are in place.

I was not involved from the beginning of the project. However, from what I remember, we did the implementation directly with the help of a support engineer from Microsoft. Their involvement ensured the setup was not such a big deal.

Deployment took maybe one year in our environment, however, this was because we had a lot of time to tune it up and to test it, to have a pilot for a few months and then add more people to the pilot before we started migrations for mobile, for example. We took our time to really prepare the product as best as possible and then deployed it to the users and migrated them over.

We have two levels of people at a global level that handle deployment and maintenance. They mostly focus on improving the environment, not troubleshooting WiFi issues. 

In my organization, it is a hybrid deployment. I was not involved in its initial deployment, but I know that it is a little bit complex for people who are using it from scratch. You need at least an experience with SCCM.

It is deployed at a single location. In terms of maintenance, it does not require any maintenance from our side. Everything is handled by Microsoft.

The initial setup is not overly complex or difficult.

The initial setup was very easy as Microsoft has a setup guide similar to what you would expect if you set up 365. If I'm following the set-up guide, it's very simple. You just click along. 

As with everything in IT, once you reach a certain level of complexity, which Intune does, the rule is: everything is easy when you know how, and everything is difficult when you don't.

Especially with something as complex as MDM, if you don't know everything, it can be very difficult. But if you do, it can be easy. So, it depends. There are very few people who know absolutely everything.

So, there is a difficulty there, but once you know how to do it, it's easy. Like user experience is not necessarily intuitive.

One infrastructure analyst completed the deployment.

As an IT admin, I was involved in the deployment of Intune as a consultant. The implementation was very straightforward as we're an experienced team of security professionals consisting of two IT admins and an IT manager. There was also a test environment for our benefit, and moving that over to a production environment was seamless.

The deployment was pretty straightforward; the solution came in a prebuilt configuration, and we just needed to enable it in our Azure domain.

As the product is cloud-based, we don't have to do any maintenance as a customer. 

We have a cloud environment. Its initial setup was straightforward.

It does not require any maintenance from our side.

The initial deployment was straightforward. We need a license to join the machines to Azure and then apply the policies we create.

One person is required for deployment.

The solution is worth the money for us.

Its initial setup is fine. I haven't seen any issues. I have worked as a technical lead at the architect level on different products. For that reason, I haven't had many challenges.

Its implementation was a bit longer because we took our time in testing on multiple machines and multiple users. We wanted to ensure that we are able to achieve what we wanted. We completed all the use case scenarios and what we were expecting from the security point of view.

Complexity-wise, it's not hard to set up. It's just a lot of small steps, such as making sure the firewall ports are open and certain things are in place, and all the perquisites are taken care of, as the wizard, the installation wizard for Endpoint Manager, is pretty straightforward. As long as you have SQL and some other features turned on to support the different functions of Endpoint Manager, you're fine. You'll need WSS or you'll need WSS for patching and you'll need SQL reporting services for the reporting portion of it. All those small things. The more lights you turn on, the more configuration you have to do.

The deployment itself took me four hours end to end, to put all the prerequisites in, however, understanding, of course, may take a while for someone new. I've done this now for over 25 years. For me, it's pretty straightforward and I have, a lot of these things PowerShell scripted so it works very well. You can create a PowerShell script and set the whole thing up from Powershell, which is what I've done.

Maintenance requirements are low. Since it lives on SQL, if you put a SQL maintenance plan in place, it's pretty much, it's very healthy, it's very stable.

There are no challenges with the deployment of Microsoft Intune.

It's not much of a stretch to say that it's simple to integrate with third-party services. In terms of integration, Microsoft is good.

Its initial setup is very easy. We don't need to deploy any servers anywhere. With just a few clicks, we can set up Intune. We just need to set the MDM authority, and we need to set the automatic enrollment. That's it.

Intune is all on the cloud. I wasn't there when they migrated. 

We have it on a public cloud. We have Microsoft 365. 

It is not difficult to maintain because it is in the cloud. It is important for us that the capabilities of the Intune Suite are integrated with Microsoft 365 and Microsoft Security for both cloud and co-managed devices.

I reviewed its implementation. It was straightforward. There were some technical difficulties in getting it started, but after we resolved them, it was easy. There were some architectural issues we had to resolve because we had legacy architecture.

Deploying Intune isn't easy, but it isn't too complicated. Someone with two or three years of experience can do it. I completed the initial installation quickly, but migration took a long time because it's a manual process. We deployed Intune in-house with only two people. 

After deployment, Intune doesn't require any maintenance. It's a cloud solution, so Microsoft is responsible for maintaining it. However, we need to handle any tenant-level configuration.

It's very simple to set up. To set up the terminals, it's very easy. You have a manual, and it's very easy to follow. You can configure functionalities for specific users or a specific group of users or things like that. It's great.

The time it takes to deploy depends on the number of terminals and it also depends on the number of different groups. Perhaps you have to configure the different policies for different groups. That might take longer than a straightforward setup. In an installation with, for example, 1,000 terminals, it typically takes less than a month -three weeks or so.

I don't personally handle the deployment myself, however. I offer it to clients. I'm not the one to actually do the manual work of implementing it. 

The amount of people we need to deploy a solution depends on the number of terminals that we have to manage.

Some customers configure everything at the beginning and nothing changes over time. That said, we have other customers that they are continuously asking for changes. This group of customers will likely need three people more to handle maintenance. For every 1,000 devices, you typically need one and a half full-time employees.

It's not trivial, but it's okay. It's not too complicated. You do have to make sure you read your documentation, and you get an idea of what you're trying to do.

The initial setup was complex, and the full deployment took us one year.

Microsoft Intune is essentially software as a service for mobile device management. To configure Microsoft Intune, we only have to register the domain name and register the DNS. We can log in to enroll the device with Microsoft Intune. After we register the DNS and the domain name, we configure the policies. All policies like user access and permissions. After that, the admin can send the license to every user.

The configuration takes one to five days. But it takes a long time to educate the users on how they can use it. This is because some things change after we implement Intune. Users may complain that they can't do what they did before, but it's better from a security perspective.

Microsoft will maintain it. The customer only maintains the policy and the license.

The initial installation isn't too difficult, but it can be complex if you have a large number of devices and need to do lots of customization. It is more complicated to onboard Windows PCs versus mobile devices, which are pretty easy.

The number of staff members required also varies according to the job and the timeline for deployment. For example, I would probably need additional resources if I'm enrolling 20,000 devices in under a month. However, we don't need too many resources if we have enough time

Intune is a cloud-based solution, so Microsoft is responsible for maintaining the infrastructure. We only need to handle the administrative and configuration adjustments on our side. 

The initial setup was quite straightforward.

We do not need much staff for the maintenance of the solution. It's pretty low maintenance.

Our parent company makes the deployment process very complex by using non-Microsoft tools. 

The initial setup is complex.

You have to appreciate two points with Microsoft Endpoint Manager. Microsoft Endpoint is based in Microsoft's cloud, 365 Azure. And Microsoft has simplified it quite a bit. They also work well with Intune. Many of their services are complementary to the solution. Autopilot is being sent out. You can have a machine auto-built from a remote location, or you can order an Autopilot deployment from your HP, Dell, or Lenovo. They've simplified it considerably since the old days, but there is still a technical element. For those with a technical nature, it is quite simple. Anything is simple if you understand the product.

We have projects all over the world. It took us four months to implement Intune Microsoft Intune for approximately 100 clients in three countries. We implemented it in many locations, such as Germany in three cities, Croatia, and Bosnia, there is a total of 50 locations. Microsoft Intune is easy to work with.

The initial setup is not simple, you need a specialist to be involved that has the appropriate experience. This is not a solution where out of the box you run the executable file on your system and hit next, next, to finish the installation.

It was simple. I would rate it a four out of five in terms of the setup. It took about a week.

It is a cloud product. It doesn't require any maintenance from our side. We get an update every time they upgrade a feature.

Microsoft Intune's deployment is straightforward. 

The initial setup is not complex. We started by setting up the environment on the cloud, then configured the devices and profiles. However, certain aspects of the deployment required the assistance of engineers.

The deployment is relatively straightforward; we send out an email, and our users click the link; it downloads the tool to their phones, and they can log in using their credentials. If it's set up correctly, then the deployment is easy.

The solution requires a small amount of maintenance; I have one full-time member of staff to maintain 420 total devices split between two of our clients. 

The initial setup is easy. Deployment usually takes around eight weeks of time, including pilot testing. We do requirement gathering, designing, and building, so it takes us a minimum of eight weeks.

As far as the set up, we only have the first half-a-dozen technical people on the product just to do a pilot. We have had issues with it. This is the reason we have not even deployed it for the users' space yet to deploy to a larger test group. I would expect the deployment would be a bit easier. That could eventually be a changing factor in what we do moving forward.  

The initial setup is straightforward. We used our own certified people for the deployment.

It depends on the use case. If you only focus on Mobile Device Management, then it is very easy to setup. You just have to define the use case in the context you want to protect. If you are talking about how to integrate with the lock analytics and how to classify data in context, then this is another thing.

The initial setup is straightforward. To set it all up, we need to connect to the OEM and then provide all the hash information and more. Everything should be pre-configured on the laptop, and then the user is good to go.

The vendor ships the machine directly to you. All you need to do is connect it to the internet. It takes around 30 minutes or 40 minutes depending on the configuration. After that, you're ready to go. Post setup, if you need anything, you can simply go to the built-in Intune company portal and shop from there. This saved us a lot of time.

Still, the initial setup was not straightforward. When we initially started with Windows, there were a lot of open items. There were a lot of things which were not there. Obviously, we couldn't just move a company directly from on-prem to cloud. There is complexity, there are some legacy procedures that we had to follow. At that point in time, Intune was not ready, but currently, there are a lot of options that can fulfill your security requirements, your network requirements, your application requirements, user accessibility requirements, and the user experience. All of these things are pretty much in the place now. To start with, it was not this way. 

When I started using this solution, it took me roughly one year and three months to understand how to build it, to do due diligence, etc. Now, I can migrate an organization within 13 days.

The initial setup is not complex. It's relatively straightforward.

Deployment was basically a three-day engagement.

I set up Intune without any assistance.

I was involved in some areas of the deployment, and it was quite straightforward, especially on the client side where we handled it internally. Rolling it out to nearly 1,0000 computers took some time, just under a year. We managed it with a team of three people.

Normally, customers need a pilot. It takes around two or three weeks for the pilot. After that, we do the deployment. We start with a limited number of policies. Overall, it's done in three to four weeks.

It was easier than expected. We did the full deployment for 44 companies and about 120 users in about three months.

The initial setup was straightforward. I actually prefer Microsoft Intune over VMware Workplace ONE because it's a bit more complicated. The setup was also easy because I've worked with Intune before.

The solution is cloud-oriented. As long as you have a valid Microsoft Enterprise Subscription, it's all subscription-driven. From an installation or deployment perspective, it's pretty quick and pretty straightforward. It's not complex. As long as you paid for at least a standard enterprise subscription.

I've been on multiple deployments. The range from the pilot can take from a couple of weeks to a full-scale deployment, which can be a couple of months to a year. The longest I have been involved in was eight months.

Implementing Microsoft Intune is easy. Total deployment takes about one to two weeks. You access the portal, buy the subscription, and configure everything. We have three administrators managing the solution.

If the customer is already operating on a cloud environment, then it's easy, but if a customer has a hybrid environment, then it can be complex.

If they've got people who are now working home that previously used to work in the office and they still want them to use their work laptops at home, it gets complex. You would need to start looking at registering the devices into Azure AD, which then leads to Azure AD premiums. Therefore, you would need to find out from Microsoft whether to add the device into Azure AD, to register it, that you would also need MDM or an Intune license added on top.

Too much information was provided regarding the initial setup, and it was too difficult to understand sometimes. You would have to read each and every article and try to understand exactly where and what you need to deploy. That's a bit challenging, but if you have seen the videos or attended Microsoft's training, then it's easier.

I attended the training and was able to configure and understand really well. However, if you give it to a layman, then it would really be a challenge.

Hardly any maintenance is required, so a few people will be able to handle the occasional issues and iOS upgrades.

The implementation process is very complex due to the global use of the product. It started small. They used naming conventions just for the home country, so we had to deal with redesigns of the naming conventions for global use. Yeah.

In terms of the deployment itself, it's software as a service. The product itself is immediately available, however, onboarding devices is a huge effort. That's mostly the case at this moment. We used Microsoft Intune, before that we used MobileIron, and we did migration for MobileIron to Intune, so we had a quick start originally. 

The initial setup can be a bit difficult. I'm not certified in any way for Microsoft. 

I cannot speak to how many people are required for deployment or maintenance tasks. 

We did not encounter issues with the deployment. 

The initial setup was straightforward and easy to roll out.

We found the initial setup to be quite easy and straightforward. It's not complex. If a company wants to set it up themselves, they shouldn't have an issue doing so.

The deployment didn't take very long. It was a pretty quick process overall. 

It's really simple to implement Intune. Everything is already deployed on the cloud and you get everything you need. If you have a Windows 10, you can perform this connection from the Windows control panel and it's quite easy. We are now working to get the Android and iOS cell phones enrolled as well. We are on a pilot right now for macOS. Computers running macOS are already in a pilot period. We're just verifying that everything works well. We're also proceeding with the implementation for the macOS computers as well. Deployment took one or two weeks and I did it myself. 

It's a cloud solution. The cloud depends on the customer, but Microsoft Intune is a cloud solution serviced by Microsoft. My customers have various cloud environments. It could be a hybrid, public cloud, or private cloud. It depends on the customer.

It's quite straightforward to deploy it, but configuring it and doing it right is something else. The deployment duration varies. Some customers have 100 devices and others have 10,000. It depends on the landscape of a customer. Even though nothing changes technically, it's more difficult to move large enterprise organizations to a mobile device management platform.

The number of people required depends on the qualifications of the person who is deploying Intune. Intune can be deployed by one person. 

Its maintenance depends on the company. If you have a very big landscape with tens of thousands of devices, you want to have more engineers monitoring Intune and configuring. If it's a smaller environment, you can manage it with one or two people.

It was quite extensive, and it took a few days for them to set it up.

At an enterprise level, it is always a complex initial setup. However, with the cloud, if you use that and you start from scratch, it would be pretty simple plug-and-play. That said, the moment the data comes in from the enterprise, there are complexities as there's only one system you are going to have to handle multiple devices and users from 300 to 30,000 to 300,000. It depends on how you are going to handle it.

For per device, it is not much work to set up the solution as there are only one or two apps that need to be installed. For policy conservation and many other things, you require some time to think about what needs to be done. You usually, for example, create the profile, which takes a month's time - or a month and a half.

You do not need much of a team technical team for the deployment. You just require a couple of experts - at least one or two - who have a good understanding.  We have around ten people involved in active management of it, and that includes a 24/7 support team to help manage different devices.

The initial setup is not complex.

The length of time required for deployment depends on the number of people in the environment. It also depends on how adopted people are with this type of technology. Six months is enough to complete a full deployment.

Some of our deployments are on-premises, whereas others are on the cloud.

It is very easy to set up compared to other MDM products.

I find it pretty straightforward, which could be because I have been working on this solution for three years. It mostly involves clicking the Next button. It will also depend on your requirements and policies, but it is generally straightforward.

The initial setup is easy. We can complete the Intune implementation in one hour, but for the base configuration, we require Microsoft support. Because at the end of the day, it's a cloud product, and we don't have many resources on it.

In terms of deployment, what is difficult about Microsoft is that you need to have a broad knowledge of Azure and the other components because the endpoint manager is just a small part of your workspace. You need to have that experience and there's a lot of custom work for every single client. There isn't really an automated way, like a template base, within Microsoft, to fully deploy endpoint environments.

I help our customers with the design and deployment. Normally it includes making a list of all the applications they have within the company and seeing how much work it is for us to deploy an environment and how much application work is within it. In that way, we see which strategy fits them the best. Because there are a lot of on-premises applications that are really difficult to fit into a cloud environment, we will look to build more of a hybrid solution than a fully cloud-based solution.

We usually need three or four people for deployment.

Maintenance involves keeping up to date with the application. The only downside is that if you upload an application today, it doesn't download an update that comes out next week. That means you need to package and deploy it again.

Setting up Intune was straightforward. Microsoft provided all the materials we needed, and we had support from their team. We had about five guys working on the solution. It can be from one to five guys, depending on the scale of the solution. 

The installation is not complex.

Intune is essentially a SaaS solution. Although Intune is a SaaS solution, it can be integrated with the ACCM. You can integrate a co-management solution in two modes, or you can integrate only the cloud. As a result, the cloud is mostly used by small and medium-sized businesses. However, for enterprise customers, we must use co-management, the team, the ACCM, and Intune.

Maintenance isn't that based on the volume. For example, if you want to go with 500 devices, you need to size the people accordingly. If you want to implement 5,000, 10,000, one lakh, or one million people, you must size the people accordingly. As a starting baseline, we need to assign one person to manage every 5,000 devices.

Based on my conversation with my customer, they say that VMware Workspace ONE is easier to install.

While I have not tried to install VMware Workspace ONE myself, I don't find Microsoft Intune to be difficult to install.

The initial setup can be a bit complex, although this ultimately depends on the requirements of the business. If a proper framework is established then the solution is simpler to deploy. 

Moreover, the company culture impacts the complexity of the deployment. There are times when we must provide guides or that user training is required. When deploying in the developer community, in which the participants are tech savvy, the process will be easier. Conversely, when doing so in a non-developer community, this process can take awhile. 

It is straightforward for somebody who has got experience. It is certainly not something that somebody who came off the street can do easily. There is a lot of documentation, but the documentation varies widely, and it can be difficult to set up. Microsoft does offer some good support and assistance with it. If you have a user base of 300 devices or more, they'll actually walk you through the entire setup and assist you.

Currently, I am solely providing support for eight different clients who probably have over a thousand devices in total. So, the maintenance isn't difficult.

The installation of Microsoft Intune was not difficult, it was smooth. Once it was set up it was up and running, we only had to configure the policies. Integrating was easy with Active Directory.

I do not think it is ever straightforward to use a Mobile Device Management System. Especially in our case, we were enrolling a lot of different devices that were already in use. That is always complicated and I do not think the fault is with Intune. It is complicated because Android can be used by different manufacturers, such as Huawei, Samsung, or Sony, and all of them can be very different.

Its initial deployment is probably the biggest challenge. It is complex because Intune encompasses so many features and things that you can do with it, and it is so broad in scope. There are a lot of different things you can do with it, and there are a lot of different ways in which you can deploy it, which makes deploying it for a particular customer's environment complicated. It takes some time. I would rate it a three out of five in terms of the ease of setup.

We've had deployments that took weeks. We've had some simpler deployments that took days. So, it varies. The product is so big, and it encompasses so much. So, it depends on what the customer is implementing. One of our most recent customers wanted to use it for a lot of things. So, it was pretty complex. It took us time to get all the devices onboard and registered and so forth.

We might have multiple people working on a deployment, but that doesn't mean it takes that many. Overall, it doesn't take that many people to deploy it, but it typically takes a higher technical level person to deploy. You don't need a bunch of folks, but they have to really know what they're doing.

The initial setup was not easy for me.

It was not easy, but not too complex. If an engineer knows what he or she is doing, then it is not difficult.

Initial setup was straightforward.

The installation is simple and it can be done quickly, within minutes.

The initial setup is not overly complex or difficult. It is easy. The implementation is straightforward.

The deployment process is pretty quick. It takes a couple of days, and not quite a week.

It is simple. It is easier than easy.

The installation was straightforward.

The initial setup is very simple. 

Initial setup is of average difficulty. It requires a lot of people. We need to have an Azure AD license, so some AD integration is required. A kind of firewall is included.

In Jamf, it's not like that, so we have a single console and we can implement it. But here, we have multiple because it can be integrated and co-managed. I can't say it is very easy to deploy. For very small-scale industries, then it's definitely easy if you have minimal user devices or user IDs. If you're looking to deploy the solution on a corporate-level, and if they have multiple tenants, in that case, it is definitely complex.

If you are looking for it to be co-managed, there'll be an SCCM and an AD team. Otherwise, one or two engineers is fine for Itune.

We did not experience any complexity in the initial deployment and there was no problem with the installation, I do not think. The complexity definitely depends on what you are trying to accomplish. I do not remember exactly because I do not directly deal with deployment anymore. I am actually leading it. We have a team that deploys the product. I do not look over their shoulder to know how much time it takes exactly and what factors it requires for successful deployment.  

It's hard to find the information to work out what you need to configure, but it's easy once you get to know how to work it.

The initial setup was simple and it took us about two days to deploy it.

Intune only supports mobile devices in the cloud version. Because a number of my clients have both PCs and mobile devices, I deployed it in a hybrid model.

The setup for this solution was straightforward. It was quick and it was easy, but it would still depend on the policies.

The implementation was straightforward and it took approximately two months.

The installation is very easy. However, to be able to configure it you will need special knowledge, such as training or self-studies to have a proper level of security. There are many settings one has to understand before being able to implement Microsoft Intune.

Microsoft Intune is very simple to install on a local desktop. You can use remote access and install the software. The configuring of the solution is done online on a portal and the policies are pushed to the desktop where Microsoft Intune is installed.

It is pretty straightforward. There is good documentation for that.

The initial setup is pretty straightforward.

The initial setup requires user participation. You can't push it without the client being engaged. That is part of the configuration.

The initial setup is a very simple process. You don't have to do anything on on-prem. Since it's a solution from Azure, it's a software service. You just have to buy the subscription. You just need to have the license in place and then you can just start using it. There is not much setup involved. If you want to integrate your Azure solution with your on-prem solutions, then you have to do a bit of integration.

If you're going with standalone Intune, you don't have to think of setting up anything. You can just use it, pay for whatever your problems are, find a solution for that, and start using it — that's all. You don't have to worry about the setup for standalone Intune.

The configuration is straightforward and there is nothing complex about it.

Application delivery to Windows 10 was straightforward for someone with prior System Centre Configuration Manager and application deployment skill sets.

Its setup is easy. It is a Microsoft solution, and everything is easy with Microsoft.

The initial setup is a bit difficult.

It took almost a month to deploy. There were several requirements to set up the conditions.

The implementation process is simple. It's very straightforward. 

I'd rate the overall initial setup process at a four out of five. 

Deployment times vary. It depends on the product. Our clients, for example, we're deploying it to all of their mobile devices. We use architects and engineers for the deployment process. How many we need depends on the project. We typically need, let's say, one architect and then, depending on the size of the project, one or more engineers.

The setup was very simple and fast.