IBM MaaS360 Licensing Strategies for ITAM Leaders

IBM MaaS360 Licensing: A Comprehensive Guide for ITAM Professionals

Executive Summary: IBM MaaS360 is a cloud-based Unified Endpoint Management (UEM) solution offered on a subscription licensing model.

Global IT asset managers must understand IBM MaaS360 licensing to optimize costs and avoid surprises.

This guide offers an in-depth examination of licensing plans, cost drivers, negotiation strategies, and best practices to ensure you achieve maximum value and compliance from your MaaS360 investment.

Understanding the IBM MaaS360 Licensing Model

IBM MaaS360 is licensed on a subscription basis per managed device (or optionally per user), with monthly or annual billing. Each smartphone, tablet, or laptop enrolled in MaaS360 typically requires its license.

The model is straightforward – more devices and more advanced features mean higher costs – but careful management is needed to align licensing with actual usage.

For enterprise ITAM teams, this means continuously tracking the number of active devices and identifying which features are truly necessary.

By understanding the fundamentals of IBM MaaS360 licensing, organizations can prevent overspending and ensure compliance with their licensing requirements.

Remember that unused licenses still incur costs, and exceeding purchased quantities may require a true-up or risk service limitations (unless you enable an “overage” setting to allow auto-expansion with additional fees).

In short, MaaS360’s SaaS licensing offers flexibility to grow or shrink your deployment, but it’s on you to regularly adjust license counts to fit your evolving needs.

Comparing MaaS360 License Editions and Features

IBM offers four main MaaS360 editions: Essentials, Deluxe, Premier, and Enterprise. Each tier adds progressively more features and security capabilities. Choosing the right edition is crucial for striking a balance between functionality and cost.

Below is a comparison of the plans and what they include:

Pricing Note: Costs are indicative per-device list prices. Large enterprises often negotiate discounts below these list rates.

Additionally, while IBM quotes per device, consider discussing per-user licensing options if many users carry multiple devices – this can simplify management and potentially reduce costs in certain scenarios.

Each plan builds on the previous one, so understanding these feature bundles helps ITAM professionals determine which devices or user groups truly require the top-tier functionalities.

For example, you might license most employees under Essentials for basic device compliance, but use Enterprise licenses for a subset of devices that handle sensitive data and require threat defense. The key is not to overbuy features you don’t need – every upgrade in tier should correspond to a clear business requirement.

Aligning License Plans with Business Needs

Selecting the optimal MaaS360 plan requires aligning it with your organization’s specific needs and usage patterns.

Key considerations include:

• Device Types & Platforms: Identify the mix of devices you need to manage – e.g., iOS and Android phones, tablets, Windows or macOS laptops. Ensure the chosen MaaS360 edition supports all required platforms and form factors. Example: If your field teams only use iPads and require simple remote configuration, the Essentials plan may be sufficient. But if you also manage laptops with corporate email, you might require Deluxe for secure email integration.
• Security and Compliance Requirements: Assess your security policies and regulatory demands. Organizations with strict data protection needs may require the advanced security features in Premier or Enterprise (like identity management or threat detection). Conversely, if your environment is low-risk, you might avoid paying for capabilities you won’t use. Takeaway: Match the plan’s security features (encryption, threat defense, containerization) to your actual risk profile to avoid under-protecting or overspending.
• User Roles and Feature Needs: Different roles or departments may have varying needs. Executives and developers might need access to corporate email and content on mobile (pointing to Deluxe or Premier), whereas a shop-floor device might just need basic MDM (Essentials). Map features to user groups. This role-based approach prevents purchasing Enterprise licenses for everyone when only a fraction of users require those features. Actionable example: One enterprise segmented its licenses – standard employees on Essentials, sales staff on Deluxe (for mobile email), and IT admins on Enterprise (to leverage threat defense for critical devices). This tailoring saved costs by avoiding a one-size-fits-all tier.
• Scalability and Growth: Plan for the future. If you anticipate rapid growth in device count or are rolling out a BYOD program, consider how easily you can scale up licenses or upgrade tiers. All MaaS360 subscriptions are scalable; however, higher volumes should trigger discussions about volume discounts with IBM. Also, avoid locking into a long-term plan that cannot be flexed. Tip: Ensure your contract or purchasing vehicle allows adding (or removing) licenses as needed, and periodically re-evaluate if a higher tier might become necessary as your organization evolves (or vice versa).

