Download to read offline
More Related Content
Similar to Cloud First: Be Prepared
More from Alan Eardley
Cloud First: Be Prepared
- 1. Cloud First: BePrepared MSFT Stack 30 Oct 2018
- 2. About me • Twitter:@al_eardley • LinkedIn: Alan Eardley • Helping clients adopt Microsoft 365 • MCSE: SharePoint 2016 • MCSE: Productivity • MCSE: Cloud • ProSci Practitioner • ScrumMaster • PRINCE2 Practitioner
- 3. What will Icover? • What is the Microsoft cloud? • What are objectives of moving to the cloud? • What is Azure? • Core concepts and considerations • SaaS • IaaS • PaaS • Summary
- 4. What is theMicrosoft cloud?
- 5. A network ofremote servers hosted on the Internet and used to store, manage, and process data in place of local servers or personal computers. - Bing
- 6.
- 7. What are objectivesof moving to the cloud?
- 8. Business drivers Changing waysof working Expectations of customers Expectations of external partners Cost benefits
- 9. Hardware Less hardware Different userdevices Fewer data centres Reduced support cost Increased high availability
- 10. Software New features Increased security Easierintegration Cheaper scale Global distribution of resources
- 11.
- 12. Microsoft Azure isan ever-expanding set of cloud services to help your organization meet your business challenges. It’s the freedom to build, manage, and deploy applications on a massive, global network using your favourite tools and frameworks. - Microsoft
- 13. … as aService Applications Data Runtime Middleware O/S Virtualisation Servers Storage Networking On-Premises Applications Data Runtime Middleware O/S Virtualisation Servers Storage Networking Infrastructure … Applications Data Runtime Middleware O/S Virtualisation Servers Storage Networking Platform … Applications Data Runtime Middleware O/S Virtualisation Servers Storage Networking Software …
- 14. How is itstructured? • Region • Data centre • Services
- 16.
- 17. Network topologies USA UKAsia USA UK Asia USA UK Asia
- 18. 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
- 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. Security Identity management Threat detection Devicemanagement Manage permissions to resources Conditional access Azure is a data centre Expose endpoints direct from Azure
- 21. Integration Access to IaaS Access to PaaS Access toSaaS Kerberos Java
- 22.
- 23. Considerations • Follow bestpractices for customisation • APIs for access to data can be constraining • Identity impersonation • Licences • Throttling
- 24. 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
- 25. 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
- 26.
- 27. Scenarios Dev/Test Labs Backup/Recovery High Power Computing BigData Analysis Web Apps
- 28. Components Virtual Machines • OS • Server software Storage •Disks Network • IP addresses • VNET • Load balancer • Security
- 29. Concepts Update domains Fault domains Availabilitysets Availability zones
- 30.
- 31.
- 32.
- 33.
- 34. Components Storage Blob File Queue Data SQL DB (Postgres,MySQL, MariaDB) SQL DWH Cosmos DB Redis Cache Table Storage Compute App Service Functions Web Apps APIs
- 35. Components Integration Event Grid Logic Apps(Flow) Service Bus Data Factory Notifications Notification Hubs Logic Apps (Flow) Logging App Insights
- 36. Components Networking Content Delivery Network Traffic Manager AzureFirewall Application Gateway Security Azure Active Directory Key Vault Management Azure Monitor Azure Resource Manager Scheduler
- 37.
- 38.
- 39. Azure DevOps Azure Boards Epics Stories Tasks Bugs AzureRepos GIT repositories Azure Pipelines Connect to GIT Build Test Deploy Azure Test Plans Automated Manual Azure Artefacts Maven npm NuGet
- 40.
- 41.
- 42. Considerations System integrations Data consistency Reporting Pilot– Phased migration User adoption
- 43.
- 44. Azure Architecture Centre •Architecture guidance • Example scenarios • Reference architectures • Design patterns – 32 patterns • Build an adoption strategy
- 45. Thank you • Twitter:@al_eardley • LinkedIn: https://www.linkedin.com/in/alaneardley/
Editor's Notes
- #10 Patching and upgrading of OS and Software Reduced cost – management, high availability, distadter recovery
- #11 Teams, SharePoint, Stream
- #15 https://azure.microsoft.com/en-us/global-infrastructure/regions/ https://azure.microsoft.com/en-us/global-infrastructure/services/ .;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;/we223333333333333333 22gghhe3wwwwwwwwwwwwwwwwwwq ````````````` \tps://azure.microsoft.com/en-us/global-infrastructure/services/?products=app-service,functions®ions=all
- #19 Tunnel to Azure – 100MB BA Azure can scale globally – not if all traffic is routed through a single datacentre
- #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
- #21 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
- #30 Unplanned hardware maintenance event Unexpected downtime Planned maintenance
- #41 1 Change application source code. 2 Commit application code and Web Apps web.config file. 3 Continuous integration triggers application build and unit tests. 4 Continuous deployment trigger orchestrates deployment of application artifacts with environment-specific parameters. 5 Deployment to Web Apps. 6 Azure Application Insights collects and analyzes health, performance, and usage data. 7 Review health, performance, and usage information. 8 Update backlog item.
- #45 https://docs.microsoft.com/en-us/azure/architecture/ https://docs.microsoft.com/en-us/azure/architecture/patterns/