· CMMC  · 6 min read

The Microsoft Product Placemat for CMMC 2.0: How to Read It

Microsoft’s CMMC 2.0 Product Placemat is a Preview planning aid that shows where Microsoft cloud services can support practices, and you need to validate each entry against your scope, tenant, assessment guide, and evidence plan.

Microsoft’s CMMC 2.0 Product Placemat is a Preview planning aid that shows where Microsoft cloud services can support practices, and you need to validate each entry against your scope, tenant, assessment guide, and evidence plan.

Microsoft publishes the Product Placemat for CMMC 2.0 as a Preview workbook that shows how Microsoft cloud services can support CMMC practices. Treat it as a planning aid. Validate every mapping against your scope, tenant configuration, and the official CMMC assessment guidance.

Product Placemat purpose

Microsoft presents the Product Placemat as an interactive view that represents how Microsoft services can support CMMC practices. Microsoft labels the current workbook as version 2.0 Preview and names the file “Microsoft Product Placemat for CMMC - Preview Sept 2024.xlsm.” Microsoft positions the companion Technical Reference Guide for CMMC 2.0 as a helpful resource to use with the placemat for CMMC Level 2 planning.

The placemat helps you form a starting point for solution design. You still need to define what sits inside your CUI scope and what evidence proves implementation. Use the placemat to drive specific design choices, not to claim completed implementation.

Preview status and limits

Microsoft publishes the placemat as informational guidance, not as an authorization, certification, or assessment result. Microsoft does not claim that a line in the placemat proves a contractor implemented a practice. The workbook helps you shortlist services. Your team must configure those services, operate them, and produce evidence that meets the assessment guide.

DoD guidance governs assessment scope and evidence. The DoD CIO CMMC Level 2 Assessment Guide sets expectations for practices, objectives, and assessment methods. The model stacks levels, so Level 2 includes Level 1. Plan solutions and evidence with that stack in mind.

Practice mapping interpretation

Microsoft aligns services to practices in the placemat. Read those alignments as pointers to capabilities, not as finished implementations. Ask two questions for each practice and row in scope.

  • Does the listed service exist in your target cloud and tenant with the needed feature set?
  • Can your team configure, monitor, and document the service in a way that meets the practice objectives?

Use the Technical Reference Guide to understand how Microsoft intends a service to support a practice. Then crosswalk those notes to assessment objectives in the Level 2 Assessment Guide. That confirms that a capability maps to the assessment lens, not only to a control label.

Cloud boundary and shared responsibility

Define your cloud boundary first. The placemat spans commercial, GCC, GCC High, and DoD offerings. Service names travel across clouds, but features, compliance posture, and interconnect patterns differ. Microsoft’s public sector guidance explains differences across commercial, government, and DoD clouds. Match placemat rows to the cloud you will run for CUI. If you still weigh options, review our GCC High migration decision framework.

Decide what you expect Microsoft to operate and what you will operate. Shared responsibility splits tasks between the cloud provider and your organization. Microsoft delivers platform controls and service features. Your team sets policy, enables features, and runs processes. The assessment team evaluates your implementation in your system. The placemat does not shift that line.

Two actions anchor this step.

  • Draw the system boundary diagram that shows tenant, enclaves, and trust paths.
  • Identify inherited controls from Microsoft or other providers and write inheritance statements.

Evidence planning and assessment alignment

Assessment teams look for evidence in your system security plan, procedures, records, and configured systems. Build that evidence as you translate placemat rows into your environment. The placemat points at potential tools for a practice. Your team needs to prove real use tied to objectives in the assessment guide.

Tie each selected placemat entry to an evidence plan.

  • Name the artifact types you will produce, for example, policy records or screenshots.
  • Name the person or role who will operate the control and sustain the records.

Record those details in your SSP and related procedures. If you discover gaps, track them in a POA&M with tasks and milestones. Our posts on NIST 800-171 and CMMC Level 2 mapping and CUI boundary scoping provide practical ways to structure that work.

Product availability and tenant verification

Service names in the placemat do not guarantee availability or parity in your tenant. Verify each service in the target cloud. Microsoft’s public sector material outlines differences across Commercial, GCC, GCC High, and DoD environments. Check plan tiers, licensing, and feature availability in your tenant before you commit a control approach that depends on them.

