Inforcer, a company specializing in multi-tenant management for Microsoft 365, has been selected by Microsoft to join a new initiative aimed at helping Managed Service Providers (MSPs) handle the complexities of managing dozens or hundreds of customer tenants while preparing them for Copilot and other AI services. The announcement, made on September 18, 2025, positions Inforcer as one of the first partners in Microsoft’s #IntuneforMSPs program, giving MSPs access to streamlined tooling, direct engagement with Microsoft product teams, and readiness assessments for Copilot deployment.

The Details: What Inforcer’s Partnership Actually Delivers

According to the press release, Inforcer is one of only two software development companies selected for the initial phase of Microsoft’s new global initiative. The program is designed to help MSPs consolidate tooling, reduce operational overhead, and accelerate the delivery of Microsoft 365 and Copilot services for their customers.

Through the partnership, MSPs gain access to:

  • Integrated multi-tenant management across the Microsoft technology stack, including Intune, Azure Active Directory (now Microsoft Entra), Defender, Purview, and Sentinel.
  • Direct engagement with Microsoft product teams and MSP-focused sponsors, offering tailored support, training, and enablement resources.
  • Opportunities to influence Microsoft’s roadmap for MSP-focused features.
  • A purpose-built platform that standardizes Microsoft 365 policy configurations across tenants, enforces security baselines, monitors compliance, and prepares environments for Copilot and other AI services.

Inforcer also announced its membership in the Microsoft Intelligent Security Association (MISA), an invitation-only ecosystem of security vendors whose solutions integrate with Microsoft Security technologies. This cements its role inside Microsoft’s security partner sphere.

The company says its platform already serves over 800 MSPs, and it recently closed a $35 million Series B funding round, following a $19 million Series A, signaling strong market traction.

“We founded inforcer to give MSPs the tools and support they need to grow their Microsoft practices, deliver more value to their customers, and lead the way into the next wave of managed services,” said Jamie Daum, CEO and Co-founder of inforcer, in the announcement.

Jason Roszak, VP of Product for Intune at Microsoft, added: “Our partners like inforcer are building innovative capabilities on top of Microsoft Intune allowing MSPs to scale their operations, and deliver more secure and consistent services.”

A key highlight is a major platform release planned for October 2025, which will include a comprehensive Copilot readiness assessment that MSPs can run across their customers’ environments. This tool aims to audit data labeling, knowledge boundaries, and pilot configurations, reducing the risk of sensitive data exposure when generative AI features are enabled.

A note on the exclusivity claim: While the press release and several trade outlets report that Inforcer is “one of only two software development companies” in the initial phase, Microsoft has not publicly listed the roster or confirmed the exact number. Treat the “one of two” phrasing as vendor-reported until Microsoft provides direct confirmation.

Why Multi-Tenant Management Is a Headache for MSPs

Microsoft 365 has become the backbone of productivity for millions of small and medium businesses, but its native admin consoles were never built for high-volume, multi-tenant operations. MSPs routinely juggle multiple Microsoft portals—Partner Center, Intune, Microsoft Entra, Defender, Purview, Sentinel—on top of their own RMM (Remote Monitoring and Management) and PSA (Professional Services Automation) tools. This fragmentation leads to:

  • Repetitive, manual onboarding and configuration for every new customer.
  • Inconsistent policy enforcement across tenants, increasing security risk.
  • Difficulty proving continuous compliance and delivering repeatable Copilot pilots.
  • High administrative overhead that eats into margins.

A platform that centralizes policy templates, automates remediation, and provides tenant-level assessments can dramatically reduce per-tenant effort. That frees engineers to focus on advisory and advanced services rather than grunt work. Inforcer’s value proposition squarely targets this operational gap.

Copilot Readiness: The Hidden Requirement

Microsoft is pushing Copilot—and its security-focused sibling, Security Copilot—deep into the Microsoft 365 and Intune experience. Security Copilot’s integration with Intune and Entra, for instance, brings AI assistance into core admin workflows. Microsoft’s role-based Copilot offerings are set to hit general availability in a release wave starting October 1, 2025.

But Copilot’s effectiveness (and safety) hinges on clean tenant hygiene. If data isn’t properly labeled, access controls aren’t scoped, or governance is loose, AI tools can inadvertently expose sensitive information or make bad decisions at scale. Preparing for Copilot therefore requires more than just buying licenses; it demands verified data governance, sensitivity labeling, and policy baseline enforcement.

