Start with one coverage arrangement

Imagine a village office arranging email coverage while a department employee is away. Someone sets up forwarding, the covering employee answers requests, and the original employee eventually returns. Months later, can the office explain which messages still go to the covering person and why? A useful review starts with that specific arrangement and follows it through to its current destination.

For Michigan township, village, and city teams, write down the mailbox address, the municipal purpose, and who approved the coverage. Identify the person responsible for answering requests and the date the arrangement should be reviewed. Include temporary assignments that continued after a staff change. Give IT the actual addresses through the municipality's approved support channel so the review concerns the correct accounts.

Have IT check both forwarding routes

Microsoft documents two automatic-forwarding mechanisms in Microsoft 365: Inbox rules that users can configure and mailbox forwarding that administrators configure. Ask IT to inspect both for the accounts under review. Staff can explain the intended workflow, while the authorized administrator checks the effective configuration and any additional routing involved in your environment.

Build a short record for each route: source mailbox, destination address, forwarding method, any conditions, and the approved purpose. Have IT distinguish an automatic forwarding rule from an ordinary folder-sorting rule. Record unclear entries as questions for follow-up. Ask the department owner to confirm the operational need before an old setting is accepted as part of the current workflow.

Confirm the destination and the working copy

Identify who currently controls each receiving account and whether that destination is approved for the information involved. Pay particular attention to an outside address, a former employee's account, or a temporary contact. Use known municipal contacts to verify ownership. If a vendor or another organization receives messages, have the responsible official confirm the purpose and approved handling before continuing the arrangement.

Microsoft's Exchange Online mailbox-forwarding guidance includes an option to deliver messages to both the forwarding address and the original mailbox. Have IT confirm how the actual route handles the original message. Then agree where staff will work the request, who will answer it, and how covering employees will see the response. Keep those decisions consistent with the office's existing information-handling and records procedures.

Review the controls for external forwarding

Microsoft 365 has controls specifically for automatic external forwarding. Microsoft explains that outbound spam policies can restrict it, while remote-domain settings and mail flow rules can also affect the result. A blocking control can override an allowance elsewhere. Ask IT to explain which controls apply to the reviewed route and whether an approved exception exists.

Microsoft also distinguishes these external-forwarding controls from automatic forwarding between internal users. Include internal routes in the municipal workflow review even when they are outside that particular policy's scope. If an expected message does not reach its destination, give support the time, source, destination, and any error received. Have IT diagnose the route before proposing a change to organization-wide protections.

Give unrecognized routes a prompt handoff

A destination nobody recognizes needs a timely review through the municipality's known IT support route. Describe what staff found, which mailbox is involved, and when it was noticed. Let the authorized technical team direct any evidence collection and account response. The immediate staff task is to get the finding to someone responsible for investigating it.

Keep a named owner on the follow-up and record the response in the approved support process. Have IT determine whether the setting reflects an old coverage arrangement, a configuration mistake, or a security issue. If broader decisions about disclosure or other obligations are needed, involve the municipality's designated officials and advisers through the established incident process.

Verify coverage after an approved change

Before an approved forwarding change, agree who will receive and handle new requests afterward. Ask IT to carry out the change and verify the technical result. Use a harmless sample message with an agreed subject and approved recipients to check the complete route. Have staff confirm the intended receipt, original-mailbox behavior, and person responsible for the reply.

In the village coverage example, close the temporary arrangement by confirming the returning employee's workflow and the covering person's remaining responsibilities. Record the result and any unresolved delivery question. Put forwarding review into future coverage closeouts and role changes so the next review starts with a documented purpose, an accountable owner, and a clear end point.

Keep this record for each reviewed route

Choose one department's coverage arrangement and collect these details with its owner and IT provider.

  • Source mailbox, forwarding method, and any conditions.
  • Exact destination and the person responsible for that account.
  • Approved purpose, original-message handling, and response owner.
  • Applicable external-forwarding controls and approved exceptions.
  • Unrecognized settings, assigned follow-up, and resolution.
  • Verified coverage after changes and the next review date.

YOUR NEXT STEP

Review one real email-coverage arrangement with staff and IT. Trace its automatic routes, confirm the destinations and approved purpose, resolve unfamiliar settings, and verify who will receive and answer the next request.

Need a hand putting a plan in place? Explore our Managed IT services for Michigan municipalities or talk with our team.

Further reading