By aligning licensing choices with these factors, IT asset managers can ensure they are right-sizing their MaaS360 investment – getting the needed functionality without paying for extras that don’t add value.

Managing Costs and Negotiating Better Deals

Cost drivers for IBM MaaS360 are relatively transparent: the number of devices (or users) under management, the chosen edition tier, and any additional add-ons or services.

However, enterprise agreements and negotiations can significantly affect your spend. Here’s how to manage costs and strengthen your position when negotiating with IBM:

• Volume Discounts: IBM typically offers scaled pricing for larger deployments. If you’re managing thousands of devices, don’t settle for paying the flat list price per device. Engage IBM or your reseller to discuss volume-based discounts or tiered pricing. Insight: Enterprises that widely deploy MaaS360 have reported substantial per-device price reductions (e.g., 15-30% off list) once they demonstrated the volume of licenses required. Always ask – the list price is often just a starting point for big customers.
• Multi-Year Commitments: Committing to a multi-year subscription can unlock better rates and benefits. IBM may provide pricing incentives for 2-3 year terms or enterprise license agreements (ELAs) that include MaaS360. Weigh the benefits of a locked-in lower rate against the flexibility you might sacrifice. Important: If you sign a multi-year deal, negotiate caps on annual price increases or currency adjustments. IBM periodically adjusts prices (for example, a general ~5-6% price “harmonization” increase took effect in 2025 for many software products). Protect your organization by having price increase limits or renewal price locks written into the contract.
• Bundling and Enterprise Agreements: Consider if MaaS360 can be bundled with other IBM products you use. Sometimes MaaS360 is included or discounted as part of a broader IBM security suite or ELA. For example, bundling MaaS360 with IBM’s broader Security portfolio (like QRadar SIEM or BigFix endpoint management) might yield overall cost savings. Just ensure the bundle indeed covers your needs – don’t pay for unnecessary IBM software just to get a slight discount on MaaS360. Always model the à la carte cost versus bundled cost across the term of the agreement.
• Per-User vs. Per-Device Licensing: By default, MaaS360 is sold per device. However, if each user in your company has multiple devices (such as a phone, a laptop, and possibly a tablet), consider asking IBM if per-user licensing is available. Some customers have negotiated user-based licensing where one user license covers a set number of devices. This can simplify tracking and potentially reduce costs if the average devices per user is high. It’s not an advertised model, but in negotiations, vendors can be flexible to win business.
• Leverage Competitive Alternatives: As an ITAM professional, you know there are alternatives (e.g,. Microsoft Intune, VMware Workspace ONE, MobileIron/Ivanti). While your organization may have chosen MaaS360 for good reasons (features or integration with IBM products), it’s useful to politely remind IBM that you have options. If Microsoft Intune is already included in your Microsoft 365 subscriptions, for instance, you can compare the incremental value MaaS360 provides against the cost. This leverage can encourage IBM to be more flexible on pricing or contract terms to keep your business. (Keep the tone collaborative, not adversarial: the goal is a fair deal, not a hostile negotiation.)
• Contract Flexibility: Negotiate terms that allow you to adjust license counts or editions as needs change. Avoid strict clauses that lock you into a set number of licenses for a long period without the ability to reduce if your device count falls. Additionally, clarify the process for true-ups or overages: Will IBM automatically bill for overuse (and at what rate), or will new licenses be blocked once the limit is reached? Understanding these details prevents budget surprises. A best practice is to disable auto-renew at list price and set your contract to require a quote/confirmation before renewal. This forces a pricing discussion each year, rather than silently renewing at potentially higher rates.

In summary, treat MaaS360 licensing like any major software investment: negotiate actively, forecast your needs, and lock in favorable terms.

