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
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
Volume is not reputation
A mailbox can stay under its configured send limit and still have poor reputation. For example: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
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