Configuration and integration paths also differ. A capability in Microsoft 365 might rely on Azure services or connectors that behave differently across clouds. Test enforcement paths with representative users and devices in the target cloud. Confirm that logging, alerting, and retention settings meet your evidence plan.

Program status and contract context

DoD policy updates shape timing and assessment paths. The DoD CIO CMMC model page reports that the department suspended CMMC Phase II on July 13, 2026, and that Phase I self-assessment requirements remain active. During the suspension, DFARS 252.204-7012 still requires safeguarding covered defense information and cyber incident reporting. Contractors should keep NIST SP 800-171 implementations current and maintain SPRS scores during this period.

The placemat does not change contract obligations. Treat it as a planning input that can speed selection of Microsoft services that support your control set. Your contract, your system design, and your assessment evidence drive outcomes.

Practical reading workflow

You can read the placemat with a focused workflow that preserves traceability from a product row to assessment evidence.

  • Fix the CUI scope and system boundary that you will bring to an assessment.
  • Select a target Microsoft cloud, then filter placemat rows to that cloud and to in-scope practices.

Anchor each selected row to assessment objectives.

  • Map the listed capability to the relevant objectives in the Level 2 Assessment Guide.
  • Identify required configurations, procedures, and records that turn capability into evidence.

Close the loop in your documentation.

  • Update your SSP with the system description, control implementations, and inheritance statements.
  • Build test cases and capture initial evidence to confirm the control works as described.

Use the Microsoft Technical Reference Guide to deepen service-specific steps. Keep the Preview label in mind and confirm that workbook content still reflects current service behavior in your tenant.

Common misreads to avoid

Teams run into recurring errors when they overread the placemat. Avoid these patterns.

  • Treating a product name as proof of a practice, without configuration, procedures, and records.
  • Assuming commercial, GCC, and GCC High services carry the same features, controls, and dependencies.

Microsoft publishes the placemat and the technical guide to help with planning. DoD publishes the assessment guide to set the bar for evidence. You must connect these two sets of inputs in your system and in your tenant, then keep evidence current as services and policies change.

Key takeaways for buyers

A buyer who owns a CMMC deadline can use the placemat to clear early design decisions, then move fast to implementation and evidence.

  • Use the placemat to form the short list of Microsoft services for each practice in your scoped system.
  • Confirm each selection in the target cloud, write the implementation in the SSP, and collect initial evidence that matches the Level 2 Assessment Guide.

Sustain the program across policy shifts. The DoD CIO model page posts current program status. Microsoft posts current service information. Keep those in view as you adjust the control set and the evidence plan.

Sources

Microsoft Product Placemat for CMMC 2.0 - Preview (Microsoft) Microsoft Technical Reference Guide for CMMC 2.0 (Microsoft) CMMC Level 2 Assessment Guide (DoD CIO) CMMC Model (DoD CIO) Understanding compliance between Commercial, Government, DoD, and Secret offerings (Microsoft)

Want a structured starting point?

Our 27-question CMMC technical readiness self-survey covers tenant, identity, endpoint, data protection, audit logging, documentation, and the 72-hour DFARS reporting plan. The score is produced in your browser from your answers alone. Nothing is verified or stored.

Back to Blog

Related Posts

View All Posts »
Vulnerability Management Programs That Satisfy SI Controls

Vulnerability Management Programs That Satisfy SI Controls

A CMMC Level 2 vulnerability management program succeeds when you run risk-based scanning on a defined cadence and on new advisories, correct flaws within set timeframes, protect systems from malicious code, and keep evidence tied to the in-scope asset inventory.

Selecting a C3PAO: Practical Criteria for CMMC Level 2 Assessments

Selecting a C3PAO: Practical Criteria for CMMC Level 2 Assessments

Contractors should verify Cyber AB authorization, independence, ISO/IEC 17020 status, and alignment to the CAP and NIST SP 800-171 when choosing a C3PAO for future CMMC Level 2 assessments, while using Microsoft resources as implementation references, not as assessment criteria.

Audit Log Sources Required for a CMMC Level 2 Assessment

Audit Log Sources Required for a CMMC Level 2 Assessment

CMMC Level 2 assessors expect complete audit coverage across your CUI boundary, so identify, collect, protect, retain, and review logs from identity, endpoints, networks, applications, cloud services, and security tools in line with NIST SP 800-171 AU controls.