IBM is a large vendor accustomed to enterprise negotiations – there is often wiggle room for savvy customers who come prepared with data and alternatives.

Optimizing MaaS360 License Usage

Securing a good price is only half the battle; you also need to optimize how licenses are utilized on a day-to-day basis.

Effective license management ensures you derive full value from what you’re paying and avoid compliance issues. Consider these best practices to optimize usage:

• Regular Usage Audits: Establish a cadence (monthly or quarterly) to review how many devices are enrolled and active in MaaS360 versus how many licenses you’re paying for. Identify unused or under-utilized licenses – for example, devices that were enrolled but haven’t checked in for 60+ days (perhaps due to employee attrition or device retirement). Reclaim those licenses promptly. One global enterprise discovered that 10% of their MaaS360 licenses were still attached to devices that were no longer in service, and reclaiming them resulted in significant savings on renewals.
• Retire and Reassign Licenses: IBM MaaS360 allows administrators to revoke a license from one device and reassign it to another. Make this part of your employee offboarding and device refresh process. When someone leaves or a device is decommissioned, ensure the MaaS360 license is freed up for reuse. This practice minimizes the need to purchase new licenses when new employees or devices are added.
• Implement Role-Based Access & Feature Controls: Not every user needs every feature. MaaS360 enables you to configure policies and access based on user roles. Use this to restrict high-end features to those who truly need them. For instance, only enable secure corporate chat or advanced mobile content management for specific groups. This doesn’t change the license tier requirement (all devices on a given tier have the features available). Still, it does ensure you’re not turning on features for everyone and potentially driving demand for higher tiers unnecessarily. It’s about aligning usage with the license level: if most users only use core MDM features, you might keep them on a lower-cost plan and only upgrade those who need more.
• Use the Self-Service Portal: IBM MaaS360 includes a self-service portal for end-users (for tasks like enrolling a new device, password resets, or locating a lost phone). Encourage your employees to use these self-service capabilities. This reduces the support burden on IT helpdesks. Indirectly, this is a cost optimization – fewer IT support hours spent on device management issues means the overall cost of managing the solution drops. In large deployments, empowering users can delay the need to hire additional IT staff or purchase separate support tools.
• Integrate with Existing Systems: Leverage MaaS360’s integrations with identity management (e.g., Azure AD for single sign-on) or security information and event management (SIEM) systems. Integration can streamline user onboarding and offboarding, as well as consolidate security monitoring. For example, integrating with your identity provider means that when a user is disabled in HR systems, their device can be automatically unenrolled, preventing license waste on former employees. Similarly, feeding MaaS360 alerts into a SIEM helps your security team see device compliance issues in context. These efficiencies don’t directly cut the subscription cost. Still, they maximize the value you get from the licenses and reduce indirect costs (by simplifying administration and improving security, which avoids incident costs).
• Monitoring and Reporting: Utilize the built-in license usage reports available in the MaaS360 portal. IBM’s tools can display real-time and historical usage, showing how many licenses are assigned versus purchased, and even provide alerts for approaching limits. As an ITAM manager, set up dashboards or schedule regular emails based on these reports. This proactive monitoring ensures you can react quickly – whether it’s to purchase more licenses before a big project rolls out (avoiding a last-minute scramble) or to reduce counts at renewal if you consistently see slack. Staying data-driven in your license management will impress stakeholders and avoid both overspend and compliance headaches.

By continually optimizing usage in these ways, enterprises can ensure they only pay for what they need and that the MaaS360 deployment runs efficiently. Optimization is an ongoing process – what’s true this year (e.g., number of devices, required features) might change next year, so make optimization a habit, not a one-time effort.

Avoiding Common Licensing Pitfalls

Even with the best intentions, organizations can stumble into some classic licensing pitfalls.

Here are common MaaS360 licensing mistakes and how to avoid them:

• Over-Licensing: This occurs when companies err on the side of caution and purchase far more licenses or higher-tier plans than they use. For instance, purchasing Enterprise licenses for all devices “just in case” but only using Enterprise features on a handful of devices. To avoid this, use the audits and role-based assignments described above. Start with what you need and remember you can always scale up later. Regularly compare active device counts and feature usage to your entitlements. If you consistently have a surplus, adjust your renewal quantities down or negotiate credits with IBM.
• Underestimating Security Needs: The flip side is being too frugal and not getting a high enough tier where it’s truly needed. If your environment suffers a security incident because devices lacked a needed capability (say you chose Essentials but later faced a mobile malware issue that Enterprise’s threat defense could have mitigated), the cost savings evaporate in the face of a breach. The lesson: assess risks and invest in the appropriate edition for those use cases that genuinely require advanced security. It may be that a hybrid approach (mixing license tiers) is best – just be careful not to leave critical assets under-protected to save a few dollars.
• Failure to Scale or Evolve: Businesses grow, merge, or change IT strategies. A common pitfall is sticking rigidly to the initial license count or plan and not revisiting it to ensure it remains effective. For example, an organization might initially purchase 500 licenses and then grow to 800 devices. Still, procurement bureaucracy causes a delay in acquiring more licenses – potentially leaving 300 devices unmanaged (non-compliant) or incurring unapproved overage charges. Avoid this by planning for growth: if a major rollout is approaching (e.g., a new mobile deployment to staff), engage IBM early to expand licenses, ideally at a pre-negotiated rate. Conversely, if you downsize or move some devices to another solution, don’t keep paying for MaaS360 licenses you no longer need. Build flexibility and review points into your contract to handle scaling up or down.
• Ignoring Renewal and Auto-Renewal Terms: Many SaaS contracts, including IBM’s, will auto-renew by default – often at list price if you had a discounted introductory term. If you ignore renewal dates, you could suddenly face a budget spike. This pitfall is avoidable by tracking contract end dates and initiating renewal talks well in advance. Always renegotiate the renewal – do not assume the vendor will extend the same discounts. If you’ve reduced usage, try to scale down at renewal. Set internal reminders 90 days before renewal to review your needs and engage with IBM or your reseller. Never let a renewal happen passively; use it as a checkpoint to optimize terms.
• Not Leveraging Support and Resources: IBM provides support services and a customer success team for MaaS360. Some organizations fail to tap into this, which is a missed opportunity. IBM’s experts can help you configure the solution optimally (which might reveal you don’t need certain add-ons or can use a feature more effectively) and ensure you’re aware of all features you’re entitled to. For instance, if you purchased the Deluxe option, are you using the Watson AI advisor feature that comes with it? Under-utilization of included features means lost value. By engaging with IBM support or partners, you can learn to use the product to its full potential (getting better ROI on the license) and also get tips on the most cost-effective license allocations. Additionally, if you encounter an unexpected usage pattern – such as a sudden surge in devices due to a new project – communicating with IBM can sometimes lead to short-term accommodations or a tailored solution rather than a punitive bill.

Avoiding these pitfalls comes down to staying proactive and informed. Licenses are not a “set and forget” asset – they need active management.

Regular training, vendor communication, and internal process checks will help steer clear of these common traps.

Future Outlook: IBM MaaS360 Licensing in 2025 and Beyond

The endpoint management landscape is continually evolving, and IBM has been enhancing MaaS360 with new capabilities, particularly in the areas of AI and security.

Looking ahead, ITAM professionals should keep an eye on a few emerging trends and potential changes in MaaS360 licensing:

• AI-Driven Features and Possible Add-Ons: IBM MaaS360 already touts AI (with Watson) for analytics and support. As AI capabilities expand (for example, more intelligent threat detection or automated policy recommendations), IBM might introduce these as new features or even new service tiers. Be prepared for the possibility of add-on licenses for advanced AI analytics or other premium capabilities. When planning budgets, leave room for these innovations if they could add value to your device management strategy.
• Consolidation into Broader Offerings: IBM has a history of bundling products (e.g., Cloud Paks). There is potential that MaaS360 could be packaged within a larger IBM security or cloud suite. If this happens, licensing might shift to a more holistic metric (like a platform fee or a broader license covering multiple tools). In 2025 and beyond, watch for any IBM announcements on unified licensing programs that might let you use MaaS360 alongside other IBM security products under a single entitlement. This could simplify management and potentially be cost-effective if you need those tools; however, it can also complicate things if you only want MaaS360. Stay informed and evaluate such offers carefully.
• Pricing Adjustments and Market Pressures: IBM periodically reviews its pricing. As noted, 2025 saw a general price adjustment across IBM software. Moreover, competition in UEM (from Microsoft, VMware, etc.) will likely influence IBM’s pricing strategy. We might see IBM introduce more flexible licensing (such as user-based subscriptions or SMB-friendly bundles) if the market demands it. Large enterprise customers should expect list prices to increase gradually (due to inflation, enhancements, etc.), so factor in an annual increase in your long-term cost projections (e.g., 5% per year). However, also use your leverage to negotiate that any increases correlate with genuine value gains (such as new features or improved support), not just inflation.
• Device Proliferation and IoT: The definition of “endpoint” is expanding. Beyond phones and laptops, organizations are managing IoT devices, wearables, and other non-traditional endpoints. MaaS360’s licensing in the future might extend to such devices or offer specialized plans for them. For example, if your company starts deploying smart glasses or rugged IoT sensors that require management, IBM may need to provide additional licensing or new modules to support them. Engage with IBM product management through user groups or your account reps to understand the roadmap. If you foresee a need (like managing a fleet of IoT devices), raise the question of how it’s licensed sooner rather than later. Being an early adopter might give you negotiation room for favorable terms on new device types.
• Cloud Integration and Data Residency: As more global enterprises utilize MaaS360, IBM could introduce region-specific cloud hosting or integration with local cloud providers to ensure data residency compliance. While this is more of a platform feature than a licensing change, sometimes regional hosting options come with different pricing or minimum commitments. If your enterprise has strict data residency requirements (such as keeping data in the EU or Asia), be aware of any licensing implications associated with these options (e.g., a specific SKU for EU-only services).

In summary, the roadmap for IBM MaaS360 will likely bring incremental changes rather than radical shifts.

The core per-device subscription model has been stable and is expected to remain so, but enhancements to capabilities and packaging are likely.

ITAM professionals should maintain a dialogue with IBM and industry peers, and revisit their MaaS360 licensing strategy at least annually to incorporate any new offerings or changes.

The goal is to ensure that as your enterprise’s device management needs evolve, your licensing remains aligned and your negotiations capitalize on the latest market developments.

Recommendations

In light of the above insights, here are expert tips to help you manage IBM MaaS360 licensing effectively:

