MOS Outlook Associate common mistakes
MOS Outlook Associate · Understand the traps and how to avoid them.
Setting up an Automatic Reply (Out of Office) but leaving it disabled or scoped to the wrong date range, so the reply never fires during the test scenario.
Candidates enable the rule in the Automatic Replies dialog but forget to click OK to turn it on, or they set a start/end time that excludes the current simulated date. The dialog's on/off state is separate from the message text, and the toggle is easy to overlook.
What to do instead
After typing the message, verify the 'Send automatic replies' radio button is selected, confirm the date range covers the scenario, and click OK. Reopen the dialog to confirm the setting persisted before moving on.
Using Bcc incorrectly or placing recipients in To/Cc when the task explicitly asks for blind copies, exposing addresses the scenario says must be hidden.
The Bcc box is hidden by default in the message compose window, so candidates who do not enable it either skip Bcc entirely or dump everyone into Cc to compensate.
What to do instead
Enable Bcc via Options > Bcc (or the Bcc button in the compose ribbon) before adding recipients, then place only the intended hidden recipients there. Double-check To and Cc are empty or correct per the instructions.
Creating a rule that runs on all incoming mail instead of the specified conditions, or ordering conditions so the rule never matches the target messages.
The Rules Wizard presents many checkboxes and candidates tick broad conditions (e.g., 'from people or distribution list') without filling in the specific value, or they add 'stop processing more rules' too early so later rules never run.
What to do instead
Build the rule condition-by-condition: select the specific condition, then click the underlined value in the description to set the actual sender/subject/word. Test with a sample message and review rule order under Manage Rules & Alerts.
Replying with Reply All when only the sender should receive the response, or forwarding when a reply was requested, causing unintended recipients in the scenario.
Reply, Reply All, and Forward are adjacent buttons and keyboard shortcuts (Ctrl+R vs Ctrl+Shift+R) are easy to confuse under time pressure, especially when the original message had multiple recipients.
What to do instead
Before composing, confirm the intended audience from the task wording. Use Ctrl+R for Reply and Ctrl+Shift+R for Reply All deliberately, and check the To/Cc fields of the new message before sending.
Failing to attach a file that the task requires, or attaching the wrong file because the Insert File dialog defaulted to a different folder.
Candidates click Attach File, navigate quickly, and select a similarly named file; or they insert the file as a link/cloud attachment instead of a traditional attachment, which the scenario may not accept.
What to do instead
After attaching, read the attachment chip in the message header to confirm the filename and size. Use 'Attach as Copy' rather than 'Attach as Link' unless the task specifies a cloud link, and verify the file exists in the stated location.
Moving or copying a message to the wrong folder, or deleting it permanently when the task expects it in Deleted Items, because drag-and-drop landed on the wrong target.
Folder panes are narrow and drag targets are easy to miss; also Delete (moves to Deleted Items) and Shift+Delete (permanent) behave differently, and candidates use the wrong one.
What to do instead
Use the Move command (or right-click > Move) and pick the folder from the list rather than dragging. Confirm the message appears in the destination and is gone from the source. Use plain Delete unless permanent deletion is explicitly requested.
Scheduling a meeting without inviting required attendees or without checking the Scheduling Assistant for conflicts, resulting in a meeting the scenario would reject.
The To field in a meeting request is separate from the calendar, and candidates fill only the subject/location, or they ignore the Scheduling Assistant's conflict indicators and pick a time that clashes.
What to do instead
Add all required and optional attendees in the To field, open Scheduling Assistant to view free/busy, and choose a slot with no conflicts for required attendees. Verify the meeting appears on the calendar with the correct attendees.
Creating a recurring appointment or meeting with the wrong recurrence pattern (e.g., weekly instead of every weekday, or wrong end date), so the series does not match the task.
The Recurrence dialog defaults to weekly on the current weekday, and candidates accept defaults or misread 'every weekday' versus 'every week on Monday'. The end-date option is also easy to leave as 'No end date'.
What to do instead
Open Recurrence and explicitly set the pattern (Daily > Every weekday, or Weekly with the correct days), then set the range (end after N occurrences or by a date). Open one occurrence to confirm the series matches the described schedule.
Building a contact group but adding individual contacts instead of the intended members, or saving the group in the wrong folder so it is not found later.
The New Contact Group dialog requires using 'Add Members > From Outlook Contacts' and candidates sometimes type addresses directly, creating one-off entries; the group is also saved to the default Contacts folder, which may differ from the requested one.
What to do instead
Create the group with New Items > Contact Group, use Add Members > From Outlook Contacts to select the exact people, name it as specified, and save it in the folder named by the task. Open the group to verify the member list.
Creating a task with the wrong due date, start date, or status, or failing to assign it to the correct category/folder, so it does not reflect the required follow-up.
The task form shows Due date and Start date in separate fields, and candidates set only one; status defaults to 'Not Started' and is left unchanged even when the task is described as in progress. The To-Do Bar and Tasks folder also differ from flagged email.
What to do instead
Open the task and set Start date, Due date, Status, and Priority explicitly per the task text. Save in the specified Tasks folder or list, and confirm the task appears with the correct dates and status in the Tasks view.