Opinion: Mobile Device Management (MDM) Co-Existence

Introduction: The Reality of Multi-MDM Environments

In my fifteen years of enterprise mobility consulting, I’ve encountered a persistent question that makes many IT leaders uncomfortable: “Can we run multiple MDM platforms simultaneously?” The textbook answer is always “no”—every vendor, consultant, and best practice guide will tell you to standardize on a single platform. But the reality I see in enterprise environments tells a different story.

Today, I want to share my perspective on MDM co-existence—when it makes sense, when it doesn’t, and how to manage it successfully when you have no choice. This isn’t about advocating for complexity; it’s about acknowledging the real-world constraints that force organizations into multi-MDM scenarios and providing practical guidance for managing them effectively.

The Case Against MDM Co-Existence

Why Single-Platform is the Gold Standard

Before diving into co-existence scenarios, let’s acknowledge why the industry consensus favors single-platform deployments. These aren’t theoretical concerns—they’re real operational challenges I’ve seen organizations struggle with.

Operational Complexity:

• Administrative Overhead: Managing multiple consoles, policies, and procedures
• Skill Requirements: Teams need expertise across multiple platforms
• Inconsistent User Experience: Different management approaches confuse users
• Support Complexity: Troubleshooting becomes exponentially more difficult

Cost Implications:

• Licensing Costs: Multiple platform licenses and support agreements
• Training Expenses: Staff training across multiple platforms
• Integration Costs: Connecting multiple platforms to enterprise systems
• Operational Overhead: Increased time and resources for routine tasks

Security and Compliance Risks:

• Policy Inconsistency: Different security policies across platforms
• Compliance Gaps: Difficulty ensuring consistent compliance across platforms
• Visibility Challenges: Incomplete view of enterprise device security posture
• Incident Response: Complex investigation and response procedures

When Single-Platform Makes Perfect Sense

Most organizations should absolutely pursue single-platform standardization. Here are the scenarios where this approach is not just preferred but essential:

Greenfield Deployments:

If you’re starting fresh with no existing MDM infrastructure, there’s no excuse for multi-platform complexity. Choose the platform that best meets your requirements and stick with it.

Homogeneous Environments:

Organizations with consistent device types, user requirements, and operational models should standardize on a single platform that serves all needs effectively.

Strong Governance:

Organizations with strong IT governance and the ability to enforce technology standards should leverage that capability to maintain single-platform discipline.

Adequate Platform Capabilities:

When a single platform can meet all organizational requirements without significant compromises, there’s no justification for additional complexity.

The Reality of MDM Co-Existence

Why Organizations End Up with Multiple MDM Platforms

Despite the clear preference for single-platform deployments, I regularly encounter organizations running multiple MDM platforms. These aren’t cases of poor planning—they’re often the result of legitimate business constraints and requirements.

Acquisition and Merger Scenarios:

This is the most common driver of multi-MDM environments I encounter. When Company A (running Workspace ONE) acquires Company B (running Microsoft Intune), the immediate priority is business integration, not technology standardization.

Real-World Example: A financial services client acquired three smaller firms over two years. Each had different MDM platforms (Workspace ONE, Intune, and MobileIron). The business demanded immediate integration of sales teams and customer data, but IT was given 18 months to standardize technology platforms. During that period, they had to maintain all three platforms while gradually migrating to their chosen standard.

Regulatory and Compliance Requirements:

Some industries have regulatory requirements that effectively mandate platform separation. I’ve worked with healthcare organizations that must maintain separate MDM platforms for different types of data and user populations.

Real-World Example: A healthcare system needed to maintain separate MDM platforms for clinical devices (requiring FDA-validated configurations) and administrative devices (requiring standard corporate policies). The regulatory requirements made platform consolidation impossible without compromising compliance.

Geographic and Jurisdictional Constraints:

Multinational organizations often face data sovereignty requirements that complicate platform standardization. Different countries may have different approved platforms or data residency requirements.

Real-World Example: A global manufacturing company discovered that their preferred MDM platform wasn’t approved for use in certain countries where they operated. They had to maintain regional platforms while working through the approval process for their global standard.

Business Unit Autonomy:

Large organizations with autonomous business units sometimes end up with different MDM platforms due to independent technology decisions. While this can be addressed through governance, the business impact of forced standardization may outweigh the operational benefits.

Real-World Example: A conglomerate with diverse business units (manufacturing, retail, and services) found that each unit had different mobility requirements and had independently selected MDM platforms. Forcing standardization would have required significant business process changes that the organization wasn’t willing to make.

Technical Limitations and Gaps:

Sometimes organizations discover that their chosen platform can’t handle specific requirements, leading to supplementary platform deployment.

Real-World Example: A logistics company standardized on Microsoft Intune but discovered it couldn’t effectively manage their ruggedized Android devices used in warehouses. They had to deploy a specialized MDM platform for those devices while maintaining Intune for office workers.

The Spectrum of Co-Existence Scenarios

Not all multi-MDM scenarios are created equal. Based on my experience, they fall into several categories with different complexity levels and management approaches.

Temporary Co-Existence (Migration Scenarios):

Duration: 6-18 months
Complexity: Moderate
Management Approach: Migration-focused with clear end state

This is the most manageable form of co-existence because it’s temporary and goal-oriented. Organizations maintain multiple platforms during migration periods with a clear plan to reach single-platform state.

Segmented Co-Existence (Different User Populations):

Duration: Long-term or permanent
Complexity: High
Management Approach: Clear segmentation with minimal overlap

Different user populations or device types are managed by different platforms. This can work well when segmentation is clear and there’s minimal need for cross-platform integration.

Geographic Co-Existence (Regional Platforms):

Duration: Long-term
Complexity: Very High
Management Approach: Regional management with global coordination

Different geographic regions use different platforms due to regulatory, technical, or business requirements. This requires sophisticated coordination and governance.

Hybrid Co-Existence (Overlapping Capabilities):

Duration: Variable
Complexity: Extreme
Management Approach: Complex orchestration and integration

Multiple platforms manage overlapping device populations or provide complementary capabilities. This is the most complex scenario and should be avoided if possible.

Managing MDM Co-Existence Successfully

Governance and Strategy

If you find yourself in a multi-MDM scenario, strong governance becomes absolutely critical. Without clear policies and procedures, co-existence quickly becomes chaos.

Establishing Clear Platform Boundaries:

1. Device Type Segmentation:
   • Define which device types are managed by which platform
   • Document exceptions and approval processes for deviations
   • Establish clear criteria for platform assignment
   • Create decision trees for edge cases
2. User Population Segmentation:
   • Define user groups and their assigned platforms
   • Establish procedures for user transitions between groups
   • Document approval processes for exceptions
   • Create clear communication about platform assignments
3. Geographic or Business Unit Segmentation:
   • Define geographic or organizational boundaries
   • Establish coordination procedures between regions/units
   • Document escalation procedures for cross-boundary issues
   • Create governance structure for global coordination

Policy Standardization Across Platforms:

One of the biggest challenges in multi-MDM environments is maintaining consistent security and compliance policies across platforms.

1. Security Policy Alignment:
   • Document security requirements independent of platform
   • Map requirements to platform-specific configurations
   • Establish regular policy review and alignment processes
   • Create testing procedures to verify policy consistency
2. Compliance Management:
   • Define compliance requirements that apply across all platforms
   • Establish monitoring and reporting procedures
   • Create audit procedures that cover all platforms
   • Document compliance validation processes

Operational Management

Running multiple MDM platforms requires sophisticated operational procedures to maintain efficiency and effectiveness.

Administrative Structure:

1. Team Organization Options:
   • Platform-Specialized Teams: Dedicated teams for each platform
   • Cross-Platform Teams: Teams trained on multiple platforms
   • Hybrid Approach: Platform specialists with cross-platform coordinators
   • Centralized Coordination: Central team coordinating platform-specific teams
2. Skill Development:
   • Identify required skills for each platform
   • Develop training programs for cross-platform competency
   • Establish certification and competency validation
   • Create knowledge sharing procedures between teams

Operational Procedures:

1. Device Lifecycle Management:
   • Standardize device procurement and assignment procedures
   • Create platform-specific enrollment procedures
   • Establish device transfer procedures between platforms
   • Document device retirement and data protection procedures
2. User Support:
   • Create platform-aware support procedures
   • Train support staff on all platforms in use
   • Establish escalation procedures for platform-specific issues
   • Develop user self-service capabilities for each platform

Technical Integration

Multi-MDM environments require careful technical integration to maintain operational efficiency and security visibility.

Identity and Access Management Integration:

1. Directory Integration:
   • Ensure all platforms integrate with your directory service
   • Standardize user attribute mapping across platforms
   • Establish consistent group and role structures
   • Implement automated user provisioning and deprovisioning
2. Single Sign-On (SSO) Integration:
   • Configure SSO for all platform administrative consoles
   • Standardize authentication policies across platforms
   • Implement consistent session management
   • Establish audit logging for administrative access

Monitoring and Reporting Integration:

1. Centralized Monitoring:
   • Implement SIEM integration for all platforms
   • Establish consistent alerting and notification procedures
   • Create unified dashboards for operational visibility
   • Implement automated compliance monitoring
2. Unified Reporting:
   • Develop cross-platform reporting capabilities
   • Standardize metrics and KPIs across platforms
   • Create executive dashboards with unified views
   • Establish regular reporting schedules and procedures

Platform-Specific Co-Existence Considerations

Microsoft Intune + VMware Workspace ONE

This is one of the most common co-existence scenarios I encounter, often resulting from Office 365 adoption alongside existing VMware infrastructure.

Strengths of This Combination:

• Complementary Capabilities: Intune excels at Windows and Office 365 integration; Workspace ONE provides superior cross-platform management
• Natural Segmentation: Windows devices on Intune, other platforms on Workspace ONE
• Identity Integration: Both platforms integrate well with Azure AD
• Licensing Synergies: Intune may be included in existing Microsoft licensing

Management Considerations:

1. Device Assignment Strategy:
   • Navigate to Azure AD admin center → Devices → Device settings
   • Configure device registration settings for clear platform assignment
   • Use Azure AD groups to control device enrollment eligibility
   • Implement conditional access policies that respect platform boundaries
2. Application Management:
   • Use Intune for Microsoft 365 apps on Windows devices
   • Use Workspace ONE for cross-platform applications
   • Avoid overlapping application management where possible
   • Establish clear procedures for application conflicts

JAMF Pro + Microsoft Intune

This combination is common in organizations with significant Mac populations alongside Windows devices.

Strengths of This Combination:

• Platform Specialization: JAMF Pro provides superior Mac management; Intune handles Windows effectively
• Clear Segmentation: Natural platform-based boundaries
• Specialized Features: Each platform provides deep, native capabilities for its target platform
• User Experience: Platform-native management experiences

Management Considerations:

1. Identity Integration:
   • Configure JAMF Pro to integrate with Azure AD or your directory service
   • Ensure consistent user attribute mapping between platforms
   • Implement SSO for both administrative consoles
   • Establish consistent password and authentication policies
2. Policy Alignment:
   • Document security requirements independent of platform
   • Map requirements to platform-specific configurations
   • Establish regular policy review procedures
   • Test policy consistency across platforms

Specialized + General Purpose Platforms

Some organizations use specialized MDM platforms for specific device types alongside general-purpose platforms.

Common Scenarios:

• Ruggedized Devices: SOTI MobiControl for warehouse devices + Intune for office devices
• Healthcare Devices: Specialized healthcare MDM + general corporate MDM
• IoT Devices: IoT-specific management + traditional MDM for user devices
• Legacy Devices: Legacy platform for older devices + modern platform for new devices

Management Approach:

1. Clear Use Case Definition:
   • Document specific requirements that justify specialized platform
   • Establish criteria for device assignment to specialized platform
   • Create approval processes for exceptions
   • Regular review specialized platform necessity
2. Integration Strategy:
   • Minimize integration complexity where possible
   • Focus on security and compliance alignment
   • Establish monitoring and reporting procedures
   • Plan for eventual consolidation if possible

Cost Management in Multi-MDM Environments

Understanding the True Cost of Co-Existence

Multi-MDM environments have both obvious and hidden costs that organizations must understand and manage.

Direct Costs:

• Licensing: Multiple platform licenses and support agreements
• Training: Staff training across multiple platforms
• Integration: Additional integration and development costs
• Support: Vendor support agreements for multiple platforms

Hidden Costs:

• Operational Overhead: Increased time for routine tasks
• Complexity Tax: Additional effort for changes and troubleshooting
• Opportunity Cost: Resources that could be used for other initiatives
• Risk Costs: Potential costs from security or compliance issues

Cost Optimization Strategies

If you must operate multiple MDM platforms, there are strategies to minimize costs and maximize value.

Licensing Optimization:

1. Right-Sizing:
   • Regularly review device counts and licensing requirements
   • Optimize licensing tiers based on actual feature usage
   • Negotiate volume discounts across platforms where possible
   • Consider bundled licensing options
2. Feature Rationalization:
   • Avoid paying for duplicate capabilities across platforms
   • Choose licensing tiers that match actual requirements
   • Regularly review and optimize feature usage
   • Eliminate unused or redundant features

Operational Efficiency:

1. Automation:
   • Automate routine tasks across all platforms
   • Implement cross-platform monitoring and alerting
   • Use APIs to integrate platforms where beneficial
   • Automate reporting and compliance checking
