Selected work

02 / TECHNICAL WRITING / PUBLISHED WORK

Microsoft documentation

From product change to a clear next step.

Product documentation is a chain of decisions: what a reader needs to know, where they need it, and how to make the instructions match the product. These public contributions show three different kinds of that work.

MY CONTRIBUTION

Feature guidance, procedural and reference writing, product-feedback revisions, and coordinated updates to related documentation.

THE RESULT

Published Microsoft Learn articles, with public commit history showing my contribution to each sample.

READ THE WORK / VERIFY THE CONTRIBUTION

Three published examples.

01

NEW GUIDE / COLLABORATIVE · June 2026

Multiple managed accounts

A feature guide connecting account separation, supported scenarios, policy behavior, and troubleshooting.

Contributed the new guide with peer review. The accepted commit credits Paolo Matarazzo as coauthor and declares AI assistance.

02

NEW GUIDE + SUBSTANTIVE REVISION · April 2026

Windows app inventory

Prerequisites, configuration steps, property references, and comparisons that help administrators understand an inventory capability.

Authored the new guide and refined its technical details following product-manager feedback.

03

TARGETED UPDATE TO AN EXISTING ARTICLE · April 2026

Power BI connector migration

Migration guidance and connection examples supporting the transition from the earlier Intune Data Warehouse connector.

Added the migration procedure and coordinated supporting notices and links. This is an update to an existing article.

THE PROBLEM

What needed to change.

An administrator needs more than a feature announcement. They need to understand prerequisites, supported behavior, configuration choices, and what to do when something changes. Documentation has to connect those answers across the product.

THE DECISIONS

01

Organize around the reader’s decision.

The multiple managed accounts guide brings account separation, supported scenarios, policy behavior, and troubleshooting into one navigable explanation. I contributed the new guide with peer review and coauthorship.

02

Use product feedback to refine the model.

The Windows app inventory work includes both a new guide and a substantial revision following product-manager feedback. The changes refine terminology, required and optional properties, report mappings, and collection behavior.

03

Turn a retirement notice into a migration path.

For the Power BI connector update, I added targeted migration guidance to an existing article and connected the change to related pages. Readers get an actionable path through the transition.

CURRENT STATE

What works today.

The samples below are accepted contributions in the public MemDocs history. They are part of a broader background in Microsoft Intune, Microsoft 365 Apps, Office deployment, and support documentation.

Microsoft Learn pages continue to evolve. The linked commits show my specific contribution; the current pages include subsequent work by other contributors.