CoreView and the art of handing over fewer keys

Consider the City University of New York. Twenty-five campuses, hundreds of thousands of students, and roughly 700,000 mailboxes of different kinds. Now consider a smaller question: how much authority should the person fixing a problem at one campus have over everyone else?

CUNY wanted campuses to manage their own users. It also wanted security and a manageable workload for central IT. Those ambitions can pull in different directions. Centralize every decision and local teams wait. Distribute broad administrative powers and the consequences of one mistake can travel. CoreView sells software for that awkward space between the help desk and the master key.

01One tenant. Many boundaries.

A Microsoft 365 tenant is an organization’s environment for services such as Exchange Online, Teams, SharePoint, and Entra ID. CoreView adds a management and security layer across that environment. Its Virtual Tenants divide administration into logical scopes: a campus, a country, a department. These are administrative divisions within the platform, rather than newly created Microsoft tenants.

An administrator gets a defined combination of things they can see and actions they can take. That distinction is the product’s interesting trick. A local team can do useful work without receiving authority over the entire organization. At CUNY, virtual segmentation and role-based access were paired with automation and rules for consistent group naming.

The university’s case study describes nearly 4,000 automated change actions in one week. That is a count of actions, rather than a measurement of hours saved. Still, it makes the problem tangible. A repetitive task performed once is an inconvenience. Repeated across a university system, it becomes a staffing decision.

02The rental company that found €70,000

Mateco, an aerial work platform rental business, faced a related difficulty while expanding internationally. It wanted employees on one Microsoft 365 platform, with local administration appropriate to each country. Its teams needed to onboard users without acquiring excessive privileges. According to CoreView’s account, local training and native administrative capabilities were insufficient for the assignment.

CoreView supplied country-level segmentation, granular roles, and automation. License visibility produced a second benefit: Mateco reported €70,000 in licensing savings. The figure describes this customer’s experience, not the price of CoreView or a return every buyer should expect. The revealing detail is how a permissions project exposed a purchasing problem. Access and spending were hiding in the same administrative fog.

The lesson is available even to a company that never buys the software. Define who owns each population of users. Specify the actions those owners need. Inspect assigned licenses against actual requirements. Then automate a repeatable process. Software can carry out that arrangement; someone still has to decide what the arrangement should be.

“CoreView was the bedrock of our global expansion.”Imre Tholen · Mateco

03From a dashboard to a rewind button

Founded in 2014 by Ivan Fioravanti and David Mascarella, CoreView grew from the Microsoft management world. It received a $20 million investment led by Insight Venture Partners in 2018, followed by a $10 million Series B led by Insight Partners in 2020. Those disclosed rounds total $30 million. They describe financing, rather than revenue or the company’s present value.

A consequential expansion arrived in November 2023. CoreView acquired Simeon Cloud and appointed Simon Azzopardi as CEO. Simeon brought configuration management: baselines, backups, drift detection, and restoration. CoreView could connect everyday administration with the settings governing the environment itself. The acquisition announcement explicitly connected the deal to demand from customers and partners for configuration management.

That distinction matters during an incident. Recovering a file and restoring a security configuration answer different questions. CoreView’s proposition includes comparing configurations with an approved baseline, detecting changes, and restoring trusted settings. In January 2026, it announced Tenant Resilience alongside Tenant Management, making security and operational administration distinct buying priorities on its platform.

04The bill follows the identities

CoreView is business-to-business subscription software. Its current pricing page says charges depend on the number of Microsoft 365 licensed identities in the tenant, across plans and modules. It does not charge per administrator. Buyers request a quote, with support and onboarding options included in that discussion. Additional capabilities can change the scope of the purchase.

That model fits distributed administration: adding another local administrator does not itself trigger another administrator fee. The economic test remains specific to the buyer. Compare the quote with license waste, repeated work, and the cost of maintaining equivalent controls. An organization with simple requirements and little delegation may find less to justify than a multinational or university system.

Alternatives include Microsoft’s own administration tools and PowerShell, along with products such as ManageEngine M365 Manager Plus and AdminDroid. CoreView’s distinctive proposition is the combination of scoped delegation, operational automation, and configuration recovery around Microsoft 365. A buyer should test those workflows against its own environment, rather than assume a longer feature list settles the comparison.

05AI meets the permissions cupboard

CoreView’s newer products follow the same trail of accumulated access. Corey, its natural-language AI agent, reached general release in March 2026 after early access in 136 organizations. The company describes uses including investigating configurations, finding risky permissions, generating governance reports, and managing licensing. Its usefulness depends on the task and operator permissions.

Control for SharePoint followed in June 2026. It examines permissions at file, folder, and item level, ranks risks, and supports remediation with an audit record. The timing makes sense: AI-assisted discovery raises the stakes of old sharing decisions. A forgotten access grant becomes more consequential when information becomes easier to find.

There is an organizational condition underneath all of this. An approved configuration needs an owner. A delegated role needs a clear purpose. An automated action needs an agreed outcome. Buying a console does not resolve disagreements about those things. For a team evaluating CoreView, a useful pilot would follow one real onboarding task and one configuration change from request to review. Can the right person act? Can another person understand what happened? Can the team reverse a bad change? Those questions turn a demonstration into a working test.

The company’s Intelligence Labs now publishes practitioner research on Microsoft 365 security. Across these additions, the through-line is unusually consistent. Organizations need a way to understand authority, distribute it deliberately, and recover when settings change. The practical test for CoreView is whether the people nearest a problem can solve it while the boundaries still hold.