Skip to content

MO-110 Microsoft Word Associate (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-110
Blueprint checked2026-10-28
Review stateSources + objectives checked — human review pending
Guide-only active reading30 min–45 min

Prerequisites: No formal prerequisite; Microsoft recommends about 150 hours of instruction and hands-on experience creating and managing practical Word 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. Microsoft recommends about 150 hours of instruction and hands-on use; that is preparation guidance, not a prerequisite.
Current scope: documents; text, paragraphs, and sections; tables and lists; references; graphics; collaboration.
Change watch: No MO-110 retirement or replacement is listed on the credential page or the exam retirement list, checked October 28, 2026. The current credential-expiration policy specifies five years for MOS; check your own earned credential's dates.
Review depth: The three-page skills outline contains 70 detailed tasks. The review report records their mapping, sources and limits. No Word desktop lab was executed during this review.

How to use this guide

MO-110 rewards accurate document production under time pressure. Build every practice document from a short requirement, save a clean result, then inspect formatting marks, navigation, accessibility, print layout, and sharing state. Learn more than one route to common commands, but choose the fastest route you can verify. Practice in the desktop Microsoft 365 Apps environment used by your testing center; browser, Mac, and newer release-channel features can differ. The credential page currently lists 16 languages and no dedicated Learn training collection. The time estimates below are this guide’s study suggestions, not provider runtimes or exam prerequisites.

About related items: A Related item: callout adds useful workflow or design context. It is supporting knowledge, not a claim that the wording appears in the published objectives.

Objective map

Published domain Working question
Manage documents (20–25%) Is the file configured, navigable, printable, and protected as requested?
Insert and format text, paragraphs, and sections (20–25%) Are structure and layout controlled with styles and breaks rather than fragile manual formatting?
Manage tables and lists (20–25%) Is structured content readable, sortable, and stable when edited?
Create and manage references (5–10%) Can readers navigate citations, notes, links, and document landmarks?
Insert and format graphic elements (15–20%) Do visuals fit the layout and remain accessible?
Manage document collaboration (5–10%) Are comments, changes, and sharing handled deliberately?

1. Manage documents

Know Save As, export to PDF, print settings, document properties, page setup, views, zoom, Navigation pane, and find/replace. Inspect compatibility and accessibility before delivery. Restrict editing only after confirming what collaborators still need to do, and never treat a password as a substitute for an authorized storage boundary.

Headers, footers, page numbers, margins, orientation, and page size affect the whole document unless sections divide the layout. A page break starts a page; a section break can change headers, numbering, columns, margins, or orientation. Reveal formatting marks when the result seems inexplicable.

Related item: A document can look correct on screen and still fail in PDF or print. Always check page boundaries, repeated headings, image movement, hidden markup, and metadata in the delivered format.

For precise navigation, use Find for matching text, the Navigation pane for styled headings, and Go To for a page, section or object. A bookmark names a destination; an internal hyperlink takes the reader there. Test the destination after moving content. Show hidden text and paragraph marks when diagnosing layout; their visibility is a display choice, not removal.

A style set coordinates the document's styles; individual style changes affect paragraphs using that style. Page color, borders and watermarks are document-background choices: inspect their appearance in the required output. Save a separate copy before converting formats, and use the Compatibility Checker when a recipient needs an older format.

Document Inspector should run on a delivery copy. Select removal categories deliberately: removing headers can also remove required page numbers. It does not find every visually concealed item, including white-on-white text or an object hidden behind another object. Inspect the visible output too; a clean report is not proof of confidentiality.

Worked production — prepare two distinct deliverables

Use a local practice copy of a three-page proposal. In Windows desktop Word, choose Layout > Margins and enter the brief's custom margins; set its required paper size/orientation and inspect every section before continuing. In Insert > Header or Footer, choose an editable header, enter the proposal title and add the required document information; inspect section linkage and close header/footer editing. Add a restrained page border through Design > Page Borders and check the preview. Margins, header/footer fields and border troubleshooting distinguish the settings from their printed result. A printer's minimum margin can clip a border that appears on screen.

Open File > Info and modify the Title property to match the brief; distinguish this editable metadata from the file name and automatically maintained statistics. Save, close and reopen to verify it. The Office properties reference explains those property classes. Use Save As to preserve an editable .docx source and save/export a separate PDF copy. Open the PDF independently and compare headings, page numbers, table breaks and image placement; see Word's basic file tasks.

In File > Print, select the intended printer, page range, copy count and markup setting, then preview the selected pages before printing. If the brief requests pages 1 and 3 without review markup, a three-page all-pages preview with comments is the wrong result. Windows printing guidance documents page selection and markup separately. A PDF export and a print-job selection are distinct outputs.

Run Review > Check Accessibility. Select a reported item, navigate to the affected object and apply a meaningful correction, such as replacing an unhelpful image description with its purpose in this proposal. Recheck the finding and inspect reading order and contrast yourself; the Accessibility Checker procedure is a finding-and-repair workflow, not a certificate of accessibility.

For electronic collaboration, save the authorized test copy to OneDrive, choose Share, name the intended test recipient and select view/edit permissions before creating the link. Verify access as that recipient and check that a viewer cannot edit. Sending an attachment creates another copy; sharing a cloud link points to the shared document. Use the Windows sharing steps, with current organizational policy. VERIFY CURRENT: UI, cloud permissions and testing-center platform; use synthetic content and authorized test accounts. These are proposed exercises: no Word, print, cloud sharing or email operation was performed for this review.

2. Text, paragraphs, and sections

Use styles for repeated structure. Direct formatting changes one selection; modifying a style changes every paragraph using it. Clear accidental formatting before rebuilding a consistent hierarchy. Know character formatting, paragraph alignment and spacing, indentation, tabs, columns, drop caps, themes, and format copying.

Use Keep with next for headings, Keep lines together for indivisible paragraphs, and widow/orphan control for readable pagination. Apply columns or orientation to the intended section, not accidentally to the rest of the document. Replace text, formatting, and special characters carefully; verify scope before Replace All.

When inserting a special character, use the symbol dialog rather than a look-alike font glyph. Text effects such as outline and shadow change appearance; a character style makes repeated emphasis consistent. Format Painter copies formatting, not the underlying words. After clearing formatting, reapply the intended style and check both character and paragraph settings.

Columns flow within a section. A column break moves subsequent text to the next column; a page break moves it to a new page without creating independent section settings. Place section breaks before and after a landscape insert when the following pages must return to portrait. Check each section's header/footer linkage separately before editing its contents.

3. Tables and lists

Create tables from scratch or delimited text; insert/delete rows and columns; merge/split cells; set alignment, margins, height, width, AutoFit, borders, shading, and repeating header rows. Sorting a table depends on the correct header and data type. Converting between text and a table depends on a delimiter that does not also occur inside the data.

For lists, distinguish bullets, numbering, and multilevel lists. Continue or restart numbering intentionally. Link heading levels to a multilevel list when the document needs durable outline numbering; manual numbers become wrong as content moves.

Splitting a table creates a separate table; splitting a cell subdivides a cell inside it. Cell margins control the inset between content and its border, while cell spacing separates cells. After merging cells, recheck row structure before sorting. Custom list symbols and number formats should use a consistent definition; changing a list level is different from adding spaces before its text.

For repeating table headers, select rows beginning with the table's first row. Verify in Print Layout or print output. Repetition works across automatic page breaks; a manually inserted page break inside the table prevents the expected repetition. Edit the original header rather than trying to edit its repeated display.

Worked build — a table with a predictable shape

Insert a blank three-column, four-row table: one header row and three inventory records. Use Insert > Table and choose the row/column counts, using the dialog for dimensions beyond the visible grid. Enter headings for Item, Quantity and Location; enter each record in its own row rather than inserting paragraphs to imitate rows. The table insertion procedure distinguishes a selected grid from an explicit dimension dialog. Verify twelve cells before any merges, then sort the three data rows by Item with the header identified. Check that every quantity remains with its original item. Save a separate copy before experimenting with merges/splits or text conversion. This is a proposed desktop exercise, not an observed file result.

4. References

Create and update tables of contents from heading styles. Insert footnotes/endnotes, hyperlinks, bookmarks, and cross-references, then test navigation. References are fields: after headings, captions, or pagination change, update them and inspect the result.

Footnotes appear near their referenced page; endnotes collect at the end of a section or document. Set location, number format and restart behavior in the note dialog, and check the reference mark and note together after edits.

A contents table can be customized for heading depth, page-number alignment and leader style. If headings were renamed or added, update the entire table; updating page numbers alone leaves old heading text. A manually typed contents list cannot be regenerated from heading structure. Cross-references are useful additional practice alongside the PDF's note and contents tasks.

5. Graphic elements

Insert pictures, shapes, icons, text boxes, SmartArt, screenshots, and symbols; resize proportionally, crop, align, distribute, group, layer, rotate, and apply a restrained style. Understand In Line with Text versus floating wrap modes and anchors. Add meaningful alt text; mark an image decorative only when it conveys no information.

Practice each graphic type rather than substituting a picture for every task. Use a screenshot for a whole window and a screen clipping for a selected area. Enter and revise text inside a shape or text box, and use the SmartArt text pane to edit nodes without treating the diagram as one flat image. Artistic effects alter a picture's rendering; picture styles add coordinated framing/effects. For background removal, inspect the proposed foreground and refine the areas to keep or remove before accepting; cropping merely hides outer portions.

For a 3D model, insert a local model, select a useful view, then adjust size and placement. The 3D control changes the model's viewpoint; rotating its frame is a different operation. Keep the important feature visible and provide an equivalent text explanation. Check the final PDF because an interactive model's behavior should not be assumed to survive export.

6. Collaboration

Add, reply to, resolve, and delete comments. Track changes records insertions, deletions, moves, and formatting; showing No Markup does not accept changes. Review by author or change type, then accept/reject deliberately. Compare identifies differences between versions; combine can consolidate revisions. Before sharing, inspect permissions, comments, tracked changes, document properties, and hidden content.

Track Changes has separate controls for recording, display and acceptance. Turning it off stops tracking future edits; it leaves existing revisions. In Windows, use Review > Tracking > Track Changes > Lock Tracking when the exercise requires a password-controlled review. Unlock before accepting/rejecting revisions. Resolving a comment marks the discussion dealt with; deleting removes it. Neither action substitutes for reviewing the associated text change.

Useful current article

Rubba's August 13, 2026 Microsoft article on location links explains copying a cloud link to selected content. It lists Windows 2605/build 20011.20000 and Mac 16.109/build 26051019 or later. Use it as optional collaboration practice: distinguish a link into a shared file from a bookmark/hyperlink inside the document, and test the recipient's access. The announcement does not establish the build or features present in an exam workstation.

Worked examples

  1. A landscape appendix affects the remaining pages. A six-page portrait proposal needs a wide table in the middle. Create a section for the table and another boundary before the following text; apply landscape only to the middle section. Inspect the three regions and their header/footer linkage. A page break alone does not isolate orientation.
  2. A contents page preserves an old title. Rename “Delivery” to “Implementation” and add a heading beneath it. Updating only page numbers cannot fix the text or add the entry. Update the entire automatic table and verify the new name, level and destination.
  3. A repeated header disappears. A long inventory table repeats correctly until someone forces a page break within it. Remove that manual break and let the table paginate; confirm the selected repeat rows include the first row. Compare Print Layout and exported output.
  4. A clean-looking review still contains revisions. Four edits are present, two approved and two rejected. No Markup hides the evidence. Unlock tracking if needed, accept the two approved edits and reject the other two, then inspect all reviewers and save a separate final copy. Keep the review copy for the revision history.
  5. Sanitizing a file removes required material. The delivery copy contains an author name, internal comments and a page-number footer. Remove only the unwanted categories, retain the required footer, and reinspect. Also look for visually hidden content that the inspector does not detect. Verify the PDF separately.

Integrated practice scenarios

  1. Policy memo: Apply heading styles, numbered procedures, a landscape table section, cross-references, page numbering, alt text, and a clean PDF.
  2. Client proposal: Import supplied text, build branded styles, place images with stable wrapping, create a contents page, and remove hidden review data before delivery.
  3. Team procedure: Track two revision rounds, reconcile comments, compare with a baseline, accept only approved changes, and preserve a review copy.

Hands-on labs

Use synthetic text and local practice copies. These are proposed desktop exercises, not executed results.

Lab Task Completion evidence
1 Rebuild a plain report with styles, text effects, special characters, paragraph settings and a style set Heading navigation works; changing a style updates its paragraphs without changing unrelated text
2 Add a landscape table section, a two-column passage, separate headers and page backgrounds Portrait resumes after the insert; column/page/section breaks are distinguishable with formatting marks
3 Convert tab-delimited text to a table; sort, resize, merge/split cells, split the table and repeat its header Every original record remains; headers repeat under automatic pagination and the chosen delimiter round-trips
4 Build custom numbered/bulleted lists and alter nesting and restart points Inserting a step keeps intended numbering and hierarchy
5 Insert notes, a custom contents table, bookmarks and internal links Notes use the requested location/numbering; renamed headings appear after a full contents update
6 Insert a picture, icon, shape, text box, SmartArt, screenshot and local 3D model Each object remains editable in its native form; text, view, wrapping, effects and alt text match the brief
7 Track two rounds of changes, lock/unlock tracking, reply to/resolve/delete comments Approved and rejected revisions have different final outcomes; no hidden pending revisions remain in the final copy
8 Inspect accessibility, compatibility and hidden properties; save another format and export PDF Required headers remain; internal review content is removed from the delivery copy and the source is preserved
9 Remove a picture background and refine a mistaken foreground selection; compare with cropping The important subject remains intact, and the learner can explain the different operations
10 Complete a mixed brief in 50 minutes, reserving five minutes for inspection Correct filename, destination, print settings and delivered content; record missed requirements for the next attempt

Original readiness checks

  1. Which break permits one page to use landscape orientation? 2. Why prefer styles over repeated direct formatting? 3. What does No Markup do to tracked changes? 4. When is In Line with Text useful? 5. What must be updated after headings move? 6. Why inspect formatting marks? 7. What makes a table sort reliable? 8. What is a bookmark for? 9. When should an image be decorative? 10. What is the risk of Replace All? 11. How do repeated table headings help? 12. Why can numbering break after edits? 13. What does Compare produce? 14. What should be inspected before sharing? 15. How do Keep with next and Keep lines together differ? 16. Why test the PDF? 17. What controls a floating image's position relationship? 18. What happens when a style definition changes? 19. Why preserve a review copy? 20. What proves a lab is complete?

Answer guide

  1. A section break. 2. Styles make structure consistent and centrally maintainable. 3. It hides the display; changes still exist. 4. When the object should behave like a text character. 5. Fields such as the table of contents and cross-references. 6. To expose breaks, tabs, spaces, and paragraph marks causing layout behavior. 7. Correct headers, range, and data types. 8. A named navigation target. 9. Only when it adds no information. 10. An incorrect scope or pattern can change valid content. 11. They preserve context across pages. 12. Manual numbering or disconnected list definitions do not follow structure. 13. A document showing differences. 14. Permissions, markup, comments, metadata, and hidden content. 15. The first binds a paragraph to the next; the second avoids splitting its own lines. 16. Pagination and layout can differ from edit view. 17. Its anchor and wrapping/position settings. 18. All content using it updates. 19. To retain the revision trail. 20. The delivered file meets requirements after inspection, not merely that commands were clicked.

Additional answer checkpoints

  1. What distinguishes a column break from a section break? The first advances within columns; the second creates a boundary for independent layout settings.
  2. Can a manual page break fix missing repeated table headers? It can cause the problem; use automatic table pagination and a repeat selection starting at the first row.
  3. What refresh is needed after renaming a heading? Update the entire automatic contents table.
  4. Does stopping Track Changes accept earlier edits? No; acceptance/rejection is a separate action.
  5. Why unlock tracking before final review? Locked tracking prevents the accept/reject operation.
  6. Is a resolved comment necessarily deleted? No; the discussion's state and removal are different operations.
  7. Does cropping remove an image background around the subject? No; it hides material outside the crop boundary.
  8. What does a model's 3D control change? Its viewpoint, which differs from rotating the flat frame.
  9. Why inspect a copy? Removal may not be reversible and can discard required content.
  10. Does a clean inspector report prove no concealed content remains? No; inspect visual hiding and the exported result too.
  11. Are cloud location links guaranteed in the exam? No; the article describes specified application builds, not the exam environment.
  12. Does no exam retirement notice mean a credential lasts forever? No; current MOS expiration policy and exam availability are separate.

Readiness checklist

  • I can complete all ten labs without step-by-step prompts.
  • I use styles, sections, fields, and list definitions rather than visual workarounds.
  • I can diagnose a layout problem with formatting marks and object anchors.
  • I can deliver both an editable collaboration copy and a clean final copy.
  • I can finish a mixed task set inside 50 minutes with time to inspect the result.

Places to learn

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

Focused source-to-evidence route

A report that survives revision — public task reference; about 45–75 minutes. Use Update a table of contents after building your own three-page report with heading styles and an automatic contents table. Rename a heading and insert a page; compare updating page numbers with updating the entire table. Save the revised .docx and a short before/after checklist, then reopen the file. The estimate covers the short article, original document creation and two revisions; it is not publisher runtime. The article lists Microsoft 365 Word on Windows and Mac; use the matching desktop environment and record its build. Web workflow and exam-environment equivalence were not evaluated. No article publication/update date is displayed. Text was inspected October 28, 2026; Word was not executed.

Resource Access Estimated time
Official MO-110 page Public 20 minutes for scope and exam logistics
Microsoft Word help and learning Public 8–12 hours for targeted reading and reproduction
Ten labs in this guide Microsoft 365 Apps required 10–14 hours plus two timed repeats
Detailed skills PDF Public; use as a task checklist 30–45 minutes, then revisit weak tasks
Microsoft task references linked in Sections 1–6 Public; practice the result in Word 2–3 hours selected reading, included in targeted study above
Location-link article Public; optional current-workflow context 10–15 minutes reading and reproduction