It's always DNS: Pain points when combining Azure PaaS and vNets

Virtual networks have become the defacto approach when organisations need to secure their cloud services. But what happens when those services are PaaS? Azure provides several ways in which we can enclose our cloud applications within a virtual network bubble, but all add complexity and often bring pain.

Azure

Architecture

In this session we'll use a real example to talk about how we create an application architecture composed of PaaS services. We will look at the implications of needing separate environments for dev/test/prod, and how hub/spoke and connection to a corporate network affects our configuration.
You'll leave this session with an understanding of how to approach this situation in your own projects, things you should do and avoid doing, and the importance of collaboration between the development and infrastructure teams to ensure success.

Rik Hepworth

Rik helps organisations use Cloud better as CEO and co-founder of Zure UK. Whether that is a new adoption where governance and management are key, or an application modernisation project where technology choice and team knowledge are important factors in success.
Through his public speaking and community involvement, Rik is a recipient of the Microsoft MVP Programme award for his work with Azure. He is also proud to be a member of the Microsoft Regional Director Programme. As an event organiser, speaker and lapsed blogger, Rik is keen to share his knowledge with the community, and encourage and support others as they do the same.
His grey hair is an indication of how long he has worked in IT, and in that time he's done most things you'd expect of an IT Pro: From crawling under floors pulling cables, to managing large scale automated OS rollouts, to architecting solutions for on-premises and cloud. Now he spends more time working with his customers' management, sharing that breadth of experience and learning.