Inforcer’s planned Copilot readiness assessment directly addresses this. By checking labeling, knowledge boundaries, and pilot configs, it gives MSPs a repeatable, sellable pre-flight service. Instead of ad-hoc checks, they can offer a formal readiness engagement.

What This Means for You

For MSPs

If you manage multiple Microsoft 365 tenants, this partnership signals that Microsoft is finally acknowledging the tooling gap for service providers. Inforcer offers a chance to:

  • Standardize security baselines across all tenants, reducing drift and making audits simpler.
  • Automate remediation and rollback—which is critical when Microsoft changes default policies or new requirements emerge.
  • Launch tiered service offerings (e.g., baseline management, advanced security, Copilot enablement) with repeatable, automated processes.
  • Centralize telemetry from Defender, Sentinel, and other tools into one pane of glass, enabling SOC-like monitoring and faster incident response.
  • Shorten the time-to-revenue for Microsoft 365 projects and AI pilots.

But don’t take the marketing at face value. As we’ll cover below, you need to pilot the platform carefully before committing.

For In-House IT Teams (Especially at Mid-Sized Companies)

If you’re not an MSP, you may still feel the multi-tenant headache if your organization has multiple subsidiaries, locations, or environments. Inforcer is primarily MSP-focused, but the underlying capabilities—policy templating, drift detection, centralized security telemetry—are relevant for any organization managing multiple tenants. Your MSP may soon offer these services, so it’s worth understanding what’s possible.

For the Microsoft Ecosystem

This move signals that Microsoft is accelerating its investment in the MSP channel for Intune and Azure. Expect more partner tools and tighter integration between Microsoft’s admin surfaces and third-party platforms. MSPs that don’t adopt purpose-built multi-tenant management may find themselves at a competitive disadvantage as peers deliver faster onboarding, stronger security, and AI-ready environments.

Before You Jump In: What to Verify

No platform is a silver bullet. As you evaluate Inforcer (or any similar tool), dig into these areas:

1. Technical Pilots with Real Tenants

Test with a representative mix—regulated clients, standard SMBs, edge cases. Specifically:

  • How accurate are automated remediation suggestions? Run them side-by-side with manual audits.
  • How long does onboarding take per tenant, including consent, permissioning, and data access reviews?
  • Does it integrate smoothly with your existing RMM, PSA, and ticketing workflows?
  • What are the fail-safe rollback procedures when an automated change needs to be reversed?

2. Data Access and Privacy Boundaries

Copilot readiness tools—and any automation that reads tenant metadata or content—raise governance questions. Map out exactly what data the platform ingests, where it’s stored, and how it’s protected. Request SOC2 or equivalent audit reports, data residency guarantees, and deletion policies. For regulated customers, contractual protections for customer data are critical.

3. Vendor Lock-In and Portability

Ensure you can export policy templates, audit logs, and historical remediation data. If you switch platforms down the road, you don’t want to lose years of configuration intelligence. Look for open standards or documented APIs that reduce switching costs.

4. Operational Resilience

Centralizing management into one tool can create a single point of failure. Verify the vendor’s SLA commitments, incident response plans, and security posture (SOC2, penetration test history, etc.). Inforcer’s website references compliance certifications, but always ask for proof.

5. The “One of Two” Exclusivity

As noted, the claim that Inforcer is in a tiny exclusive cohort has not been publicly corroborated by Microsoft. If that exclusivity affects your purchasing decision or strategic value assessment, ask your Microsoft partner representative directly for confirmation.

Looking Ahead: October 2025 and Beyond

The next few months will be decisive. Microsoft’s release wave 2 for role-based Copilot begins on October 1, 2025, which means customers will soon be asking about AI pilots. Inforcer plans to drop its major release—including the Copilot readiness assessment—that same month, aligning neatly with Microsoft’s timeline.

Simultaneously, Security Copilot integrations with Intune and Entra are moving from preview to broader availability, embedding AI-assisted admin workflows into production environments. MSPs that prioritize governance and data labeling now will be better positioned to offer secure, repeatable AI-enabled services.

Watch for Inforcer’s actual release notes in October—check for feature parity with promises, real-world performance feedback from early adopters, and any new integrations that deepen the Microsoft stack coverage. Also keep an eye on whether Microsoft publicly confirms the initiative’s partner roster and what other tools might join the program.

For MSPs, the strategy is clear: start pilots now, validate the technology, and if it checks out, build a service catalog that turns AI readiness into a reliable revenue stream.