MO-111 Microsoft Word Expert (Microsoft 365 Apps) Study Guide

Independent AI-assisted resource — HUMAN REVIEW PENDING. The October 28, 2026 team refresh reconciles this complete guide and detailed objectives with current public exam, product and learning evidence. See the current group report and sources-and-objectives record. Source limits and unexecuted exercises remain explicit. This is not human review or live product validation. The official blueprint is authoritative.

Study guide at a glance

Start here

Report an issue with MO-111

Blueprint checked2026-10-28

Review stateReview required

Guide-only active reading30 min–1 hr

Prerequisites: No formal certification prerequisite; build approximately 150 hours of hands-on Word experience with long, reusable, collaborative, and specialized documents.

Exam essentialsRead the objective map, key distinctions, and readiness checklist.

Deep understandingWork through every domain, including decisions, failure modes, and related items.

Hands-on labsBegin with Use the first hands-on exercise in the guide, then use the remaining labs to produce evidence you can inspect and explain.

Official objective domains

• See the objective map in this guide

The active-reading range uses 90–130 words per minute for technical material. Labs, troubleshooting, note-taking, spaced review, and prerequisite gaps add time; it is not a total preparation promise.

Assessment contract: 50-minute proctored practical assessment; about 150 hours of advanced hands-on use is Microsoft preparation guidance.
Current scope: document options/settings; advanced editing/formatting; custom elements; advanced Word features.
Change watch: No retirement or replacement is listed on the credential page, checked October 28, 2026. The current Microsoft expiration policy gives MOS a five-year lifetime; check the dates on your earned credential.
Detailed coverage: All 47 tasks in the three-page skills PDF are mapped in the review report. The automatic page monitor covers four broad domains. No desktop Word lab was executed during this review.

How to use this guide

Expert work is systems work: reusable templates, durable styles, controlled sections, dynamic fields, automated bulk output, and safe review. Practice long documents in copies so you can diagnose field, section, protection, and automation failures without losing evidence. The current credential page lists ten exam languages and no dedicated Learn training collection. Use the desktop application and confirm the testing center’s environment; a web workflow or an Insider feature is not proof of exam availability. All study-time estimates below are suggested practice budgets, not provider runtimes.

VERIFY CURRENT — practice platform: Confirm the testing center's exact delivery/build before scheduling. For Compass Cloud: In-Center, Certiport's October 22, 2026 candidate guide says MOS Live-in-the-App exams run in a Windows VM even when the client is a Mac or Chromebook. This does not establish that every center uses Cloud. Mac and web product practice can teach concepts, but it does not establish parity with the assessed Windows workflow. Keep the platform boundaries beside each task. See Certiport candidate platform guidance. The public MOS Microsoft 365 Apps interface tutorial distinguishes exam controls from ordinary application practice: some commands, including Encrypt with Password, are disabled in the exam environment. Local product exercises below are learning tasks, not a promise of the available exam UI or actual assessment items.

About related items: A Related item: callout adds architecture, governance, or troubleshooting context. It is supporting knowledge, not a claim that its wording is in the published objectives.

Objective map

Published domain	Working question
Manage document options and settings (20–25%)	Can the file be prepared, protected, navigated, and delivered for a specialized audience?
Use advanced editing and formatting features (20–25%)	Is complex structure reusable and stable as content changes?
Create custom document elements (20–25%)	Can templates, styles, building blocks, indexes, and references be maintained centrally?
Use advanced Word features (25–30%)	Can forms, mail merge, fields, macros, and collaborative controls produce verified output?

1. Document options and settings

Configure themes, style sets, defaults, properties, templates, compatibility, language, hyphenation, line numbering, pagination, and print/export behavior. Use sections for distinct headers, footers, numbering, columns, orientation, or page setup; control Link to Previous explicitly.

Restrict formatting/editing, mark final, and use document inspection according to the actual control requirement. Protection influences editing behavior but does not replace storage permissions, encryption, records controls, or a retained source copy. Create reusable templates without overwriting the master with case-specific data.

