Target-state architecture document template
The future environment, design decisions and rationale. Free download in Word and PowerPoint.
Download the target-state architecture template
Describes the future environment, the design decisions taken to get there and the rationale behind each one, so the change board, security and operations can approve the build.
Free to use and adapt. Document ID CM-TPL-DES-01, version 1.0, November 2026.
What the template includes
Document sections
- Purpose and scope · State which environment this design covers, which workloads are in and out of scope, and who must approve it.
- Design principles · List the five to eight principles every decision in this document is tested against. Keep them short and testable.
- Logical architecture overview · Insert the logical diagram, then summarise each major component in one or two sentences.
- Identity and access · Describe the source of authority, sync method, UPN format, authentication methods and admin model.
- Mail flow and messaging · Describe inbound and outbound mail routing, coexistence during migration, and any connectors or relays.
- Files, collaboration and information architecture · Show how existing shares and shared drives map to SharePoint sites, hubs and Teams. Include naming and permission rules.
- Endpoints and devices · State how Windows, macOS and mobile devices will be joined, enrolled, configured and patched.
- Security and compliance · Summarise the controls and refer to the Security baseline checklist for detail. Note any accepted risks.
- Design decisions · Record every material decision. One row per decision; link to the Issue and decision log ID.
- Operations and support model · Describe who runs each component after go-live, monitoring, backup and how changes are made.
- Risks, assumptions and constraints · List design-level risks and assumptions only. Project risks belong in the RAID log.
- Approval · Obtain sign-off from each accountable role before build starts.
Slides
- Target-state architecture
- Scope
- Design principles
- Logical architecture
- Identity and access
- Mail flow and coexistence
- Files and collaboration
- Key design decisions
- Risks and assumptions
- Decision requested
How to use this template
- Complete the current-state architecture first; this document describes only what will be different.
- Replace every example paragraph and table row with your design; delete sections that genuinely do not apply.
- Record each design decision with its options, rationale and approver in the decision table, not buried in prose.
- Attach or link diagrams (logical, identity, network, mail flow) rather than describing topology in words.
- Use the PowerPoint version for the design authority or CAB walk-through, and the Word version as the record.
- Re-baseline the version number whenever a decision changes after approval.
Ready to share with your steering committee
- Branded cover or instructions page with document ID and version
- QR code linking to the latest version, and a Code128 barcode for your document register
- Document control, approval block and a clear disclaimer
- Example rows written for real migration projects, which you replace with your own
Guides that use this template
Questions about this template
Is the target-state architecture template free?
Yes. Download it in Word and PowerPoint and adapt it for your organisation. No sign-up is needed.
Can I use it in Google Sheets or Google Docs?
Yes. Upload the file to Google Drive and open it with Google Sheets or Docs. Dropdowns and most formulas carry across; check conditional formatting after converting.
Can I remove the Cloud-Migrations branding?
Yes. Replace the logo and footer with your own. Keep the disclaimer in mind: the template is general guidance and needs adapting to your project.
How do I know I have the latest version?
Scan the QR code on the cover or instructions sheet. It opens this page, which always links to the current version.