> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tenantcore.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring & Reputation

> Understand the difference between infrastructure monitoring, sending reputation signals, and automatic enforcement in TenantCore.

# Monitoring & Reputation

TenantCore continues monitoring infrastructure after domains and mailboxes are created.

The goal is not just to tell you whether a resource exists. TenantCore also tracks signals that can show when an outbound environment is degrading.

## Infrastructure monitoring

TenantCore can monitor or surface conditions such as:

* tenant access
* Microsoft licence state
* application permission health
* DNS readiness
* sending IP or location
* mailbox usage
* sending-platform connection state

These are operational signals.

They tell you whether the infrastructure is configured and reachable as expected.

## Reputation monitoring

Reputation monitoring looks at sending outcomes rather than only configuration.

Important signals include:

* hard bounces
* outbound spam-related verdicts
* Microsoft restriction state where available
* sending counts and utilization

These signals can be evaluated at mailbox, domain, and tenant level.

## Volume is not reputation

A mailbox can stay under its configured send limit and still have poor reputation.

For example:

```text theme={null}
25 sends/day
+
bad list quality
=
high bounce or spam rate
```

Send limits control volume.

Reputation monitoring evaluates what happens to the messages being sent.

## Authentication is not reputation

Healthy SPF, DKIM, and DMARC are important, but they do not guarantee good sending reputation.

A correctly authenticated message can still be unwanted mail.

TenantCore therefore treats DNS/authentication health and reputation as related but separate parts of infrastructure health.

## BYOT vs. managed enforcement

Reputation visibility is useful across TenantCore plans.

The enforcement boundary is different depending on infrastructure ownership.

### BYOT tenants

TenantCore can provide:

* monitoring
* Reports
* alerts
* notifications
* reputation and risk visibility

For customer-owned Microsoft 365 tenants, TenantCore does **not** automatically make reputation-remediation changes to Exchange. The operator remains in control of that infrastructure.

### TenantCore-managed infrastructure

When TenantCore-managed infrastructure becomes available, managed environments may support automatic remediation under TenantCore's managed-infrastructure policy.

That distinction is based on who manages the infrastructure, not on the customer's plan tier.

## Reports

Reputation data feeds the broader Reports experience.

This lets the operator review:

* current state
* historical incidents
* resource-specific activity
* measured counts and rates
* related TenantCore actions

Monitoring tells you what is happening now.

Reports help explain what happened over time.