A template defines the starting environment, but an existing document is its own artifact. To change a template, open that template for editing and save a new version; creating a document from it does not edit the master. Changes to Normal.dotm, including its default font, apply to future documents based on it. Preserve a copy of custom templates before a practice change. Keep a template containing macros in a macro-enabled format, and distinguish that template from a macro-enabled document.

For a concrete Windows review exercise, save a synthetic Original with “Delivery within 10 days,” and a Revised copy changing 10 to 15. Use Review → Compare with the correct original/revised files and explicitly show changes in a new document; inspect the one intended text difference and retain both sources. If either source already has tracked changes, inspect the comparison prompt and the implications before proceeding on copies. Reversing the two inputs reverses the meaning of insertion/deletion. For two reviewer copies, make one tracked wording change and one separate tracked punctuation change, then Review → Compare → Combine, label unmarked changes and retain a new combined copy. Inspect both contributions and deliberately accept/reject them there. Comparison, combining reviewer contributions and restoring a storage revision remain different operations. See comparison scope and destination choices and combining labeled reviewer revisions.

Customize the Quick Access Toolbar with the commands the task requires, and expose hidden tabs such as Developer through ribbon customization. Check whether a customization belongs to the application, a document or a template before relying on it on another machine. Editing/proofing language controls language-specific assistance and hyphenation; display language controls the interface. Neither setting translates existing text.

Version history, comparison and combination solve different problems: history retrieves a saved revision where the storage system supports it; comparison shows differences; combination consolidates reviewers' revisions. A link to external content retains a dependency on its source, unlike a pasted copy. Test refresh behavior with the source available and unavailable, and decide which form the recipient needs. A password to open a file differs from editing restrictions inside it; verify the specific requested operation.

Worked document dependency and protection check

VERIFY CURRENT: these command names describe desktop Windows; Mac and web capabilities differ. In a disposable report, use Insert → Object → Create from File, select a synthetic source file and select Link to file. Save both files, change the source and update the linked object; compare with a separately embedded copy. Close/reopen the destination, then temporarily rename the source to test the missing dependency. Restore the source afterward. The linked representation should reflect a deliberate source update; the embedded copy should remain independent. A cached display with the source unavailable does not prove a successful refresh. See linked versus embedded objects.

For an editable form copy, open Developer → Restrict Editing, choose the intended editing restriction and start enforcement. Check both an allowed entry and an attempted change outside the allowed region; stop protection with the practice password to prove recovery. On another copy, use File → Info → Protect Document → Encrypt with Password, confirm a temporary password, save, close and reopen. Test an incorrect password and the retained correct password, then remove the password and save again. Keep the unprotected synthetic original and password recoverable. Restricting edits and requiring a password to open produce different outcomes. See form restrictions and Word password protection.

2. Advanced editing and formatting

Use advanced Find/Replace for styles, formats, fields, special characters, and patterns; prove the scope before replacement. Define multilevel lists linked to heading styles. Control pagination through section/page breaks, Keep settings, widow/orphan control, and table-row behavior.

Manage styles by inheritance: base style, following style, priority, visibility, and direct-formatting exceptions. Use columns, tabs, leaders, drop caps, text direction, and linked text boxes deliberately. Sort lists/tables and perform calculations only after confirming data type and range.

Related item: A long document is maintainable when meaning drives formatting. If every heading is merely bold 16-point text, navigation, automatic contents, outline numbering, and global revision all become fragile.

Word wildcard patterns are not general-purpose regular expressions. Enable the appropriate search mode, test on a copy, inspect several matches and check formatting/style criteria separately. After replacing, verify both the replacement count and nearby text. Choose an insertion point deliberately before using paste options: preserving source formatting, adopting destination characteristics, retaining text only, and pasting a picture produce different editable results. Plain-text paste can still preserve list markers according to the application's settings.

Create and modify paragraph, character and table styles separately. Use the style Organizer to copy a named style into the required document/template and confirm the destination before overwriting a same-named style. Test it on representative content: transferring a style definition does not itself prove all intended paragraphs now use it. Hyphenation and line numbering are layout controls; they do not replace paragraph pagination rules.