• Regularly Right-Size License Counts: Conduct quarterly reviews to ensure active devices align with purchased licenses. Remove or reassign licenses for devices that are no longer in use to avoid paying for idle subscriptions.
• Tier for Need, Not Want: Align each user or device to the appropriate edition. Use lower-cost Essentials licenses for basic needs and reserve higher tiers (Deluxe/Premier/Enterprise) for use cases that justify the added features. This targeted allocation prevents overspending on premium plans that aren’t fully utilized.
• Negotiate Before Every Renewal: Treat each renewal as an opportunity to improve the terms. Don’t let contracts auto-renew without scrutiny. Engage IBM or your vendor well in advance to seek improved discounts, especially if your deployment has grown or if you can commit to a longer term.
• Leverage IBM and Partner Expertise: Utilize IBM’s customer success resources or certified partners. Have them review your MaaS360 setup and licensing. They might identify unused features you’re entitled to or suggest license optimizations. This external insight can ensure you’re getting full value for what you pay.
• Monitor Vendor Announcements: Stay updated on IBM’s product and pricing news (e.g., via IBM’s website, newsletters, or industry analysts). If IBM introduces new licensing models, add-ons, or price changes for MaaS360, you want to be among the first to know so you can adapt your strategy or negotiate accordingly.
• Secure Volume and Multi-Year Deals Strategically: If you have a large device count, push for volume discount pricing brackets. Similarly, consider multi-year deals for cost predictability, but only if you’re confident in long-term usage. Always include clauses to adjust if your needs change (e.g., the ability to drop some licenses or renegotiate if new features render your current plan obsolete).
• Integrate License Tracking into ITAM Tools: If you have an ITAM or software asset management tool, integrate MaaS360 license data into it. Having a single pane of glass for all software licenses (including MaaS360) helps ensure nothing slips through the cracks. You can set alerts in your ITAM system for approaching license limits or contract end dates to enable proactive management.
• Plan for the Worst (Audit/Compliance): Although MaaS360 is a cloud service with usage easily measured, treat compliance with the utmost seriousness. IBM could audit the license usage of large customers. Use the product’s reports to ensure you’re within purchased limits. Document your license entitlements and keep proof of any extra licenses purchased or special terms agreed upon. Being prepared protects you against any compliance dispute and demonstrates good governance.
• Compare ROI with Alternatives Periodically: As a best practice, periodically re-evaluate the endpoint management market every couple of years. Ensure MaaS360 still provides the needed value for its cost relative to competitors (which might be evolving quickly). This doesn’t mean you have to switch, but having current knowledge of alternatives’ capabilities and pricing arms you with data to either negotiate better with IBM or justify internally why MaaS360 remains the right choice.
• Foster Internal Awareness: Educate your IT and procurement teams about how MaaS360 licensing works. Simple actions, such as notifying managers that adding a new mobile line for an employee isn’t just a hardware cost, but also requires a MaaS360 license, can help control “license creep.” When everyone understands that licenses have a real cost, they are more likely to use them judiciously (e.g., uninstalling MaaS360 from devices that don’t truly need management).

Checklist: 5 Actions to Take

For a practical approach, here’s a step-by-step checklist to get a handle on your IBM MaaS360 licensing:

1. Inventory Your Endpoints: Compile a list of all devices currently managed (or needing management) in MaaS360. Break it down by type (mobile, tablet, laptop) and business unit. This is your baseline demand for licenses.
2. Map Devices to License Editions: For each group of devices/users, determine which MaaS360 edition best fits their needs. Create a simple matrix of departments/roles versus the required edition (E.g., Essentials, Deluxe). Use this to identify how many of each license type you ideally should have.
3. Compare Entitlements to Usage: Retrieve your current MaaS360 license entitlement (i.e., the number of each tier you own) and match it against the needs outlined in step 2. Note any discrepancies – e.g., are you under-licensed for a needed feature or over-licensed in areas where Essentials would do? Also, check the current usage in the MaaS360 admin portal to ensure all purchased licenses are in use.
4. Engage IBM or Your Reseller: Armed with the data, arrange a meeting with IBM or your licensing provider. Discuss any necessary adjustments–such as additional licenses, removing unused ones, or upgrading some licenses to different tiers. If renewal is within the next 6-12 months, start negotiating now based on your findings (volume discounts for growth, etc.). Ensure that you address contract terms, such as renewal pricing and flexibility, during this discussion.
5. Implement Ongoing Governance: Set up processes to keep this on track:
   • Schedule the next license review/audit on your calendar (at least quarterly).
   • Use MaaS360’s reporting to get a monthly email on license usage.
   • Update internal documentation: record your current license counts, contract terms (expiry, any special pricing), and points of contact at IBM.
   • Communicate any policy changes (like who can approve adding new devices to MaaS360) within IT to prevent uncontrolled growth.
     By having governance in place, you ensure that MaaS360 licensing remains optimized and no action items are overlooked.

Following this checklist will establish control over your IBM MaaS360 licensing and set you up for continuous improvement in cost management and compliance.

FAQ

Q1: How is IBM MaaS360 licensed in simple terms?
A: IBM MaaS360 is generally licensed on a subscription per device per month basis. You pay a recurring fee for each device that you enroll and manage through the platform. The exact fee depends on which edition of MaaS360 you choose for that device (Essentials, Deluxe, Premier, or Enterprise, each with increasing capabilities). In some cases, IBM can offer a per-user licensing model (where one user covers multiple devices), but this is typically arranged by special request. For most enterprises, counting managed devices is the core licensing metric.