2. Standardization:
   • Standardize procedures across platforms where possible
   • Use common tools and processes
   • Implement consistent naming and organizational standards
   • Create reusable templates and configurations

Security Considerations in Multi-MDM Environments

Maintaining Security Posture

Multi-MDM environments create additional security challenges that require careful attention and management.

Policy Consistency:

1. Security Baseline Development:
   • Define security requirements independent of platform
   • Map requirements to platform-specific configurations
   • Establish regular policy review and validation procedures
   • Test policy effectiveness across all platforms
2. Compliance Monitoring:
   • Implement unified compliance monitoring across platforms
   • Establish consistent compliance reporting
   • Create audit procedures that cover all platforms
   • Implement automated compliance validation

Incident Response:

1. Unified Incident Response:
   • Develop incident response procedures that cover all platforms
   • Train incident response teams on all platforms
   • Establish communication procedures between platform teams
   • Create escalation procedures for cross-platform incidents
2. Forensics and Investigation:
   • Ensure forensic capabilities across all platforms
   • Standardize evidence collection procedures
   • Establish chain of custody procedures
   • Train investigators on all platforms in use

Identity and Access Management

Consistent identity and access management becomes critical in multi-MDM environments.

Centralized Identity Management:

1. Directory Integration:
   • Ensure all platforms integrate with centralized directory
   • Standardize user attribute mapping
   • Implement consistent group and role structures
   • Automate user lifecycle management
2. Access Control:
   • Implement role-based access control across platforms
   • Establish consistent administrative permissions
   • Use principle of least privilege
   • Regular access reviews and certification

Planning Your Exit Strategy

Why Exit Planning Matters

Even if multi-MDM co-existence is necessary today, you should always have a plan for eventual consolidation. Technology landscapes change, business requirements evolve, and what’s necessary today may not be necessary tomorrow.

Benefits of Exit Planning:

• Cost Reduction: Eventual consolidation reduces licensing and operational costs
• Complexity Reduction: Simplified operations and management
• Improved Security: Consistent security policies and monitoring
• Better User Experience: Consistent management experience for users

Consolidation Strategies

When the time comes to consolidate, there are several approaches depending on your specific situation.

Natural Attrition:

Allow one platform to naturally shrink through device refresh cycles and user transitions.

Approach:

• Stop enrolling new devices on the platform to be retired
• Migrate devices during natural refresh cycles
• Gradually reduce licensing and support agreements
• Maintain platform until device count reaches acceptable threshold

Best for: Organizations with high device refresh rates and flexible timelines.

Planned Migration:

Execute a structured migration project to move devices from one platform to another.

Approach:

• Develop comprehensive migration plan
• Execute phased migration with pilot groups
• Provide user training and support
• Decommission old platform after migration completion

Best for: Organizations that need to consolidate quickly and have resources for migration projects.

Platform Evolution:

Choose a single platform and enhance it to meet all requirements, eliminating the need for multiple platforms.

Approach:

• Identify gaps in chosen platform
• Work with vendor to address gaps
• Implement additional tools or integrations as needed
• Migrate devices as platform capabilities mature

Best for: Organizations with strong vendor relationships and influence over platform development.

Conclusion: Making Multi-MDM Work When You Have No Choice

Let me be clear: I’m not advocating for multi-MDM environments. Single-platform standardization remains the gold standard for good reason. But I’ve learned that the real world doesn’t always align with best practices, and sometimes you have to make the best of a complex situation.

If you find yourself managing multiple MDM platforms, remember these key principles:

• Acknowledge the Complexity: Don’t underestimate the operational overhead and challenges
• Invest in Governance: Strong governance is absolutely critical for success
• Focus on User Experience: Don’t let platform complexity impact user productivity
• Maintain Security Standards: Ensure consistent security across all platforms
• Plan Your Exit: Always have a consolidation strategy, even if it’s long-term
• Measure and Optimize: Continuously monitor costs and effectiveness

The organizations I’ve seen succeed with multi-MDM environments share common characteristics: they treat it as a temporary necessity rather than a permanent solution, they invest heavily in governance and procedures, and they never stop looking for opportunities to simplify.

Most importantly, they’re honest about the costs and complexity. Multi-MDM co-existence isn’t free, and it’s not easy. But with proper planning, governance, and execution, it can be managed successfully while you work toward a simpler future state.

The key is recognizing that sometimes the perfect solution isn’t available, and the best approach is to manage complexity effectively rather than pretend it doesn’t exist. In my experience, organizations that acknowledge this reality and plan accordingly are far more successful than those that ignore the complexity and hope it goes away.