A global media and communications conglomerate with 4,000 employees and multiple operating subsidiaries was managing a substantial Microsoft 365 environment across its communications, automotive, and media businesses.
The organization believed it had a reporting problem. Tenant administrators could not reliably see what was happening across the Microsoft 365 environment. App registrations were increasing, the secrets attached to them had expiration dates that were not being consistently tracked, and licenses were being assigned and forgotten. On top of this, temporary contractor accounts remained active after people left, holding licenses that cost the group money and created access risk.
Individually, these issues looked like operational inconveniences. Collectively, they pointed to a wider Microsoft 365 governance issue: the organization did not have a complete, current picture of what was running, who had access to it, or what would happen if it changed.
The IT team was relying on native Microsoft 365 reporting and manual processes to manage tenant visibility. That approach created several challenges. Native Microsoft 365 tooling required significant effort to aggregate data, was not proactive, and did not act on what it found. Tracking app secret expirations meant someone had to go looking. License reviews meant manually pulling data, interpreting it, and then creating a ticket to take action.
When a contractor became inactive, reclaiming their license depended on someone noticing the issue and following a process. None of this scaled easily across a tenant of this size, and none of it happened fast enough to prevent the exposure window between a condition appearing and someone acting on it.
Configuration changes created a similar problem. Tenant settings could shift, deliberately or otherwise, with no systematic record of what changed, when it changed, or who made the change.
In a multi-subsidiary environment where different teams administered different parts of the tenant, the cumulative effect of unmanaged configuration changes was significant. It created a gap between what administrators believed their environment looked like and what it actually looked like.
The organization first adopted CoreView for reporting, drawn by the platform’s ability to surface accurate, current data across a complex Microsoft 365 tenant. One subsidiary had already been using CoreView for nearly 10 years before the parent organization formalized its own deployment.
Over time, the organization has expanded its use of CoreView beyond reporting and into broader Microsoft 365 governance.
The team set up policies within CoreView’s Entra Apps Reporting capabilities to monitor app registration secrets and alert application owners ahead of expiration. Instead of waiting for an expired secret to break a service, the alert now reaches the owner before the problem reaches the user.
Through CoreView’s license optimization policies, the team now monitors inactive contractors and manages license downgrades and upgrades with minimal manual intervention. Across a 4,000-person organization operating across multiple subsidiaries, that has helped the organization recover thousands in wasted license spend.
The team adopted CoreView Configuration Manager to capture snapshots of Microsoft 365 tenant settings and monitor for change. That gave the organization two important capabilities: it could detect when a configuration drifted from its intended state, and it had a recovery point if something needed to be reversed.
Before Configuration Manager, a misconfigured setting would surface only when something downstream broke. Now, the team can see the change when it happens.
With CoreView, the organization moved from manual reporting and reactive cleanup toward a more controlled Microsoft 365 governance model.
The key benefits include:
CoreView gave the organization the reporting, automation, license optimization, and configuration management capabilities needed to move beyond manual Microsoft 365 administration.
For a multi-subsidiary enterprise, that control layer matters. It helps the organization see what is happening across the tenant, automate recurring governance tasks, detect configuration changes, and reduce the gap between what administrators think the environment looks like and what is actually happening inside Microsoft 365.
