Redesign for the cloud: Building a cloud-first network at Microsoft
Transitioning to the cloud? Adopting cloud technology requires that you support legacy applications as well as new application models for cloud computing—like platform as a service (PaaS), infrastructure as a service (IaaS), and software as a service (SaaS). Listen in as our experts talk about how we evaluated our network and redesigned our infrastructure to support the cloud-first, mobile-first culture at Microsoft.
These questions — and more — are discussed during this session:
- [30:45] How do you distinguish between managed and unmanaged clients?
- [31:50] For EHC, what are the primary benefits of platform as a service over infrastructure as a service?
- [32:42] For an attribute-based security policy, what kind of attributes are you looking for and what tools are you using to create those attributes?
- [34:36] For EHC, what if your back-end application never migrates to platform as a service? Are there implications in that constraint?
- [35:29] For EHC, are you stuck between choosing PaaS or IaaS? Is it one or the other?
- [36:35] What sorts of services and workloads are going to remain private and on-premises at Microsoft, and does this conflict with our cloud-first, mobile-first goals to move services to the internet?
- [38:12] What are the advantages of EHC over other hybrid connectivity options?
- [40:52] Is your future state a completely parameter-less network? And if so, where does all that security monitoring and policy go?
- [43:32] For EHC, what about outbound needs from a private domain to Azure to the Internet. Do you manage outbound connectivity as well?
- [46:34] Are there manageability and security differences as you move clients and their resources to the Internet?
Access additional technical content, discover new and exciting career opportunities in IT, and much more:
This conversation has been locked by the site admins. No new comments can be made.