Missing Municipal Email: A Quarantine Review Checklist

Identify the message and the work waiting for it

Imagine a village employee expecting a resident's photos of a broken streetlight. The resident says the email was sent, but the employee cannot find it. The office needs to follow up on the report while someone investigates the message. A clear process gives both jobs an owner and helps staff avoid repeated requests that leave everyone unsure which copy is being reviewed.

For Michigan township, village, and city teams, begin with the exact sender address, intended municipal recipient, approximate sending time and time zone, and subject if known. Confirm the address used rather than relying only on a person's displayed name. Describe the work that is waiting and identify the employee who will handle it when the message is located. Share investigation details through the office's approved support channel.

Check the right mailbox and folders first

Confirm which mailbox should have received the message, including any shared department address. Use the approved mail application to search the folders that the employee is authorized to access. Include Junk Email, Deleted Items, and relevant filing folders. Check the search scope and date range. Record where you looked so IT can continue the investigation without asking staff to repeat the same search.

If the message is found, confirm its sender, recipient, date, and contents before treating it as the expected correspondence. Ask IT to review any mailbox rule or forwarding arrangement that may explain an unexpected destination. Keep the initial search focused on locating the item. Have the mailbox owner and IT agree on any changes needed to the way incoming work is routed.

Understand the quarantine actions available to staff

For Microsoft 365 cloud mailboxes, Microsoft's guidance explains that quarantine holds potentially dangerous or unwanted messages. What an employee can view, release, or request for review depends on the protection feature and quarantine policy. Some messages are available only to administrators by default. Ask IT to show staff the approved route for checking their actual environment and requesting help with an item they cannot see or manage.

Use that agreed review process when a legitimate message appears to be held. Provide the details of the expected correspondence and let the authorized reviewer assess the message and available action. Reach the review page through the municipality's known navigation or bookmark. Keep a suspicious notification or attachment with the established reporting process instead of following an unfamiliar sign-in link while trying to resolve the missing message.

Assign review and absence coverage

Microsoft documents quarantine notifications as dependent on the configured policy, with a configurable notification frequency. Ask IT to explain whether notifications are enabled, who receives them, and how the office handles an urgent missing-message inquiry between notifications. For a shared mailbox, have the primary employee and backup verify that they can perform the review tasks approved for that address.

Name the person responsible for following a review request through to a decision and covering that work during absences. Microsoft also documents an expiry time for quarantined messages; expired messages are unrecoverable from quarantine. Have IT account for that limit in the review process. Keep unresolved requests visible and give the municipal employee a clear next update rather than leaving the issue waiting in several people's inboxes.

Give IT specific evidence for a delivery investigation

If the message remains missing, send the known details and search results to IT. Microsoft's Exchange Online message-trace guidance describes following messages through the service and identifying receipt, rejection, deferral, delivery, and processing actions. An authorized administrator can use that information to investigate the particular message. Ask the technician to explain the result in terms of where the correspondence went and what remains to be checked.

Keep the sender, recipient, and time window consistent as the investigation moves between providers. If the sender received a failure notice, have IT explain how to supply the relevant notice through an approved route. Include only the information needed for the case. A useful support update identifies the evidence reviewed, the next responsible person, and whether staff need to take another action.

Confirm receipt and finish the follow-up

After an approved release or other correction, have the intended employee locate the message and confirm that the expected information is available. Match it with the original inquiry before requesting another copy. In the streetlight example, the assigned employee should know whether the photos were received, which report they belong to, and who is handling the next step for the resident.

If correspondence still cannot be recovered, have the municipal owner direct any further submission through the office's established intake process while IT continues its work. Record the technical outcome and the resident follow-up separately so neither is overlooked. For recurring problems, ask IT to review the cause and assess a targeted correction under the approved email-security policy. Verify another agreed sample message after the change.

Use this checklist for the next missing message

Walk through the process with the mailbox owner, absence backup, and IT provider using harmless sample correspondence. Record any unclear handoff and assign its correction.

• Identify the sender, intended address, sending time, and waiting work.
• Search the correct mailbox, folders, and date range.
• Use the approved quarantine review route and available permissions.
• Confirm notification settings, review ownership, and absence coverage.
• Give IT consistent evidence for the delivery investigation.
• Verify receipt and complete the department's follow-up with an assigned owner.