What CoreView announced
CoreView's launch announcement makes a statistical claim: in large enterprise tenants of around 90,000 managed objects, it observes close to 100 configuration changes a day. The announcement adds that roughly one in 25 of those touches a security-relevant control. It also says over three-quarters of those sit in privileged role assignment and Conditional Access. These are CoreView's own figures. They are not independently validated, and the company's own telemetry may not match your tenant.
The product itself:
- Hardening findings: the tool runs more than 100 checks. Examples in the announcement include an enterprise app holding
Directory.ReadWrite.All, an admin with a permanent privileged role, an app secret valid for more than 180 days, and an administrator with no MFA method registered. Each finding comes with evidence from the tenant. - Severity ranking and score: findings are broken down by severity.
- Drift detection: checks run daily for the first 30 days, then weekly.
- Configuration history: a versioned before-and-after record of the checked settings, stored in CoreView.
- Corey: CoreView's AI assistant, which explains findings and detected changes.
- Executive view: a summary of findings that can be shared with leadership.
The product page also lists some check types that are not in the press release. One is a Conditional Access MFA policy that sits in report-only mode and never blocks a sign-in. Another is a tenant setting that lets any user consent to apps. The page's screenshots are labelled illustrative, so treat them as examples of the output, not as results from a real tenant.
The limits that matter
This is where a careful reader should slow down.
It is not real-time. CoreView's FAQ says plainly that the history reflects the settings checked at each scheduled check. The tool compares the tenant's configuration with how it looked at the last check. A setting flipped and flipped back between two weekly checks may never appear. After the first month, the gap between checks is a week. If you need a full audit trail, the Microsoft 365 audit logs remain the source of record.
It is not a backup. The configuration history is a record to investigate with. CoreView says automated restoration belongs to its paid Tenant Resilience product. The announcement says teams that want to fix what they find can move to Tenant Resilience with their history already in place. That is a plain upsell path. The free tier is a legitimate tool, but it is also the front door to a commercial platform.
It cannot remediate anything. The product page says it cannot reset passwords, change directory settings, fix findings or restore configurations. Corey can only explain.
Corey has a cap. The product page says Corey is included within a monthly allowance. Neither the press release nor the page quantifies it.
How connecting works
CoreView's onboarding documentation (last updated November 18, 2026) describes a multi-tenant application that CoreView hosts and operates. Connecting it needs tenant-wide admin consent:
- Open the consent link you receive by email.
- Sign in as a Global Administrator or Privileged Role Administrator in Microsoft Entra ID.
- Follow the onboarding wizard and review the permissions on the Microsoft consent screen.
- Select Accept. You are then redirected to Tenant Observer.
CoreView estimates this takes about a minute. It says no software, user accounts or service accounts are needed. Submitting the sign-up form does not grant access by itself.
Permissions requested
The documentation lists these read-only Microsoft Graph application permissions:
- AccessReview.Read.All
- Application.Read.All
- AuditLog.Read.All
- DeviceManagementConfiguration.Read.All
- Directory.Read.All
- Domain.Read.All
- Reports.Read.All
- Policy.Read.All
- RoleManagement.Read.Directory
- SharePointTenantSettings.Read.All
- User.Read.All
- Group.Read.All
- Organization.Read.All
Read-only does not mean low-sensitivity. This set covers sign-in and directory audit logs, Intune configuration and compliance policies, Conditional Access and authentication-method policies, app credentials and permissions, and user and group data. CoreView says it does not read mailbox content, files, chats or Teams messages. Even so, a security team should weigh that breadth of metadata, because it describes your privileged structure in detail. That is what an attacker would want to see too.
Data retention and revocation
CoreView says the history it collects is kept while you stay connected and is deleted 90 days after you revoke consent. It says the application is hosted on Azure and holds ISO 27001, ISO 27018 and SOC 2 Type II certifications. Those are vendor statements, so verify them against your own vendor-risk process.
To review or remove the app, the documentation points to the Microsoft Entra admin center under Enterprise applications:
- Search for CoreView Tenant Observer.
- Select Permissions to see what was granted.
- Open Properties and either set "Enabled for users to sign in?" to No, or delete the application.
CoreView's FAQ says consent can be revoked in Entra without contacting the vendor.
How it sits next to Secure Score
CoreView positions the tool as a companion, not a replacement. It says Tenant Observer works alongside Microsoft Secure Score, adding the evidence behind each finding and a record of how each setting has changed. No comparative testing backs that up, so the claim is unproven. The concrete difference is the history and the named findings. Secure Score, by contrast, is Microsoft's own native tool. A cautious admin could treat Tenant Observer as a second opinion with a change log, not as an authority.
CoreView also offers a separate free Tenant Security Scanner. It uses a PowerShell script to scan the tenant against CIS Microsoft 365 v6.0.0 guidance and key Microsoft best practices. That is a different approach from Tenant Observer's hosted, connected service.
Practical advice for admins
- Treat consent as a change request. Granting tenant-wide consent to any multi-tenant app belongs in your normal approval process, even when the permissions are read-only.
- Check the consent screen yourself. Compare the permissions shown by Microsoft with CoreView's published list before you accept.
- Start in a test tenant if you have one. Then you can see the finding quality before touching production.
- Watch for the app showing up in your own audits. A new enterprise application with broad read access should be an expected, documented entry in your inventory.
- Don't mistake findings for fixes. Someone still has to remove the permanent Global Administrator or shorten the long-lived secret.
Bottom line
For small and mid-sized teams with no configuration-drift tracking, a free tool that names risky apps, admins and secrets is a useful starting point. The announcement's framing, with its big change-rate statistics, is marketing. The substance is a scheduled, read-only assessment with CoreView-hosted history and a clear route to a paid product. The free tool is real and the limits are stated openly by CoreView. Whether the trade-off suits you depends on your appetite for a third-party app holding broad read access to your tenant's identity configuration.
References
- CoreView launches free Tenant Observer for Microsoft 365 as tenants face close to 100 configuration changes a day - EIN Presswire EIN Presswire · 2026-11-19T14:00:00+00:00
- CoreView — Grant consent to Tenant Observer for Microsoft 365 help.coreview.com
- Free Microsoft 365 Tenant Observer | CoreView coreview.com