User mailbox full despite archive policy

Issue Summary

This article covers a Business Applications issue where User mailbox full despite archive policy. Use the path below to confirm scope, rule out simple causes, and move from user-safe checks into deeper administrator remediation without changing the article URL or taxonomy.

Symptoms and Scope

• The reported problem matches the article title: User mailbox full despite archive policy.
• Users can reproduce the issue consistently or after a recent change in Business Applications.
• A comparison with one known-good user, device, or workflow shows what is failing and what still works.

Tier I: Basic Checks

1. Confirm business impact, who is affected, and whether the issue is isolated or broader.
2. Ask what changed shortly before the first failure: password reset, update, policy change, device swap, migration, or network move.
3. Validate the simplest path first: sign out and back in, retry from a clean browser or app session, and compare with a known-good workflow.
4. Capture the exact error text, time of failure, and reproduction steps before deeper changes are made.

Tier II: Admin Investigation

1. Check mailbox, Teams, OneDrive, or SharePoint health plus any policy, license, permission, or sync changes affecting Business Applications.
2. Compare configuration, policy assignment, permissions, certificates, routing, or cache state against a working example.
3. Test the failing path in a controlled way so you isolate whether the break is user-specific, device-specific, location-specific, or service-side.
4. Apply the least disruptive fix first and verify whether the result survives a restart, reauthentication, or cache refresh.

Tier III: Advanced Remediation

1. Move to advanced remediation only after basic checks are documented and reversible.
2. Rebuild the affected profile, cache, OST, sync relationship, or client registration only after confirming the issue is not purely service-side.
3. If infrastructure is involved, review upstream dependencies such as identity, DNS, certificates, routing, storage, or application back-end health.
4. Validate the final state from the end-user view and from the administrative view so the fix is not only cosmetic.

Escalation Guidance

• Escalate when the issue affects multiple users, multiple locations, or a business-critical workflow with no safe workaround.
• Include exact symptoms, timestamps, what changed, what matched the known-good comparison, and which Tier I / Tier II / Tier III steps were completed.
• Attach screenshots, logs, event IDs, trace output, policy names, or node and article references as needed for the next technician.

Prevention and Documentation

• Document the confirmed root cause, the stable fix, and any setting that should become standard for future deployments.
• Update onboarding, change-control, or maintenance notes if the problem followed an avoidable rollout pattern.
• Where possible, add monitoring or validation that would catch the same failure earlier next time.