Skip to content

Plan to migrate the Microsoft Solutions Playbook to Microsoft Learn

This page summarizes the plan we are following to migrate the Microsoft Solutions Playbook to Microsoft learn.

!!! note Goal: Minimize contributor impact

It's important to note that we are striving to make the playbook migration to MS Learn as low-impact as possible for playbook contributors, including Tech Domain TPMs and developers, and contributors from other teams.

All technical work to migrate the playbook is being done by the playbook team (such as it is). If you are a playbook contributor, you don't need to do anything beyond quickly learning about some small technical differences when we move contributions from our existing `opsplaybook` repo to the new `solutions-playbook-pr` repo.

The overall migration plan can be summarized in six steps.

  • Phase I - Foundation: Establish relationship and approach with Microsoft Learn team (complete)
  • Phase II - Pilot: Pilot AI playbook to validate that the Learn team is a good partner, that their platform meets our needs, that migration can be done at a reasonable cost and with low impact, and that their is business upside.
  • Phase III - Automate: Build automation in order to eliminate manual migration effort from playbook contributors, to assure consistency of approach across all content, and to discover and mitigate all technical issues. Identify risks, issues, and mitigations. Develop clear plan for expanding overall effort from small core team to all stakeholders.
  • Phase IV - Live on Learn: Make both the internal and public playbooks live on MS Learn while continuing to work within the existing opsplaybook repo.
  • Phase V - Migrate repos: Educate all contributors on differences between old and new repos, understand and address their requirements and concerns, migrate GitHub issues, and thereafter cut over publishing from the old repo to the new.
  • Phase VI - Learn and iterate: Archive the old repo, roll-out MS Learn reporting to business leaders and stakeholders, establish cross-linking relationships with product teams and other documentation owners.

Phase I: Foundation

More content coming soon. This is currently a skeleton of ideas that needs to be fleshed out.

  • Establish relationship and approach with Microsoft Learn team (complete)

Phase II: Pilot

More content coming soon. This is currently a skeleton of ideas that needs to be fleshed out.

  • Pilot AI playbook to validate that the Learn team is a good partner
  • Validate Learn platform meets our needs
  • Assess whether migration can be done at a reasonable cost and with low
  • Assess value prop of migration for both customers and business

Phase III: Automate

More content coming soon. This is currently a skeleton of ideas that needs to be fleshed out.

  • Build automation in order to
    • Eliminate manual migration effort from playbook contributors
    • Assure consistency of approach across all content
    • Discover and mitigate all technical issues
  • Identify risks, issues, and mitigations
  • Develop clear plan for expanding overall effort from small core team to all stakeholders.

Phase IV: Live on Learn

More content coming soon. This is currently a skeleton of ideas that needs to be fleshed out.

  • Make both the internal and public playbooks live on MS Learn while continuing to work within the existing opsplaybook repo.

Phase V: Migrate repos

More content coming soon. This is currently a skeleton of ideas that needs to be fleshed out.

  • Educate all contributors on differences between old and new repos
  • Understand and address their requirements and concerns
  • Migrate GitHub issues
  • Cut over publishing from the old repo to the new

Phase VI: Learn and iterate

More content coming soon. This is currently a skeleton of ideas that needs to be fleshed out.

  • Archive the old repo
  • Roll-out MS Learn reporting to business leaders and stakeholders
  • Establish cross-linking relationships with product teams and other documentation owners