Transition Licensing to the Microsoft Cloud
The cloud is coming – be prepared with a proactive strategy.
RETIRED CONTENT
Please note that the content on this page is retired. This content is not maintained and may contain information or links that are out of date.The release of Office 365 and other cloud-based software adds a new layer of complexity to the licensing process:
- The shift to cloud-based products has introduced a new style of licensing for Microsoft products. Fully understanding licensing options requires a significant commitment.
- Many IT departments are staying on premise, simply because they lack the resources to monitor cloud capabilities.
- Incorrect licensing can represent a significant financial risk. With the introduction of Office 365, Azure, and Dynamics CRM cloud-based options, licensing Microsoft products has changed again, introducing new compliance risks.
- Added pressures from Microsoft resellers and the press are rushing your cloud transition and you may make mistakes. Take the time to make an educated and calculated change.
Microsoft’s cloud products shift licensing of its core products in a way that is better suited to the demands of the modern workplace:
- Microsoft’s cloud products allow users to work, share, and communicate easily from anywhere, at any time. Products are licensed per user, and in most cases, users can link up to 15 different devices – 5 computers, 5 tablets, and 5 mobile devices.
- Automatic upgrades mean that cloud licensing is more manageable for smaller IT departments.
- Cloud licensing allows for annual true-up or true-down. Licenses can be tracked clearly and have to be added through Microsoft, meaning that licensing compliance is more manageable.
Book Your Workshop
Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.
Module 1: Assemble and Review Documentation
The Purpose
- Assemble licensing documentation.
- Build effective licensing position (ELP).
Key Benefits Achieved
- Licensing documentation identified and organized.
- ELP created.
| Activities: | Outputs: | |
|---|---|---|
| 1.1 | Assemble licensing documentation |
|
| 1.2 | Obtain and review Microsoft ELP |
|
| 1.3 | Identify Microsoft cloud options that align with your ELP and desired future state goals |
|
Module 2: Identify and Review Current State vs. Future State
The Purpose
- Align technology and business goals to workshop.
Key Benefits Achieved
- Business and IT Microsoft licensing goals aligned.
| Activities: | Outputs: | |
|---|---|---|
| 2.1 | Create cloud transition framework overview |
|
| 2.2 | Create transition timeline |
|
| 2.3 | Map future state license options for cloud products |
|
Module 3: Analyze Gaps and Plan Cloud Licenses
The Purpose
- Identify gaps in current licensing and identify ideal future state.
Key Benefits Achieved
- Gaps in current licensing identified.
- Ideal future state identified.
| Activities: | Outputs: | |
|---|---|---|
| 3.1 | Identify gaps between on-premise current state and cloud/hybrid future state |
|
| 3.2 | Identify product license changes, requirements, and license rules |
|
| 3.3 | Model high-level cost impact |
|
Module 4: Develop Cloud Transition Strategy Options
The Purpose
- Create transition strategy.
Key Benefits Achieved
- Licensing transition planned and documented.
| Activities: | Outputs: | |
|---|---|---|
| 4.1 | Document licensing migration paths for cloud/hybrid future state |
|
| 4.2 | Discuss migration options, costs, and overall license strategy |
|
| 4.3 | Develop cloud migration product list and action items |
|
Module 5: Present Cloud Transition Options and Costs
The Purpose
- Presentation of cloud transition options and costs.
Key Benefits Achieved
- Final deliverables.
| Activities: | Outputs: | |
|---|---|---|
| 5.1 | Preparation of final deliverables |
|
| 5.2 | Finalize viable migration options and costs |
|