1. 05 | Making the Cloud Transition
Christian Buckley | Office 365 MVP, Managing Director at GTconsult
Craig Tarr | MCTS, MCP, Co-Founder and COO at GTconsult

2. Module Overview Adjusting to Office 365 updates
‘Big Picture’ of management considerations
What governance should look like

3. Preparing for the inevitable transition toward the cloud

4. Keeping up to date with the Office 365 Roadmap

5. Adjusting to Office 365 Updates
No access to Correlation errors or backend.
No ability to troubleshoot. If you receive an error, the logs don’t provide much help because it can take Microsoft days or weeks to come back with a correlation ID, if they do at all.
The continual updates to the site can also cause strange errors. For example, for a couple of weeks you couldn’t save a template of a site. This was caused by some code changes the developers had made on the server which obviously needed to be rolled back or fixed, but requires the entire O365 environment to be hot-fixed.

6. Adjusting to Office 365 Updates
You may have to use different management tools.
Moving to Office 365 means giving up some level of control. For example, you won't have any control over the patch management process, software upgrades, and other similar administrative tasks.

7. Management considerations for hybrid

8. Need space and maintenance planning
12/9/2018
On Premises
Cloud
Hybrid
Need space and maintenance planning
Need space and maintenance planning
Location / facilities
Most likely provided
Licensing costs, but also upgrades and ongoing support
Licensing costs, but also upgrades and ongoing support
Software licenses and support
Included in vendor- hosted solutions
Need to purchase, support and maintain, and upgrade as platform matures
Need to purchase, support and maintain, and upgrade as platform matures
Point out that in this example, cloud = Office365
Hardware and maintenance
Included in vendor- hosted solutions
Still requires administrative and possibly dev skills, end user training
Administrative, developer, and end user skills and training
Administrative, developer, and end user skills and training
Onsite support, personnel skills
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9. Limited ability to integrate depending on SaaS, PaaS, or IaaS
On Premises
Cloud
Hybrid
Limited to none in SaaS, some control over PaaS, full control over IaaS
Limited ability to integrate depending on SaaS, PaaS, or IaaS
Level of customization
Full control
Very complex across on prem and cloud components, very manual
Many limitations OTB, but very robust tools from partners
Governance, auditing, security, compliance
Limited
Very complex across on prem and cloud components, very manual
Disaster Recovery and Business Continuity
Needs to be planned, limited features OTB
Defined in SLAs
Some OTB capabilities, 3rd party for tighter control and predictability
Some OTB capabilities, 3rd party for tighter control and predictability
Microsoft recommends 3rd party tools
Upgrades and migration

10. Planning Best Practices
Identify requirements
Map requirements to SharePoint functionality
Make the difficult decisions
Ongoing operations management
Business Need
Service

11. What does “governance” mean?

12. Best Practices Focus on the user experience Make governance a priority
Know your KPIs and legal/regulatory constraints
First define what policies, procedures, and metrics are needed to manage your environment, and then look at what is possible across your various tools and platforms
Clarify and document your permissions, information architecture, templates, content types, taxonomy -- and ownership of each

13. Technical Governance Means…
Logins work
Data is secure
Systems perform well
Metadata applied
End users can quickly find their content
Storage is optimized
Content lifecycles in place, regularly reviewed
Legal and regulatory requirements being met

14. Management Readiness
How important is governance in your organization today?
Do you know who is getting access to what information?
Do you know who has access, or who has accessed your environments and content?
Do you have specific compliance requirements or regulations that you must meet?
If there was a security breach, who would be held responsible?
Do you regularly run audits on usage, security, or permissions?
How do you respond to compliance requirements for audits?
What does your governance process look like today?

15. Summary Moving to the cloud is more than moving content
Think of how your SharePoint Online administration fits into the Office 365 management continuum
Governance is critical to the long-term success of your environment, and spans more than just SharePoint