The interface is clunky and the layout is a bit outdated. Also, I don't think MaaS360 has as many features as Intune. It doesn't integrate with Office as seamlessly as Intune does, which isn't surprising, given that Intune and Office are Microsoft products. It's also somewhat buggy. For example, we had an issue recently where IBM had to release some licenses from the back because we weren't able to sign onto the devices. 

IBM MaaS360 needs to have stronger points when it comes to the area of BYOD. IBM MaaS360 covers a very broad range of operating systems and devices.

It's difficult for someone like me to set up a phone that doesn't require a SIM card, like Apple's new phones. I prefer to open up a phone and ensure it's properly set up before the user starts using it. As soon as the phone is turned on, it automatically connects to the network and becomes the user's new phone. If the phone isn't set up properly before this happens, it could cause problems for the user. Additionally, without a SIM card, the speaker can't monitor or remotely wipe the phone if necessary.

Configuring policies is difficult in IBM MaaS360. It also needs to improve usability. 

IBM MaaS360 can improve the location reporter. There is a 15-minute delay and this does not allow for any usefulness.

The solution's integration with Microsoft Teams could be better.

IBM MaaS360 can improve the information provided for DLP control. Some of our customers would benefit from this.

In a future release, they should add more compatibility with different types of devices, Zebra. Our clients needed to control different types of devices using the same license to control mobile phones.

An area for improvement would be handshaking with Microsoft in terms of trying to get a DLP on Microsoft OS. It would also be useful to be able to do containerization with Microsoft. There are also issues with email security when the functionality is defined from your AD or Exchange.

When we have MaaS360 installed on smartphones, it consumes the battery of the device at a much faster pace. This is one of the areas of improvement that I would like to highlight. We have also observed that in the contact list, a lot of duplication is happening. A single contact is duplicated three or four times, which also consumes more memory resources. If they can work on improving it for these aspects, it will have a more positive impact not only on the way the application is being consumed by the user but also on user satisfaction.

A lot of new features are being deployed or rolled out by companies that are competitors of IBM MaaS360. IBM will have to ensure that all those features are on board so that we have a complete suite of features in the platform, rather than deploying multiple diverse solutions to cater to the requirements of our customers.

The look needs to be updated and it could be simpler to use.

The portal itself looks old and outdated.

I would like to see more automation and better reporting. Their reports are a bit archaic.

IBM MaaS360’s threat management feature needs improvement. It could identify even more malicious attacks. Additionally, it should support other platforms, including Linux.

The user interface could definitely use some improvement. It's good enough, albeit pretty basic. However, anybody that is not used to it might require some assistance early on because it is not very intuitive.

It is fairly simple to use, yet a little complex to manage. At least, the initial setup is complex to manage.

One of the things that I would like to see in the next release is improvements at the account level. it is a little bit difficult to identify the number of licenses that are visible in my account, and to which suite each belongs. If there are four suites, we sometimes have to have segregation. Some users require the full set of enterprise services, whereas some users who are our partners or just employees are just given basic inventory management tools.

Being able to identify and account for these licenses would definitely help. This is not related to the actual usage, but rather, it's more of an administrative task. It can be overcome with manual bookkeeping but still, a bit more effort would be needed. If this can be simplified then that would be great.

Overall, I haven't been happy with it.

Their licensing platform is absolutely awful. We've got locked out of our own account several times and that just has put a bad taste in my mouth. 

The initial setup is not exactly straightforward.

There have been some changes in its software. The portal, for example, has changed. One nuisance feature is that, when you login, you have to always press enter, which is annoying. With most sites, you just click on the login and you go. With this portal, you have to specifically hit enter.

The solution needs to offer live technical support. Right now, it's just a chat window and it's rather unhelpful.

Sometimes IBM MaaS360 seems buggy. The buggy nature of the solution is the first impression it gives out due to some mismatches in the solution, though in the background, it really works. At first, the tool may not look so efficient, but it is quite efficient in reality. The aforementioned area of concern can be considered for improvement.

In the future, I would like to see better integration capabilities in IBM MaaS360 that allow it to integrate with productivity software from Microsoft.

We had a problem with Microsoft computers. If you downloaded emails on a Microsoft Windows Surface PC, that would also require a license. The Outlook application didn't look great for us on a PC. 

The user interface could definitely use some improvement. It's very basic, but anyone not used to it might require some assistance. It's not really intuitive. I'd like to see more access at the account level. It's difficult to identify the number of licenses available in our account and to which interface they belong. We sometimes have to segregate; some users require the full enterprise features while others, who are partners or employees, are just given basic access. Being able to identify and assign the licenses would be very helpful. It's more of an administrative thing in terms of bookkeeping, but it would be great if that issue could be addressed.

We opted to go with Microsoft Intune because it just seemed to be a more mature and comprehensive enterprise solution, whereas IBM MaaS360 didn't seem to have the necessary breadth to manage all of our equipment. Along with laptops, I've had some BYODs. IBM MaaS360 just didn't seem as mature in our assessment.

The main issue we have with the solution is synchronization between the information and between the devices and the portal. The information that we see in the portal sometimes does not reflect, or not show, the real-time situation.

The user experience really isn't so good. It's important that they work to improve this aspect.

The product needs to improve tech support. 

The reporting and alerting could be improved.

From an improvement perspective, I would say that it could be more granular. MaaS360 could take features from both AirWatch and Jamf and integrate them into their solution.

Zero day support is something they can work on. They can make it a little bit more user-friendly as compared to Jamf or AirWatch.

Sometimes I would like to have local support because a company that provides 24/7 support means that the technical support staff are not always fluent English speakers. My English is  not fluent, but it's better to have an English speaker. It's sometimes hard to make yourself understood. We are looking at that now with the single sign-on and MFA, but that's been fairly smooth. 

• It would be ideal to add support for the distribution of windows.exe applications.
• They should allow for the building of custom reports with graphics. 

The cost has room for improvement.

The UI has room for improvement.

Possibly a notification if a device is wiped and no longer has the security policy on the phone. The product can also install the certificates on the phone in a 'smoother' way. It currently sometimes fails and we have to re-enroll the device multiple times.

I would like to see one-click app distribution to a single device or user. Perhaps I need further instruction in this area if it is supposed to function in this way currently. I would also like the ability to add a nagging message to any user that falls out of compliance.

Android device enrollment is a difficult process compared to how easy Apple IOS enrollment is. Also, there is a glaring security flaw were users can wipe their phones and they still show compliant in Maas360.

Another issue is when new Android phones come out, Maas360 is not able to implement the new features that have been introduced on the phone. For example when fingerprint login was available for Galaxy S5, Maas360 was not even ready to offer that feature as part of the policy you implement for your phone. Apple on the other hand usually has their features ready for Maas360 within the first few weeks of release.

Initial deployment and configuration.

Can be added process of export/import environment configuration to simplify any migration processes.

Overall, the solution is good, although I have not conducted a detailed examination of it. This said, I feel the pricing to be very high.

I would like advanced notifications of subscription renewals. Subscriptions automatically renew, and if you've downsized your user base, and you've overlooked the subscription, then you have to go through the exhaustive task of adjusting the contract. I don't think it's too much to ask for. I don't know of any other vendors that we currently use, who do not send out renewal notices

Improve user based licensing, so a customer can purchase named licenses for multiple devices. They do have the option, but I think it's 2.5 x the price of a device license, and users are limited to 3 devices. This isn't comparable to cpomp

Maybe more flexibility on user management, e.g. deleting users and editing corporate identifier.

Regarding laptop management, some features are not right. IBM needs to improve the features for the laptop.

It also needs a feature to restrict USBs.