Detailed Course Outline
Programme Topics
We have structured the programme into four topics, i.e. solution areas: Azure and Hybrid Cloud, Microsoft 365, Copilot and AI, Microsoft Security. All four solution areas follow a consistent seller-oriented structure: essential terminology, licensing and commercial mechanics, business value, current-state discovery, optimisation signals, next-step questions and proposal application. The six modules below are covered across five sessions. Microsoft foundations and licensing establish the baseline in Session 1; Microsoft 365 and Copilot readiness begin in Session 2; Azure and hybrid cloud, Microsoft Security and applied Copilot value are brought together onsite in Session 3. Proposal and customer conversation skills run throughout, with a first draft developed in Session 3, refinement in Session 4 and executive pitches in Session 5.
Modules
- Microsoft foundations and licensing: Microsoft ecosystem overview; CSP and indirect reseller context; subscription and consumption concepts; licensing baselines; renewal and upgrade moments; tenant visibility; how to identify gaps without turning the seller into a licensing specialist.
- Azure and hybrid cloud: Core cloud concepts; subscriptions, resource groups and common workloads; Azure consumption and commercial models; cost drivers; Azure cost optimisation / FinOps; reservations and Azure Hybrid Benefit; hybrid scenarios; migration, modernisation and governance conversation starters.
- Microsoft 365: Core workload landscape; user and tenant concepts; Business and Enterprise suite positioning; practical distinction between E1, E3 and E5; adoption and utilisation; tenant consolidation and M&A complexity; productivity, collaboration and compliance value.
- Copilot and AI: Microsoft Copilot landscape; Microsoft 365 Copilot terminology and licensing considerations; Copilot readiness; identity, data, security and adoption prerequisites; role-based value scenarios; responsible introduction of AI; and discovery questions that separate general interest from a qualified opportunity.
- Microsoft Security: Security as a cross-solution conversation; identity, endpoint, email and collaboration, data protection and cloud security concepts; relevant suite and addon licensing considerations; security posture and tenancy risks; suite-level business value; and identification of consolidation, uplift and managed-service opportunities.
- Proposal and customer conversation: Translate findings into a concise current-state summary, opportunity hypotheses, prioritised recommendations, expected business outcomes, dependencies, risks and a practical next-step plan.
Learning Experience
In addition to covering the topics outlined above in greater detail, participants will apply their learning to concrete customer leads and build proposals for real customer opportunities. A common proposal canvas will be used to ensure that each output is commercially consistent while remaining specific to the selected customer.
Proposal element / Required Content
- 1. Customer context Business priorities, relevant change events, current Microsoft footprint and known constraints.
- 2. Current-state view Licensing and tenant landscape, adoption signals, cloud usage, security posture indicators and Copilot readiness observations.
- 3. Opportunity hypotheses Where optimisation, consolidation, adoption, security uplift, cloud modernisation or AI enablement may create value.
- 4. Recommended direction Prioritised recommendations across Azure, Microsoft 365, Copilot and Microsoft Security, including what should be explored now versus later.
- 5. Business value Expected productivity, resilience, risk, cost, governance or growth outcomes, expressed in customer language.
- 6. Discovery and validation Unanswered questions, stakeholders to involve, evidence required and assumptions to validate.
- 7. Next-step plan Recommended assessment, workshop, licensing review, proof of value, technical discovery or service engagement.
- 8. Customer conversation Opening narrative, key questions, likely objections and a concise executive pitch.
The practical exercises and proposal-development activities will, wherever appropriate, use the Partner’s existing customer assets and demand-generation materials. The programme is therefore intended to strengthen the Microsoft knowledge underpinning the existing sales approach, rather than introduce a separate sales methodology.