Q2: What are the main differences between the MaaS360 license editions?
A: The four editions mainly differ in the feature sets they include:

• Essentials covers basic device management (policy enforcement, app management, inventory).
• Deluxe includes Essentials features plus secure email (containerized email app), an AI virtual assistant for users, and data containerization to separate work/personal data on BYOD devices.
• Premier includes everything in Deluxe and adds stronger content and identity management – think document distribution, secure browser for web access, and single sign-on integrations.
• Enterprise is the top tier, encompassing all prior features and incorporating advanced security, including mobile threat defense (for malware and phishing on devices), a secure chat app for encrypted communications, and integration hooks for security event monitoring systems.
  In short, higher tiers add more security and productivity features. Enterprises should match the edition to the device’s role – not all users will need Enterprise-level capabilities.

Q3: Can we mix and match different MaaS360 license tiers within our organization?
A: Yes, you can purchase a mix of license types to suit different needs. Many global organizations do this to optimize costs. For example, you might have 100 Enterprise licenses for high-risk or VIP users, 500 Deluxe licenses for general staff using email on mobile devices, and another 100 Essentials licenses for shared or kiosk devices. Technically, you manage all devices from the same MaaS360 portal; the license applied to each device just unlocks the respective features. Just be mindful to keep track of how many of each tier you’ve purchased. IBM’s license management tools will show if you try to assign more devices to a tier than you have entitlements for. Mixing tiers is a smart way to avoid overspending, as long as each device gets the appropriate license for its needs.

Q4: What if we exceed our licensed number of devices?
A: IBM provides options to handle this. You can enable “overage” in the MaaS360 portal settings, which allows the system to accept extra devices beyond your purchased licenses, reporting the overage. You would then need to true-up (purchase the additional licenses), typically at the next billing cycle. If you do not allow overage, the system will prevent new device enrollments once you hit your limit. For enterprises, it’s crucial to proactively manage this: regularly check license usage so you can purchase more licenses before they run out, or remove unused devices to free up licenses. Exceeding your entitlement without planning can lead to compliance issues or service disruption. IBM is usually cooperative in resolving overages (they’d rather sell you the needed licenses than shut off service), but it’s better to never let it get to that point. In short, monitor your usage; if you need more licenses, secure them via your IBM rep promptly.

Q5: Are there any hidden costs or unexpected fees associated with IBM MaaS360 licensing?
A: MaaS360 licensing is fairly transparent (no complex CPU or user metrics to calculate), but a few things to watch:

• Support Costs: Basic support is typically included in a SaaS subscription; however, check if you require premium support or dedicated account management, as IBM may charge extra for advanced support packages or professional services. Ensure you understand the level of support included with your subscription.
• Add-On Features: While the core features are in the bundles, IBM sometimes offers add-ons (for instance, integration with third-party tools like remote support software or specialized compliance modules). These usually cost extra. Clarify upfront if any feature you plan to use is an add-on versus included in your edition.
• Auto-Renewal at List: As mentioned earlier, if you got a discounted price for year one, be aware that at renewal, unless negotiated, the price might revert to standard rates. That’s not exactly a hidden fee, but it can catch teams off guard. Mark your calendar to renegotiate the renewal instead of accepting an auto-renewal invoice blindly.
• Currency and Region: IBM’s list prices might vary by country or region due to currency conversion and local market factors. If you operate globally, ensure that the licenses you purchase in different regions align. Sometimes enterprises end up with multiple contracts (e.g., one in Europe, one in North America) at slightly different rates. It could be beneficial to consolidate, if possible, or at least be aware of the total cost when calculating it.
  Overall, surprises are few if you carefully read your agreement. The “gotcha” most commonly reported by peers is simply paying for more licenses or higher tiers than needed, which our guide helps you avoid. Good governance and open communication with IBM will mitigate most hidden issues.

Do you want to know more about our IBM Advisory Services?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit