Download to read offline
Uploaded byBIWUG
Cloud First. Be Prepared
The document discusses moving a company called Acme.com to the cloud by using Office 365. It outlines business drivers for moving to the cloud like changing work styles and costs savings. It then describes Acme.com's current environment and objectives for a new cloud solution. Key hurdles for moving to the cloud are also summarized like managing identity across cloud and on-premises systems, integrating applications, security, and network topologies. The document emphasizes planning thoroughly for technology changes, risks, and user adoption when transitioning to the cloud.
More Related Content
Similar to Cloud First. Be Prepared
![Computer Networks 01[1 using all terms].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/computernetworks011-251214040533-327dd9f8-thumbnail.jpg?width=640&height=640&fit=bounds)
Cloud First. Be Prepared
- 1. Cloud First: BePrepared Alan Eardley | @al_eardley SharePoint Saturday Belgium 2018 #SPSBE
- 2.
- 3. About me • Twitter:@al_eardley • LinkedIn: https://www.linkedin.com/in/alaneardley/ • Helping clients adopt Microsoft 365
- 4. What will Icover? • Why companies are moving to the cloud? • Example scenario • Hurdles to overcome
- 5. Why move tothe cloud?
- 6. Business drivers Changing waysof working Expectations of new staff Expectations of external partners Cost benefits
- 7. Hardware Less hardware Different userdevices Fewer data centres Reduced cost Increased high availability
- 8. Flexibility and scalability Newfeatures Increased security Easier integration Cheaper scale Global distribution of resources
- 9.
- 10. Acme.com Global company Growing rapidly Datacentres need to be increased in capacity Existing solutions at end of life
- 11. Solution objectives New enduser devices Better security Consolidated platform New capabilities Retire existing server hardware Increased speed of delivery of enhancements
- 12. Current state Windows 7VDI On-Premises file shares SharePoint 2010 and SharePoint 2013 Existing data must be migrated Continuous reporting across both platforms during migration period
- 13. Functionality Document management andgovernance Project scheduling and resource management Identity management and compliance Data warehouse for reporting Import legacy data from on-premises application Report on data using existing tools Report on data using PowerBI
- 14.
- 15.
- 16.
- 17.
- 18.
- 19. Identity On-Premises • acmealea01 • alan.eardley@acme.com Cloud •alaneardley@acme.com • alan.eardley@acme.com Other • Other systems • Other solutions • Other products • Other devices External collaboration • Authentication • Permissions • Invite process
- 20. Integration Access to IaaS Access to PaaS Access toSaaS Kerberos Java
- 21. Security Identity management Threat detection Devicemanagement Manage permissions to resources Conditional access Azure is a data centre Expose endpoints direct from Azure
- 22. Network topologies USA UKAsia USA UK Asia USA UK Asia
- 23. Network On-Premises to Azure • VPN •Bandwidth Data Centre vulnerability • Routing to single DC • DC goes down • Speed Global connectivity • Designed for local break- out
- 24.
- 25. Data access Push datainto Azure Read data direct from Azure Process data in Azure?
- 26. Application lifecycle management Environments •Tenant level • Site Collection level • Multiple sets of resources • Integration – Identity • Licencing Rollover • SaaS – no access to DBs • Tooling • GUIDs Deployment • Scripted, repeatable, automated • Environmental differences
- 27. Disaster recovery andarchiving for SaaS SaaS applications rely on vendor tools Legislative archiving requirements Can’t roll back to a point in time Can’t restore to a different tenant
- 28. Adoption Users don’t likechange Pilot roll out Dependencies between users Dependencies between systems
- 29.
- 30. Assess in advance Identity Security Networkaccess Data access Application lifecycle management Disaster recovery and archiving
- 31. Planning Plan for technology Validateconcerns and risks Plan for user adoption
- 32. Contact details –Alan Eardley • Twitter: @al_eardley • LinkedIn: https://www.linkedin.com/in/alaneardley/
- 33.
- 34. SharePoint Saturday Belgium2018 #SPSBE
Editor's Notes
- #5 Most of us know why to a move to cloud is good Many organisations are now satisfied with the security, or motivated by the security The impending end of support for Windows 7 is driving clients to Windows 10 and therefore Microsoft 365
- #8 Patching and upgrading of OS and Software Reduced cost – management, high availability, distadter recovery
- #9 Teams, SharePoint, Stream
- #15 Office 365 and identity management
- #16 Build of data warehouse and surface in PowerBI
- #17 Import data from legacy solution
- #18 Access from on-premises tools
- #20 Without the ability to access the cloud, the project stops Different technical approaches such as cloud identity, federation and passthrough Common issues are more related to changes in user behaviour
- #22 Like any other data centre, access needs to be controlled Delegation of permissions works well in Azure – grant permissions to different resource groups containing logical sets of Azure resources Azure resources have different methods for exposing endpoints Azure SQL has firewalls to allow restriction to allowed IP addresses by default Web based applications can accept traffic from anywhere, or be restricted to a range of IP addresses
- #24 Tunnel to Azure – 100MB BA Azure can scale globally – not if all traffic is routed through a single datacentre
- #31 Change management