Worked page repair

On a two-page synthetic document, place a heading near the bottom of page 1. In Paragraph → Line and Page Breaks, apply Keep with next to the heading and Keep lines together to its short following paragraph. Add text above them: the pair should move together when space is insufficient. Compare Page break before, which deliberately starts the selected paragraph on a new page. Avoid chains of Keep with next on every paragraph, which can make a large block jump unexpectedly. See paragraph pagination controls.

In Layout, enable automatic hyphenation for ordinary body text, then set Don't hyphenate on one selected paragraph and inspect a long word near the margin. Use Layout → Line Numbers → Restart Each Page, inspect Print Layout on both pages, then suppress numbering for one paragraph. Page numbering and numbered lists should remain independent. The line-number reference explains why lines inside tables/text boxes do not behave like ordinary body lines. Check actual pagination after changing margins or fonts. See Windows and Mac hyphenation controls.

3. Custom document elements

Create, modify, organize, and reuse custom styles, templates, themes, Quick Parts/building blocks, AutoText, headers/footers, and content controls. Understand whether an element lives in the document, its attached template, or another template so it travels and updates as intended.

Build and update tables of contents, figures, authorities, citations/bibliographies, captions, cross-references, indexes, bookmarks, and fields. Mark entries consistently, choose formats/options, then update all fields before output. Field codes and results are distinct; locking a field prevents an accidental update but can also leave stale output.

For Quick Parts, save the selected reusable content with a recognizable name, gallery/category and intended template. Retrieve it into a second document to prove it is available there. Custom color/font sets feed a theme; a style set coordinates styles. Change one layer at a time and inspect text with direct formatting, which may not follow the expected theme change.

Worked reusable design pack

Create a synthetic two-paragraph Delivery Clause and save it through Insert → Quick Parts → Save Selection to Quick Part Gallery into the intended practice template. Include its paragraph mark if paragraph formatting must travel. Reinsert, revise its text and save with the same name/category/gallery to redefine it; use Building Blocks Organizer → Edit Properties to rename it. Delete only the disposable entry, then confirm an already inserted instance remains but the gallery entry is gone. This distinguishes stored building blocks from document instances. See Quick Parts creation and management.

In Design → Colors → Customize Colors, change Accent 1 and save a named color set. In Design → Fonts → Customize Fonts, choose heading/body fonts and save a named font set. Apply both, choose an effects set and use Themes → Save Current Theme to create a named .thmx. Apply it to a second document containing theme-aware headings and a shape; compare direct-formatted text that may not follow it. A color/font set is one theme component, and this document theme is separate from the application's interface color scheme. See custom theme components and saving.

Optional validation exercise — not a required lab outcome: investigate saving a coordinated style set after modifying Heading 1 and Body Text definitions, including paragraph spacing. VERIFY CURRENT — Unconfirmed — validation needed: the precise Save as New Style Set gallery action is supported here only by a December 2020 firsthand Windows Word 365 report and named MVP replies; current first-party style guidance confirms definition changes but does not document this save action. If you choose to investigate, use only a disposable Windows desktop document/template. If the target build offers the action, save the named set, create a new second document, close/reopen Word and apply the saved set there; inspect both named styles and retain the saved set artifact. Otherwise record the build, missing/different command and unresolved artifact gap; do not require successful creation to complete this exercise. Do not change Normal.dotm merely to make the exercise succeed. A saved .thmx or general .dotx template alone is not evidence that a reusable style set was created.

An index is built from marked entries, not from a table of contents. Mark a main entry and a subentry, insert the index, move the source text and update the index. Captions supply the labels and numbering for tables of figures: distinguish a figure label from a table label and verify the corresponding generated list. Maintain bibliography source records, insert citations tied to them and then generate the bibliography; editing typed citation text is not equivalent to correcting its source record.

Worked captions and generated lists

Select each of two synthetic figures and use References → Insert Caption with the Figure label, descriptive text and the requested position/numbering format. Caption a table with the Table label. Insert a table of figures at a clear location, choose the Figure label and adjust its format/options; insert a separate Table list when requested. Change one caption's wording, move another object/caption and update the entire table, then compare entry text and page numbers. Updating only page numbers will not incorporate changed caption text. If the table appears in the figure list, inspect its caption label. See caption properties and updates and table-of-figures insertion and options.

Worked fields and fillable controls

On Windows desktop, set the document's Title property to Practice Pack. Use Insert → Quick Parts → Field, choose DocProperty and Title, and insert the result. Change the property, update the field and inspect the result; use Edit Field to change its selected property to Author and inspect the code/result distinction. Braces typed as text do not create fields. Field insertion/editing guidance explicitly bounds full field editing to Windows desktop; Mac/web capabilities vary by field.

In a separate form copy, expose Developer and insert a plain-text control for a reference, a date picker for the requested date, a check box for acknowledgment and a drop-down with Standard and Urgent choices. Select each control and use Properties to set a meaningful title and its appropriate defaults/options. Use Design Mode for instructional text, then leave Design Mode. Prevent accidental deletion where required while allowing contents to change. Test both listed choices, a date and a long text entry after applying suitable form protection; Contents cannot be edited would defeat an intended drop-down selection. A combo box allows typed choices whereas a drop-down constrains them. These are Windows controls; the form reference gives a different Mac workflow and says web form creation is unavailable.

4. Advanced features

Mail merge separates main document, data source, field mapping, filtering/sorting, rules, preview, and final merge. Validate several records—including blank and long values—before producing all labels, envelopes, email, or documents. Never send directly until recipients and individualized fields have been checked.

Build forms with content controls, properties, instructional text, grouping, and protection that permits intended entry. Record or run a macro only in a trusted file and understand what range/selection assumptions it makes. Use compare/combine, tracked changes, comments, coauthoring, and version control without confusing a hidden view with accepted changes.

Insert a field through Word's field command rather than typing characters that merely look like field braces. Review its code, properties and displayed result. Content controls need appropriate types, titles, default instructions and allowed choices; locking the control against deletion is a different requirement from preventing edits to its contents. Test entry after applying protection.

Field updates need verification. Ctrl+A then F9 is useful, but Microsoft notes that tables containing fields/formulas may need separate selection and F9. Inspect headers, footers, cross-references and generated lists in their own context. A deleted bookmark must be repaired; refreshing cannot reconstruct the missing reference. Word table formulas are fields, so do not assume spreadsheet-style continuous recalculation. Table calculations are useful supporting practice, not a separately named MO-111 objective.

For macro practice, choose an unambiguous name and the intended storage document/template before recording. Record a harmless formatting operation, stop recording, inspect or edit the simple procedure, then copy it with Organizer to a second disposable template. Keyboard selection can be recorded; mouse selection is not captured by the recorder. Confirm the target selection before each run. Word for the web cannot run the desktop VBA workflow.

Internet-origin macros are blocked by default in supported Office on Windows. A macro-enabled extension does not grant permission to execute. Use a locally authored exercise and follow the organization's approved trust policy; a blocked downloaded file is not evidence that the recorded procedure is incorrect. No blanket macro-enablement change is required for learning this distinction.

Prepare merge data before connecting it: clear headers, one record per recipient, consistent types and postal identifiers imported as text. Changing the format after zeros were discarded does not recover the original identifier. Apply filters, inspect missing values and preview individual recipients. Finish into documents first. For labels, verify record progression rather than repeating the first recipient in every position; for envelopes, inspect address placement and paper size.

With the cleaned synthetic recipient source connected, place the insertion point in a letter and choose Mailings → Insert Merge Field for FirstName, RecipientID and the required address columns. Type spaces/punctuation outside the fields. Use Address Block/Greeting Line only after checking their field mapping; typing «FirstName» as ordinary characters does not establish a data binding. If the commands are disabled, inspect Select Recipients and the connection. Preview first/last/blank-name records, then finish into individual documents and reconcile identities. Repeat the address fields in the appropriate label/envelope main-document layout and verify label record progression before printing. See inserting individual and grouped merge fields.

Useful article and its limits

Ali Forelli's paste-default article, originally published May 7, 2024, explains why Merge Formatting helps when pasting from other programs. Its Windows 2405/build 17624.20000 boundary and configurable setting are historical feature context, not a claim that every workstation has the same default. Use the current support reference for detailed list behavior: its default text-only paste can preserve bullets/numbers, qualifying the article's broader simplification. Try all three text-paste choices on the same synthetic source and compare editable output.

Worked examples

1. A template repair seems to disappear. A learner creates a new report from a template and changes its font. The next new report remains unchanged because the master was never edited. Open the correct template, change its definition, save it, then create a fresh document to verify the result. Preserve any report-specific exceptions deliberately.
2. Pasted content carries unexpected formatting. A browser paragraph contains emphasized words and a table. Compare source formatting, merged formatting and text-only paste at the same destination. Inspect styles, retained emphasis, table editability and list settings; an attractive result alone does not prove the requested structure survived.
3. A field pass leaves an incorrect total. A supporting table contains 120, 80 and 50; its sum should be 250. Change 80 to 100; the expected total becomes 270. Refresh the table's field and inspect the result rather than assuming it recalculated immediately. Separately repair a cross-reference whose bookmark was deleted.
4. A merge produces too many letters. A six-record source has one inactive recipient and one active record with an invalid address. Four records remain eligible after those two independent exclusions. Preview all four, including one with a blank optional title, and verify four recipient identities in the output. Count recipients rather than pages because a long letter can span pages. No email is sent in this exercise.
5. A macro exists but cannot be used elsewhere. A procedure stored in one document does not automatically belong to every template. Copy it into the intended practice template, preserve a macro-enabled format, then confirm both its availability and permitted execution. Repeating a run with a different selection tests its assumptions, not merely whether a button exists.

Integrated practice scenarios

1. Policy manual: Create a template, linked outline numbering, section-specific headers, contents, figures, index, cross-references, and protected final output.
2. Contract pack: Use content controls and building blocks, compare revisions, limit editing, inspect metadata, and retain clean/review copies.
3. Personalized letters: Clean a recipient source, apply conditional merge rules, preview exception records, merge to documents, and verify totals/output.

Hands-on labs

These are proposed desktop exercises using synthetic records and disposable copies.

Lab	Task	Completion evidence
1	Edit a template's defaults, theme, named styles and building blocks; customize a toolbar and expose Developer. Investigating the unconfirmed Save as New Style Set action above is optional	A new document gets the intended supported defaults; the original template remains recoverable. For an optional style-set investigation, retain either a reproduced saved-set artifact or the build/command evidence and unresolved gap; successful style-set creation is not required
2	Repair wildcard replacements, style inheritance, outline numbering, hyphenation, pagination and section links	Match counts and representative before/after text agree; styles copied into another template are available there
3	Build an index, figure/table captions, generated figure list, citations and bibliography	Moving content and changing source records produces correct regenerated output
4	Build a form with several standard control types, field properties and suitable protection	Intended entries work, invalid choices are constrained, and required controls cannot accidentally be removed
5	Filter and merge recipients with blank/long values and textual postal codes into letters, labels and envelopes	Eligible identities and output totals reconcile; address layout and record progression are verified
6	Compare two revisions, combine reviewers, manage versions and test a link to external content	The source dependency and review trail are understood; final changes are deliberately accepted/rejected
7	Record, name, edit and copy a simple formatting macro into a disposable template	Correct storage and selection are demonstrated; no global trust-policy relaxation is needed
8	Inspect fields, table calculations, metadata, accessibility, compatibility and PDF output	A changed input yields the expected displayed value after refresh; no unresolved reference errors remain
9	Configure separate editing/display language settings and test language-specific behavior in a mixed 50-minute task	Proofing behavior, interface choice and actual document text are distinguished; delivery checks fit the time budget

Original readiness checks

1. Why link list levels to heading styles? 2. What does Link to Previous affect? 3. Template versus document? 4. Field code versus result? 5. Why update fields before output? 6. What can locked fields cause? 7. Why preview several merge records? 8. Main document versus data source? 9. What does restricting editing not provide? 10. Why retain the template master? 11. What is a building block? 12. Why organize styles? 13. Compare versus combine? 14. What does hiding markup do? 15. Why test macro selection assumptions? 16. What makes a form usable? 17. What creates an index? 18. Why inspect section boundaries? 19. What should document inspection precede? 20. What proves expert readiness?

Answer guide

1. Numbering then follows document structure. 2. Headers and footers across section boundaries. 3. A reusable starting system versus one content instance. 4. Instruction versus displayed value. 5. To remove stale references, contents, dates, and numbering. 6. Stale output. 7. Blanks, lengths, rules, and mapping fail differently. 8. Layout/rules versus recipient records. 9. A full security or access-control boundary. 10. To avoid case-specific contamination. 11. Reusable formatted content stored in a gallery/template. 12. Predictable reuse, navigation, and maintenance. 13. Differences between versions versus consolidated reviewers' revisions. 14. Only the view; revisions remain. 15. A macro may change the wrong content. 16. Clear controls, order, instructions, and appropriate protection. 17. Marked entries plus an inserted/updated index field. 18. They govern layout and header/footer behavior. 19. External delivery. 20. Building and repairing reusable, dynamic documents under time with verified output.

Additional answer checkpoints

1. Does changing a document change its template? Not automatically; edit and save the intended template definition.
2. What does changing Normal.dotm affect? Defaults of future documents based on it, not an automatic repair of every existing document.
3. Does changing the display language translate the document? No; interface language and document text are separate.
4. Why verify the style-copy destination? A same-named style in the wrong document/template does not meet the requirement.
5. Does text-only paste always remove list markers? No; current Word settings can preserve bullets/numbers.
6. Does F9 fix a deleted bookmark? No; restore or retarget the reference before refreshing.
7. What is the expected total after changing 80 to 100 in a 120/80/50 table? 270; confirm the field result after updating.
8. Does a macro-enabled extension make a macro trusted? No; storage format and execution policy are separate.
9. Are mouse selections recorded by Word's macro recorder? No; use the supported keyboard selection workflow and test it.
10. Can a postal-code display format recover lost digits? No; retain the original text during import or recover it from the source.
11. Why reconcile recipient IDs instead of page count? Letters can have different lengths, so pages do not measure the number of intended recipients.
12. Is a standalone Word Expert certification the same as a multi-application MOS Expert credential? No; check the specific credential's requirements rather than inferring the aggregate award from one exam.

Readiness checklist

• I can repair styles, numbering, fields, and sections in an unfamiliar long document.
• I understand where templates, building blocks, and macros are stored.
• I preview and reconcile mail-merge output before release.
• I can preserve review evidence while producing a clean final document.
• I complete mixed advanced tasks inside 50 minutes with a field/output inspection pass.

Places to learn

This is a selective learning path, not a complete list of Word Expert resources or a requirement to consume every item.

Focused source-to-evidence route

A merge pack with edge cases — public task references; about 60–90 minutes. Read prepare the Excel source, preview recipients and the mail-merge platform boundary. Create six synthetic recipients including a leading-zero postal code and a blank optional value. Deliver the source .xlsx, main .docx, a preview checklist and locally merged letters; do not send mail. Estimate basis: three short references plus original files and recipient-by-recipient inspection. Windows and Mac instructions differ; choose the matching desktop steps. Word for the web preserves existing merge settings but cannot perform or edit the merge. No visible article dates were established. Public text was reviewed October 28, 2026; no merge or paid lesson was executed.

Resource	Access	Estimated time
Official MO-111 page	Public	20 minutes for scope and logistics
Microsoft Word help and learning	Public	12–18 hours for advanced targeted practice
Nine labs in this guide	Microsoft 365 Apps required	12–18 hours plus two timed repeats
Detailed skills PDF	Public; task-by-task planning	30–45 minutes
Microsoft task references linked above	Public; focused task practice	3–4 hours, included in targeted practice above
Ali Forelli’s paste article	Public; bounded historical workflow explanation	15 minutes plus a comparison exercise